From: Daniel Jacobowitz <drow@false.org>
To: cygwin-patches@cygwin.com, gdb-patches@sourceware.org,
mingw-patches@lists.sourceforge.net, binutils@sourceware.org,
gcc-patches@gcc.gnu.org
Subject: Re: [RFC] Simplify MinGW canadian crosses
Date: Tue, 29 Aug 2006 16:53:00 -0000 [thread overview]
Message-ID: <20060829160923.GB20830@nevyn.them.org> (raw)
In-Reply-To: <20060829160406.GB21260@calimero.vinschen.de>
On Tue, Aug 29, 2006 at 06:04:06PM +0200, Corinna Vinschen wrote:
> On Aug 29 11:47, Christopher Faylor wrote:
> > Btw, I agree with Daniel's suggestion of using
> > ../config/no-executables.m4 if that's possible.
>
> I did that first, but the argument against this is that the
> mingw-runtime package, does not contain a top-level config directory.
> The source tree is supposed to be built stand-alone. Therefore it's
> required to have a stand-alone aclocal.m4 file.
>
> [time passes]
>
> Or do you mean I should just add an include(../config/no-executables.m4)
> to winsup/acinclude.m4 and create the aclocal.m4 files from there?
If you do that it'll just emit a sinclude into aclocal.m4 anyway, won't
it?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-29 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 12:14 Corinna Vinschen
2006-08-29 15:00 ` Daniel Jacobowitz
2006-08-29 15:24 ` DJ Delorie
2006-08-29 15:32 ` Daniel Jacobowitz
2006-08-29 15:35 ` DJ Delorie
2006-08-29 15:38 ` Daniel Jacobowitz
2006-08-29 15:47 ` DJ Delorie
2006-08-29 15:44 ` Corinna Vinschen
2006-08-29 16:00 ` Daniel Jacobowitz
2006-08-29 16:08 ` Corinna Vinschen
2006-08-29 16:49 ` Daniel Jacobowitz
2006-08-29 17:04 ` Corinna Vinschen
2006-08-29 16:04 ` Christopher Faylor
2006-08-29 16:09 ` Corinna Vinschen
2006-08-29 16:53 ` Daniel Jacobowitz [this message]
2006-08-29 17:01 ` Corinna Vinschen
2006-08-29 17:51 ` Christopher Faylor
2006-08-29 23:00 ` Christopher Faylor
2006-08-30 7:15 ` Corinna Vinschen
2006-08-29 15:10 ` DJ Delorie
2006-08-30 20:32 ` Corinna Vinschen
2006-08-31 7:23 ` Danny Smith
2006-08-31 23:37 ` Corinna Vinschen
2006-08-30 14:44 Danny Smith
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=20060829160923.GB20830@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=cygwin-patches@cygwin.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mingw-patches@lists.sourceforge.net \
/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).