From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH RFA: Build machinery: Autoconf support for Go
Date: Thu, 11 Nov 2010 06:41:00 -0000 [thread overview]
Message-ID: <20101111063403.GD3987@gmx.de> (raw)
In-Reply-To: <mcr62wekvkf.fsf@google.com>
Hello Ian,
* Ian Lance Taylor wrote on Wed, Nov 03, 2010 at 09:21:04PM CET:
> This patch adds a new file config/go.m4, which provides autoconf support
> for Go. This file is not used by anything at present, but it will be
> used by the libgo library configure script when that is committed. A
> version of this file has been proposed to the autoconf maintainers.
> When gcc moves to a version of autoconf which includes Go support, this
> file can be deleted. However, until that time, it is useful for libgo.
> Putting it in a separate file means that the libgo configure script
> itself most likely will not have to be changed when we move to a new
> version of autoconf.
>
> Bootstrapped on x86_64-unknown-linux-gnu. OK for mainline?
I cannot approve this (yet), but it looks OK except for a couple of
nits: I'd wrap the contents in m4_version_prereq([2.69],, [...])
so that they turn into a no-op once the code has been integrated into
Autoconf (assuming for the moment that this will hapenn before 2.69),
similarly to how we treat additions to config/override.m4. You could
also have added the code to that file, that would've avoided any further
dependencies of generated aclocal.m4 and configure files (and in
directories using AC_PROG_GO but not using automake the dependency on
config/go.m4 will need to be tracked manually in Makefile.in). OTOH
the size of this warrants a new file for clarity.
I'm assuming that the macro definitions here are in sync with those
posted on autoconf-patches.
Thanks,
Ralf
> 2010-11-03 Ian Lance Taylor <iant@google.com>
>
> * go.m4: New file.
>
>
next prev parent reply other threads:[~2010-11-11 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 20:31 Ian Lance Taylor
2010-11-11 6:41 ` Ralf Wildenhues [this message]
2010-11-11 23:32 ` Ian Lance Taylor
2010-11-12 0:40 ` Paolo Bonzini
2010-11-12 21:22 ` Ian Lance Taylor
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=20101111063403.GD3987@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).