From: Ralf Baechle <ralf@linux-mips.org>
To: Kurt Schwemmer <kurts@vitesse.com>
Cc: linux-mips@linux-mips.org, sde@mips.com
Subject: Re: Build errors
Date: Sun, 22 Jan 2006 03:03:41 +0000 [thread overview]
Message-ID: <20060122030341.GB11131@linux-mips.org> (raw)
In-Reply-To: <1137793865.15788.26.camel@lx-kurts>
On Fri, Jan 20, 2006 at 02:51:05PM -0700, Kurt Schwemmer wrote:
> I sync'd with git clone rsync://ftp.linux-mips.org/git/linux.git
> linux.git 2 days ago. I downloaded and installed sde:
> ftp://ftp.mips.com/pub/tools/software/sde-for-linux/6.02.03-1/mipsel-sdelinux-v6.02.03-1.i386.rpm
> ...but the one that kills me is:
> mm/msync.o: In function `msync_interval':
> msync.c:(.text+0x10c): unmatched HI16 relocation
> mipsel-linux-ld: final link failed: Bad value
> make[1]: *** [mm/built-in.o] Error 1
> make: *** [mm] Error 2
This kind of problem is usually being caused by either broken inline
assembler code or a bug in the compiler. Since we haven't done any
serious changes to the inline code recently I would put my bets on a gcc
bug, so I'm putting the SDE people at MIPS on Cc. It could be useful if
you could post your .config kernel configuration file. Also, which
kernel version exactly are you building? The command "git-describe HEAD"
will tell you something like "linux-2.6.15-g68cabd8e", can you post that
number?
> Would someone tell me what I'm doing wrong? I'm pretty sure people
> wouldn't be checking in code that doesn't even build!
We try hard - but the number of tools and configuration variants makes it
hard to ensure that kind of thing never happens.
Ralf
next prev parent reply other threads:[~2006-01-23 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 21:51 Build errors Kurt Schwemmer
2006-01-22 3:03 ` Ralf Baechle [this message]
2006-01-23 15:10 ` Nigel Stephens
2006-01-23 15:57 ` Kurt Schwemmer
2006-01-23 16:04 ` Nigel Stephens
2006-01-23 16:10 ` Maciej W. Rozycki
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=20060122030341.GB11131@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kurts@vitesse.com \
--cc=linux-mips@linux-mips.org \
--cc=sde@mips.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 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.