From: Mats Erik Andersson <mats.andersson@gisladisker.se>
To: bug-gnulib@gnu.org
Subject: Re: Messed up gl_COMPILER_PREPARE_CHECK_DECL
Date: Sat, 18 Jan 2020 23:02:42 +0100 [thread overview]
Message-ID: <20200118220242.GA63744@aun.utmark.mea> (raw)
In-Reply-To: <15957290.6tjZKmyNYO@omega>
Dear Bruno,
Lördag den 18:e january 2020, klockan 19:11, skrev Bruno Haible detta:
>
> The cause of the failure is that inetutils/configure.ac invokes
> AC_ISC_POSIX before AC_PROG_CC. But AC_ISC_POSIX is documented to expand
> into an invocation of AC_SEARCH_LIBS; therefore it requires to run the C
> compiler. It therefore does not really make sense to invoke AC_ISC_POSIX
> before AC_PROG_CC. You were just lucky that it worked before.
The new patch in itself makes the bootrapping successful without further
changes to configure.ac of Inetutils. That being said, I inserted the macro
AC_PROG_EGREP as recently as January 11th. And immediately it discloses
my ignorance of many details, sigh!
In contrast, our AC_ISC_POSIX sits fixed since 2005, but does not interfere
visibly (beyond the error log copied last time) with the advent of your most
recent change. Nonetheless, I will move it to a position where other
libraries are probed. Thank you for your most illuminating comments!
Regards,
Mats E A
next prev parent reply other threads:[~2020-01-18 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 15:11 Messed up gl_COMPILER_PREPARE_CHECK_DECL Mats Erik Andersson
2020-01-10 20:14 ` Bruno Haible
2020-01-10 21:36 ` Mats Erik Andersson
2020-01-10 22:06 ` Paul Eggert
2020-01-10 22:47 ` Bruno Haible
2020-01-11 1:32 ` Paul Eggert
2020-01-13 19:02 ` Bruno Haible
2020-01-14 0:38 ` Paul Eggert
2020-01-18 13:14 ` Bruno Haible
2020-01-18 13:34 ` Bruno Haible
2020-01-18 15:31 ` Mats Erik Andersson
2020-01-18 18:11 ` Bruno Haible
2020-01-18 22:02 ` Mats Erik Andersson [this message]
2020-01-18 22:19 ` Bruno Haible
2020-01-18 21:39 ` Paul Eggert
2020-01-18 22:11 ` Bruno Haible
2020-01-18 22:23 ` Paul Eggert
2020-01-18 22:32 ` Bruno Haible
2020-01-18 17:58 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200118220242.GA63744@aun.utmark.mea \
--to=mats.andersson@gisladisker.se \
--cc=bug-gnulib@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).