On Tue, 2006-01-03 at 20:47 +0100, Eric Botcazou wrote: > > Actually, looking more closely, the libiberty.a is the only one installed > > that way (from the gcc sources). All others (for example libstdc++.a) seem > > to follow standard convention (32 bit in lib, 64 bit in lib/sparcv9). > > Hmmm... bug in gcc-4.0.2/libiberty/Makefile.in? > > Bingo. :-) http://gcc.gnu.org/PR16513
I wonder how many more examples like that we need before we impose testing after install and not in tree... Only consequence for the few who configure with --prefix=/usr from their tree will be to change to --prefix=/some/user/dir so install doesn't break the system if the tested compiler is not up to the task. Benefit will be that we can get rid of some Makefile and script code and we'll at last test what we ship and not a random subset of it. Quick poll: who does configure for some system dir when doing development? Laurent
