From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: 64 bit build fails
Date: Fri, 15 Dec 2000 08:45:35 +0100 [thread overview]
Message-ID: <3A39CC1F.8FE7B2FE@mips.com> (raw)
In-Reply-To: 20001214215933.C28871@bacchus.dhis.org
Ralf Baechle wrote:
> On Wed, Dec 13, 2000 at 04:58:52PM +0100, Carsten Langgaard wrote:
>
> > I'm trying to build a 64bit kernel, but it fails with following message:
> >
> > mips64-linux-gcc -D__KERNEL__
> > -I/home/soc/proj/work/carstenl/sw/linux-2.4.0/include -Wall
> > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
> > -mabi=64 -G 0 -mno-abicalls -fno-pic -Wa,--trap -pipe -mcpu=r8000 -mips4
> > -Wa,-32 -c head.S -o head.o
> > head.S: Assembler messages:
> > head.S:69: Error: Missing ')' assumed
>
> Looks like an attempt to build a 64-bit Indy kernel. Various people working
> on the Origin support have completly broken the support for anything else in
> their battle tank-style approach ...
Ok, that explains why a lot of things are broken.
So who will be responsible for fixing all the broken pieces ?
>
> 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:[~2000-12-15 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 15:58 64 bit build fails Carsten Langgaard
2000-12-14 20:59 ` Ralf Baechle
2000-12-15 7:45 ` Carsten Langgaard [this message]
2000-12-15 8:24 ` Kevin D. Kissell
2000-12-15 8:24 ` Kevin D. Kissell
2000-12-15 15:32 ` Ralf Baechle
2000-12-15 22:28 ` PianoMan
2000-12-15 15:20 ` Ralf Baechle
2000-12-18 8:11 ` Carsten Langgaard
2000-12-19 17:47 ` Ralf Baechle
2000-12-17 20:19 ` Thiemo Seufer
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=3A39CC1F.8FE7B2FE@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.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.