From: Daniel Jacobowitz <drow@false.org>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org, mingw-patches@lists.sourceforge.net,
cygwin-patches@cygwin.com
Subject: Re: [RFC] Simplify MinGW canadian crosses
Date: Tue, 29 Aug 2006 13:06:00 -0000 [thread overview]
Message-ID: <20060829124525.GA13245@nevyn.them.org> (raw)
In-Reply-To: <20060829114107.GA17951@calimero.vinschen.de>
On Tue, Aug 29, 2006 at 01:41:07PM +0200, Corinna Vinschen wrote:
> Hi,
>
>
> I created the below patchset to allow to build canadian crosses with
> MinGW as host machine. It allowed me to build a linux-x-mingw-x-powerpc
> canadian cross, using the in-tree winsup directory, and so,
> consequentially, without the need to have any externally installed MinGW
> headers and/or libraries.
>
> Unfortunately, this requires changes in top-level, in libiberty, in
> winsup, in winsup/mingw, and in winsup/w32api.
Some of these patches may be good on their own. But, why go to this
much effort to support doing this complicated setup in a single tree? I
really don't think it's a good idea. If you want to build some code
that runs on mingw, I don't think that having mingw tools installed
is an unreasonable requirement.
We have to pick and choose where to invest in making our build system
even more complex.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-29 12:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 13:04 Corinna Vinschen
2006-08-29 13:06 ` Daniel Jacobowitz [this message]
2006-08-29 15:32 ` DJ Delorie
2006-08-29 15:35 ` Daniel Jacobowitz
2006-08-29 15:38 ` DJ Delorie
2006-08-29 15:44 ` Daniel Jacobowitz
2006-08-29 16:00 ` DJ Delorie
2006-08-29 15:47 ` Corinna Vinschen
2006-08-29 16:04 ` Daniel Jacobowitz
2006-08-29 16:09 ` Corinna Vinschen
2006-08-29 16:53 ` Daniel Jacobowitz
2006-08-29 17:51 ` Corinna Vinschen
2006-08-29 16:08 ` Christopher Faylor
2006-08-29 16:49 ` Corinna Vinschen
2006-08-29 17:01 ` Daniel Jacobowitz
2006-08-29 17:04 ` Corinna Vinschen
2006-08-29 18:35 ` Christopher Faylor
2006-08-30 9:16 ` Christopher Faylor
2006-08-30 12:33 ` Corinna Vinschen
2006-08-29 15:24 ` DJ Delorie
2006-08-31 11:34 ` Corinna Vinschen
2006-08-31 12:09 ` Danny Smith
2006-08-30 20:32 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=20060829124525.GA13245@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