Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <ddaney@avtrex.com>, linux-mips@linux-mips.org
Subject: Re: Gcc 4.2.2 broken for kernel builds
Date: Fri, 12 Oct 2007 20:45:29 +0200	[thread overview]
Message-ID: <20071012184529.GI3163@deprecation.cyrius.com> (raw)
In-Reply-To: <20071012175317.GB1110@linux-mips.org>

* Ralf Baechle <ralf@linux-mips.org> [2007-10-12 18:53]:
> > >  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'
> 
> If I had the time I'd have done that.  Short of that posting a warning is
> what I can do.

I cannot reproduce this (using gcc 4.2.2 and linux 2.6.22 with a
Cobalt config).  Can you append V=1 to make, run the gcc command by
hand and append --save-temps.  If you send me the .i file I'll make
sure all information is added to the bug report David opened.
-- 
Martin Michlmayr
http://www.cyrius.com/

  parent reply	other threads:[~2007-10-12 18:45 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 [this message]
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=20071012184529.GI3163@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox