Source: julia Version: 1.5.3+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramacher@debian.org julia FTBFS on armhf: | cd /<<PKGBUILDDIR>>/base && if ! JULIA_BINDIR=/<<PKGBUILDDIR>>/usr/bin /<<PKGBUILDDIR>>/usr/bin/julia -O3 -C "armv7-a;armv7-a,neon;armv7-a,neon,vfp4" --output-o /<<PKGBUILDDIR>>/usr/lib/arm-linux-gnueabihf/julia/sys-o.a.tmp --startup-file=no --warn-overwrite=yes --sysimage /<<PKGBUILDDIR>>/usr/lib/arm-linux-gnueabihf/julia/sys.ji /<<PKGBUILDDIR>>/contrib/generate_precompile.jl 1; then echo '*** This error is usually fixed by running `make clean`. If the error persists, try `make cleanall`. ***'; false; fi | Generating precompile statements... 1872 generated in 324.657783 seconds (overhead 214.562048 seconds) | LLVM ERROR: out of memory | | signal (6): Aborted | in expression starting at none:0 | unknown function (ip: 0xb6b99c66) | gsignal at /lib/arm-linux-gnueabihf/libc.so.6 (unknown line) | abort at /lib/arm-linux-gnueabihf/libc.so.6 (unknown line) | Allocations: 155132761 (Pool: 155112663; Big: 20098); GC: 199 | Aborted | *** This error is usually fixed by running `make clean`. If the error persists, try `make cleanall`. *** | make[3]: *** [sysimage.mk:86: /<<PKGBUILDDIR>>/usr/lib/arm-linux-gnueabihf/julia/sys-o.a] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=julia&arch=armhf&ver=1.5.3%2Bdfsg-2%2Bb1&stamp=1607175619&raw=0 Cheers
Hi, thanks for the report, but that is really a porter/builder box problem: Seems the machine couldn't deal with the required amount ( which is considerable from my experience). I don't know what **we** can do here ... Best Norbert
One could try the usual approaches of reducing the debug symbols to -g1 or optimization to -O1. And it's not usually the case the this is an actual out of memory issue, but a process that requires more than the mappable amount of memory. Cheers
For the record, the amount on armhf is 3 GB. The weird thing about julia is that it built for me on the porterbox, and after that it also built in the 4th attempt (sic) on the buildd. cu Adrian
Hi Adrian, thanks for your report, that is very much appreciated! Mumumu, that is really really difficult. I guess some OOM killer due to other programs running at the same time. My guess is that every new julia version will only increase the pressure on the memory, so I am not all to positive about further support for armhf. All the best Norbert
Hi Norbert, there is nothing else running on the buildds, and the build failure was not an OOM kill. What I actually wanted to try on the porterbox was whether changing the failing "julia -O3" command would help. If I had been able to reproduce this problem, I wanted to check whether changing this to a lower optimization level on armhf would help. armhf likely has some userbase for Julia due to the raspbian, so keeping it available a bit longer there has value for users. cu Adrian
Dear submitter, as the package julia has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1011382 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)