This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: gcc --prefix in chrooted environment
- From: Ian Lance Taylor <iant at google dot com>
- To: Michael Zintakis <michael dot zintakis at googlemail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Sat, 26 Mar 2011 11:10:52 -0700
- Subject: Re: gcc --prefix in chrooted environment
- References: <4D8DC506.9030308@googlemail.com>
Michael Zintakis <michael.zintakis@googlemail.com> writes:
> 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 I understand this, it should not have any effect. If you pick up the
entire gcc install tree and move it somewhere else, gcc should continue
to work fine (you can't move just part of it around, but you can move
the whole thing as a unit). That is effectively what you are doing
here.
Ian