From: Jeff Baitis <baitisj@evolution.com>
To: Jun Sun <jsun@mvista.com>
Cc: Tiemo Krueger - mycable GmbH <tk@mycable.de>,
saravana_kumar@naturesoft.net, linux-mips@linux-mips.org
Subject: Re: Cross Compilation
Date: Wed, 23 Jul 2003 11:27:27 -0700 [thread overview]
Message-ID: <20030723112727.R10468@luca.pas.lab> (raw)
In-Reply-To: <20030723100946.N3135@mvista.com>; from jsun@mvista.com on Wed, Jul 23, 2003 at 10:09:46AM -0700
I find that the uClibC tools are excellent, and have no problems generating
MIPS binaries from an i386 host ;)
-Jeff
On Wed, Jul 23, 2003 at 10:09:46AM -0700, Jun Sun wrote:
> On Wed, Jul 23, 2003 at 09:45:43AM +0200, Tiemo Krueger - mycable GmbH wrote:
> > You could even use the buildroot thing from uclibc.org:
> >
> > http://uclibc.org/cgi-bin/cvsweb/buildroot/buildroot.tar.gz?tarball=1
> >
> > It's one of the most simple way for cross toolchain beginners, it
> > provides you finally with a toolchain and rootfile system and more
> >
>
> I took a look. It looks similar to one project that I worked on
> before. Very interesting.
>
> Has anybody tried successfully to do a cross MIPS yet? From a Linux/i386 host
> obviously ...
>
> Jun
>
--
Jeffrey Baitis - Associate Software Engineer
Evolution Robotics, Inc.
130 West Union Street
Pasadena CA 91103
tel: 626.535.2776 | fax: 626.535.2777 | baitisj@evolution.com
next prev parent reply other threads:[~2003-07-23 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 6:20 Cross Compilation SaravanaKumar
2003-07-23 6:40 ` debashis
2003-07-23 7:45 ` Tiemo Krueger - mycable GmbH
2003-07-23 17:09 ` Jun Sun
2003-07-23 17:40 ` Bruno Randolf
2003-07-23 18:27 ` Jeff Baitis [this message]
2003-07-24 0:55 ` Lyle Bainbridge
2003-07-24 0:55 ` Lyle Bainbridge
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 6:22 JinuM
2003-07-23 10:01 eric_sy_huang
2003-07-23 10:07 Jim Thompson
2003-07-23 10:07 ` Jim Thompson
2003-07-23 21:16 Jim Thompson
2003-07-23 21:16 ` Jim Thompson
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=20030723112727.R10468@luca.pas.lab \
--to=baitisj@evolution.com \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=saravana_kumar@naturesoft.net \
--cc=tk@mycable.de \
/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