Control: notfixed -1 8.0-5
Control: reopen -1
Control: severity -1 minor
You're right. I knew that we split the docbuild away (I did that, even) but I
thought that the tests passing indicated that the bug was fixed.
However I tried a full build on another ppc64el machine just now, and it seems
Just for the record, this was fixed by building the documentation only in the
indep build. Building the documentation on these architectures will probably
still fail, but I agree that the bug can be closed.
Best, Tobias
--
debian-science-maintainers mailing list
debian-science-maintainers@list
Aaron M. Ucko:
> Ximin Luo writes:
>
>> The error occurs right when the docbuild starts, before it actually
>> attempts to build anything, so my guess is that it would also occur
>> when starting the normal Sage CLI. So I don't think we should skip the
>> docbuild and release the build products a
Ximin Luo writes:
> The error occurs right when the docbuild starts, before it actually
> attempts to build anything, so my guess is that it would also occur
> when starting the normal Sage CLI. So I don't think we should skip the
> docbuild and release the build products as-is.
Thanks for clari
Hi, this does not look like a simple out-of-memory, but a bug involving
libgomp. A quick Google search of the error message shows that there was some
issue involving libgomp, dlopen and GCC years ago, but it's unclear if this is
issue here is related.
The error occurs right when the docbuild st
Source: sagemath
Version: 7.4-3
Severity: important
Justification: fails to build from source
The automatic builds of sagemath for arm64 and ppc64el both ran out of
memory when trying to build documentation:
[dochtml] ImportError: /usr/lib/«ARCH»/libgomp.so.1: cannot allocate memory
in static
