All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Oldham <beth@the-hug.org>
To: buildroot@busybox.net
Subject: [Buildroot] How to build gcc with -m24k option
Date: Wed, 17 Oct 2007 22:11:57 +0100	[thread overview]
Message-ID: <47167A9D.5050008@the-hug.org> (raw)
In-Reply-To: <760119.69994.qm@web7914.mail.in.yahoo.com>

sathesh babu wrote:

> td/.tmp_mtd_blkdevs.o drivers/mtd/mtd_blkdevs.c
> mips-linux-ld: final link failed: Bad value

Thought I recognised this, it's been on the linux-mips.org mailing list. 
Here is a response to that OP:

-------- Original Message --------
Subject: Re: Linux-2.6.18.8 compilation errors with GCC-4.2.1 and 
binutils-2.17 on MIPS
Date: Wed, 17 Oct 2007 09:21:43 -0700
From: David Daney <ddaney@avtrex.com>
To: veerasena reddy <veerasena_b@yahoo.co.in>
CC: linux-kernel.org <linux-kernel@vger.kernel.org>,        linux-mips 
<linux-mips@linux-mips.org>
References: <304090.76321.qm@web8411.mail.in.yahoo.com>

veerasena reddy wrote:
 > Hi,
 >
 > I tried to compile Linux-2.6.18.8 for MIPS24KE
 > processor using cross-compiler built from gcc-4.2.1,
 > binutils-2.17 and uClibc-0.9.27. But, the compilation
 > failed with below error message ("mips-linux-ld: final
 > link failed: Bad value"):
 > ================================

The likely cause is:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33755

As indicated in the PR, Richard has a patch that he is testing.  I would
think that by the time gcc-4.2.3 is released that it would be fixed.

I would recommend using a non-4.2.x version of gcc until the problem is
fixed.

David Daney

>   Can you pls tell what could be the reason.

I guess 4.2.1 is broken :)
Beth

      reply	other threads:[~2007-10-17 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 10:11 [Buildroot] How to build gcc with -m24k option sathesh babu
2007-10-16 16:52 ` Elizabeth Oldham
2007-10-17  6:55   ` sathesh babu
2007-10-17 21:11     ` Elizabeth Oldham [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=47167A9D.5050008@the-hug.org \
    --to=beth@the-hug.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.