"Prashant Batra (prbatra)" <prbatra@xxxxxxxxx> writes: > -----Original Message----- > From: Ian Lance Taylor [mailto:iant@xxxxxxxxxx] > Sent: Monday, February 13, 2012 1:29 AM > To: Prashant Batra (prbatra) > Cc: Jonathan Wakely; gcc-help@xxxxxxxxxxx > Subject: Re: help needed for builing gcc tool-chain > > "Prashant Batra (prbatra)" <prbatra@xxxxxxxxx> writes: > >>> Anyhow, you can use the --sysroot option at runtime. >> >> [Prashant] Does that mean I need to create a complete path which gcc >> expects starting from the sysroot with this option. >> [Prashant] <some-path-on-target>/<prefix given while configuring> > > I'm sorry, I don't understand the question. > [Prashant] If I want to use --sysroot option with gcc on a different > machine then the one on which it was built, > [Prashant] and gcc ecpects the paths "<path-x>/bin/gcc", then I need to > create <path-x> on this machine and put the built > tool chain under <path-x>. So, when gcc tries to find the path, it does > find it. > > If, not correct, then can you elaborate on the usage of --sysroot? --sysroot is not for finding the gcc binary itself. --sysroot is for finding the files which traditionally live in /usr/include, /usr/lib, and /lib. You need to pass a --sysroot option which tells gcc where to find those files, if they are not found in the --with-sysroot option passed to configure. You may want to look at --with-build-sysroot and --with-sysroot. Ian
