https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112862
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to r...@cebitec.uni-bielefeld.de from comment #4) > > --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- > > OK. So I realise the reason you see this and I wasn't: I have the habit of > > installing before running the testsuite. When I test uninstalled, then I > > get > > the issue. > > Right: I always avoid installing before testing to make extra certain to > test the freshly built bits and nothing else. I would not have that problem, since I always delete the previous install (otherwise its shared libraries could be found during the current build, since the GCC command lines usually include the installation paths). > > Now I have a concern that we have instances of -Bpath/to/libsomething/.libs > > that are present to allow for specs substitution and we also need them for > > providing run paths at test time. BUT, we do not want duplicates (since, > > that > > triggers a different warning for some Xcode versions, and is inefficient > > anyway > > - albeit probably a very minor contribution to testing time). > > Still there is going to be an impact, even on non-Darwin. However, this > duplication of -B and -L options is present all over the testsuite > already, just nobody cared to do something about it so far. Those Xcode > 15 ld warnings my change this, though... Actually, since -B produces a -L for every -B directory that exists, if we add -B we really ought to omit the -L if it's the same - otherwise we get useless duplicates on the link line. Do you know of any exception to the B implies L?
