Re: Possibility of patching 2.0.5 for armhf support

[ludo@gnu.org (Ludovic Courtès)]

Rob Browning <rlb@defaultvalue.org> skribis:

> I've had a request for armhf support in wheezy (which has 2.0.5), so I
> thought I'd ask if you might know offhand what fixed the armhf build in
> more recent versions (assuming it was a code change and not something
> else like the build toolchain).
>
> For example, 2.0.11 works fine there, but 2.0.5 dies like this:
>
>   https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=armhf&ver=2.0.5%2B1-3&stamp=1332497200
>
> (...segmentation faults in 3 of the tests.)

Namely:

--8<---------------cut here---------------start------------->8---
/bin/bash: line 5: 16859 Segmentation fault      srcdir="." builddir="." CHARSETALIASDIR="/build/buildd-guile-2.0_2.0.5+1-3-armhf-r0xLJm/guile-2.0-2.0.5+1/lib" GUILE_AUTO_COMPILE=0 "../../meta/uninstalled-env" ${dir}$tst
FAIL: test-with-guile-module
PASS: test-scm-with-guile
/bin/bash: line 5: 16924 Segmentation fault      srcdir="." builddir="." CHARSETALIASDIR="/build/buildd-guile-2.0_2.0.5+1-3-armhf-r0xLJm/guile-2.0-2.0.5+1/lib" GUILE_AUTO_COMPILE=0 "../../meta/uninstalled-env" ${dir}$tst
FAIL: test-scm-spawn-thread
/bin/bash: line 5: 16959 Segmentation fault      srcdir="." builddir="." CHARSETALIASDIR="/build/buildd-guile-2.0_2.0.5+1-3-armhf-r0xLJm/guile-2.0-2.0.5+1/lib" GUILE_AUTO_COMPILE=0 "../../meta/uninstalled-env" ${dir}$tst
FAIL: test-pthread-create
SKIP: test-pthread-create-secondary
--8<---------------cut here---------------end--------------->8---

I suspect the main difference is the libgc version, no?  That
test-pthread-create-secondary was skipped indicate that
libgc < 7.2alpha5 was being used here, which may explain the
other problems.

That said, there have been many changes both in Guile and in libgc over
the last 2.5 years.

Ludo’.