public inbox for binutils@sourceware.org
 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 17:04:00 -0000	[thread overview]
Message-ID: <20060829165259.GD21260@calimero.vinschen.de> (raw)
In-Reply-To: <20060829160848.GA20830@nevyn.them.org>

On Aug 29 12:08, Daniel Jacobowitz wrote:
> On Tue, Aug 29, 2006 at 06:00:45PM +0200, Corinna Vinschen wrote:
> > 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.
> 
> There's a lesson here for both of us, I think :-)
> 
> Your patches do things which are to me _quite_ mysterious, as in I
> stared at them and couldn't work out what they were for.  I think this
> is because you described your goal, but not how you were getting there.

Uh, sorry about that.

> As I described, CodeSourcery already builds this way regularly:
> 
> > 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
> 
> So since we didn't encounter any of these bugs you've described, I
> assumed you were doing something different.  I apologize.
> 
> I'm not familiar with our linux-linux-mingw process, but I don't see
> any reason it should be fundamentally different from this.  Except,
> doh, it appears we only build the compiler and not the runtime from
> scratch :-(  No wonder I was confused.
> 
> Sorry again!

No worries :)


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

  reply	other threads:[~2006-08-29 16:53 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 [this message]
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=20060829165259.GD21260@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).