Re: Bug#861281: rnahybrid: FTBFS on armel
On Tue, Sep 26, 2017 at 12:21:20PM -0400, Lennart Sorensen wrote:
> Here is a patch that removes all the warnings I see. Maybe that will
> help. I don't have an armel to test on.
>
> Most of the warnings are due to missing #include in a lot of places.
The failure in build may in fact just be because the build machine is
too slow.
The file it timed out on takes almost 1 minute to compile on a 2GHz x86.
That one file is about 90% of the total build time of the package.
How long does it take on the armel build box and how much memory does
it use while doing it? My x86 hit close to 150MB for the cc1 process
on that file. Memory bandwidth could possible affect the compile time
on that file a lot.
So perhaps the real answer is that the timeout on this package needs
to be increased, or it should only be built on the fastest of the
armel build machines.
The energy.c file is over 12000 lines long and contains massive nested
loops that the optimizer is probably trying to do nice things to.
I highly doubt there is a bug in gcc, or any infinite loop. Just gcc
is trying harder to optimize than it used to, and the timeout is too low.
I would be very surprised if a manual attempt to build it on armel would
not succeed, although you are probably looking at 4 hours to do it.
--
Len Sorensen
Reply to: