RE: help needed for builing gcc tool-chain

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

-----Original Message-----
From: Ian Lance Taylor [mailto:iant@xxxxxxxxxx] 
Sent: Sunday, February 12, 2012 12:50 PM
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:

> [Prashant] Now I did,
> ../binutils-2.21/configure
> --prefix=/auto/nobackup-bgl-mitg-dev56/prbatra/fresh2/build/
> t/
> make
> make install
> ../gcc-4.1.2/configure
> --prefix=/auto/nobackup-bgl-mitg-dev56/prbatra/fresh2/build/
> t --enable-languages=c,c++,objc
> make
> It fails at the same point : /usr/bin/ld: this linker was not
> to use sysroots

This is odd, because the newly built gcc ought to be running the newly
built linker rather than /usr/bin/ld.  I'm not sure why this would not
happen for you.
[Prashant] Actually after looking at the config status, I found gcc was
looking for x86_64-unknown-linux-gnu prefix
[Prashant] before all binutils utilities, but I did not configured
binutils with --program-prefix.
After doing that while configuring binutils, it seems to proceed and use
the custom linker.
And I see that the built is successful.

So, now I can take my built tree completely and relocate to all the
Is there a way to check this by seeing "--print-search-dirs" or some
other option with gcc/g++, 
before actually  relocating the tool-chains.


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

Add to Google