Re: Kernel compile error with make-kpkg
----- Original Message -----
From: "Chris Metzler" <cmetzler@speakeasy.net>
To: <debian-user@lists.debian.org>
Cc: "Esben Laursen" <lists@hyber.dk>
Sent: Saturday, July 12, 2003 3:18 PM
Subject: Re: Kernel compile error with make-kpkg
> On Sat, 12 Jul 2003 13:08:39 +0200
> "Esben Laursen" <lists@hyber.dk> wrote:
> > From: "Chris Metzler" <cmetzler@speakeasy.net>
> > >On Fri, 11 Jul 2003 23:50:06 +0200
> > >"Esben Laursen" <lists@hyber.dk> wrote:
> >>>
> >>> Here is the error I get:
> >>>
> >>> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> >>> mkdir -p pcmcia; \
> >>> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf
> >>> ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F
> >>> System.map -b/usr/src/linux/debian/tmp-image -r 2.4.21-test; fi
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ media/radio/miropcm20.o depmod:
> >>> aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6
> >>> depmod: aci_version_Rsmp_93350c87
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ net/wan/comx.o depmod: proc_get_inode
> >>> make[2]: *** [_modinst_post] Error 1
> >>> make[2]: Leaving directory `/usr/src/linux-2.4.21'
> >>> make[1]: *** [real_stamp_image] Error 2
> >>> make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >>>
> >>> Can anyone help me with what's wrong??
> >>
> >> You need to provide more information than you've given. Specifically,
> >> what version of gcc did you use (the output of linux/scripts/ver_linux
> >> would provide lots of info, but the gcc version you're using is
> >> probably enough). Also, and especially, what architecture are you on,
> >> and did you specify that architecture in your kernel config?
> >
> > Here is the output from a gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> > gcc version 2.95.4 20011002 (Debian prerelease)
> >
> > Im trying to compile a kernel with support for the PII CPU, and my
> > kernel now is a standart Debain kernel-image-2.4.18-bf2.4 with the 386
> > architecture. Im also importing the /boot/config-2.4.18-bf2.4 from the
> > "make menuconfig" so that I get all the things I need and only have to
> > change a few things like the architecture. I've attached the
> > /usr/src/linux/scripts/var_linux file so you can see it.
>
> Heh, OK, but as I wrote above, what I was interested in was the *output*
> from var_linux, not the contents of the script itself. But you gave me
> the most important thing that output would have told me, which was your
> gcc version.
>
> The reason I was interested in gcc version is because there have been
> numerous and various problems lately compiling kernels with gcc 3.3.
> In some cases, for reasons I don't understand and other people here
> probably do, this has resulted in unresolved symbols issues, akin to
> what you ran into (mistakes in parsing the text of files, maybe?). But
> no probs have been reported with 2.95 -- in fact, that's what most
> people who've experienced problems with 3.3 have dropped back to -- and
> 2.95 is what you're using. So that probably isn't it.
>
> I was also curious about architecture because I was wondering if you
> were trying to make a kernel for an architecture other than x86. The
> reason: the errors you're getting are for drivers for some old ISA
> bus hardware from the mid-90's; and in Googling, I found instances of
> people getting errors like this when compiling on architectures that
> didn't even support the ISA bus in the first place. But, you're
> compiling for a PII, so that isn't it either.
>
> In the meantime, though, until someone with more clue than I jumps
> in, the below may help.
>
> The first error:
>
> } depmod: *** Unresolved symbols in /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/media/radio/miropcm20.o
> } depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> } depmod: aci_port_Rsmp_0d82adb6
> } depmod: aci_version_Rsmp_93350c87
>
> This is coming from miropcm20.o, which is the driver for the MiroSOUND
> PCM20 radio card. Do you need that driver? If not, you could turn it
> off, and this problem may very well go away. But in the meantime, when
> I read about this driver in linux/Documentation/Configure.help, I see:
>
> } miroSOUND PCM20 radio
> } CONFIG_RADIO_MIROPCM20
> } Choose Y here if you have this FM radio card. You also need to say Y
> } to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound")
> } for this to work.
>
> Note that last sentence. The unresolved symbols you're getting are all
> defined in linux/drivers/sound/aci.c or aci.h (hence the "aci_" prefix).
> If you need support for this card (the MiroSOUND PCM20), then you also
> need to turn on CONFIG_SOUND_ACI_MIXER under the sound section. I'm
> betting you don't have that turned on when you should, and that's the
> reasons for these unresolved symbol messages. If I'm right, then you
> need to either have them both on, or both off, as per that last sentence
> quoted above.
>
> Incidentally, normally, there should be code in the miropcm20-radio.c
> driver that prevents the compile of that driver if you haven't set the
> config options it depends on (in this case, CONFIG_SOUND_ACI_MIXER); it
> doesn't look like that code is there. That's a mistake, IMHO, if true.
>
>
> The second error:
>
> } depmod: *** Unresolved symbols in /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/net/wan/comx.o
> } depmod: proc_get_inode
>
> This is a driver for the MultiGate/COMX set of synchronous serial
> adapters. I googled for this, on "Unresolved symbols comx.o proc_get_inode".
> It turns out that this is a well-known problem with the comx driver. For
> example, from the Linux Kernel Mailing List, Google gave me:
>
> http://www.cs.helsinki.fi/linux/linux-kernel/2001-23/0018.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0206.3/0473.html
> http://lists.insecure.org/lists/linux-kernel/2003/Jun/7021.html
>
> So what's the solution to this problem? If you don't need the COMX
> support, turn it off: set
>
> CONFIG_COMX=n
>
> If you *do* need it, then you're gonna need to head off to the LKML
> and convince the COMX maintainers to fix the driver.
>
> I hope this helps.
>
> -c
>
>
> --
> Chris Metzler cmetzler@speakeasy.snip-me.net
> (remove "snip-me." to email)
The funny part is that if I do a "make dep && make && make modules" there is no error message and it compile correct. why is that?
Could it be possible that I are missing some kind of lib to the kernel-package where make-kpkg is in??
Regards
Esben
Reply to: