#1125102 deal.ii: FTBFS on arm64: collect2: fatal error: ld terminated with signal 6 [Aborted] #1125102
- Package:
- src:deal.ii
- Source:
- src:deal.ii
- Submitter:
- Graham Inggs
- Date:
- 2026-11-19 15:15:02 UTC
- Severity:
- normal
deal.ii has a very bad track record for building on arm64 [1] I couldn't find a previous bug where help was requested from the arm porters, so here goes: when linking with ld.mold (as in 9.7.1-3~exp1) I see: collect2: fatal error: ld terminated with signal 6 [Aborted] when linking with ld.bfd (as in 9.7.1-2) the build times out, but I have also seen: relocation truncated to fit: R_AARCH64_CALL26 against symbol `dealii::ExceptionBase::ExceptionBase()' defined in .text section in base/CMakeFiles/object_base_debug.dir/exceptions.cc.o To me, at least the first failure seems very similar to bug #1112274 in Trilinos [2]. Also, the loong64 porters proposed a patch in #1120656 [3] to 'Fix relocation R_LARCH_B26 overflow on loong64'. Any help would be appreciated. Thanks in advance Graham [1] https://buildd.debian.org/status/logs.php?pkg=deal.ii&arch=arm64 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112274 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120656
Hey Graham, It seems that building without outline atomics is a possible workaround, so on arm64 you could try: export DEB_CXXFLAGS_MAINT_APPEND=-mno-outline-atomics The build times out for me, with an ld process maxing out one core for a long time, but at least I get no relocation failures!
Hi Emanuele Thanks! Which version did you try to build? Version 9.7.1-3~exp1 in experimental should use the mold linker, and might avoid the time out. Regards Graham
Ah yes I built the version in unstable (9.7.1-2). 9.7.1-3~exp1 fails with the same error as trilinos bug #1112274: /usr/lib/aarld.mold: ./src/thunks.cc:217: void mold::OutputSection<E>::create_range_extension_thunks(mold::Context<E>&) [with E = mold::ARM64LE]: Assertion `thunk.size() < max_thunk_size' failed. I tried both with and without adding -ffunction-sections to LDFLAGS, same error.
That's a pity. Thanks for trying. For what it's worth, deal.ii builds in Ubuntu on arm64 with the mold linker but fails with ld.bfd.
Hi, Update as of November 2026! Graham and I were wondering why the package fails to build in unstable and yet builds successfully in Ubuntu tenacious. The important difference turned out being -Wl,-Bsymbolic-functions, which Ubuntu uses by default. With ld.bfd the package fails building in unstable due to inefficiencies in the way ld.bfd deals with the 843419 Cortex erratum. It seems that -Wl,-Bsymbolic-functions is an effective workaround for that problem. So the options to fix the arm64 FTBFS in unstable are either: 1) linking with ld.bfd and -Wl,-Bsymbolic-functions 2) linking with ld.lld and leaving link flags unchanged (see #1154021)
We believe that the bug you reported is fixed in the latest version of deal.ii, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1125102@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs <ginggs@debian.org> (supplier of updated deal.ii package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Thu, 19 Nov 2026 10:56:52 +0000 Source: deal.ii Built-For-Profiles: noudeb Architecture: source Version: 9.8.0-5~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org> Changed-By: Graham Inggs <ginggs@debian.org> Closes: 1125102 Changes: deal.ii (9.8.0-5~exp1) experimental; urgency=medium . * Link with -Bsymbolic-functions everywhere (Closes: #1125102) Checksums-Sha1: f92a85fe37b0c05e743a7377fe3eedc685e39c1a 2813 deal.ii_9.8.0-5~exp1.dsc 445f39d00ce28546a3e40a8c9a42f89fa01925c0 18736 deal.ii_9.8.0-5~exp1.debian.tar.xz Checksums-Sha256: 0852226f794f42db81763c9d9f0710f488546b802203832bf75f28ecd7856801 2813 deal.ii_9.8.0-5~exp1.dsc 55fa19f74aa90046c1b7bd0bd02f39633b66231ca1a8e0d7721a8bbece6eebab 18736 deal.ii_9.8.0-5~exp1.debian.tar.xz Files: 1628d7278b8076de954ff1ef974e977c 2813 libs - deal.ii_9.8.0-5~exp1.dsc 4a26fb89d87fc667da357710a2d5923b 18736 libs - deal.ii_9.8.0-5~exp1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmr+10kACgkQr8/sjmac 4cKMbhAAjTUqyopmFmwk7cyatUL01Zo6tJb5wC/9CuYh8np6vPSAhXZStJmFBMdu +rw4yZALvjeC8z9/MhS1LaqdtzyVH7ld5M2wIVHcdsCFW1+aujw/QRuDNc60Lty4 GCa+guLVW0FxKXFj9WziquTP35oL3Spm90IPEN/szwSOACQXPhAWpFgbRffb7mDg V2frfjNWD2h2pgjBI4LQnXUrO+yNJ3ySrH6A0c+jsM4z1rY0MV3QvdhQzWGi022y cqyFfxZ3iz6BJERZp5XU3ONaT8ETimDCxyn4rXfJsHqF0sEbgzpYni5zeNWWBL12 o/QEhLzRQa8ladD+CqGOl9/kfTlWxLeUfy8YHCm5jp1xUcJgPcOk9pVtxbO3UVDY ao7hkcTGSca1tQYYoEVl+Y3dHeADNMBsC38lLzlVCMHvGVN3WLIeup0FcLJJWa13 H/EeZvwuYm1MCN+JsT74akugVL992gGHX8ydEkFXn+gF0SPyxZv85pyTrgr6WYdQ RUwu5yTPGhvL5+DBAw7gOYqRDbSvoxeATU5/DrruPc9AJ4YcwP9/X5Pamqe6qYt3 5fdSqXUBLE5y/3qQ5h/4vnzJ4NmZbeqHISPA5sMwRObs0Jjrt8gbeQ4yMS4lMsD/ d99BW1G7XbCwX2WsEhPwL5ZaEZALrpZxiQnHohaDjtKsA37PEBE= =XvJe -----END PGP SIGNATURE-----
Bah, I should not have closed this bug in my upload to experimental. Although the build already succeeded on arm64, let's wait for the other architectures. I like this option since we are already doing it for ppc64el since #1022973, and it is the default in Ubuntu for all architectures. For what it's worth, linking with ld.lld fails Ubuntu 26.04.