poudriere-devel -w tar files are sometimes empty for failure (no contained files): an amd64->armv7 cross build example
Mark Millard
marklmi at yahoo.com
Thu Dec 20 20:59:39 UTC 2018
FYI: This is based on FreeBSD head -r341836 and ports head -r484783 and was an
amd64->armv7 cross build of the port(s) using amd64-native tools.
For the following failure:
. . .
-- Build files have been written to: /wrkdirs/usr/ports/multimedia/gstreamer1-qt/work-qt5/.build
===========================================================================
=======================<phase: build >============================
===> Building for gstreamer1-qt5-1.2.0_14
=>> Killing runaway build after 21600 seconds with no output
=>> Cleaning up wrkdir
===> Cleaning for gstreamer1-qt5-1.2.0_14
Killed
build of multimedia/gstreamer1-qt at qt5 | gstreamer1-qt5-1.2.0_14 ended at Thu Dec 20 07:20:09 PST 2018
build time: 06:04:03
!!! build failure encountered !!!
The tar file ends up as (note the small size):
# ls -lTdt /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailArmV7-default/default/gstreamer1-qt5-1.2.0_14.tar
-rw-r--r-- 1 root wheel 1024 Dec 20 07:20:08 2018 /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailArmV7-default/default/gstreamer1-qt5-1.2.0_14.tar
For which:
# tar -tvf /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailArmV7-default/default/gstreamer1-qt5-1.2.0_14.tar | more
#
While the above is from a more general build that got there via dependencies,
this repeats for:
# poudriere bulk -jFBSDFSSDjailArmV7 -w multimedia/gstreamer1-qt at qt5
It leaves me wondering if the @FLAVOR use messes up the production of the tar (wrong path used?).
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
More information about the freebsd-ports
mailing list