From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com, Eli Zaretskii <eliz@is.elta.co.il>,
amodra@bigpond.net.au, drow@mvista.com
Subject: Re: [5.1] Re: po/POTFILES.in doesn't exist
Date: Mon, 12 Nov 2001 14:06:00 -0000 [thread overview]
Message-ID: <oritby9476.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Andrew Cagney's message of "Sun, 14 Oct 2001 14:48:33 -0400"
Sorry about the long delay, I've been way behind in my GDB e-mailing
folders :-(
On Oct 14, 2001, Andrew Cagney <ac131313@cygnus.com> wrote:
> cd /home/scratch/51/gdb/src/bfd && autoconf
> configure.in:8: AC_TRY_COMPILE was called before AC_ISC_POSIX
> configure.in:8: AC_TRY_RUN was called before AC_ISC_POSIX
> autoconf: Undefined macros:
> ***BUG in Autoconf--please report*** AC_FD_MSG
Which version of autoconf was this?
This last error is generally a symptom of under-quoted macro
invocations in configure.in or aclocal.m4. Typical scenario is a
construct such as:
AC_FOO(AC_BAR(...))
The correct way to write this is:
AC_FOO([AC_BAR([...])])
^ ^ ^ ^
I.e., every argument of every macro should be enclosed in quotation
brackets. Sometimes, you may get on without so much quoting, in the
hopes that the argument of the macro won't contain any active content
(i.e., no other m4 macro). But, if any macro argument does, you may
observe this kind of problem.
As for the errors about AC_ISC_POSIX, they can't be helped. There are
two macros called in bfd's configure that both want to be expanded
before any compilation takes place, but both of them do compiles
themselves. So, one of them gets to be second and generate these
messages.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-11-25 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-29 4:38 Eli Zaretskii
2001-08-07 16:04 ` Andrew Cagney
2001-08-07 16:11 ` Daniel Jacobowitz
2001-09-26 21:35 ` Andrew Cagney
2001-10-02 6:51 ` Alan Modra
2001-10-02 9:05 ` Andrew Cagney
2001-10-02 10:05 ` Eli Zaretskii
2001-10-14 11:49 ` [5.1] " Andrew Cagney
2001-10-20 18:32 ` Andrew Cagney
2001-11-12 14:06 ` Alexandre Oliva [this message]
2001-11-19 6:53 ` Andrew Cagney
2001-11-27 23:26 ` Andrew Cagney
2001-10-02 16:03 ` Alexandre Oliva
2001-10-02 18:44 ` Alan Modra
2001-10-02 20:25 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oritby9476.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@cygnus.com \
--cc=amodra@bigpond.net.au \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox