From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>, cygwin-announce@cygwin.com
Subject: Re: Updated: gcc-5.3.0-2 (x86/x86_64)
Date: Sat, 20 Feb 2016 18:41:00 -0000 [thread overview]
Message-ID: <CAGHJv4eGk3YfYrQwKxyBX0O2QsZ=p+avuGSfF29tMJv8V58Xqw@mail.gmail.com> (raw)
In-Reply-To: <56C8438F.3000607@gmail.com>
On 20 February 2016 at 05:44, JonY wrote:
> gcc-5.3.0-2 has been uploaded for 32bit and 64bit Cygwin and marked as
> stable.
Not sure if I'm missing something, but i686-pc-cygwin is still at
4.9.2. How do I access 32-bit 5.3.0? I'm natively on 64-bit and when
I use cygport to compile for 32bit, it looks for i686-pc-cygwin
compilers.
Thanks,
Chris
--
Chris Sutcliffe
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2016-02-20 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56C8438F.3000607@gmail.com>
2016-02-20 18:41 ` Chris Sutcliffe [this message]
2016-02-20 18:49 ` Achim Gratz
2016-02-21 2:09 ` Yaakov Selkowitz
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='CAGHJv4eGk3YfYrQwKxyBX0O2QsZ=p+avuGSfF29tMJv8V58Xqw@mail.gmail.com' \
--to=ir0nh34d@gmail.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).