building m4 in poudriere cross-build
Vick Khera
vivek at khera.org
Wed Dec 14 14:42:22 UTC 2016
I have a poudriere cross-building configuration set up on a Xeon running
FreebSD 11.0. The jail was set up with the "-x" option to use the native
cross-build tools. This has worked really well for a while, but today I am
trying to update the packages for my raspberry pi 2, and poudriere just
kind of sits there in the configure step when building m4 (as a dependency
trying to build subversion). I haven't built this set of packages in over a
month.
The logs show this:
checking for dirent.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for working C stack overflow detection... make: Working in:
/usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
make: Working in: /usr/ports/devel/m4
The build machine is: FreeBSD 11.0-RELEASE-p5/amd64 with Poudriere 3.1.14
The build jail target is 11.0-RELEASE-p5/armv6 freshly updated.
I let this run for over 18 hours, and it just kept repeating that last
line. Has anyone had success with this set up recently? Maybe the
qemu-arm-static is not working right now?
More information about the freebsd-arm
mailing list