On Jan 10, 2020, at 15:52, Michael Käppler <[email protected]> wrote:
>
> Hi Dan,
> GUB still fails to build lilypond in offset.cc. See attached log.
> Anyone out here using LilyDev1, who can build current master through GUB?
> Now testing, if I can build release/unstable.
>
> What I would like to understand is why this issue does arise only within
> GUB and
> not for a normal build.
> Could you give me a hint?
/home/dev/gub/target/linux-64/src/lilypond-localhost--lilypond.git-issue5658/flower/offset.cc:41:25:
note: candidates are:
In file included from
/home/dev/gub/target/linux-64/root/usr/cross/lib/gcc/x86_64-linux/4.9.4/include-fixed/features.h:317:0,
from
/home/dev/gub/target/linux-64/root/usr/include/assert.h:36,
from
/home/dev/gub/target/linux-64/root/usr/cross/x86_64-linux/include/c++/4.9.4/cassert:43,
from
/home/dev/gub/target/linux-64/src/lilypond-localhost--lilypond.git-issue5658/flower/include/axis.hh:23,
from
/home/dev/gub/target/linux-64/src/lilypond-localhost--lilypond.git-issue5658/flower/include/offset.hh:23,
from
/home/dev/gub/target/linux-64/src/lilypond-localhost--lilypond.git-issue5658/flower/offset.cc:20:
/home/dev/gub/target/linux-64/root/usr/include/bits/mathcalls.h:202:1: note:
int isinf(double)
It seems that this implementation of the standard library declares ::isinf when
<cassert> is included. The three solutions I can think of are (a) finish issue
4550, (b) require a version of the library that does not do this, or (c)
investigate whether it is possible to avoid including <cassert> or any other
header that triggers the same problem.
I've been working on issue 4550.
—
Dan
