binutils-mingw-w64 test failure on ppc64el

Bug #1669728 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
binutils-mingw-w64 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

ppc64el only, tests succeed on all other architectures.
see https://launchpad.net/ubuntu/+source/binutils-mingw-w64/7.4build1/+build/12079821

make[4]: Entering directory '/<<PKGBUILDDIR>>/build/i686-w64-mingw32/libiberty'
make[5]: Entering directory '/<<PKGBUILDDIR>>/build/i686-w64-mingw32/libiberty/testsuite'
gcc -DHAVE_CONFIG_H -g -O3 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -I.. -I../../../../upstream/libiberty/testsuite/../../include -o test-demangle \
 ../../../../upstream/libiberty/testsuite/test-demangle.c ../libiberty.a
./test-demangle < ../../../../upstream/libiberty/testsuite/demangle-expected
/bin/bash: line 1: 2299 Segmentation fault (core dumped) ./test-demangle < ../../../../upstream/libiberty/testsuite/demangle-expected
Makefile:53: recipe for target 'check-cplus-dem' failed
make[5]: *** [check-cplus-dem] Error 139
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/i686-w64-mingw32/libiberty/testsuite'
Makefile:500: recipe for target 'check-subdir' failed
make[4]: *** [check-subdir] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/i686-w64-mingw32/libiberty'
Makefile:8100: recipe for target 'check-libiberty' failed
make[3]: *** [check-libiberty] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/i686-w64-mingw32'
Makefile:2202: recipe for target 'do-check' failed
make[2]: *** [do-check] Error 2

Matthias Klose (doko)
Changed in binutils-mingw-w64 (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Matthias Klose (doko) wrote :

can be worked around building with -O2 instead of -O3

Stephen Kitt (steve-sk2)
Changed in binutils-mingw-w64 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.