From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/sim] flip and separate; Was: [commit/sim] Add common/common.m4; Was: [commit/sim] switch autoconf 2.59
Date: Fri, 14 Jan 2005 21:46:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0501141640170.60707@dair.pair.com> (raw)
In-Reply-To: <41E826A9.7030203@gnu.org>
On Fri, 14 Jan 2005, Andrew Cagney wrote:
> Hello,
>
> The attached patch does what the discussion below suggests:
>
> - flips the common.m4/aclocal.m4 include order
> - separates out AC_CONFIG_HEADER adding it explicitly to each file
> (including common/configure.ac)
>
> Next?
Cool, frv-sim works (used as a model for sim/cris).
Thanks!
Now all that's left to appease us pedants is to remove the
now-uncalled SIM_AC_COMMON macro (fix all references to it in
comments to say something like "when X is in a macro"), adjust
all AC_PREREQ examples to say 2.59 and the related stuff in
README-HACKING. ;-)
brgds, H-P
next prev parent reply other threads:[~2005-01-14 21:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 3:40 Andrew Cagney
2005-01-08 4:07 ` Daniel Jacobowitz
2005-01-10 16:18 ` Andrew Cagney
2005-01-11 20:20 ` Hans-Peter Nilsson
2005-01-11 21:06 ` Andrew Cagney
2005-01-12 1:17 ` Hans-Peter Nilsson
2005-01-12 1:26 ` Andrew Cagney
2005-01-12 2:00 ` Hans-Peter Nilsson
2005-01-12 16:29 ` [commit/sim] Force generation of configure and other stuff; Was: " Andrew Cagney
2005-01-12 17:15 ` [commit/sim] Add common/common.m4; " Andrew Cagney
2005-01-13 4:04 ` Hans-Peter Nilsson
2005-01-13 13:17 ` Hans-Peter Nilsson
2005-01-13 21:50 ` Andrew Cagney
2005-01-14 20:11 ` [commit/sim] flip and separate; Was: " Andrew Cagney
2005-01-14 21:46 ` Hans-Peter Nilsson [this message]
2005-01-12 17:53 ` [commit/sim] Force generation of configure and other stuff; " Hans-Peter Nilsson
2005-01-12 18:12 ` Andrew Cagney
2005-01-12 18:19 ` Hans-Peter Nilsson
2005-01-12 18:50 ` Andrew Cagney
2005-01-13 2:01 ` Hans-Peter Nilsson
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=Pine.BSF.4.58.0501141640170.60707@dair.pair.com \
--to=hp@bitrange.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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