drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols
in discarded section .text.exit'
drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in
discarded section .text.exit'
drivers/sound/sounddrivers.o(.data+0xb4): undefined reference to `local
symbols in discarded section .text.exit'
drivers/usb/usbdrv.o(.data+0x234): undefined reference to `local symbols
in discarded section .text.exit'
make: *** [vmlinux] Error 1
On Mon, 2001-12-03 at 09:54, real wrote:
> drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols
> in discarded section .text.exit'
> drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in
> discarded section .text.exit'
> drivers/sound/sounddrivers.o(.data+0xb4): undefined reference to `local
> symbols in discarded section .text.exit'
> drivers/usb/usbdrv.o(.data+0x234): undefined reference to `local symbols
> in discarded section .text.exit'
> make: *** [vmlinux] Error 1
Same here. How many other people are finding this to be a problem?
same problem with 2.4.17-pre2
Upon further investigation this is related to the specific version of
binutils used in linking the kernel after compilation. Please see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122179&repeatmerged=yes
for more details. Additionally, not all kernel .configs will trigger
it. The USB segment is definitely in a common point, though. 2.2 kernels
don't seem to exhibit it; but any 2.4 with certain .configs will.
---
Dan Chen [email protected]
GPG key: http://www.cs.unc.edu/~chenda/pubkey.gpg.asc
On 4 Dec 2001, safemode wrote:
> On Mon, 2001-12-03 at 09:54, real wrote:
> > drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols
> > in discarded section .text.exit'
> > drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in
> > discarded section .text.exit'
> > drivers/sound/sounddrivers.o(.data+0xb4): undefined reference to `local
> > symbols in discarded section .text.exit'
> > drivers/usb/usbdrv.o(.data+0x234): undefined reference to `local symbols
> > in discarded section .text.exit'
> > make: *** [vmlinux] Error 1
>
> Same here. How many other people are finding this to be a problem?
> same problem with 2.4.17-pre2
That would explain why I could compile fine when 2.4.16 was released,
but not now....Thanks -- anytime frame you know of for a fix?
-Ben Carrell
[email protected]
Daniel T. Chen wrote:
>Upon further investigation this is related to the specific version of
>binutils used in linking the kernel after compilation. Please see
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122179&repeatmerged=yes
>for more details. Additionally, not all kernel .configs will trigger
>it. The USB segment is definitely in a common point, though. 2.2 kernels
>don't seem to exhibit it; but any 2.4 with certain .configs will.
>
>---
>Dan Chen [email protected]
>GPG key: http://www.cs.unc.edu/~chenda/pubkey.gpg.asc
>
>On 4 Dec 2001, safemode wrote:
>
>>On Mon, 2001-12-03 at 09:54, real wrote:
>>
>>>drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols
>>>in discarded section .text.exit'
>>>drivers/net/net.o(.data+0xbb4): undefined reference to `local symbols in
>>>discarded section .text.exit'
>>>drivers/sound/sounddrivers.o(.data+0xb4): undefined reference to `local
>>>symbols in discarded section .text.exit'
>>>drivers/usb/usbdrv.o(.data+0x234): undefined reference to `local symbols
>>>in discarded section .text.exit'
>>>make: *** [vmlinux] Error 1
>>>
>>Same here. How many other people are finding this to be a problem?
>>same problem with 2.4.17-pre2
>>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
The Debian binutils maintainer is aware and abreadst of the situation; a
fix is imminent.
---
Dan Chen [email protected]
GPG key: http://www.cs.unc.edu/~chenda/pubkey.gpg.asc
On Mon, 3 Dec 2001, Ben Carrell wrote:
> That would explain why I could compile fine when 2.4.16 was released,
> but not now....Thanks -- anytime frame you know of for a fix?
>
> -Ben Carrell
> [email protected]