Were you using your old config file?

I saw the same thing, but I was using my old .config from RC1, to build explicitly
for my hardware configuration. I'm using 9.2RC2 with cooker updates as of Saturday
PM (PST) and the 2.4.22-8mdk kernel. The configuration variable 
CONFIG_USB_STORAGE_ZIOCF
was not defined in my config file (there was a comment line to that effect), but is 
defined in /boot/config-2.4.22-8mdk. I added
   CONFIG_USB_STORAGE_ZIOCF=y
to the section headed
   # USB Device Class drivers
in my .config, did a 'make mrproper' and 'make clean' and rebuilt everything with no
errors.

I didn't try to build with the provided (RC2, config-2.4.22-6) config file nor with
the one for 2.4.22-8mdk, so I don't know if this reproduces in those cases.  
Neither did I explore the config make process to see what was going on
with the ZIO definition.

tony


#########################################################################################
On Saturday 13 sep 2003 [nasa01] wrote:
List:     mandrake-cooker
Subject:  [Cooker] [Bug 5633] [kernel] New: Compiling Kernel moduels stops at 
usb/storage
From:     "[nasa01]" <bugzilla () linux-mandrake ! com>
Date:     2003-09-13 14:43:12
[Download message RAW]

http://qa.mandrakesoft.com/show_bug.cgi?id=5633

           Product: kernel
         Component: smp
           Summary: Compiling Kernel moduels stops at usb/storage
           Product: kernel
           Version: 2.4.22-8mdk
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: P1
         Component: smp
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Hi, 

I have been trying to compile my kernel -- the kernel it self compiles fine, but
I get the following errors when I try to compile the moudles:

unusual_devs.h:251: error: `US_PR_ZIOCF' undeclared here (not in a function)
unusual_devs.h:251: error: initializer element is not constant
unusual_devs.h:251: error: (near initialization for
`us_unusual_dev_list[25].useTransport')

Reply via email to