Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: drow@mvista.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 18:18:00 -0000	[thread overview]
Message-ID: <200308271817.h7RIHrR23997@greed.delorie.com> (raw)
In-Reply-To: <20030827171507.GA14215@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 27 Aug 2003 13:15:07 -0400)


> 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?

> 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.


  reply	other threads:[~2003-08-27 18:18 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 [this message]
2003-08-27 19:14   ` Daniel Jacobowitz

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=200308271817.h7RIHrR23997@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=drow@mvista.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