From: Daniel Jacobowitz <drow@mvista.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [toplevel] GCC_NO_EXECUTABLES
Date: Wed, 27 Aug 2003 19:14:00 -0000 [thread overview]
Message-ID: <20030827191452.GB31968@nevyn.them.org> (raw)
In-Reply-To: <200308271817.h7RIHrR23997@greed.delorie.com>
On Wed, Aug 27, 2003 at 02:17:53PM -0400, DJ Delorie wrote:
>
> > DJ, I know you asked for this to be added to acx.m4 instead. Unfortunately,
> > it uses constructs that autoconf 2.13 can't parse, thus breaking
> > regenerating the toplevel configure. So I put it in a separate file after
> > all.
>
> No version conditionals?
There's probably a way to do it, but my m4 fu is too weak to figure it
out.
> > Tested, along with the patches to follow momentarily, on an extensive
> > collection of targets (all --build=i686-linux). Is this OK?
>
> Ok.
>
> /me wonders if function-per-file is a good precident to start.
No opinion here. Zack seemed in favor of this but I don't recall
why...
Checked in to gcc and src.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-08-27 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 17:15 Daniel Jacobowitz
2003-08-27 18:18 ` DJ Delorie
2003-08-27 19:14 ` Daniel Jacobowitz [this message]
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=20030827191452.GB31968@nevyn.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.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