#1091266 darkradiant: FTBFS on armhf: make: *** [debian/rules:9: binary] Error 25

Package:
src:darkradiant
Source:
src:darkradiant
Submitter:
Lucas Nussbaum
Date:
2025-08-17 18:14:44 UTC
Severity:
normal
Tags:
#1091266#5
Date:
2024-12-23 17:38:37 UTC
From:
To:
Hi,

During a rebuild of all packages in sid, this package failed to build
on armhf.

This package currently has binary packages on armhf, so this is a regression.
Also, there are no known issues on amd64 or arm64 according to recent (a couple
days ago) rebuilds.

The rebuild was done using an armhf chroot on an AWS "m6g" instance (Graviton2
CPU).

Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2024/12/23/darkradiant_3.9.0-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241223;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241223&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
#1091266#10
Date:
2024-12-23 18:02:50 UTC
From:
To:
On Mon, Dec 23, 2024 at 06:38:37PM +0100, Lucas Nussbaum wrote:

Hi Lucas,

did your VM run out of memory?
#1091266#15
Date:
2024-12-23 18:02:50 UTC
From:
To:
On Mon, Dec 23, 2024 at 06:38:37PM +0100, Lucas Nussbaum wrote:

Hi Lucas,

did your VM run out of memory?
#1091266#20
Date:
2024-12-23 19:38:02 UTC
From:
To:
retried alone on the VM). And this is the only package where I detected
an issue related to a lack of memory.

Does this package need a particularly high amount of memory to build?

Lucas
#1091266#25
Date:
2025-01-01 10:59:07 UTC
From:
To:
On Mon, 23 Dec 2024 20:38:02 +0100 Lucas Nussbaum <lucas@debian.org> wrote:
gnueabihf/darkradiant/modules/libradiantcore.so: Could not allocate
memory: Cannot allocate memory
was
detected


I've enable the armhf builder on salsa, and there the package builds
fine. So I will downgrade this bug to non RC and the next upload will
show if your observed behaviour also happens on the buildds.

(I don't think darkradiant need particular high RAM amounts, if there is
a problem, this might be a problem with dwz.)
#1091266#34
Date:
2025-01-01 12:46:12 UTC
From:
To:
If it becomes necessary, overriding dh_dwz to do nothing (on armhf,
or in general) might be a suitable workaround.

    smcv