These are failures that are probably due to problems in the gcc
toolchain. We should file a proper bug report against gcc-4.8, but I
lack the understanding that Yavor has to do it (as far as we understand
it, it is described in bug 1343945).
This failure is intermittent, rebuilding probably helps. We should
disable the testcases for now to work around this issue (also present on
amd64). But I don't think that makes sense as long as the ppc issue is
not solved yet.
On 25-07-14 09:46, Daniel Holbach wrote: /launchpadlibra rian.net/ 180535732/ buildlog_ ubuntu- utopic- ppc64el. gnustep- base_1. 24.6-2ubuntu1_ FAILEDTOBUILD. txt.gz /launchpadlibra rian.net/ 180535689/ buildlog_ ubuntu- utopic- powerpc. gnustep- base_1. 24.6-2ubuntu1_ FAILEDTOBUILD. txt.gz
> Build logs for the individual FTBFSes:
> - ppc64el: https:/
> - powerpc: https:/
These are failures that are probably due to problems in the gcc
toolchain. We should file a proper bug report against gcc-4.8, but I
lack the understanding that Yavor has to do it (as far as we understand
it, it is described in bug 1343945).
> - i386: https:/ /launchpadlibra rian.net/ 180539099/ buildlog_ ubuntu- utopic- i386.gnustep- base_1. 24.6-2ubuntu1_ FAILEDTOBUILD. txt.gz
This failure is intermittent, rebuilding probably helps. We should
disable the testcases for now to work around this issue (also present on
amd64). But I don't think that makes sense as long as the ppc issue is
not solved yet.
Paul