From: JonY <jon_y@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: multiple definition of `atan2l' on the current Cygwin
Date: Thu, 14 Apr 2016 22:32:00 -0000 [thread overview]
Message-ID: <57101A7A.1070300@users.sourceforge.net> (raw)
In-Reply-To: <20160414135235.GE1264@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 340 bytes --]
On 4/14/2016 21:52, Corinna Vinschen wrote:
>
> This is actually a problem in libstdc++-v3. On platforms missing
> certain long double functions libstdc++-v3 is built with stub functions
> using the same name.
>
> Jon, any chance to rebuild the gcc packages ASAP?
>
Already on it, uploads should start over the weekends.
[-- Attachment #1.2: 0xD4EBC740.asc --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-04-14 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 8:11 Tatsuro MATSUOKA
2016-04-12 13:39 ` Corinna Vinschen
2016-04-13 0:09 ` Tatsuro MATSUOKA
2016-04-13 8:11 ` Corinna Vinschen
2016-04-13 16:57 ` René Berber
2016-04-13 17:26 ` Marco Atzeri
2016-04-14 7:52 ` Corinna Vinschen
2016-04-14 10:00 ` Takashi Yano
2016-04-14 13:52 ` Corinna Vinschen
2016-04-14 22:32 ` JonY [this message]
2016-04-17 4:29 ` Tatsuro MATSUOKA
2016-04-17 5:15 ` Tatsuro MATSUOKA
2016-04-18 23:33 ` Tatsuro MATSUOKA
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 23:54 Mintty font problem Paul Ausbeck
2016-04-10 19:50 ` john refling
2016-04-10 20:18 ` Postinstall script errors on cygwin x86 install Tatsuro MATSUOKA
2016-04-11 6:37 ` Achim Gratz
2016-04-11 20:42 ` Tatsuro MATSUOKA
2016-04-11 20:56 ` Ken Brown
2016-04-12 3:07 ` multiple definition of `atan2l' on the current Cygwin Tatsuro MATSUOKA
2016-04-12 17:03 ` Warren Young
2016-04-12 8:15 ` Tatsuro MATSUOKA
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=57101A7A.1070300@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--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).