From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: gcc-5.3.0-1 (Test x86/x86_64)
Date: Fri, 12 Feb 2016 17:42:00 -0000 [thread overview]
Message-ID: <56BE197A.9010805@cygwin.com> (raw)
In-Reply-To: <56B0427F.3010005@cygwin.com>
On 2016-02-01 23:45, Yaakov Selkowitz wrote:
> On 2016-02-01 13:04, Yaakov Selkowitz wrote:
>> On 2016-01-28 03:56, JonY wrote:
>>> gcc-5.3.0-1 has been uploaded for 32bit and 64bit Cygwin.
>>
>> A few issues so far with this version:
>>
>> * the -rdynamic flag still isn't recognized;
>>
>> * the libgomp plugin loader is using the wrong library names;
>>
>> * the libstdc++ gdb/python scripts need to be rearranged.
>>
>> A merged and fixed patch 0011, a new patch 0022, and the necessary fixes
>> to the .cygport can be found here:
>>
>> https://github.com/cygwinports/gcc/commit/3a4ccda91fdddf766696d0fdf2efda1e6881b34e
>>
>> Can you spin a 5.3.0-2 with these changes?
>
> Update: I added a patch 0023 to enable _GLIBCXX_USE_C99, which enables
> std::stod, std::to_string, etc. However, some newlib headers need to be
> fixed, so let me get those in first.
Jon,
I have added several other improvements:
https://github.com/cygwinports/gcc/
In addition to the aforementioned changes, these patches allow enabling
_GLIBCXX_USE_C99 with cygwin-devel-2.4.1 (but see below), as well as
enabling libitm and cilkplus.
If you could, applying the following fix to your /usr/include/ieeefp.h
before building will help a bit as well:
https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=ac2f9e23ecd197758e7cc2ca1b8717add3d8762b;hp=8b8952064cfacf91b18aed37fbd44f621edb6941
I believe a 5.3.0-2 with all those changes should be ready for stable.
--
Yaakov
--
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
prev parent reply other threads:[~2016-02-12 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:35 JonY
2016-02-01 19:04 ` Yaakov Selkowitz
2016-02-02 5:45 ` Yaakov Selkowitz
2016-02-12 17:42 ` Yaakov Selkowitz [this message]
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=56BE197A.9010805@cygwin.com \
--to=yselkowitz@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).