FTBFS in quantal
Bug #1029458 reported by
Michael Terry
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GCC-XML |
Fix Released
|
Unknown
|
|||
| wrapitk-python (Debian) |
Fix Released
|
Unknown
|
|||
| wrapitk-python (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
wrapitk-python FTBFS on amd64 in quantal.
The first problem is due to upstream gccxml bug http://
The workaround in that bug (define __STRICT_ANSI__) works to get around the current FTBFS. To define __STRICT_ANSI__ so it is picked up by gccxml, add -DCONFIG_
Unfortunately, we then later fail with "c++: internal compiler error: Killed (program cc1plus)" at about 40% of the build. I don't know if that's related to the strict ANSI flag or is an unrelated problem.
| Changed in gccxml: | |
| status: | Unknown → Fix Released |
| Changed in wrapitk-python (Debian): | |
| status: | Unknown → Fix Released |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in wrapitk-python (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This was fixed by merging these two changes from Debian:
gccxml (0.9.0+
* Fix parsing of <limits> under GCC 4.7.1. Closes: #675181
+ debian/
-- Mathieu Malaterre <email address hidden> Thu, 26 Jul 2012 16:53:41 +0200
insighttoolkit (3.20.1+
* Fix gcc 4.7.1 build failure of wrapitk-python. Closes: #667417
+ debian/patches/bug667417.patch
-- Mathieu Malaterre <email address hidden> Thu, 26 Jul 2012 17:38:47 +0200
I confirmed success in the test rebuild archive.