Re: glibc issue while build in epel

2014-09-08 Thread Denis Fateyev 
On Mon, Sep 8, 2014 at 4:59 PM, Petr Pisar  wrote:

>
> The failure on ppc64 is a permanent bug in Digest-Whirpool. See
> .
>
> -- PEtr
>

Thanks for clarifications. I will try to get more details from the
Digest-Whirlpool author to check if we could do something here.

-- 
wbr, Denis.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Re: glibc issue while build in epel

2014-09-08 Thread Petr Pisar 
On Sun, Sep 07, 2014 at 04:31:21AM +0600, Denis Fateyev wrote:
> I'm facing an issue while making arch-specific scratch builds in EPEL
> branches. They fail during test stage while they build just fine on my own
> machine(s) with the same arch.
> 
> Build log:
> ---
> t/clone...ok
> t/digest..*** glibc detected *** /usr/bin/perl: corrupted
> double-linked list: 0x00d4afa0 ***
> === Backtrace: =
> /lib64/libc.so.6[0x7f83973cc283]
> /lib64/libc.so.6(__libc_malloc+0x6e)[0x7f83973cddfe]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_safesysmalloc+0x3b)[0x7f839863801b]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_init+0x8d)[0x7f83985f945d]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_fetchmeth+0xaa)[0x7f83985f9b0a]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_fetchmeth_autoload+0x91)[0x7f83985fbb81]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_Gv_AMupdate+0x1f9)[0x7f83985fbe09]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_handler+0x5c)[0x7f83985fc0dc]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clear+0x13d)[0x7f839865346d]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_free+0x80)[0x7f8398653b50]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gp_free+0xad)[0x7f83985f8ead]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clear+0x561)[0x7f8398653891]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_free+0x80)[0x7f8398653b50]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so[0x7f83986510c5]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clean_objs+0x3a)[0x7f839865113a]
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(perl_destruct+0x11be)[0x7f83985f785e]
> /usr/bin/perl(main+0xb3)[0x401773]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x7f83973779f4]
> /usr/bin/perl[0x401609]
> ... and so on.
> ---
> More details here:
> https://kojipkgs.fedoraproject.org//work/tasks/8985/7538985/build.log
> 
> Failed builds:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=7538983 (EPEL 5)
> https://koji.fedoraproject.org/koji/taskinfo?taskID=7538987 (EPEL 6)
> https://koji.fedoraproject.org/koji/taskinfo?taskID=7538976 (EPEL 7)
> 
> Is it a temporary bug there?

The failure on ppc64 is a permanent bug in Digest-Whirpool. See
.

-- PEtr


pgp7wxt0F60cP.pgp
Description: PGP signature
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

glibc issue while build in epel

2014-09-06 Thread Denis Fateyev 
Hello there,

I'm facing an issue while making arch-specific scratch builds in EPEL
branches. They fail during test stage while they build just fine on my own
machine(s) with the same arch.

Build log:
---
t/clone...ok
t/digest..*** glibc detected *** /usr/bin/perl: corrupted
double-linked list: 0x00d4afa0 ***
=== Backtrace: =
/lib64/libc.so.6[0x7f83973cc283]
/lib64/libc.so.6(__libc_malloc+0x6e)[0x7f83973cddfe]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_safesysmalloc+0x3b)[0x7f839863801b]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_init+0x8d)[0x7f83985f945d]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_fetchmeth+0xaa)[0x7f83985f9b0a]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_fetchmeth_autoload+0x91)[0x7f83985fbb81]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_Gv_AMupdate+0x1f9)[0x7f83985fbe09]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gv_handler+0x5c)[0x7f83985fc0dc]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clear+0x13d)[0x7f839865346d]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_free+0x80)[0x7f8398653b50]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_gp_free+0xad)[0x7f83985f8ead]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clear+0x561)[0x7f8398653891]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_free+0x80)[0x7f8398653b50]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so[0x7f83986510c5]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_sv_clean_objs+0x3a)[0x7f839865113a]
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(perl_destruct+0x11be)[0x7f83985f785e]
/usr/bin/perl(main+0xb3)[0x401773]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x7f83973779f4]
/usr/bin/perl[0x401609]
... and so on.
---
More details here:
https://kojipkgs.fedoraproject.org//work/tasks/8985/7538985/build.log

Failed builds:
https://koji.fedoraproject.org/koji/taskinfo?taskID=7538983 (EPEL 5)
https://koji.fedoraproject.org/koji/taskinfo?taskID=7538987 (EPEL 6)
https://koji.fedoraproject.org/koji/taskinfo?taskID=7538976 (EPEL 7)

Is it a temporary bug there?

-- 
wbr, Denis.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel