Professional Web Applications Themes

Kernel compile error with make-kpkg - Debian

When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get this error no matter what I try!! The command im useing is: make-kpkg --append_to_version -test kernel-image I think it's when the package is being build there is an error, or am I wrong? 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/drivers/media/radio/miropcm20.o depmod: aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6 depmod: ...

  1. #1

    Default Kernel compile error with make-kpkg

    When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get this error no matter what I try!!
    The command im useing is: make-kpkg --append_to_version -test kernel-image

    I think it's when the package is being build there is an error, or am I wrong?

    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/drivers/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/drivers/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??

    Kind Regards

    Esben


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Esben Laursen Guest

  2. #2

    Default Re: Kernel compile error with make-kpkg

    On Fri, 11 Jul 2003 23:50:06 +0200
    "Esben Laursen" <listshyber.dk> wrote:
    >
    > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
    > this error no matter what I try!! The command im useing is: make-kpkg
    > --append_to_version -test kernel-image
    >
    > I think it's when the package is being build there is an error, or am I
    > wrong?
    >
    > 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/drivers/
    > 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/drivers/
    > 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?

    -c

    --
    Chris Metzler [email]cmetzlerspeakeasy.snip-me.net[/email]
    (remove "snip-me." to email)

    "As a child I understood how to give; I have forgotten this grace since I
    have become civilized." - Chief Luther Standing Bear


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Chris Metzler Guest

  3. #3

    Default Re: Kernel compile error with make-kpkg


    ----- Original Message -----
    From: "Chris Metzler" <cmetzlerspeakeasy.net>
    To: "Esben Laursen" <listshyber.dk>
    Cc: <debian-userlists.debian.org>
    Sent: Saturday, July 12, 2003 12:43 AM
    Subject: Re: Kernel compile error with make-kpkg

    > On Fri, 11 Jul 2003 23:50:06 +0200
    > "Esben Laursen" <listshyber.dk> wrote:
    > >
    > > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
    > > this error no matter what I try!! The command im useing is: make-kpkg
    > > --append_to_version -test kernel-image
    > >
    > > I think it's when the package is being build there is an error, or am I
    > > wrong?
    > >
    > > 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/drivers/
    > > 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/drivers/
    > > 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?
    >
    > -c
    >
    > --
    > Chris Metzler [email]cmetzlerspeakeasy.snip-me.net[/email]2.4.18-bf2.4
    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.

    Esben
    Esben Laursen Guest

  4. #4

    Default Re: Kernel compile error with make-kpkg

    ----- Original Message -----
    From: "Esben Laursen" <listshyber.dk>
    To: <debian-userlists.debian.org>
    Sent: Saturday, July 12, 2003 1:08 PM
    Subject: Re: Kernel compile error with make-kpkg



    ----- Original Message -----
    From: "Chris Metzler" <cmetzlerspeakeasy.net>
    To: "Esben Laursen" <listshyber.dk>
    Cc: <debian-userlists.debian.org>
    Sent: Saturday, July 12, 2003 12:43 AM
    Subject: Re: Kernel compile error with make-kpkg

    > On Fri, 11 Jul 2003 23:50:06 +0200
    > "Esben Laursen" <listshyber.dk> wrote:
    > >
    > > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
    > > this error no matter what I try!! The command im useing is: make-kpkg
    > > --append_to_version -test kernel-image
    > >
    > > I think it's when the package is being build there is an error, or am I
    > > wrong?
    > >
    > > 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/drivers/
    > > 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/drivers/
    > > 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?
    >
    > -c
    >
    > --
    > Chris Metzler [email]cmetzlerspeakeasy.snip-me.net[/email]2.4.18-bf2.4
    >
    >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.
    Isn't the correct syntax something like:
    make-kpkg --append-to-version=.something kernel_image (note the = and .)?




    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    JZidar Guest

  5. #5

    Default Re: Kernel compile error with make-kpkg

    On Sat, 12 Jul 2003 13:08:39 +0200
    "Esben Laursen" <listshyber.dk> wrote:
    > From: "Chris Metzler" <cmetzlerspeakeasy.net>
    > >On Fri, 11 Jul 2003 23:50:06 +0200
    > >"Esben Laursen" <listshyber.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/Doentation/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:

    [url]http://www.cs.helsinki.fi/linux/linux-kernel/2001-23/0018.html[/url]
    [url]http://www.ussg.iu.edu/hypermail/linux/kernel/0206.3/0473.html[/url]
    [url]http://lists.insecure.org/lists/linux-kernel/2003/Jun/7021.html[/url]

    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 [email]cmetzlerspeakeasy.snip-me.net[/email]
    (remove "snip-me." to email)

    "As a child I understood how to give; I have forgotten this grace since I
    have become civilized." - Chief Luther Standing Bear


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Chris Metzler Guest

  6. #6

    Default Re: Kernel compile error with make-kpkg


    ----- Original Message -----
    From: "Chris Metzler" <cmetzlerspeakeasy.net>
    To: <debian-userlists.debian.org>
    Cc: "Esben Laursen" <listshyber.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" <listshyber.dk> wrote:
    > > From: "Chris Metzler" <cmetzlerspeakeasy.net>
    > > >On Fri, 11 Jul 2003 23:50:06 +0200
    > > >"Esben Laursen" <listshyber.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/Doentation/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:
    >
    > [url]http://www.cs.helsinki.fi/linux/linux-kernel/2001-23/0018.html[/url]
    > [url]http://www.ussg.iu.edu/hypermail/linux/kernel/0206.3/0473.html[/url]
    > [url]http://lists.insecure.org/lists/linux-kernel/2003/Jun/7021.html[/url]
    >
    > 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 [email]cmetzlerspeakeasy.snip-me.net[/email]
    > (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




    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Esben Laursen Guest

  7. #7

    Default Re: Kernel compile error with make-kpkg

    On Sat, 12 Jul 2003 13:39:35 +0200
    "JZidar" <zeeemail.si> wrote:
    > Isn't the correct syntax something like:
    > make-kpkg --append-to-version=.something kernel_image (note the = and .)?
    The period isn't required; I used it to separate the kernel version from the
    rest of the append-to-version value.

    I thought the = was required but apparently it isn't. Many people report
    using "--append-to-version <whatever>" and it works.

    Kevin


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Kevin McKinley Guest

  8. #8

    Default Re: Kernel compile error with make-kpkg

    On Sat, 12 Jul 2003 17:15:13 +0200
    "Esben Laursen" <listshyber.dk> wrote:

    Please trim replies.
    > 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??
    How do you know it compiles correctly?

    Have you installed and run the kernel that results?

    make-kpkg is a script; it requires no libraries so that's not the issue.

    Kevin


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Kevin McKinley Guest

  9. #9

    Default Re: Kernel compile error with make-kpkg

    On Sat, 12 Jul 2003 17:15:13 +0200
    "Esben Laursen" <listshyber.dk> wrote:
    >
    [ past traffic trimmed ]
    >
    > 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?
    Read your original error messages again. You're not running into
    compile problems; you're running into problems with depmod. It
    *compiled* correctly for you under make-kpkg, just as it does for
    you with "make dep && make && make modules". But make-kpkg does
    more than just those things; it also verifies that your module set
    will work through depmod, and in your case it runs into trouble.
    If after "make dep && make && make modules" you tried to *install
    and run* that kernel/module set, you'd have run into the same
    trouble, I'd bet. Right about when it ran depmod in order to
    build the dependency file for modprobe to use.

    So what about all the rest of the stuff I typed; was it helpful?

    -c


    --
    Chris Metzler [email]cmetzlerspeakeasy.snip-me.net[/email]
    (remove "snip-me." to email)

    "As a child I understood how to give; I have forgotten this grace since I
    have become civilized." - Chief Luther Standing Bear


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    Chris Metzler Guest

Similar Threads

  1. Kernel 2.6 test4 compile error
    By Spaceboy in forum Linux Setup, Configuration & Administration
    Replies: 1
    Last Post: September 2nd, 01:00 PM
  2. make-kpkg question about version
    By Bill Moseley in forum Debian
    Replies: 1
    Last Post: July 29th, 05:50 AM
  3. does make-kpkg work for kernel 2.5/2.6?
    By Nick Hastings in forum Debian
    Replies: 2
    Last Post: July 18th, 04:20 PM
  4. make-kpkg producing error
    By DePriest, Jason R. in forum Debian
    Replies: 2
    Last Post: July 7th, 11:10 PM
  5. make-kpkg fully recompiles kernel
    By Ricardo BUG!Herrmann in forum Debian
    Replies: 3
    Last Post: July 3rd, 01:10 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139