From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygwin32-gcc, cygwin64-gcc 5.3.0-1 etc.
Date: Mon, 22 Feb 2016 08:58:00 -0000 [thread overview]
Message-ID: <201602220854.u1M8sgig029368@int-mx10.intmail.prod.int.phx2.redhat.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygwin32-2.4.1-1
* cygwin32-clang-3.7.1-1
* cygwin32-gcc-core-5.3.0-1
* cygwin32-gcc-g++-5.3.0-1
* cygwin32-gcc-fortran-5.3.0-1
* cygwin32-gcc-objc-5.3.0-1
* cygwin32-gcc-objc++-5.3.0-1
* cygwin32-gcc-ada-5.3.0-1
* cygwin32-gcc-cilkplus-5.3.0-1
* cygwin32-gettext-0.19.5.1-1
* cygwin32-libiconv-1.14-2
* cygwin32-libtool-2.4.6-1
* cygwin32-w32api-headers-4.0.4-1
* cygwin32-w32api-runtime-4.0.4-1
* cygwin64-2.4.1-1
* cygwin64-clang-3.7.1-1
* cygwin64-gcc-core-5.3.0-1
* cygwin64-gcc-g++-5.3.0-1
* cygwin64-gcc-fortran-5.3.0-1
* cygwin64-gcc-objc-5.3.0-1
* cygwin64-gcc-objc++-5.3.0-1
* cygwin64-gcc-ada-5.3.0-1
* cygwin64-gcc-cilkplus-5.3.0-1
* cygwin64-gettext-0.19.5.1-1
* cygwin64-libiconv-1.14-4
* cygwin64-libtool-2.4.6-1
* cygwin64-w32api-headers-4.0.4-1
* cygwin64-w32api-runtime-4.0.4-1
The GNU Compiler Collection includes front ends for C, C++, Objective-C,
Fortran, Java, and Ada, as well as libraries for these languages
(libstdc++, libgfortran,...). These packages are 32<->64-bit cross-compilers
for Cygwin; for the native compilers, use the 'gcc-*' packages.
This is an update to match native gcc-5.3.0-2, clang-3.7.1, as well as
other updates to these toolchains.
Please note while these remain to simplify building both Cygwin versions
on one system, other cygwin32-*/cygwin64-* packages which were created
primarily to help bootstrap x86_64-cygwin will soon be removed from the
distribution.
--
Yaakov
reply other threads:[~2016-02-22 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201602220854.u1M8sgig029368@int-mx10.intmail.prod.int.phx2.redhat.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.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).