This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: building gcc tool-chain to be used across machines
- From: Markus Henschel <markus dot henschel at yager dot de>
- To: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Fri, 10 Feb 2012 10:13:20 +0100
- Subject: RE: building gcc tool-chain to be used across machines
- References: <B97B134FACB2024DB45F524AB0A7B7F205CFDAFB@XMB-BGL-419.cisco.com>
> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
> Behalf Of Prashant Batra (prbatra)
> Sent: Freitag, 10. Februar 2012 06:40
> To: gcc-help@gcc.gnu.org
> Subject: RE: building gcc tool-chain to be used across machines
>
> Hi,
>
> If I want to build a gcc tool-chain on one machine and copy it to
> different machines, and use it there, what are the things I need to
> take care of.
> With initial tries, I have seen that after copying a built tool chain
> to a different machine, gcc tries to search for include and libs into
> the paths given during building (as prefix).
>
> That paths may not be always present on other machines where I wish to
> use the tool chain.
>
> Any help would be appreciated.
>
> Thanks,
> Prashant
I had similar problems. To get a relocatable toolchain I configured gcc with --prefix and --with-sysroot pointing to the same path. This made gcc use relative paths.