From: Craig Rodrigues <rodrigc@mediaone.net>
To: Adam Megacz <gcc@lists.megacz.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mingw32 target broken [cygwin as well]
Date: Fri, 07 Dec 2001 23:40:00 -0000 [thread overview]
Message-ID: <20011208021237.A11499@mediaone.net> (raw)
In-Reply-To: <86d71qfdw3.fsf_-_@megacz.com>; from gcc@lists.megacz.com on Sat, Dec 08, 2001 at 01:02:20AM -0500
Hi,
I don't think building a mingw cross compiler is a
straightforward thing. You need the header files
for the mingw runtime and for the w32api.
See:
http://members.telering.at/jessich/mingw/index.html
http://sources.redhat.com/ml/crossgcc/2001-q4/msg00310.html
And you might want to ask on the mingw mailing lists
at http://www.mingw.org
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
next prev parent reply other threads:[~2001-12-08 7:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 21:06 mingw32 target broken Adam Megacz
2001-12-07 22:01 ` Adam Megacz
[not found] ` <20011208003722.A14955@mediaone.net>
2001-12-07 23:12 ` mingw32 target broken [cygwin as well] Adam Megacz
2001-12-07 23:40 ` Craig Rodrigues [this message]
2001-12-08 0:00 ` mingw32 target broken [cygwin as well] [didn't know cross-compilers were such an ordeal] Adam Megacz
2001-12-08 16:00 ` Jeff Sturm
2001-12-08 16:05 ` Adam Megacz
2001-12-08 14:42 ` mingw32 target broken [cygwin as well] Jeff Sturm
2001-12-08 16:04 ` mingw32 target broken [cygwin as well] [the saga continues] Adam Megacz
2001-12-08 18:19 ` Craig Rodrigues
2001-12-08 18:30 ` Adam Megacz
2001-12-08 18:39 ` Craig Rodrigues
2001-12-08 18:56 ` Adam Megacz
2001-12-09 9:07 ` Jeff Sturm
2001-12-09 20:38 ` Adam Megacz
2001-12-10 12:36 ` DJ Delorie
2001-12-10 12:48 ` Joseph S. Myers
2001-12-10 12:57 ` DJ Delorie
2001-12-10 21:06 ` Jeff Sturm
2001-12-10 21:08 ` DJ Delorie
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=20011208021237.A11499@mediaone.net \
--to=rodrigc@mediaone.net \
--cc=gcc@gcc.gnu.org \
--cc=gcc@lists.megacz.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).