From: David Daney <ddaney@avtrex.com>
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
Date: Fri, 12 Oct 2007 15:42:01 -0700 [thread overview]
Message-ID: <470FF839.8070507@avtrex.com> (raw)
In-Reply-To: <20071012172254.GA10835@linux-mips.org>
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:
It seems to be a GCC problem, not binutils related.
Have you successfully built with 4.2.0 or 4.2.1?
If it is a regression from a previous gcc-4.2.x version I would be
inclined to fix it. But if all gcc-4.2.x are broken, I might recommend
skipping this version and using 4.3 when it is released.
David Daney
>
> 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 ...
>
> Ralf
>
prev parent reply other threads:[~2007-10-12 22:42 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
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 [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=470FF839.8070507@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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.