Linux MIPS Architecture development
 help / color / mirror / Atom feed
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: Mon, 18 Dec 2000 09:11:38 +0100	[thread overview]
Message-ID: <3A3DC6BA.DAC68261@mips.com> (raw)
In-Reply-To: 20001215162023.B28594@bacchus.dhis.org

Ralf Baechle wrote:

> On Fri, Dec 15, 2000 at 08:45:35AM +0100, Carsten Langgaard wrote:
>
> > > > 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 ?
>
> This is the question you'd ask a company.  This is Free Software, not some
> company's product ...

What I mean is that we need some discipline, as you mention yourself, it is
unfortunate with this battle tank-style approach.
And I think you do a pretty good job trying to make the rest of the code as clean
as possible.
Of course some time it is a little bit annoying you doesn't just accept my patches
:-)
Just kidding, I think that's the right way to do things.

I was just hoping that the 64bit code was in the same condition as the rest of the
code.

/Carsten


--
_    _ ____  ___   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

  reply	other threads:[~2000-12-18  8:12 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
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 [this message]
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=3A3DC6BA.DAC68261@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox