* Sébastien Noel <sebast...@twolife.be> [250108 16:37]: > > [...] > > > > Segmentation fault (core dumped) > > > > > > that's new to me. > > > I never tried to build it on aarch64, only amd64 :-/ > > > > This might very well be a compiler bug on aarch64, who knows. > > I'm totally out of my comfort zone now ^^
I briefly tried to look at the core dump, but gdb is not giving me much: ch@sbuild:/build/reproducible-path/serious-engine-0~git20230724+dfsg/Sources$ gdb --core core.344 GNU gdb (Debian 15.2-1+b1) 15.2 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". [New LWP 344] Core was generated by `/build/reproducible-path/serious-engine-0~git20230724+dfsg/build_tfe/Ecc/ecc En'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x006fffffb92a23f8 in ?? () (gdb) thread apply all bt full Thread 1 (LWP 344): #0 0x006fffffb92a23f8 in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) quit ch@sbuild:/build/reproducible-path/serious-engine-0~git20230724+dfsg/Sources$ > > > So, I suppose i have to search for an old rpi3 somewhere at home and > > > get > > > back to work... > > > > Can't promise to find an amd64 box that I trust enough to build > > something for NEW anytime soon. If you can get it to build on > > aarch64 that would be awesome. > > I quickly rent an Ampere A1 (arm64) based VM in the cloud; > installed bookworm as the OS, installed sbuild from bookworm-backports; > and no problem to build the packages in an brand new arm64 unstable > chroot... > I'm lost. > > What kind of hardware are you using ? I'm building in sbuild (from git, but basically 0.88.1) in an unstable VM on top of an M3 cpu. Kernel is: Linux 6.12.8-arm64 #1 SMP Debian 6.12.8-1 (2025-01-02) aarch64 GNU/Linux So, interesting problem! I'll try later today on an rk3588 platform. Chris
