Hi, On 29/09/16 18:17, Matthias Klose wrote: > Control: tags -1 + help > > Please find out why libgo isn't configured to use libffi. It looks like the necessary support for go closures on mips isn't implemented in the version of libffi in gcc 6. There appears to be a PR here which fixes it: https://github.com/libffi/libffi/pull/197 It's not in GCC's copy of libffi though. James > On 29.09.2016 12:30, Martín Ferrari wrote: >> Package: libgo9 >> Version: 6.2.0-4 >> Severity: normal >> >> Hi, >> >> Recently, I modified golang-goprotobuf to use gccgo in non-native go arches, >> and found that it FTBFS in mips/mipsel/mps64el due to this error: >> >> fatal error: libgo built without FFI does not support reflect.Call or runtime.SetFinalizer >> >> Here is one of the build logs: >> >> https://buildd.debian.org/status/fetch.php?pkg=golang-goprotobuf&arch=mips&ver=0.0~git20160815.0.7390af9-2&stamp=1474830436 >> >> I don't know if this is a mistake, or if there is a reason for this FFI support >> not being included in these arches, but without it, a big number of packages >> are BD-Uninstallable as they depend transitively on protobuf support. >> >> -- System Information: >> Debian Release: stretch/sid >> APT prefers unstable >> APT policy: (500, 'unstable'), (500, 'testing') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) >> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: sysvinit (via /sbin/init) >> >> Versions of packages libgo9 depends on: >> ii gcc-6-base 6.2.0-4 >> ii libc6 2.24-3 >> ii libgcc1 1:6.2.0-4 >> >> libgo9 recommends no packages. >> >> libgo9 suggests no packages. >> >> -- no debconf information >> >
Attachment:
signature.asc
Description: OpenPGP digital signature