Re: Patch to update libtool in GCC and binutils trees

[Steve Ellcey <sje at cup dot hp dot com>]

> could you post the difference of the toplevel Makefile and config.log
> files with old/new libtool?  AFAICS these lines get added there, but
> I don't see yet how Libtool comes into play for this difference.
> 
> Thanks, and please Cc: me on replies,
> Ralf

Hm, The toplevel Makefile does not appear to be different between the
versions with the new and old libtool.  But I noticed, looking at
obj_gcc/x86_64-suse-linux-gnu/32/libstdc++-v3/config.log, in the old
libtool tree I see:

=========

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by package-unused configure version-unused, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ /proj/opensrc/sje/svn.reg/src/trunk/libstdc++-v3/configure --with-multisubdi
r=32 --with-multisrctop= --enable-multilib --cache-file=./config.cache --enable-
multilib --prefix=/proj/opensrc/sje/svn.reg/gcc-x86_64-suse-linux-gnu-trunk --wi
th-local-prefix=/proj/opensrc/sje/svn.reg/gcc-x86_64-suse-linux-gnu-trunk --disa
ble-nls --with-gmp=/proj/opensrc/be/x86_64-suse-linux-gnu --with-mpfr=/proj/open
src/be/x86_64-suse-linux-gnu --enable-languages=c,c++,fortran --program-transfor
m-name=s,y,y, --with-target-subdir=x86_64-suse-linux-gnu --build=x86_64-suse-lin
ux-gnu --host=x86_64-suse-linux-gnu --target=x86_64-suse-linux-gnu --srcdir=/pro
j/opensrc/sje/svn.reg/src/trunk/libstdc++-v3 CPPFLAGS= build_alias=x86_64-suse-l
inux-gnu host_alias=x86_64-suse-linux-gnu target_alias=x86_64-suse-linux-gnu -sr
cdir=/proj/opensrc/sje/svn.reg/src/trunk/libstdc++-v3

=========

And in the new libtool tree I see:

=========

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by package-unused configure version-unused, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ /proj/opensrc/nightly/src/trunk/libstdc++-v3/configure --with-multisubdir=32
 --with-multisrctop= --enable-multilib --cache-file=./config.cache --enable-mult
ilib --prefix=/proj/opensrc/nightly/gcc-x86_64-suse-linux-gnu-trunk --with-local
-prefix=/proj/opensrc/nightly/gcc-x86_64-suse-linux-gnu-trunk --disable-nls --wi
th-gmp=/proj/opensrc/be/x86_64-suse-linux-gnu --with-mpfr=/proj/opensrc/be/x86_6
4-suse-linux-gnu --enable-languages=c,c++,fortran --program-transform-name=s,y,y
, --with-target-subdir=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --hos
t=x86_64-suse-linux-gnu --target=x86_64-suse-linux-gnu --srcdir=/proj/opensrc/ni
ghtly/src/trunk/libstdc++-v3 CPPFLAGS= CXXFLAGS=-g -O2 -D_GNU_SOURCE CXX= /proj/
opensrc/nightly/build-x86_64-suse-linux-gnu-trunk/obj_gcc/./gcc/xgcc -shared-lib
gcc -B/proj/opensrc/nightly/build-x86_64-suse-linux-gnu-trunk/obj_gcc/./gcc -nos
tdinc++ -L/proj/opensrc/nightly/build-x86_64-suse-linux-gnu-trunk/obj_gcc/x86_64
-suse-linux-gnu/libstdc++-v3/src -L/proj/opensrc/nightly/build-x86_64-suse-linux
-gnu-trunk/obj_gcc/x86_64-suse-linux-gnu/libstdc++-v3/src/.libs -B/proj/opensrc/
nightly/gcc-x86_64-suse-linux-gnu-trunk/x86_64-suse-linux-gnu/bin/ -B/proj/opens
rc/nightly/gcc-x86_64-suse-linux-gnu-trunk/x86_64-suse-linux-gnu/lib/ -isystem /
proj/opensrc/nightly/gcc-x86_64-suse-linux-gnu-trunk/x86_64-suse-linux-gnu/inclu
de -isystem /proj/opensrc/nightly/gcc-x86_64-suse-linux-gnu-trunk/x86_64-suse-li
nux-gnu/sys-include LDFLAGS= build_alias=x86_64-suse-linux-gnu host_alias=x86_64
-suse-linux-gnu target_alias=x86_64-suse-linux-gnu -srcdir=/proj/opensrc/nightly
/src/trunk/libstdc++-v3

========

So in the old version, when the top-level Makefile calls the libstdc++-v3
configure it doesn't pass values for CXX or CXXFLAGS.  But in the new call
it does.  I think this is where we are going wrong.

I don't see any differences between the top-level Makefile in the old
and new versions so I don't understand why they are different.

The 64 bit (standard) x86_64 libstdc++-v3 config.log doesn't show
CPPFLAGS, CXX, or CXXFLAGS being passed as args when the configure is
done.  Only in the 32 bit version do I see this.  But that is the same
for old and new versions.

The hunt continues.

Steve Ellcey
sje@cup.hp.com