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?


Dan Kegel wrote:
Ken Wolcott wrote:

I feel that I'll be told that I'm re-asking an already answered question, but I still have a linking problem with the cross compiler generated by crosstool.

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.


Hi Ken!

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

Remember, if you're looking at shared libraries, the path
embedded in the executable is only interpreted at runtime!
- 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





he wants the actual cross compiler and cross binutils to be statically linked.
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???



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