From: safemode <safemode@speakeasy.net>
To: real <haxmail@subdimension.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compilation error with Kernels 2.4.16 && 2.5.X
Date: 04 Dec 2001 00:10:42 -0500 [thread overview]
Message-ID: <1007442642.5959.1.camel@psuedomode> (raw)
In-Reply-To: <3C0B921F.80206@subdimension.com>
In-Reply-To: <3C0B921F.80206@subdimension.com>
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
next prev parent reply other threads:[~2001-12-04 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 14:54 Compilation error with Kernels 2.4.16 && 2.5.X real
2001-12-04 5:10 ` safemode [this message]
2001-12-04 6:16 ` Daniel T. Chen
2001-12-04 6:41 ` Ben Carrell
2001-12-04 6:44 ` Daniel T. Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1007442642.5959.1.camel@psuedomode \
--to=safemode@speakeasy.net \
--cc=haxmail@subdimension.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox