From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: configure{.in,} question
Date: Sun, 24 Oct 2010 15:38:26 -0400 [thread overview]
Message-ID: <c28w1n5qkt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3mxq3jy5d.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun\, 24 Oct 2010 19\:31\:10 +0200")
Lars Magne Ingebrigtsen wrote:
> I was going to remove the (BROKEN) from the gnutls conf option in
> configure.in, but when I then said "autoconf" (aren't we supposed to
> after all configure.in changes?), I got a somewhat big change in the
> configure file, with lots gcc changes and stuff:
Big changes are expected if you use a different version of autoconf to
the previous guy. I try to use the same version always to avoid this.
> ! if test x$GCC = xyes && test "x$GCC_LINK_TEST_OPTIONS" != x
> ! then
> ! ac_link="$ac_link $GCC_LINK_TEST_OPTIONS"
> ! fi
> !
> ! if test x$GCC = x && test "x$NON_GCC_LINK_TEST_OPTIONS" != x
> ! then
> ! ac_link="$ac_link $NON_GCC_LINK_TEST_OPTIONS"
> fi
I did not bother regenerating configure for that change, since it
purely cosmetic.
next prev parent reply other threads:[~2010-10-24 19:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 17:31 configure{.in,} question Lars Magne Ingebrigtsen
2010-10-24 19:38 ` Glenn Morris [this message]
2010-10-24 19:56 ` Lars Magne Ingebrigtsen
2010-10-24 20:07 ` Glenn Morris
2010-10-25 0:57 ` Stephen J. Turnbull
2010-10-25 8:38 ` Andreas Schwab
2010-10-25 14:43 ` Stephen J. Turnbull
2010-10-25 14:58 ` Andreas Schwab
2010-10-25 15:41 ` Stephen J. Turnbull
2010-10-25 8:47 ` Julien Danjou
2010-10-25 9:00 ` Andreas Schwab
2010-10-25 9:15 ` Eli Zaretskii
2010-10-25 16:06 ` Stefan Monnier
2010-10-25 18:04 ` Eli Zaretskii
2010-10-25 18:37 ` Glenn Morris
2010-10-25 19:59 ` Stefan Monnier
2010-10-25 19:34 ` Stefan Monnier
2010-10-25 16:43 ` Glenn Morris
2010-10-25 19:11 ` Ted Zlatanov
2010-10-25 19:13 ` Lars Magne Ingebrigtsen
2010-10-25 19:16 ` Ted Zlatanov
2010-10-25 20:08 ` Lars Magne Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c28w1n5qkt.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).