From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27750@debbugs.gnu.org
Subject: bug#27750: i686-linux perl not reproducible
Date: Tue, 18 Jul 2017 13:54:08 +0200 [thread overview]
Message-ID: <87y3rmyn8f.fsf@gnu.org> (raw)
In-Reply-To: <20170718103034.64cd6e0c@scratchpost.org> (Danny Milosavljevic's message of "Tue, 18 Jul 2017 10:30:34 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> $ diff -ru /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0 /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0-check
> diff -ru /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0/lib/perl5/5.24.0/i686-linux-thread-multi/Config_heavy.pl /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0-check/lib/perl5/5.24.0/i686-linux-thread-multi/Config_heavy.pl
> --- /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0/lib/perl5/5.24.0/i686-linux-thread-multi/Config_heavy.pl 1970-01-01 01:00:01.000000000 +0100
> +++ /gnu/store/y5mrlqyphzr5iqf51d7ks9ai3arhhnl2-perl-5.24.0-check/lib/perl5/5.24.0/i686-linux-thread-multi/Config_heavy.pl 1970-01-01 01:00:01.000000000 +0100
> @@ -1041,7 +1041,7 @@
> longdblinfbytes='0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0xff, 0x7f, 0x00, 0x00'
> longdblkind='3'
> longdblmantbits='64'
> -longdblnanbytes='0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xc0, 0xff, 0xff, 0xd1, 0xf7'
> +longdblnanbytes='0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xc0, 0xff, 0xff, 0xce, 0xf7'
Could you check if that is still the case on ‘core-updates’, which has
Perl 5.26.0?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-07-18 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 8:30 bug#27750: i686-linux perl not reproducible Danny Milosavljevic
2017-07-18 11:54 ` Ludovic Courtès [this message]
2019-02-04 12:27 ` Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3rmyn8f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27750@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).