From: "H. J. Lu" <hjl@lucon.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: bug-binutils@gnu.org, linux-mips@linux-mips.org
Subject: Re: 'final link failed: Bad value' when building Linux/MIPS kernels.
Date: Fri, 16 Mar 2007 07:45:24 -0700 [thread overview]
Message-ID: <20070316144524.GA32203@lucon.org> (raw)
In-Reply-To: <17914.38675.653000.256@gargle.gargle.HOWL>
On Fri, Mar 16, 2007 at 09:09:39AM -0400, Paul Koning wrote:
> >>>>> "Steven" == Steven J Hill <sjhill@realitydiluted.com> writes:
>
> Steven> Greetings. I have been chasing down a binutils regression
> Steven> that is preventing me from building a Linux/MIPS kernel using
> Steven> a gcc-4.2 based toolchain. Here is the snippet of output when
> Steven> building a 2.6.12 kernel for my platform:
>
> Steven> LD drivers/mtd/maps/built-in.o
> Steven> LD drivers/mtd/nand/built-in.o
> Steven> LD drivers/mtd/built-in.o
> Steven> mipsel-linux-uclibc-ld: final link failed: Bad value
> Steven> make[1]: *** [drivers/mtd/built-in.o] Error 1
> Steven> make: *** [_module_drivers/mtd] Error 2
>
> I've run into the same message when building things for a NetBSD/MIPS
> target. I had assumed it was some error on my end.
>
> The problem with this message is that it is completely content-free.
> It doesn't contain a meaningful problem statement, and it doesn't say
> anything at all about where the problem is. It doesn't even indicate
> what input file triggered the problem! How is a user supposed to fix
> a failed build when this error message appears?
Please file a bug report with all input files for the linker. I
will at least provide clear diagnostic messages.
H.J.
prev parent reply other threads:[~2007-03-16 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 2:35 'final link failed: Bad value' when building Linux/MIPS kernels Steven J. Hill
2007-03-16 4:17 ` H. J. Lu
2007-03-16 13:09 ` Paul Koning
2007-03-16 14:45 ` H. J. Lu [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=20070316144524.GA32203@lucon.org \
--to=hjl@lucon.org \
--cc=bug-binutils@gnu.org \
--cc=linux-mips@linux-mips.org \
--cc=pkoning@equallogic.com \
/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