As interesting as this is, can you take me, Peter Steffen and Matthias
Hoechsmann off this list?
Thanks, and good luck
Marc
On 27/09/17 16:30, "Lennart Sorensen" wrote:
On Tue, Sep 26, 2017 at 08:19:59PM +0100, Edmund Grimley Evans wrote:
> It's a possibility to bear in mind, definite
On Tue, Sep 26, 2017 at 08:19:59PM +0100, Edmund Grimley Evans wrote:
> It's a possibility to bear in mind, definitely, but the
> perhaps-infinite loop can be observed with a cross-compiler:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876825
I just tried doing the cross compile manually
> The failure in build may in fact just be because the build machine is
> too slow.
It's a possibility to bear in mind, definitely, but the
perhaps-infinite loop can be observed with a cross-compiler:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876825
(I will test with the compilers in uns
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 be
On Tue, Sep 26, 2017 at 05:48:40PM +0200, Andreas Tille wrote:
> Hi Lennart,
>
> thanks for your suggestions. I hereby will forward it upstream hoping
> for comments.
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 warni
Hi Lennart,
thanks for your suggestions. I hereby will forward it upstream hoping
for comments.
Kind regards
Andreas.
On Tue, Sep 26, 2017 at 11:10:04AM -0400, Lennart Sorensen wrote:
> On Tue, Sep 26, 2017 at 09:57:09AM +0100, Edmund Grimley Evans wrote:
> > The infinite loop is still th
On Tue, Sep 26, 2017 at 09:57:09AM +0100, Edmund Grimley Evans wrote:
> The infinite loop is still there with gcc-7. I've created bug #876825.
>
> Before you exclude armel, you could perhaps try doing something about
> this warning, which is given not just on armel and may or may not be
> related
The infinite loop is still there with gcc-7. I've created bug #876825.
Before you exclude armel, you could perhaps try doing something about
this warning, which is given not just on armel and may or may not be
related to the compiler going into an infinite loop:
energy.c:539:104: warning: iterati
Hi,
On Fri, Apr 28, 2017 at 11:45:43AM +0100, Edmund Grimley Evans wrote:
> There may be no demand for this package (rnahybrid) on armel, but the
> FTBFS might be caused by a bug in gcc-6, which would be worth
> reporting if someone can confirm it.
We have gcc-7 now. Would anybody volunteer to c
There may be no demand for this package (rnahybrid) on armel, but the
FTBFS might be caused by a bug in gcc-6, which would be worth
reporting if someone can confirm it.
On Thu, Apr 27, 2017 at 07:23:20AM +, Gianfranco Costamagna wrote:
> Hello,
>
> > rnahybrid FTBFS on armel:
>
>
> the warning above is somewhat important
> (too many nested loops), and this usually relates badly with
> high optimization levels
>...
The warning is about an off-by-one in the
Hi Gianfranco,
On Thu, Apr 27, 2017 at 07:23:20AM +, Gianfranco Costamagna wrote:
> > rnahybrid FTBFS on armel:
>
> the warning above is somewhat important
> (too many nested loops), and this usually relates badly with
> high optimization levels
>
> gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/includ
Hello,
> rnahybrid FTBFS on armel:
>
the warning above is somewhat important
(too many nested loops), and this usually relates badly with
high optimization levels
gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -g
-O0 -fdebug-prefix-map=/home/locutusofborg/rnahybr
tags 861281 help
thanks
Hi,
I admit I have no idea what the problem might be and the build log (see
below) does not enable me to spot the issue. Any help would be welcome
since otherwise the only solution I could imagine is to ask ftpmaster to
remove the armel port of this package.
Kind regards
14 matches
Mail list logo
