From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>,
SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: kernel build problem.
Date: Wed, 23 Dec 1998 05:44:40 +0100 [thread overview]
Message-ID: <19981223054440.E6183@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.96.981222182405.22999A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Tue, Dec 22, 1998 at 06:26:08PM -0500
On Tue, Dec 22, 1998 at 06:26:08PM -0500, Alex deVries wrote:
> So, I'm building 2.1.121 that's in cvs using egcs-2.90.27 980315 and
> binutils 2.8.1. Both are from Rough Cuts.
>
> Here's the error:
>
> make[2]: Entering directory `/usr/src/linux/arch/mips/mm'
> egcs -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips2 -pipe
> -c -o r6000.o r6000.c
> {standard input}: Assembler messages:
> {standard input}:384: Warning: Unmatched %hi reloc
> {standard input}:487: Internal error!
> Assertion failure in tc_gen_reloc at ./config/tc-mips.c line 10203.
> Please report this bug.
> make[2]: *** [r6000.o] Error 1
> make[2]: Leaving directory `/usr/src/linux/arch/mips/mm'
Add -mno-split-addresses to CFLAGS. Your egcs still enables that optimization
by default.
> Any ideas on what I should do here? Also, Ralf, are you going to upload
> 2.1.131 soon?
Somewhen, when it's working and when I'm done with more urgent non-software
things of live ...
Ralf
next prev parent reply other threads:[~1998-12-24 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-22 23:26 kernel build problem Alex deVries
1998-12-23 4:44 ` ralf [this message]
1998-12-24 15:31 ` Alex deVries
1998-12-25 17:14 ` ralf
1998-12-26 4:08 ` Alex deVries
-- strict thread matches above, loose matches on Subject: below --
1999-06-11 10:44 Kernel Build Problem Andrew Linfoot
[not found] <2A9AA9C52024F94A96634E39B9858FF166B969@empwilex1.empirix.com>
2004-09-01 16:23 ` Kernel build problem Vladimir G. Ivanovic
2004-09-01 18:45 ` Erik Mouw
2004-09-01 18:50 ` Bryan Henderson
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=19981223054440.E6183@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.engr.sgi.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.