Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Cc: Nicu Popovici <octavp@isratech.ro>
Subject: Re: [Fwd: CrossGcc steps!]
Date: Fri, 20 Oct 2000 15:18:30 +0200	[thread overview]
Message-ID: <20001020151830.E23056@lug-owl.de> (raw)
In-Reply-To: <39F040D4.4BFB2E26@isratech.ro>; from octavp@isratech.ro on Fri, Oct 20, 2000 at 03:55:48PM +0300

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Fri, Oct 20, 2000 at 03:55:48PM +0300, Nicu Popovici wrote:
> > Yupp. Your .config is wrong. What kind of machine do you exactly ghave?
> 
> I have a Intel pentium III at 500 Mhz which is running RedHat 6.2.

No, I thought of your mips machine...

[ ] I've not got any MIPS based machine
[ ] I've got a MIPS based machine. It is called

	______________________________________

[ ] I've build a cross compiler with --target=mips-linux
[ ] I've build a cross compiler with --target=mipsel-linux

> > You need to have an *exactly* fitting config. You're responsible
> > to make it by config/oldconfig/menuconfig/xconfig, as what you prefer.
> 
> Can you help me with the options ?

Therefor I'd need to know what machine you are compiling for...

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2000-10-20 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-20 12:55 [Fwd: CrossGcc steps!] Nicu Popovici
2000-10-20 13:18 ` Jan-Benedict Glaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-20  7:03 Nicu Popovici

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=20001020151830.E23056@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-mips@oss.sgi.com \
    --cc=octavp@isratech.ro \
    /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