shibboleth-sp2 version 2.3.1+dfsg-5ubuntu1 failed to build on armel

Bug #745880 reported by Steve Langasek
This bug report is a duplicate of:  Bug #736661: armel FTBFS due to compiler ICE. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shibboleth-sp2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

shibboleth-sp2 version 2.3.1+dfsg-5ubuntu1 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/shibboleth-sp2/2.3.1+dfsg-5ubuntu1/+buildjob/2239993

Direct link to the build log: https://launchpad.net/ubuntu/+source/shibboleth-sp2/2.3.1+dfsg-5ubuntu1/+buildjob/2239993/+files/buildlog_ubuntu-natty-armel.shibboleth-sp2_2.3.1%2Bdfsg-5ubuntu1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1832 lines into the build log:

impl/XMLServiceProvider.cpp: In member function 'std::pair<bool, bool><unnamed>::XMLConfig::_ZTv0_n24_NK12_GLOBAL__N_19XMLConfig7getBoolEPKcS2_(const char*, const char*) const':
impl/XMLServiceProvider.cpp:311:25: internal compiler error: in expand_expr_real_1, at expr.c:8454
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions.
make[4]: *** [XMLServiceProvider.lo] Error 1
make[4]: Leaving directory `/build/buildd/shibboleth-sp2-2.3.1+dfsg/shibsp'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/build/buildd/shibboleth-sp2-2.3.1+dfsg/shibsp'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/shibboleth-sp2-2.3.1+dfsg'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/shibboleth-sp2-2.3.1+dfsg'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110323-0359
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/shibboleth-sp2-2.3.1+dfsg

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.