This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Is a target glibc really needed to build full crossgcc?


On Wed, 14 Sep 2005, Henrik Bechmann wrote:

Of course you need the cross compiled library functions to link your
target application, but do you need more than the glibc header files to
compile the full crosscompiler? The only reason I can think of, is that
the library functions, that are built with gcc, are statically linked with
glibc.

Theoretically, possibly, you *could* get away with just the glibc headers. AFAIK there are no target executable binaries generated when providing the c++,objc,... compilers and libraries. However, I know only one way to obtain these glibc headers, and that is to _build_
glibc. :-)


Maybe you could experiment with glibc's configure and Makefile stuff, possibly there even is a "make install-headers", but I doubt it is that easy. Since glibc uses an elaborate directory overlay system to get to the final set of .c and .h files for a specific platform, it is not very easy to extract only the headers as it is with the Linux kernel, for instance.

Regards,
Marius

--
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]