From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8
Date: Sun, 20 Mar 2016 11:14:00 -0000 [thread overview]
Message-ID: <56EE8621.2010001@gmail.com> (raw)
In-Reply-To: <8760whmn3a.fsf@Rainer.invalid>
On 20/03/2016 11:59, Achim Gratz wrote:
> Corinna Vinschen writes:
>>> If so, it might be a good idea for maintainers to test that nothing
>>> unexpected happens when they build their packages.
>>
>> Yes, that's really a good idea.
>
> I've run a fresh build of Perl on this.
>
> - there's a new signal: SIGIOT
>
> - two new symbols are found: _POSIX_C_SOURCE _POSIX_SOURCE
>
> - compilation complains about implicit declaration of fseeko and ftello
> (it could have used fseek and ftell since it's a 64bit build).
>
> - eaccess is also implicitly defined
>
> - some math functions are available on 32bit, but not 64bit: acosh,
> asinh, atanh, cbrt, copysign, erf, erfc, expm1, finite, hypot, ilogb,
> j0, lgamma, lgamma_r, log1p, lobg, nan, nextafter, remainder, scalbn
> (this has likely been that way for as long as 64bit exists)
only for the long double version as in 32 bit
They exist in 2.4.1
asinh
asinhf
casinh
casinhf
>
> I've also found that the configure script doesn't check correctly for
> import libs and thus misses libgdm on 64bit (where only libgdm.dll.a
> exists, but not libgdm.a). On 64bit gdm is also a different version
> from 32bit. What's the expected standard here, really? Just .dll.a or
> both that and .a?
preferred only .dll.a
> Regards,
> Achim.
>
next prev parent reply other threads:[~2016-03-20 11:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20160318203409.GA11113@calimero.vinschen.de>
[not found] ` <56EC6BDA.7050505@cornell.edu>
2016-03-18 21:45 ` Corinna Vinschen
2016-03-18 22:25 ` Ken Brown
2016-03-18 22:40 ` Ken Brown
2016-03-18 23:05 ` Yaakov Selkowitz
2016-03-18 23:29 ` Yaakov Selkowitz
2016-03-19 2:24 ` Ken Brown
2016-03-19 10:32 ` Corinna Vinschen
2016-03-19 12:34 ` Ken Brown
2016-03-19 18:03 ` Ken Brown
2016-03-20 15:26 ` Corinna Vinschen
2016-03-20 19:27 ` Ken Brown
2016-03-20 19:40 ` Ken Brown
2016-03-20 20:18 ` Ken Brown
2016-03-20 20:47 ` Yaakov Selkowitz
2016-03-21 14:13 ` Ken Brown
2016-03-21 16:30 ` Corinna Vinschen
2016-03-21 17:59 ` Ken Brown
2016-03-22 11:15 ` Corinna Vinschen
2016-03-22 14:59 ` Ken Brown
2016-03-30 21:17 ` Corinna Vinschen
2016-03-31 11:55 ` Ken Brown
2016-03-20 4:50 ` Yaakov Selkowitz
2016-03-20 15:18 ` Corinna Vinschen
2016-03-20 10:59 ` Achim Gratz
2016-03-20 11:14 ` Marco Atzeri [this message]
2016-03-20 15:25 ` Corinna Vinschen
2016-03-20 19:27 ` Achim Gratz
2016-03-20 20:53 ` Corinna Vinschen
2016-03-20 21:30 ` Corinna Vinschen
2016-03-20 20:24 ` Achim Gratz
2016-03-20 20:45 ` Yaakov Selkowitz
2016-03-22 9:31 ` Achim Gratz
2016-03-25 9:00 ` Dodgy functions (was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8) Achim Gratz
2016-03-26 0:16 ` Dodgy functions Achim Gratz
2016-03-26 19:41 ` Dodgy functions (finitel, strold) Achim Gratz
2016-03-29 16:09 ` Doug Henderson
2016-03-29 16:09 ` Corinna Vinschen
2016-04-01 19:04 ` Achim Gratz
2016-03-22 17:43 ` [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8 Chris Sutcliffe
2016-03-22 18:02 ` Corinna Vinschen
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=56EE8621.2010001@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@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).