From: Marc Karasek <marc_karasek@ivivity.com>
To: Steve Langasek <vorlon@netexpress.net>
Cc: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: MIPS Cross Compiler Tools
Date: 10 Jul 2001 13:11:53 -0400 [thread overview]
Message-ID: <994785113.9191.2.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.30.0107101132510.25158-100000@tennyson.netexpress.net>
I really need the libs to cross-compile some other apps. The target is
an embedded system, so I need to crosscompile things like busybox,
tinylogin, etc. (It will NOT have a harddrive) I have done this before
with ARM and it is pretty easy once you get the tools in place.
Sometimes that is the hardest part...
On 10 Jul 2001 11:35:20 -0500, Steve Langasek wrote:
> Hi Marc,
>
> On Tue, 10 Jul 2001, Marc Karasek wrote:
>
> > I had a question about the cross compiler tools for MIPS, specifically
> > glibc. I d/l the rpms from oss.sgi.com, but they are only binutils, and
> > the compiler (C, C++).
>
> > Are most people building glibc against these or are you building the tools
> > completely from scratch? As glibc is needed to compile anything else other
> > than the kernel.
>
> You don't need a special 'cross-compiler' glibc in order to set up a
> cross-build environment for MIPS; simply grab a glibc package that's
> precompiled for MIPS and install it into your cross-build root directory.
>
> I don't know who (if anyone) would have rpms or a recent mips glibc; I use
> Debian, where I have the packages available as part of the distro.
>
> Regards,
> Steve Langasek
> postmodern programmer
--
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
(770) 986-8925
(770) 986-8926 Fax
*************************/
next prev parent reply other threads:[~2001-07-10 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 16:27 MIPS Cross Compiler Tools Marc Karasek
2001-07-10 16:35 ` Steve Langasek
2001-07-10 17:11 ` Marc Karasek [this message]
2001-07-10 16:39 ` Pete Popov
2001-07-10 17:09 ` Marc Karasek
2001-07-10 17:55 ` Pete Popov
2001-07-10 16:46 ` H . J . Lu
2001-07-10 17:05 ` Marc Karasek
2001-07-10 17:07 ` H . J . Lu
2001-07-11 8:41 ` Gleb O. Raiko
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=994785113.9191.2.camel@localhost.localdomain \
--to=marc_karasek@ivivity.com \
--cc=linux-mips@oss.sgi.com \
--cc=vorlon@netexpress.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.