gcc --prefix in chrooted environment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Very simple query which I hope someone could address for me:

When I compile, build and install GCC (to use it later on in chrooted environment) and specify the --prefix as, say ${HOME}/gcc-test/install/install-{TARGET}, what effect, if any, that would have if I am later on chrooting to ${HOME}/gcc-test/install in order to compile, build and install the rest of the software in the (then) /install-{TARGET} and use the same GCC (which will reside in /install-{TARGET}/bin instead of ${HOME}/gcc-test/install/install-{TARGET}/bin when I initially built and installed GCC) and would this also affect how GCC will look for its library files?

If so and it *does* affect GCC, how could this be avoided? I was thinking of making a symlink (as root) - "ln -s /install-{TARGET} ${HOME}/gcc-test/install/install-{TARGET}" before chrooting and then compile, build and install GCC by specifying --prefix=/install-{TARGET} which will, hopefully, use the symlink to the real ${HOME}/gcc-test/install/install-{TARGET} directory and when I later on chroot to ${HOME}/gcc-test/install/ GCC won't be affected.

Is there a better solution to this (that is provided GCC *is* affected by the --prefix, which I am not certain of!)? Many thanks in advance!


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux