All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: Gcc 4.2.2 broken for kernel builds
Date: Fri, 12 Oct 2007 19:49:09 +0100	[thread overview]
Message-ID: <20071012184909.GA4832@linux-mips.org> (raw)
In-Reply-To: <470FBE08.8090004@avtrex.com>

On Fri, Oct 12, 2007 at 11:33:44AM -0700, David Daney wrote:
> From: David Daney <ddaney@avtrex.com>
> Date: Fri, 12 Oct 2007 11:33:44 -0700
> To: Ralf Baechle <ralf@linux-mips.org>,
> 	MIPS Linux List <linux-mips@linux-mips.org>
> Subject: Re: Gcc 4.2.2 broken for kernel builds
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Ralf Baechle wrote:
> >On Fri, Oct 12, 2007 at 10:48:54AM -0700, David Daney wrote:
> >>From: David Daney <ddaney@avtrex.com>
> >>Date: Fri, 12 Oct 2007 10:48:54 -0700
> >>To: Ralf Baechle <ralf@linux-mips.org>
> >>Cc: linux-mips@linux-mips.org
> >>Subject: Re: Gcc 4.2.2 broken for kernel builds
> >>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >>
> >>Ralf Baechle wrote:
> >>>So it looks as if gcc 4.2.2 is broken for kernel builds resulting in the
> >>>following error message with binutils 2.18:
> >>>
> >>> CC      drivers/mtd/mtd_blkdevs.o
> >>>mipsel-linux-ld: drivers/mtd/.tmp_mtd_blkdevs.o: Can't find matching 
> >>>LO16 reloc against `$LC6' for R_MIPS_HI16 at 0x9e0 in section `.text'
> >>> CC      drivers/mtd/chips/chipreg.o
> >>>
> >>>Older binutils throw a more cryptic error message about the bad assembler
> >>>code generated by gcc:
> >>>
> >>> CC      drivers/mtd/mtd_blkdevs.o
> >>>mipsel-linux-ld: final link failed: Bad value
> >>>make[2]: *** [drivers/mtd/mtd_blkdevs.o] Error 1
> >>>make[1]: *** [drivers/mtd] Error 2
> >>>make: *** [drivers] Error 2
> >>>
> >>>Just as heads up ...
> >>>
> >>Could you file a bug report here:
> >>
> >>http://gcc.gnu.org/bugzilla/
> >>
> >>If you could include a pointer to the kernel sources you were using and 
> >>perhaps attach your .config to the bug that might be useful as well.
> >
> >If I had the time I'd have done that.  Short of that posting a warning is
> >what I can do.
> 
> I opened this bug:
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33755
> 
> As more information becomes available about this feel free to add it to 
> the GCC bug report.

For the moment the receipe to reproduce is to checkout
7b94a571d6f31ac6303d62c2aafcae40b66f24a3 from the linux-mips.org kernel
tree (that's on linux-2.6.18-stable) and build malta_defconfig with
gcc 4.2.2 and binutils 2.17 or 2.18, both configured for mipsel-linux.

  Ralf

  reply	other threads:[~2007-10-12 18:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 17:22 Gcc 4.2.2 broken for kernel builds Ralf Baechle
2007-10-12 17:48 ` David Daney
2007-10-12 17:53   ` Ralf Baechle
2007-10-12 18:33     ` David Daney
2007-10-12 18:49       ` Ralf Baechle [this message]
2007-10-12 19:14         ` Martin Michlmayr
2007-10-12 19:16           ` Ralf Baechle
2007-10-13 10:51             ` Richard Sandiford
2007-10-15 14:59               ` Maciej W. Rozycki
2007-10-15 16:19                 ` Richard Sandiford
2007-10-24 19:46             ` Martin Michlmayr
2007-10-12 20:33           ` Martin Michlmayr
2007-10-12 18:45     ` Martin Michlmayr
2007-10-12 22:42 ` David Daney

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=20071012184909.GA4832@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.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 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.