FS#40457 - [lib32-libffi] check fails

Attached to Project: Community Packages
Opened by Joel Teichroeb (klusark) - Tuesday, 20 May 2014, 02:57 GMT
Last edited by Laurent Carlier (lordheavy) - Thursday, 26 June 2014, 09:15 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

=== libffi tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../testsuite/config/default.exp as tool-and-target-specific interface file.
Running ../../testsuite/libffi.call/call.exp ...
FAIL: libffi.call/float2.c -O0 -W -Wall (test for excess errors)
Running ../../testsuite/libffi.special/special.exp ...

=== libffi Summary ===

# of expected passes 1818
# of unexpected failures 1
# of unsupported tests 55
Makefile:356: recipe for target 'check-DEJAGNU' failed
make[3]: *** [check-DEJAGNU] Error 1
make[3]: Leaving directory '/build/lib32-libffi/src/libffi-3.0.13/x86_64-unknown-linux-gnu/testsuite'
Makefile:431: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/build/lib32-libffi/src/libffi-3.0.13/x86_64-unknown-linux-gnu/testsuite'
Makefile:1363: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/lib32-libffi/src/libffi-3.0.13/x86_64-unknown-linux-gnu'
Makefile:2731: recipe for target 'check' failed
make: *** [check] Error 2
==> ERROR: A failure occurred in check().
Aborting...



Steps to reproduce:
sudo multilib-build
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Thursday, 26 June 2014, 09:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  lib32-libffi-3.1-1
Comment by Doug Newgard (Scimmia) - Tuesday, 20 May 2014, 04:36 GMT
Not multilib specific, pulling in the maintainer of the regular package as well.
Comment by Bartłomiej Piotrowski (Barthalion) - Thursday, 26 June 2014, 09:02 GMT
It's fixed in core/libffi 3.1-1, nothing to do here for me.

Loading...