Bug 76770 - Can not build modules for parport, lp, and ppa setting parameters for modules as part of xconfig
Summary: Can not build modules for parport, lp, and ppa setting parameters for modules...
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-26 01:29 UTC by Harry Gold
Modified: 2007-04-18 16:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-10-31 17:32:00 UTC

Attachments (Terms of Use)
Output from trying to compile modules (6.64 KB, text/plain)
2002-10-26 01:33 UTC, Harry Gold
no flags Details

Description Harry Gold 2002-10-26 01:29:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)

Description of problem:
I need to build modules for lp, parport and ppa to use my ZIP drive and 
printer. Using kernel 2.4.18-14, I do a bzImage compile. I need try to compile 
the modules using "make modules" The first module that is attempted to 
becompiled is the lp module from /drivers/char. I get numerous warning messages 
but I will attach the modules.out file with all of the error messages

Version-Release number of selected component (if applicable): 2.4.18-14

How reproducible:

Steps to Reproduce:
1.Build bzImage kernel with parport, lp, and scsi/ppa set as modules
2.attempt to make modules after kernel compile is finished

Actual Results:  Received error messages about invalid suffix on integer 
constant and parse error before numeric constant

Additional info:

RH 8.0 was obtained from mirror site and disks were checked before installation

Comment 1 Harry Gold 2002-10-26 01:33:13 UTC
Created attachment 82164 [details]
Output from trying to compile modules

Comment 2 Arjan van de Ven 2002-10-31 17:31:53 UTC
looks like you forgot a "make mrproper" as very first step

Comment 3 Harry Gold 2002-11-01 22:43:35 UTC
Using mrproper fixed the problem however, it was not obvious from the 
documentation that I looked at

Note You need to log in before you can comment on or make changes to this bug.