public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.14.4
Date: Thu, 05 Feb 2015 08:49:00 -0000	[thread overview]
Message-ID: <20150205084913.GN2635@calimero.vinschen.de> (raw)
In-Reply-To: <87iofh8l54.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]

On Feb  4 21:41, Achim Gratz wrote:
> As I said in another thread I intend to skip directly to version 5.22
> shortly after it becomes available in May (assuming the release schedule
> is still holds).
> 
> While looking into some of the test fails on 5.18.4 I've moved back to
> 5.14.4 for comparison (the fail turned out to be a combination of new
> optimizations in gcc-4.9 and undefined behaviour in Perl code).  The fix
> in this case was to add a compiler flag (-fwrapv) that disables those
> optimizations and I'm now back to having roughly the same test fails as
> the old 5.14.2 from Reini:
> 
> Failed 9 tests out of 2048, 99.56% okay.
>         ../cpan/Win32/t/GetShortPathName.t
>   --> returns a long path name when called from mintty
>         ../cpan/Win32/t/Names.t
>   --> this old version of Win32 does not know about Windows 8.1
>         ../cpan/Win32/t/Unicode.t
>   --> ANSI path functions do not return the expected results
>         ../dist/Net-Ping/t/510_ping_udp.t
>   --> same as 5.14.2
>         ../ext/XS-APItest/t/call_checker.t
>   --> same as 5.14.2
>         ../lib/File/stat.t
>   --> works if test is not run as Administrator (but then other tests fail)
>         op/filetest.t
>   --> works if test is not run as Administrator (but then other tests fail)
>         porting/exec-bit.t
>   --> global.sym has exec bit set, but not registered as such
>         porting/regen.t
>   --> also something to do with global.sym
> 
> I'll probably keep the Win32 and other bundled CPAN modules as released
> with 5.14 and provide the latest versions as unbundled perl-* packages
> so that Module::CoreList doesn't lie to the user.
> 
> So, it looks like I'm ready to bring Perl on both 32bit and 64bit to the
> same (final 5.14.4) version plus I can already do the packaging changes
> planned for the 5.22 release (dissolution of perl_vendor and creation of
> perl_base as a minimal install variant) for both architectures.  I hope
> that this would enable a much smoother transition when that version gets
> released since the dependencies of those packages relying on Perl should
> be fixable until then.
> 
> If this sounds like a good idea to everybody else I'd remove the current
> test package for 5.18.4 on 32bit and replace it with another test
> package for 5.14.4, likely in about two weeks.  Comments or suggestions?

Sounds perfect to me.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-02-05  8:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 20:41 perl-5.14.4 Achim Gratz
2015-02-04 21:57 ` perl-5.14.4 David Stacey
2015-02-04 22:10   ` perl-5.14.4 Achim Gratz
2015-02-05 17:57     ` perl-5.14.4 Reini Urban
2015-02-05 19:16       ` perl-5.14.4 Achim Gratz
2015-02-05  8:49 ` Corinna Vinschen [this message]
2015-02-05 16:13 ` perl-5.14.4 Achim Gratz
2015-02-05 17:53   ` perl-5.14.4 Reini Urban
2015-02-05 19:13     ` perl-5.14.4 Achim Gratz
2015-02-06 19:22 ` perl-5.14.4 Achim Gratz
2015-02-08 20:19   ` perl-5.14.4 Achim Gratz
2015-02-09 10:25     ` perl-5.14.4 Corinna Vinschen
2015-02-09 17:16       ` perl-5.14.4 Achim Gratz
2015-02-09 18:49         ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:06           ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:41           ` perl-5.14.4 Achim Gratz
2015-02-09 20:20             ` perl-5.14.4 Corinna Vinschen
2015-02-14 20:04     ` perl-5.14.4 Achim Gratz
2015-02-14 21:12       ` perl-5.14.4 Achim Gratz
2015-02-15 10:32         ` perl-5.14.4 Corinna Vinschen
2015-02-15 13:18           ` perl-5.14.4 Achim Gratz
2015-02-15 14:31             ` perl-5.14.4 Corinna Vinschen
2015-02-15 16:22               ` perl-5.14.4 Achim Gratz
2015-02-15 19:14               ` perl-5.14.4 Achim Gratz
2015-02-16  9:17                 ` perl-5.14.4 Corinna Vinschen
2015-02-16  9:46                   ` perl-5.14.4 Achim Gratz
2015-02-16 10:25                     ` perl-5.14.4 Corinna Vinschen
2015-02-16 12:25                       ` perl-5.14.4 Corinna Vinschen
2015-02-16 14:29                         ` perl-5.14.4 Achim Gratz
2015-02-16 15:32                           ` perl-5.14.4 Corinna Vinschen
2015-02-16 15:42                             ` perl-5.14.4 Achim Gratz
2015-03-05 13:21                               ` perl-5.14.4 Corinna Vinschen
2015-03-05 16:45                                 ` perl-5.14.4 Achim Gratz
2015-03-10  9:10                                 ` perl-5.14.4 Corinna Vinschen
2015-03-14 20:30                                   ` perl-5.14.4 Achim Gratz
2015-03-16  9:06                                     ` perl-5.14.4 Corinna Vinschen
2015-02-10 19:55 ` perl-5.14.4 Achim Gratz
2015-02-11 20:01 ` perl-5.14.4 David Stacey
2015-02-13 18:36   ` perl-5.14.4 Achim Gratz

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=20150205084913.GN2635@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).