This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: cross gcc & libstdc++
- From: Nathan Myers <ncm-nospam at cantrip dot org>
- To: libstdc++ at gcc dot gnu dot org
- Cc: duane_ellis at franklin dot com
- Date: Mon, 5 May 2003 19:17:34 -0700
- Subject: Re: cross gcc & libstdc++
- References: <200305060153.h461rq721752@europa.franklin.com>
On Mon, May 05, 2003 at 09:53:52PM -0400, Duane Ellis wrote:
> I'm trying to build the libstdc++ for a ARM_ELF cross compiler
> target is a ROM based system.
> ...
> I cannot seem to figure out how libstdc++v3 is ./configured let
> alone built. It seems - the ./configure script is not setup to
> understand a cross compiler situation.
>
> I'm not in a situation where I can build and run GCC on the target
> as it has no file system etc - and no operating system. It's a ROM
> target.
If you have networking hardware on the target, you can NFS-mount your
development platform to the ARM fs. Or, you can get an ARM box that
has a disk or NIC and enough RAM to build. Or, you can find instructions
on setting up a cross-compilation environment; you would not be able
to run configure, so instead you have to set its parameters by hand,
probably by modifying an existing configuration meant for some other
hardware with a similar execution environment. A cross-compilation
environment meant for the Sharp Zaurus might be a good place to start.
Maybe a Zaurus would be a good choice for that "ARM box with a NIC"
mentioned above.
But I haven't done this myself. I hope you get a better answer from
somebody who has. Good luck.
Nathan Myers
ncm-nospam@cantrip.org