On 11/02/2016 05:20 PM, Andreas Tille wrote: > Warning in rgl.init(initValue, onlyNULL) : > RGL: unable to open X11 display > Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE > Error: segfault from C stack overflow
Hmm, was going to take a shot at debugging your segfault, but I simply can't reproduce this: apt-get source --download-only r-cran-treescape sbuild --arch=i386 -d unstable r-cran-treescape_1.10.18-1.dsc [...] Build Architecture: i386 Build-Space: 11748 Build-Time: 24 Distribution: unstable Host Architecture: i386 Install-Time: 76 Job: .../r-cran-treescape_1.10.18-1.dsc Machine Architecture: amd64 Package: r-cran-treescape Package-Time: 107 Source-Version: 1.10.18-1 Space: 11748 Status: successful Version: 1.10.18-1 sbuild --arch=armhf -d unstable r-cran-treescape_1.10.18-1.dsc [ ... wait a long time due to qemu-user emulation ... ] Build Architecture: armhf Build-Space: 11748 Build-Time: 322 Distribution: unstable Host Architecture: armhf Install-Time: 331 Job: .../r-cran-treescape_1.10.18-1.dsc Machine Architecture: amd64 Package: r-cran-treescape Package-Time: 681 Source-Version: 1.10.18-1 Space: 11748 Status: successful Version: 1.10.18-1 While my machine is amd64, sbuild does set a 32bit personality (so uname -m returns i686) - same as the buildd that failed in your case. The armhf chroot contains the qemu-arm-static binary in /usr/bin for emulation purposes, but is otherwise pristine. (But obviously using emulation is different than a buildd on native hardware.) The resulting packages contain binaries for the respective architectures. I can provide full build logs if you need them. Maybe ask for a give-back at debian-wb-t...@lists.debian.org to have the i386 and armhf buildds try the build again? As far as I can tell the build should succeed... Notable differences between buildd chroot and my freshly created one (in the i386 case): buildd: gcc 6.2.1-5, binutils 2.27.51.20161201-1 my system: gcc 6.2.1-6, binutils 2.27.51.20161212-1 Maybe this was a toolchain bug that was fixed recently? If so, maybe wait a couple of days (buildd chroots are updated twice a week IIRC) and then ask for a give-back. Regards, Christian