Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: shaver@neon.ingenia.ca (Mike Shaver)
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Kernel compile errors...
Date: Sat, 23 Aug 1997 19:54:34 +0200 (MET DST)	[thread overview]
Message-ID: <199708231754.TAA15897@informatik.uni-koblenz.de> (raw)
In-Reply-To: <199708231606.MAA02843@neon.ingenia.ca> from "Mike Shaver" at Aug 23, 97 12:06:02 pm

> Thus spake Ralf Baechle:
> > Check the version number and file dates.  Compare with current version and
> > date.  Conclusion? ;-)
> 
> My binutils include:
> -rwxr-xr-x   2 root     root       193440 Sep 20  1996 mips-linux-as
> and the tar ball matches the one on linus.  Ditto for GCC.
> 
> And I get the same errors as Alex and the others.  Are there newer
> versions?  If so, where the heck are they?

Well, I've never build binaries of newer versions for Intel.  Since right
now my Indy is 10000km away and my workhorse is a Pentium I'll publish
updates as soon as I'm finished with some more urgent things.

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: Mike Shaver <shaver@neon.ingenia.ca>
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Kernel compile errors...
Date: Sat, 23 Aug 1997 19:54:34 +0200 (MET DST)	[thread overview]
Message-ID: <199708231754.TAA15897@informatik.uni-koblenz.de> (raw)
Message-ID: <19970823175434.ObCACpoNcPXkLI2tKH4OYgicHev4KWfSlFXRV9yrk4A@z> (raw)
In-Reply-To: <199708231606.MAA02843@neon.ingenia.ca> from "Mike Shaver" at Aug 23, 97 12:06:02 pm

> Thus spake Ralf Baechle:
> > Check the version number and file dates.  Compare with current version and
> > date.  Conclusion? ;-)
> 
> My binutils include:
> -rwxr-xr-x   2 root     root       193440 Sep 20  1996 mips-linux-as
> and the tar ball matches the one on linus.  Ditto for GCC.
> 
> And I get the same errors as Alex and the others.  Are there newer
> versions?  If so, where the heck are they?

Well, I've never build binaries of newer versions for Intel.  Since right
now my Indy is 10000km away and my workhorse is a Pentium I'll publish
updates as soon as I'm finished with some more urgent things.

  Ralf

       reply	other threads:[~1997-08-23 17:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199708231606.MAA02843@neon.ingenia.ca>
1997-08-23 17:54 ` Ralf Baechle [this message]
1997-08-23 17:54   ` Kernel compile errors Ralf Baechle
1997-08-22  2:43 Alex deVries
1997-08-22 15:49 ` Miguel de Icaza
1997-08-22 21:15   ` Alex deVries
1997-08-23  1:25     ` Ralf Baechle
1997-08-23  1:25       ` Ralf Baechle
1997-08-23  1:44       ` Alex deVries
1997-08-23  1:57         ` Ralf Baechle
1997-08-23  1:57           ` 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=199708231754.TAA15897@informatik.uni-koblenz.de \
    --to=ralf@mailhost.uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=shaver@neon.ingenia.ca \
    /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