Re: Adding _eh.o frame-dwarf2.o to libstdc++.so.3?

[Benjamin Kosnik <bkoz at redhat dot com>]

> > However, when I go to re-generate the aclocal/configure bits in the 
> > libstdc++-v3 subdir, I get this:
> 
> > ./aclocal.m4:1801: AC_LIBTOOL_SETUP was called before AC_LIBTOOL_DLOPEN
> [...]
> 
> Works for me with autoconf 2.13 and both automake 1.4 and (relatively
> recent) CVS.

Huh? You are trying to rebuild libstdc++-v3/aclocal.m4 and 
libstdc++-v3/configure by running "aclocal; autoconf" in the top level 
libstdc++-v3 directory, right? 

Note this is not libstdc++-v2, ie the gcc/libstdc++ directory.

I cannot reproduce your success. 

Fresh gcc sources, your patch, and all iterations of 

1) rh 6.2 automake 1.4 /autoconf 2.13
2) maintainer-tools archive for automake/autoconf
3) CVS automake/autoconf

Give me errors. Can somebody else try this and tell me if I'm just 
completely off here, or what? Alexandre, if you're using slightly 
different sources or whatever can you detail  your sources (or point me 
at them in private email?)

> I don't know whether it's a bug in libtool.m4 that the new autoconf
> catches or something else, and I'm not sure I'll have time to
> investigate in the very near future.  How do you feel about using a
> stable release of autoconf, meanwhile?

.... has traditionally choked on the v3 configure.in ... Perhaps this is no 
longer the case, but I sure can't get it to work. Thus the newer 
drop of autoconf, and the tarballed sources for maintainer-tools on the 
libstdc++-v3 ftp site......


-benjamin