Re: relocating the compiler and associated tools

[Dan Kegel <dank at kegel dot com>]

Jim Tison wrote:
> But we're talking about building cross-compilers here -- the ultimate
> purpose is to move cross-compiled executables (and/or dynamic libs) to
> foreign machines of the target hw/os type. If you need to build -shared
> executables, you're really in trouble when you transport that executable
> to a foreign machine where your build & PREFIX paths are unknown. You
> _might_ get away with statically linked executables, if you can make the
> link phases work. 

No, no, that's not a problem at all; crosstool removes the absolute paths
from the shared library references.  No need to build static.
- Dan


--
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

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