public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthew Tippett <matthew.tippett@sympatico.ca>
To: Dan Kegel <dank@kegel.com>
Cc: Ken Wolcott <ken.wolcott@med.ge.com>,
	 crossgcc mailing list <crossgcc@sources.redhat.com>,
	gcc-help@gcc.gnu.org
Subject: Re: gcc.exe cross compiler (Cygwin -> Linux)
Date: Sun, 23 May 2004 02:06:00 -0000	[thread overview]
Message-ID: <40B0070E.4040303@sympatico.ca> (raw)
In-Reply-To: <40AFF67A.6010801@kegel.com>

Thanks.

If this works, there will be a lot of people that will be *VERY* 
happy - gcc 3.2 vs gcc 3.3.3 is a hell of a performance jump.

Thanks for the info guys.

Regards,

Matthew

Dan Kegel wrote:
> Matthew Tippett wrote:
> 
>>>> I am looking at having a gcc-3.3.3 that runs under windows and 
>>>> generates linux binaries.
>>>>
>>>> Does anyone one know of any references for building a gcc.exe that 
>>>> generates binaries for Linux under Windows?
>>>>
>>> Try crosstool at http://www.kegel.com/crosstool/
> 
>  >
>  > I have used cross tool for Linux cross compilers for Linux.
>  >
>  > I didn't see any mention of targetting a Windows executable.  I will
>  > look deeper though.
> 
> The latest snapshot,
> http://kegel.com/crosstool/crosstool-0.28-rc16.tar.gz
> can build on Cygwin.  (However, the latest Cygwin (1.5.9-1)
> has a bug which causes it to crash when building glibc;
> the workaround is to grab the latest cygwin1.dll snapshot, e.g.
> http://cygwin.com/snapshots/cygwin1-20040520.dll.bz2,
> uncompress it, exit all Cygwin processes, and copy it
> over the old cygwin1.dll.)
> - Dan
> 

  reply	other threads:[~2004-05-23  2:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 14:54 Matthew Tippett
2004-05-21 15:05 ` Ken Wolcott
2004-05-23  1:24   ` Matthew Tippett
2004-05-23  1:58     ` Dan Kegel
2004-05-23  2:06       ` Matthew Tippett [this message]
2004-05-23  2:48         ` Dan Kegel

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=40B0070E.4040303@sympatico.ca \
    --to=matthew.tippett@sympatico.ca \
    --cc=crossgcc@sources.redhat.com \
    --cc=dank@kegel.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ken.wolcott@med.ge.com \
    /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).