From: khan@xraylith.wisc.edu (Mumit Khan)
To: help-gcc@gnu.org
Subject: Re: Binaries
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <82a508$gc2$1@news.doit.wisc.edu> (raw)
Message-ID: <19991231222400.IyFGDtaGFH9hQQRQb1vnYHo2rAGHWtlssVQqrAqQEws@z> (raw)
In-Reply-To: <829vt3$l7r$1@news5.jaring.my>
In article < 829vt3$l7r$1@news5.jaring.my >,
starman <starman@pd.jaring.nospam.my> wrote:
>Where can i get binaries (Intel Win98) for GNU C++??
See my usual blurb below.
>What is the difference between GNU g++ and GNU C++??
One and the same -- GNU g++ is the name of GNU C++ compiler. The
GNU C++ compiler driver (ie., the program you run to compile and
link C++ code) is installed as both g++ and c++.
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ for 3 different
gcc-2.95.2 ports to various win32 targets.
- Cygwin -- Uses Cygnus' POSIX API (Unix'y)
http://sourceware.cygnus.com/cygwin/
- Mingw -- Use Microsoft runtime, no POSIX (native Win32)
- UWIN -- Uses AT&T UWIN POSIX API (Unix'y)
http://www.research.att.com/sw/tools/uwin/
There is short synopsis of these terms (Cygwin, Mingw, UWIN) on my
web site to help you decide.
For either Cygwin or UWIN, you need install the base system from
respective sites. For Mingw, all you need are the compiler tools
from my site (self extracting package).
All distributions come with C, C++, F77, ObjC compilers and runtime
headers/libraries. Cygwin and UWIN also come with GNU Java compiler.
See http://gcc.gnu.org/ for information on GCC compilers.
For DOS target, see http://www.delorie.com/djgpp/ .
Regards,
Mumit
next prev parent reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-03 19:09 Binaries starman
1999-12-03 20:34 ` Mumit Khan [this message]
1999-12-31 22:24 ` Binaries Mumit Khan
1999-12-31 22:24 ` Binaries starman
2015-08-12 17:24 Binaries Teo Samarzija
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='82a508$gc2$1@news.doit.wisc.edu' \
--to=khan@xraylith.wisc.edu \
--cc=help-gcc@gnu.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).