From: Ian Lance Taylor <iant@google.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC PATCH] update to libtool-2.4.2 and regenerate
Date: Mon, 31 Oct 2011 19:21:00 -0000 [thread overview]
Message-ID: <mcrsjm9vxs9.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <yddipn5b5s0.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Mon, 31 Oct 2011 15:21:51 +0100")
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> I made a quick comparison of the libtool.m4 in libgo/config with the
> 2.4.2 version: the only relevant change seems to be an instance of
> AC_PROG_GO, which also lives in go.m4. Ian will know why that
> additional copy is necessary.
The version of AC_PROG_GO in libgo/config/go.m4 is there so that I can
rebuild libgo/configure with a version of autoconf that does not have Go
support.
The version of AC_PROG_GO in libgo/config/libtool.m4 is there because
all the languages work that way in libtool.m4.
Ian
next prev parent reply other threads:[~2011-10-31 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 23:43 Markus Trippelsdorf
2011-10-28 2:11 ` Andi Kleen
2011-10-28 6:25 ` Markus Trippelsdorf
2011-10-29 9:25 ` Markus Trippelsdorf
2011-10-29 13:01 ` Andi Kleen
2011-10-28 2:17 ` Joseph S. Myers
2011-10-28 6:51 ` Markus Trippelsdorf
2011-10-28 15:51 ` Joseph S. Myers
2011-10-28 16:07 ` Markus Trippelsdorf
2011-10-28 9:04 ` Rainer Orth
2011-10-28 14:17 ` Ian Lance Taylor
2011-10-28 18:21 ` Matthias Klose
2011-10-28 18:01 ` Andreas Tobler
2011-10-31 15:01 ` Rainer Orth
2011-10-31 19:21 ` Ian Lance Taylor [this message]
2011-10-31 21:39 ` v2[PATCH] " Markus Trippelsdorf
2011-10-31 21:47 ` [PATCH] Use gcc's libtool in libgo Markus Trippelsdorf
2011-11-01 15:19 ` v2[PATCH] update to libtool-2.4.2 and regenerate Gerald Pfeifer
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=mcrsjm9vxs9.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=markus@trippelsdorf.de \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).