From: Ulf Carlsson <ulfc@cthulhu.engr.sgi.com>
To: "Juan J. Sierralta P." <juanjo@atmlab.utfsm.cl>
Cc: Jeff Harrell <jharrell@ti.com>, linux@cthulhu.engr.sgi.com
Subject: Re: SGI, MIPS, Hardhat Linux question...
Date: Tue, 2 Nov 1999 15:53:43 -0800 [thread overview]
Message-ID: <19991102155343.F15879@engr.sgi.com> (raw)
In-Reply-To: <381F7700.AF49CEE8@atmlab.utfsm.cl>; from Juan J. Sierralta P. on Tue, Nov 02, 1999 at 08:42:56PM -0300
> I got the CVS sources for Kernel (2.3.19) and exactly the
> same error messages appears I'm using an HardHat 5.1 with
> 2.1.100 on a SGI Indy 5000 so maybe it isn't a
> cross-compiler error. I also checked the symlinks and seems
> ok....
Are you using gcc or egcs to cross-compiler? If I remember correctly that
message is caused by the gcc specs file that isn't compatible with the current
MIPS kernels. Use this cross-compiler instead:
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mips-linux/
And don't forget to turn off the -N option in arch/mips/Makefiles, or it will
not boot.
Ulf
next prev parent reply other threads:[~1999-11-03 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 21:30 SGI, MIPS, Hardhat Linux question Jeff Harrell
1999-11-02 23:42 ` Juan J. Sierralta P.
1999-11-02 23:53 ` Ulf Carlsson [this message]
1999-11-08 17:59 ` Frank B. Pound
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=19991102155343.F15879@engr.sgi.com \
--to=ulfc@cthulhu.engr.sgi.com \
--cc=jharrell@ti.com \
--cc=juanjo@atmlab.utfsm.cl \
--cc=linux@cthulhu.engr.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