This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Regenerating configure scripts
Ralf Wildenhues wrote:
* Michael Eager wrote on Mon, Mar 24, 2008 at 08:53:22PM CET:
Paolo Carlini wrote:
Michael Eager wrote:
I'm trying to update configure in gcc/libstdc++-v3.
Provided you have the correct versions of autoconf and automake, as
indicated, just running autoreconf certainly works.
Not for me. :-(
Autoreconf gives the same errors from aclocal.
Since you had problems using RPMs for the older tools, I suggest you
download and install vanilla autotools into a different --prefix;
get them from ftp.gnu.org/gnu/autoconf and /automake. To avoid yourself
hassles, use the same prefix for both of them.
After building/installing autoconf-2.59 and automake-1.6.9 into
version-specific directories, I'm able to regenerate the configure
scripts. Thanks all for the help.
I've noticed a problem with the patch:
if test "${with_newlib+set}" = set; then
AC_LIBTOOL_DLOPEN
fi
The test always succeeds. When $with_newlib is "yes",
${with_newlib+set} is "set".
If I change this to the old style test
if test "x$with_newlib" = x; then
AC_LIBTOOL_DLOPEN
fi
then it works as expected.
This is weird. I see the former idiom everywhere in configure.
The tests can't all be failing.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077