This is the mail archive of the crossgcc@sources.redhat.com 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: self-contained cross-compiler?


Roman Duka wrote:
Dan Kegel wrote:

Ken Wolcott wrote:
When the cross tool chain we've generated by crosstool (version 24 or 25) is expected to link, it references one or more libraries on the host system rather than the libraries generated by crosstool.

How do you know it's referencing libraries on the host system?

he wants the actual cross compiler and cross binutils to be statically linked.

Oh, duh, I knew that once. Sorry for being dense.


i had problems with statically linked executables, i.e. bash. running statically linked bash inside a chroot jail was fine, untill i attempted to install glibc inside the chroot jail, after the dynamic loader and libraries were installed, for some reason bash would segfault, i examined the core dump and it appeared that bash was trying to use dynamic libraries, even though it was a static executable????? does anybody know what was going on there???

Yup. glibc explicitly loads some shared libraries for things like dns resolution even if you build it statically.

I suspect binutils won't touch any of those bits, though.

By the way, if just linking -static doesn't work out, Ken might
consider building his tools in the LSB build environment,
assuming he can coax his users to load the LSB support package.
- Dan

------
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]