From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Link error with linux-2.5 bk
Date: Wed, 21 Jan 2004 18:11:52 +0000 [thread overview]
Message-ID: <20040121191152.16b162b3.ak@suse.de> (raw)
In-Reply-To: <20040120144809.GT27591@localhost>
On Wed, 21 Jan 2004 09:57:43 -0800
"Luck, Tony" <tony.luck@intel.com> wrote:
> > Andrew sent me the attached. He seems to agree with your analysis & fix.
>
> Why didn't this show up on other architecture builds? Doesn't anyone
> else discard .exit.text? Or does everyone else have the default
> for CONFIG_DUMMY set to 'n' or 'm' rather than 'y'?
Most likely the later.
>
> I'd also like to nominate:
>
> local symbol 0: discarded in section `.exit.text' from drivers/built-in.o
> for the "Least helpful error message" award(*). From previous
> experience I know that this is caused by improper use of
> __exit ... but it would really help a lot if the message
> had an actual symbol name, rather than "local symbol 0".
It can be found using create application of objdump -Sr and nm.
I had this problem in the past too with other symbols (that is
why 2.6/i386 discards some sections at runtime, not in the linker)
-Andi
prev parent reply other threads:[~2004-01-21 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 14:48 Link error with linux-2.5 bk Martin Hicks
2004-01-20 21:09 ` Darren Williams
2004-01-21 16:55 ` Luck, Tony
2004-01-21 17:20 ` Andi Kleen
2004-01-21 17:42 ` David Mosberger
2004-01-21 17:57 ` Randy.Dunlap
2004-01-21 17:57 ` Luck, Tony
2004-01-21 18:01 ` David Mosberger
2004-01-21 18:11 ` Andi Kleen [this message]
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=20040121191152.16b162b3.ak@suse.de \
--to=ak@suse.de \
--cc=linux-ia64@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