Re: Regenerating configure scripts

2008-03-24 Thread Michael Eager
Peter O'Gorman wrote: Michael Eager wrote: 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_

Re: Regenerating configure scripts

2008-03-24 Thread Michael Eager
Brian Dessent wrote: Michael Eager wrote: 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$wi

Re: Regenerating configure scripts

2008-03-24 Thread Brian Dessent
Michael Eager wrote: > 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_n

Re: Regenerating configure scripts

2008-03-24 Thread Peter O'Gorman
Michael Eager wrote: > 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_newli

Re: Regenerating configure scripts

2008-03-24 Thread Michael Eager
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

Re: Regenerating configure scripts

2008-03-24 Thread Ralf Wildenhues
* 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. > > No

Re: Regenerating configure scripts

2008-03-24 Thread H.J. Lu
I have built autoconf259-2.59-12.0.fc7.noarch.rpm and automake19-1.9.6-2.1.0.fc7.noarch.rpm for Fedora 7/8 so that I can run autoconf/automake for gcc and binutils. H.J. On Mon, Mar 24, 2008 at 12:53 PM, Michael Eager <[EMAIL PROTECTED]> wrote: > > Paolo Carlini wrote: > > Michael Eager wrote: >

Re: Regenerating configure scripts

2008-03-24 Thread Michael Eager
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. -- Michael Ea

Re: Regenerating configure scripts

2008-03-24 Thread Paolo Carlini
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. Paolo.

Re: Regenerating configure scripts

2008-03-24 Thread Michael Eager
Ralf Wildenhues wrote: $ autoconf configure.ac:177: error: possibly undefined macro: AC_LC_MESSAGES If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:185: error: possibly undefined macro: AC_DEFINE In which directory?

Re: Regenerating configure scripts

2008-03-24 Thread Ralf Wildenhues
Hello Michael, * Michael Eager wrote on Mon, Mar 24, 2008 at 07:04:40PM CET: > I'm trying to include a fix for the recurring GCC_NO_EXECUTABLES problem. > Refs: > http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html > http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html FWIW, I was going to post a couple o

Re: Regenerating configure scripts

2008-03-24 Thread Richard Guenther
On Mon, Mar 24, 2008 at 7:04 PM, Michael Eager <[EMAIL PROTECTED]> wrote: > I'm trying to include a fix for the recurring GCC_NO_EXECUTABLES problem. > Refs: > http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html > http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html > > I get no errors when I run 'acloc