lazbuild appears to stall when building on armel and armhf
Original Reporter info from Mantis: ginggs
-
Reporter name: Graham Inggs
Original Reporter info from Mantis: ginggs
- Reporter name: Graham Inggs
Description:
Since lazarus 1.4.0 appeared in the Debian unstable distribution, builds on armel and armhf have been failing, appearing to stall.
Full build logs can be viewed [1][2][3] by clicking on the Build-Attempted links for a particular architecture.
[1] https://buildd.debian.org/status/package.php?p=doublecmd&suite=unstable
[2] https://buildd.debian.org/status/package.php?p=easymp3gain&suite=unstable
[3] https://buildd.debian.org/status/package.php?p=cqrlog&suite=unstable
Steps to reproduce:
I chose a simpler project [1] and attempted to build it on real ARM hardware (NVIDIA Jetson TK1). Instead of building the Debian package, I simply ran:
lazbuild source/ddrescueview.lpi --bm="GNU/Linux Release"
The build was successful with lazarus 1.2.4 and 1.2.6, but appeared to stall with lazarus 1.4.0 and 1.4.2. In all cases, fpc 2.6.4 as it is in Debian was used. I attach build logs of the 1.2.6, 1.4.0 and 1.4.2 builds.
I noticed that the failed build logs were 4096 bytes in size and, as can be seen in the logs from the Debian buildds, the last line of the log is truncated, e.g.
TExternalTool.DoExecute Title="Compile Project, Mode: GNU/Linux Release, Target: ddrescueview" Process.CurrentDirectory="/srv/ddrescueview/source/" Executable="/usr/bin/fpc" Params:
-B
-Tlinux
-MObjFPC
-Schi
-CX
-O3
-Xs
-XX
-k-z
-krelro
-k--as-needed
-l
-vewnhibq
-Fl/opt/gnome/lib
-Fu/usr/lib/lazarus/1.4.2/lcl/units/arm-linux/gtk2
-Fu/usr/lib/lazar
After hitting ctrl-c, I noticed that the build had actually completed successfully and there was a working 'ddrescueview' executable.
[1] http://ddrescueview.sourceforge.net/
Mantis conversion info:
- Mantis ID: 28448
- OS: Debian
- OS Build: unstable
- Platform: ARM
- Version: 1.4
- Fixed in revision: r64005 (#ad65618c)
- Monitored by: » paul.gevers (Paul Gevers), » ginggs (Graham Inggs)