Hi Christian, On Wed, Dec 14, 2016 at 12:32:24AM +0100, Christian Seiler wrote: > On 11/02/2016 05:20 PM, Andreas Tille wrote: > > Hmm, was going to take a shot at debugging your segfault, but I > simply can't reproduce this: > ... > architectures.
Unfortunately autobuilders keep on reproducing it. :-( > 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. I have uploaded a package where I fixed the xvfb issue and did a source only upload to make sure also amd64 will be autobuilt. While amd64 is fine (also regarding the xserver issue - thanks to Gregor for the hints) the i386 build log[1] shows the ** inst ** preparing package for lazy loading Creating a generic function for 'toJSON' from package 'jsonlite' in package 'googleVis' Error: segfault from C stack overflow * removing '/«PKGBUILDDIR»/debian/r-cran-treescape/usr/lib/R/site-library/treescape' again even if the log also has gcc-6-base i386 6.2.1-6 and binutils i386 2.27.51.20161212-1 - so the toolchain on autobuilder is the same as it worked for you. There might be a difference between a qemu emulation and real hardware, thought. Kind regards and thanks for checking anyway Andreas. [1] https://buildd.debian.org/status/fetch.php?pkg=r-cran-treescape&arch=i386&ver=1.10.18-2&stamp=1481697760 -- http://fam-tille.de