------- Additional Comments From drow at false dot org 2005-04-12 00:06 ------- Subject: Re: Top-level gcc configure/makefile does not handle --with-sysroot
On Mon, Apr 11, 2005 at 08:39:53PM -0000, prothonotar at tarnation dot dyndns dot org wrote: > > ------- Additional Comments From prothonotar at tarnation dot dyndns dot org > 2005-04-11 20:39 ------- > One more note about the log: the failures in libstdc++'s configure are because > the options to xgcc (passed from the top-level makefile) are as I stated in my > original comment. I don't have the config.log anymore since I've performed > several clean/rebuild cycles since the time I did this build. > > If you really need them though, I can fire off another build without my patch > when I get a chance. The normal cause of this is that GCC thinks your sysroot has been relocated to be somewhere relative to the build directory, because of how it is being run. It tests whether the relocated path exists. In this case, it does, because your sysroot is the same as $prefix/$target, gcc is in $build/gcc/, and $build/$target/ exists. Maybe we should only do this if the components stripped off are the same as those we expect, i.e. if we are looking for $prefix/bin/../$target only succeed if the binary is in a directory named bin. As a workaround, name your sysroot directory something else... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20955
