powerpc64 head -r352341 ports head -r512281 poudriere-devel based boost-libs-1.71.0 build failure: =>> Killing runaway build after 7200 seconds with no output
Mark Millard
marklmi at yahoo.com
Thu Sep 19 00:25:41 UTC 2019
[This is from a system-clang 8 based FreeBSD context for
powerpc64, not the usual gcc 4.2.1 based context.]
In attempting to update the ports I normally build, jumping
ahead from -r509171, I got the following:
. . .
...updated 1359 targets...
===========================================================================
=======================<phase: run-depends >============================
===========================================================================
=======================<phase: stage >============================
===> Staging for boost-libs-1.71.0
. . .
- pthread-supports-robust-mutexes : yes (cached)
- gcc visibility : yes (cached)
- long double support : yes (cached)
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
- libbacktrace builds : no (cached)
- addr2line builds : yes (cached)
- WinDbg builds : no (cached)
- WinDbgCached builds : no (cached)
- BOOST_COMP_GNUC >= 4.3.0 : no (cached)
=>> Killing runaway build after 7200 seconds with no output
- zlib : yes (cached)
- bzip2 : yes (cached)
- lzma : yes (cached)
- zstd : no (cached)
=>> Cleaning up wrkdir
===> Cleaning for boost-libs-1.71.0
Killed
build of devel/boost-libs | boost-libs-1.71.0 ended at Wed Sep 18 16:38:56 PDT 2019
build time: 04:39:04
!!! build failure encountered !!!
When I made another large jump a couple of days ago
to -r509171 (to match other contexts that I had), the
boost-libs build did not fail.
(The overall bulk run is still ongoing.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
More information about the freebsd-ppc
mailing list