------- Comment #3 from miro dot kropacek at gmail dot com 2010-02-16 13:47 ------- >It must be hardlinked, not copied, on the systems which support hard links. I don't know, Linux copies it, too.
>it is an *internal* directory of the toolchain for *internal* use by one >toolchain binary calling another, just like libexec/gcc/$target/$version is an >*internal* directory. This is not 100% true. GCC is looking for #include <header> paths in $prefix/$target/include, libs in $prefix/$target/lib so saying $prefix/$target/bin is internal directory only for gcc/binutils purposes does not seem to be correct to me. Don't forget many libraries which provide some executables (libxml2 comes into my mind) install headers and libs into mentioned places _and_ executables into mentioned bin directory. So what we have ended with? Mixed host and native/cross binaries in one directory. But I don't say this is only gcc bug, there's no convention what should be there (cross tools, host tools, nothing?). I just wanted to make this mess a little bit less painful. >IMHO, the driver first should use "as" from $prefix/$target/bin; if not found, >look for $target-as in the $PATH; and only after that, try to invoke plain >"as". Exactly my thoughts. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43090
