bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2

[Vagrant Cascadian <vagrant@debian.org>]

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

On 2021-05-02, Vagrant Cascadian wrote:
> On 2021-05-02, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>> On 2021-04-30, Vagrant Cascadian wrote:
>>>> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>>>>
>>>>   [ 70%] GUILEC   gnu/packages/direct-connect.go
>>>>   [ 70%] GUILEC   gnu/packages/disk.go
>>>>   GC Warning: Failed to expand heap by 8388608 bytes
>>>>   GC Warning: Failed to expand heap by 8388608 bytes
>>>>   ...
>>>>   GC Warning: Failed to expand heap by 8388608 bytes
>>>>   GC Warning: Failed to expand heap by 8388608 bytes
>>>>   Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
>>>>   make[3]: *** [Makefile:6871: make-go] Aborted
>>>>
>>>>
>>>> Debian is still using guile-2.2, so I'm guessing this is not a
>>>> particularly well tested codepath anymore...
>>>
>>> But strangely enough, it built fine on debian's build machines on all
>>> supported architectures:
>>>
>>>   https://buildd.debian.org/status/package.php?p=guix&suite=experimental
>>
>> Guile 3.0’s compiler with ‘-O1’ (which is what we use for package files)
>> uses much less memory than 2.2¹.  The amount of memory may also be a
>> function of the number of threads used (‘-j’).  So it could be that the
>> build failed on a machine with less memory or more cores.
>
> The machine it failed on had 32 cores and 140GB of ram... but will
> experiment with reducing parallelism on that machine and see if that
> helps.

I just realized that the Debian guix packages are built with parallelism
disabled for reproducible builds, so that seems unlikely to be the
issue... it might just be an issue with guile-2.2 on Debian...


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]