From: Paolo Bonzini <bonzini@gnu.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Tom Tromey <tromey@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: fixup SIM_CHECK_*
Date: Wed, 26 Aug 2009 12:04:00 -0000 [thread overview]
Message-ID: <4A94E277.70205@gnu.org> (raw)
In-Reply-To: <20090825195545.GC5034@gmx.de>
On 08/25/2009 09:55 PM, Ralf Wildenhues wrote:
> * Frank Ch. Eigler wrote on Wed, Aug 19, 2009 at 09:34:37PM CEST:
>> According to the FIXME note in that file, please excise SIM_CHECK_*
>> altogether if it has been mooted by a modern autoconf.
>
> This was still left TODO. Of course, I managed to actually commit a
> patch, that would not expand AC_CHECK_MEMBERS correctly, as that uses
> _$0_BODY internally, and $0 is still SIM_CHECK_MEMBER (Paolo, it's ugly
> to have to remember this, so we maybe shouldn't use m4_defn so much):
Hey, Eric (Blake) is the big optimizer in Autoconf-land, not me. :-) I
agree with you, though of course I don't like this kind of relying on
Autoconf internals.
The patch seems fine.
Paolo
next prev parent reply other threads:[~2009-08-26 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090815112928.GB5396@gmx.de>
[not found] ` <20090815113302.GC20172@gmx.de>
2009-08-18 18:56 ` [PATCH 3/N] some minor fixes in sim, gold, gdb Ralf Wildenhues
2009-08-19 18:43 ` Tom Tromey
2009-08-19 19:34 ` Ralf Wildenhues
2009-08-19 21:57 ` Frank Ch. Eigler
2009-08-22 17:35 ` Ralf Wildenhues
2009-08-25 20:05 ` fixup SIM_CHECK_* (was: [PATCH 3/N] some minor fixes in sim, gold, gdb) Ralf Wildenhues
2009-08-26 12:04 ` Paolo Bonzini [this message]
2009-08-26 20:08 ` fixup SIM_CHECK_* Ralf Wildenhues
[not found] ` <alpine.LSU.1.99.0908151331010.19553@acrux.dbai.tuwien.ac.at>
[not found] ` <20090816094922.GB25721@gmx.de>
[not found] ` <83ocqfitb3.fsf@gnu.org>
2009-08-25 19:55 ` Do not point to sources.redhat.com for autotools tarballs Ralf Wildenhues
2009-08-25 20:57 ` Eli Zaretskii
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=4A94E277.70205@gnu.org \
--to=bonzini@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=fche@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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