Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sourceware.org
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org
Subject: Re: [RFC] Simplify MinGW canadian crosses
Date: Tue, 29 Aug 2006 16:09:00 -0000	[thread overview]
Message-ID: <20060829160045.GA21260@calimero.vinschen.de> (raw)
In-Reply-To: <20060829154413.GA19153@nevyn.them.org>

[Also dropped the lists cygwin-patches and mingw-patches here]

On Aug 29 11:44, Daniel Jacobowitz wrote:
> On Tue, Aug 29, 2006 at 05:35:40PM +0200, Corinna Vinschen wrote:
> > Sorry, but that's not the deal.  Using my patches, you can install a
> > standard source tree, including gcc, gdb, binutils, [...], and last but
> > not least the winsup directory on, say, a Linux machine, and then build
> > a complete three stage canadian cross on *Linux*, which generates a
> > i686-pc-mingw32-x-arm-elf toolchain.  You don't have to install the MinGW
> > libraries and header files somewhere on the Linux machine and tweak the
> > build process to find them.  Everything comes out of the same source
> > tree.  From my point of view this simplifies stuff, it doesn't make it
> > more complicated.
> 
> Are your changes affecting the i686-pc-mingw32 targeted compiler built
> in the middle?  Your description suggested that it affected the build
> process of the final canadian cross compiler.  If you're changing that
> second one, then none of my objections are relevant.
> 
> I guess what I'm asking is: why doesn't "make install" when you've
> built the i686-pc-mingw32 compiler install everything you need to use
> that compiler to build i686-pc-mingw32 hosted applications?

It does.  I don't quite understand your objections.  You seem to
imply that my patches try to do something mysterious, but they don't.
You build a standard canadian, three staged, as usual:

  configure/make/install linux-linux-mingw
  configure/make/install linux-linux-arm
  configure/make/install linux-mingw-arm

None of my patches is actually complicated or adds any new feature.
They only fix bugs which hinder to build canadian crosses the right
way (TM).


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat


  reply	other threads:[~2006-08-29 16:00 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
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 [this message]
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=20060829160045.GA21260@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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