From: Ranjit Mathew <rmathew@hotmail.com>
To: gcc@gcc.gnu.org
Cc: mingw-users@lists.sourceforge.net
Subject: Re: MinGW (Was: Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets)
Date: Tue, 20 May 2003 04:27:00 -0000 [thread overview]
Message-ID: <3EC9ADE0.2090005@hotmail.com> (raw)
In-Reply-To: <000001c31e67$5ef5fcf0$3c9fd783@northwood>
Stephan T. Lavavej wrote:
> I'm trying to learn. I've managed to successfully build 3.3 on GNU/Linux,
> but haven't been able to build any version of gcc on MSYS/MinGW (whether
> MinGW-patched or not).
>
> I don't entirely understand CVS yet and I have no clue how diffs/patches
> work (mechanically, not conceptually). I'm trying to learn, though. When
> MinGW gcc 3.3 is released, I'll see if I can bootstrap it, and I'll report
> any problems I encounter.
In GCC 3.3, things aren't that bad at all for MinGW. Except for
a minor glitch:
http://article.gmane.org/gmane.comp.gnu.mingw.devel/561
GCC 3.3 builds out of the box (C/C++) for MinGW, and is
quite usable as is.
If you are willing to work on Linux (and I guess you are, since
you have already compiled 3.3 for Linux), you might find this
document that I'd written a while ago, useful for this purpose:
http://ranjitmathew.tripod.com/phartz/gcj/bldgcj.html
The two step process might seem a bit roundabout but amazingly
is almost twice as fast as a native bootstrap on Windows (for
C/C++/Java)!
If you're not interested in GCJ (Java), leave out the "java"
in "--enable-languages=c,c++,java" in the configure scripts.
If you are however, do get this cross-configury patch for
libgcj before you start:
http://gcc.gnu.org/ml/java-patches/2003-q2/msg00111.html
If you'd rather wait for the "mingw-local" patchset to also
be published before you venture into this, hang on for a
while longer.
The "mingw-local" patchsets are published to the MinGW SF
repository as soon as a MinGW GCC release is made.
Hope this helps.
Ranjit.
--
Ranjit Mathew Email: rmathew AT hotmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/
next prev parent reply other threads:[~2003-05-20 4:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 1:16 Stephan T. Lavavej
2003-05-20 4:27 ` Ranjit Mathew [this message]
2003-05-20 16:15 ` E. Weddington
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 17:52 Bonzini
2003-05-20 1:24 MinGW (Was " Nathanael Nerode
2003-05-21 3:33 ` Christopher Faylor
2003-05-19 22:40 MinGW (Was: " Stephan T. Lavavej
2003-05-19 23:49 ` Joe Buck
2003-05-20 0:33 ` DJ Delorie
2003-05-21 3:27 ` Christopher Faylor
2003-05-20 4:22 ` Anthony Green
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=3EC9ADE0.2090005@hotmail.com \
--to=rmathew@hotmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mingw-users@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).