stray references

Robert Connolly robert at
Sun Aug 26 13:48:44 PDT 2007

I've seen this before but I ignored it at the time.

From what I can see with:
find /usr/ |xargs grep -n -e "/butterfly-build"
the /usr/lib/*.la GCC files reference the build directory with -L's, but not 
with -I's. Maybe some ./configure scripts are using the .la files to find 
extra include directories, but this happens with non-combined builds too, so 
this issue should be happening in LFS too.

quantum ( is running LFS-SVN-20060527, and 
has "dependency_libs=' -L/sources/binutils-build/libiberty/pic -liberty'"
in her .la files. I'm running LFS-SVN-20070514, with modifications which I can 
no longer recall but I did use a combined build (butterfly) tree, and 
my "dependency_libs=" lines are empty. So I have no idea what's going on 

Other than that, I'm not sure what could be the cause of the -I's. If they are 
hard coded in gcc/g++'s program then the grep should have matched it, and it 


On Sunday August 26 2007 03:35:24 pm goodoldmarty at wrote:
> SVN-20070820
> With a booted running system I find many references to the build source
> within the libs and binaries. ( -I /source/butterfly-build/... ).
> ie: libstdc++, cpp, libmudflap, etc
> Has not noticably hindered anything yet, but sure is strange to see when
> compiling new apps. This is wrong I presume???
> Marty B

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <>

More information about the hlfs-dev mailing list