From: Jun Sun <jsun@mvista.com>
To: Nicu Popovici <octavp@isratech.ro>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross_compiler!
Date: Wed, 08 Nov 2000 11:47:39 -0800 [thread overview]
Message-ID: <3A09ADDB.EA2A6246@mvista.com> (raw)
In-Reply-To: 3A09DE18.E55FA70F@isratech.ro
Nicu Popovici wrote:
>
> Hello you all,
>
> I have a development board ( ATLAS + QED 5261 processor ).
>
> Does anyone from you did cross compiled a kernel for mips on a i686
> machine ? I am struggling for three weeks now to do that and nothing
> works. Mr. Weselows said some days ago to get the Linux_2_2 form CVS
> and indeed I could cross compile that kernel but after that I found out
> that the kernel does not have support for ATLAS board.
>
> I tried the following kernel versions
> 1. linux.2.2.12 from the Atlas board CD
> 2. linux 2.2.13 from lineo.com
> 3. linux 2.2.14 from oss.sgi.com( linux2_2 from CVS site )
> 4. linux 2.2.17
>
> Best Regards,
> Nicu
Nicu,
You can get the cross-compile tool chains from the monta vista ftp
site. These tools are considered stable and recommeded - at least
before Ralf shows his latest toys. :-0
1. binutils 2.8.1
2. egcs 1.0.3a
3. glibc 2.0.6
The ftp site is
ftp.mvsiat.com:/pub/Area51/ddb-5476/
Hopefully before the end of this weekend, there will a little more
updated release with a new name prefix, some bug fixes and for both
little endiand and big endian. The current one is for little endian.
If you know how to use rpm, you can create your own big-endian tools
pretty easily.
Jun
next prev parent reply other threads:[~2000-11-08 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 23:13 Cross_compiler! Nicu Popovici
2000-11-08 19:47 ` Jun Sun [this message]
2000-11-08 20:05 ` Issues with R8000 nick
2000-11-08 20:05 ` nick
2000-11-12 20:10 ` Cross_compiler! Ralf Baechle
2000-11-13 19:14 ` Cross_compiler! Jun Sun
2000-11-14 16:16 ` Cross_compiler! 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=3A09ADDB.EA2A6246@mvista.com \
--to=jsun@mvista.com \
--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