From: Jan-Jaap van der Heijden <janjaap@Wit381304.student.utwente.nl>
To: GNU-Win32 list <gnu-win32@cygnus.com>
Subject: [ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available.
Date: Sun, 18 Jan 1998 16:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980118203400.3229A-100000@zoo-station.student.utwente.nl> (raw)
I upgraded the tools on my mingw32 page:
http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html
to the newly released GCC 2.8.0
The good news is that all patches needed to build mingw32 GCC have been
integrated in the FSF source, so no patches are needed anymore.
On this page, you will also find:
binutils 980103
libstdc++ 2.8.0
libg++ 2.8.0
mingw32 (Colin's 971230 + a few extra prototypes)
windows32api headers
GNU make 3.76.1
GNU bison 1.25
GNU flex 2.5.4a
GNU m4 1.4
gzip 1.2.4
All native mingw32, of course!
Enjoy,
JanJaap
---
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead. -- RFC1925.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-01-18 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-18 16:07 Jan-Jaap van der Heijden [this message]
1998-01-20 14:58 ` Paul Garceau
1998-01-24 15:34 ` Jan-Jaap van der Heijden
1998-01-27 2:27 ` Problems with mingw32 GCC 2.8.0 !!! Fabio Vignoli
1998-01-27 8:52 ` Mumit Khan
1998-01-27 16:21 ` Jan-Jaap van der Heijden
1998-01-28 0:46 ` Mikey
1998-01-28 14:54 ` Fabio Vignoli
1998-01-28 21:10 ` Isaac Kohn
1998-01-29 4:47 ` Benjamin Riefenstahl
1998-01-22 9:32 [ANNOUNCE] mingw32 GCC 2.8.0 based toolchain available Liam Fitzpatrick
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=Pine.LNX.3.96.980118203400.3229A-100000@zoo-station.student.utwente.nl \
--to=janjaap@wit381304.student.utwente.nl \
--cc=gnu-win32@cygnus.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).