From: DJ Delorie <dj@redhat.com>
To: drow@false.org
Cc: 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 15:35:00 -0000 [thread overview]
Message-ID: <200608291523.k7TFNUR6027243@greed.delorie.com> (raw)
In-Reply-To: <20060829150948.GA18308@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 29 Aug 2006 11:09:48 -0400)
> Corinna is trying to generate --host=i686-mingw32 tools, with a
> different --target. This requires at least a --target=i686-mingw32
> compiler coming from elsewhere. That compiler can build the
> --host=i686-mingw32 libraries, and usually should.
Yes. So? We build that compiler from the same tree (as a simple
cross), so it's still the same problem. We still have to build those
libraries somehow, we still need to have them in source control, etc.
Our build farm likes to see a monolithic source tree, and we already
support building cygwin out of that tree, building mingw out of it is
a minor change.
(actually, we build four compilers out of that tree:
linux-linux-linux
linux-linux-mingw
linux-linux-arm
linux-mingw-arm)
next prev parent reply other threads:[~2006-08-29 15:24 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 [this message]
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
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=200608291523.k7TFNUR6027243@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=cygwin-patches@cygwin.com \
--cc=drow@false.org \
--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).