Re: autotools transition report: need a flag day

[Dan Kegel <dank at kegel dot com>]

Dan Kegel wrote:
> Phil Edwards <phil at jaj dot com> wrote:
>
> > After this, nothing inside the library will refer to itself as
> > "libstdc++-v3".  Which means that name will not be propogated to the 
> > users.
> > The only places we'll be seeing "-v3" are references to the source 
> > directory.
>
> Grumble.  It would be Real Nice if the remaining -v3 references
> could go, too.  Having to guess how to invoke the testsuite
> is complicating my build-and-test-any-version-of-gcc script
> (http://kegel.com/crosstool).  

Here's the logic I'm using now in my build-and-test script;
I think this works for all versions of gcc >= 2.95.
(This is still easier to understand than how 'make check'
works, but just barely...)

# gcc-2.95 called the c++ library libstdc++.
# gcc-3.[0123] called the c++ library libstdc++-v3.
# gcc-3.4 calls the c++ library libstdc++, but it still lives in the libstdc++-v3 directory, grumble.
# See http://gcc.gnu.org/ml/libstdc++/2003-08/msg00034.html
if test -d $TARGET/libstdc++-v3; then
   LIBSTDCXX_DIR=libstdc++-v3
   if test -f $BUILD_DIR/$GCC_DIR/libstdc++-v3/testsuite/lib/libstdc++.exp; then
      LIBSTDCXX_TEST=libstdc++
   else
      LIBSTDCXX_TEST=libstdc++-v3
   fi
elif test -d $TARGET/libstdc++; then
   LIBSTDCXX_DIR=libstdc++
   LIBSTDCXX_TEST=libstdc++
else
   abort "can't find libstdc++ or libstdc++-v3"
fi

...

cd $TARGET/$LIBSTDCXX_DIR/testsuite
runtest --tool=$LIBSTDCXX_TEST --target=$TARGET -v || echo Some $LIBSTDCXX_TEST test failed...

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045