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_
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
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
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
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
* 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
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:
>
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
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.
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?
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
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
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 'aclocal' but I do get two
error messages when I run autoconf:
$ autoconf
configure.ac:177: e
13 matches
Mail list logo
