From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"Kevin D. Kissell" <kevink@mips.com>,
linux-mips@linux-mips.org
Subject: Re: Latest sources from CVS.
Date: Fri, 06 Dec 2002 14:24:24 +0100 [thread overview]
Message-ID: <3DF0A508.4BB7E16D@mips.com> (raw)
In-Reply-To: 20021206140732.A9345@linux-mips.org
Ralf Baechle wrote:
> On Fri, Dec 06, 2002 at 01:52:57PM +0100, Carsten Langgaard wrote:
>
> > 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:
> >
> >
> > {standard input}: Assembler messages:
> > {standard input}:329: Warning: dla used to load 32-bit register
> > {standard input}:382: Error: Number (0xffffffff) larger than 32 bits
> > {standard input}:408: Warning: dla used to load 32-bit register
>
> These are caused by an !%$@#$!$ incompatible change in gas. In essence
> the code model we're using now requires to pass the additional option
> -mgp64. arch/mips64/Makefile probes for gas accepting this new option.
>
Thanks a lot.
>
> So standard advice, update your sources.
In order to have a stable kernel at all time (for core validation), we need to stay
away from the bleeding edge.
So our local sources will always be a little bit behind the main stream.
I have started to send my last patches to you, in order to get ready for a merge
with your latest 2.4.20 sources.
>
> Ralf
--
_ _ ____ ___ 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:28 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 [this message]
2002-12-06 13:24 ` Thiemo Seufer
2002-12-06 13:34 ` Thiemo Seufer
2002-12-06 13:41 ` Carsten Langgaard
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=3DF0A508.4BB7E16D@mips.com \
--to=carstenl@mips.com \
--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