From: Carsten Langgaard <carstenl@mips.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Ralf Baechle <ralf@linux-mips.org>,
"Kevin D. Kissell" <kevink@mips.com>,
linux-mips@linux-mips.org
Subject: Re: Latest sources from CVS.
Date: Fri, 06 Dec 2002 14:41:01 +0100 [thread overview]
Message-ID: <3DF0A8ED.D9B80781@mips.com> (raw)
In-Reply-To: 20021206133448.GC23743@rembrandt.csv.ica.uni-stuttgart.de
Thiemo Seufer wrote:
> Thiemo Seufer wrote:
> > Carsten Langgaard wrote:
> > [snip]
> > > I'm afraid I have to speak up again :-(
> > > Although the new binutils (binutils-mips64el-linux-2.13.1-1.i386.rpm) work on
> > > the latest sources from linux-mips.org, I have a problem with my local sources.
> > >
> > > I get the following error from the assembler:
> > >
> > >
> > > mips64el-linux-gcc -D__KERNEL__
> > > -I/home/soc/proj/work/carstenl/linux-2.4.18/sw/linux-2.4.18/include -Wall
> > > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> > > -fno-strict-aliasing -fno-common -I
> > > /home/soc/proj/work/carstenl/linux-2.4.18/sw/linux-2.4.18/include/asm/gcc
> > > -D__KERNEL__
> > > -I/home/soc/proj/work/carstenl/linux-2.4.18/sw/linux-2.4.18/include -Wall
> > > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> > > -fno-strict-aliasing -fno-common -mabi=64 -G 0 -mno-abicalls -fno-pic
> ^^^^^^^^
> > > -Wa,--trap -pipe -mcpu=r8000 -mips4 -Wa,-32 -DKBUILD_BASENAME=sched
> ^^^^^^^
> Then again, I missed you are building for a 64 bit kernel. The
> commandline given advises the compiler to create N64 code, but
> the assembler is forced to regard it as O32.
>
> I guess the reason for this is the hack to pack 64 bit code in
> O32 binaries.
>
Exactly.
Note, Ralf has already identified the problem, please see his answer.
After hacking the Makefile (gas option), everything work fine.
>
> Thiemo
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-12-06 13:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:34 Latest sources from CVS Carsten Langgaard
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 9:09 ` Kevin D. Kissell
2002-12-04 13:04 ` Ralf Baechle
2002-12-05 3:34 ` Ralf Baechle
2002-12-05 11:14 ` Carsten Langgaard
2002-12-05 13:47 ` Maciej W. Rozycki
2002-12-05 14:12 ` Carsten Langgaard
2002-12-05 14:27 ` Ralf Baechle
2002-12-06 12:52 ` Carsten Langgaard
2002-12-06 13:07 ` Ralf Baechle
2002-12-06 13:24 ` Carsten Langgaard
2002-12-06 13:24 ` Thiemo Seufer
2002-12-06 13:34 ` Thiemo Seufer
2002-12-06 13:41 ` Carsten Langgaard [this message]
2002-12-06 13:51 ` Thiemo Seufer
2002-12-06 16:32 ` Maciej W. Rozycki
2002-12-06 16:45 ` Thiemo Seufer
2002-12-06 17:01 ` Maciej W. Rozycki
2002-12-06 17:24 ` Thiemo Seufer
2002-12-06 18:04 ` Ralf Baechle
2002-12-06 18:30 ` Maciej W. Rozycki
2002-12-06 18:41 ` Thiemo Seufer
2002-12-06 18:58 ` Maciej W. Rozycki
2002-12-06 17:02 ` Ralf Baechle
2002-12-06 17:15 ` Thiemo Seufer
2002-12-06 17:34 ` Greg Lindahl
2002-12-06 18:18 ` Dominic Sweetman
2002-12-06 18:40 ` Greg Lindahl
2002-12-06 23:17 ` Ralf Baechle
2002-12-06 23:33 ` Thiemo Seufer
2002-12-07 0:00 ` Ralf Baechle
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=3DF0A8ED.D9B80781@mips.com \
--to=carstenl@mips.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--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