This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: cross gcc & libstdc++
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: duane_ellis at franklin dot com
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Tue, 6 May 2003 12:41:56 -0500
- Subject: Re: cross gcc & libstdc++
- References: <200305060153.h461rq721752@europa.franklin.com>
>I have the compiler and binutils and newlib and gdb working
>just fine with my target hardware - all in C and some
>stuff in C++ (provided I"m not using/require the libstdc++)
This is easy to do.
>I would like to make use of libstdc++ but I am stuck.
>
>libstdc++v3 is included inside of the gcc 3.2 distribution - I believe
>that is the one that I want to make use of. If not please tell me.
This is a fine choice of sources.
>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.
Are you hosting on linux, for an arm-elf toolchain? If not, please
provide more info on what your host is, what your target is, and what
errors you get. Also, please don't email me privately about this.
Here's what you need to do:
http://gcc.gnu.org/simtest-howto.html
The target libraries are configured and built after the compilers are
done. If you are configuring with --enable-languages=c,c++ then
everything (including libstdc++) will be done for you automatically.
-benjamin