FreeBSD head -r341836 amd64->aarch64 cross-build of -r484783 ports via poudriere: devel/qt5-testlib hung-up during "Checking for POSIX monotonic clock"
Mark Millard
marklmi at yahoo.com
Wed Dec 19 22:18:54 UTC 2018
[Looks like a race or some such for devel/qt5-testlib: retry of poudreire-devel
did not hang. The other hang-up seems to be repeating and I give some details.]
On 2018-Dec-19, at 12:20, Mark Millard <marklmi at yahoo.com> wrote:
> FYI: Based on FreeBSD head -r341836 (host and target) and ports -r484783 . This
> was a rebuild based on going from perl5.26 to perl5.28 without updating the ports
> tree and from system clang 6 for the prior FreeBSD-head context used to clang 7
> this time. (I'm not attributing causes here.) poudriere was using amd64-native
> tools for speeding up the cross-build.
>
> # grep -r =perl5= /etc/ ~/src.configs/ /usr/local/etc/
> /etc/make.conf:DEFAULT_VERSIONS+=perl5=5.28 gcc=8
> /usr/local/etc/poudriere.d/make.conf:DEFAULT_VERSIONS+=perl5=5.28 gcc=8
>
> There was also a "print/texinfo:configure/runaway" but I've not looked into
> it at all yet and it may be a while before I do. The other ports attempted
> built fine as far as I can tell so far.
>
>
> The devel/qt5-testlib failure looks like:
>
> [00:00:13] Building 123 packages using 28 builders
> . . .
> [00:49:30] [10] [00:00:00] Building devel/qt5-testlib | qt5-testlib-5.11.2
> . . .
> [07:31:31] [10] [06:42:01] Saved devel/qt5-testlib | qt5-testlib-5.11.2 wrkdir to: /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailCortexA57-default/default/qt5-testlib-5.11.2.tar
> [07:31:32] [10] [06:42:02] Finished devel/qt5-testlib | qt5-testlib-5.11.2: Failed: configure/runaway
>
> With logs/errors/qt5-testlib-5.11.2.log showing:
>
> Checking for POSIX monotonic clock...
> + cd /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic && /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin/qmake "CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG += shared warn_off console single_arch" /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic
> + cd /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic && MAKEFLAGS= make
> =>> Killing runaway build after 21600 seconds with no output
> =>> Cleaning up wrkdir
> ===> Cleaning for qt5-testlib-5.11.2
> Killed
> build of devel/qt5-testlib | qt5-testlib-5.11.2 ended at Wed Dec 19 06:45:42 PST 2018
> build time: 06:41:46
> !!! build failure encountered !!!
>
>
> # less /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.log
> . . .
> test config.qtbase_corelib.libraries.librt succeeded
> executing config test clock-monotonic
> + cd /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic && /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/bin/qmake "CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG += shared warn_off console single_arch" /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic
> + cd /wrkdirs/usr/ports/devel/qt5-testlib/work/qtbase-everywhere-src-5.11.2/config.tests/clock-monotonic && MAKEFLAGS= make
>
>
> Some supporting details of context:
>
> # uname -apKU
> FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r341836M: Tue Dec 11 16:37:42 PST 2018 markmi at FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-NODBG amd64 amd64 1300005 1300005
>
> # svnlite info /usr/ports/ | grep "Re[plv]"
> Relative URL: ^/head
> Repository Root: svn://svn.freebsd.org/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 484783
> Last Changed Rev: 484783
>
I started poudriere up again with just the 2 needing to be rebuilt (plus
what depends on the 2). devel/qt5-testlib quickly completed just fine:
[00:02:16] [02] [00:00:00] Building devel/qt5-testlib | qt5-testlib-5.11.2
[00:04:54] [02] [00:02:38] Finished devel/qt5-testlib | qt5-testlib-5.11.2: Success
In the prior build that had the hang-ups I looked and dor print/texinfo :
/wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5/config.log shows for its
hang-up:
. . .
configure:6639: checking for alloca
configure:6676: /nxb-bin/usr/bin/cc -o conftest -O2 -pipe -mcpu=cortex-a57 -DLIBICONV_PLUG -g -fno-strict-aliasing -mcpu=cortex-a57 -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5
configure:6676: $? = 0
configure:6684: result: yes
configure:6794: checking for C/C++ restrict keyword
configure:6821: /nxb-bin/usr/bin/cc -c -O2 -pipe -mcpu=cortex-a57 -DLIBICONV_PLUG -g -fno-strict-aliasing -mcpu=cortex-a57 -DLIBICONV_PLUG -D_THREAD_SAFE conftest.c >&5
configure:6821: $? = 0
configure:6829: result: __restrict
configure:6844: checking whether // is distinct from /
In the poudriere re-run print/texinfo seems to be not progressing:
root 87913 0.0 0.0 12920 3668 0 I 13:29 0:00.06 | | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: build_pkg (texinfo-6.5_1,1) (sh)
root 88869 0.0 0.0 12920 3660 0 I 13:29 0:00.00 | | `-- sh: poudriere[FBSDFSSDjailCortexA57-default][01]: build_pkg (texinfo-6.5_1,1) (sh)
root 88870 0.0 0.0 10412 1848 0 IJ 13:29 0:00.01 | | `-- /usr/bin/make -C /usr/ports/print/texinfo configure
root 88974 0.0 0.0 10272 1812 0 IJ 13:30 0:00.00 | | `-- /bin/sh -e -c (cd /wrkdirs/usr/ports/print/texinfo/work/texinfo-6.5 && _LATE_CONFIGURE_ARGS="" ; if [
root 89283 0.0 0.0 11160 2108 0 IJ 13:30 0:00.10 | | `-- /bin/sh ./configure --enable-nls --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man --di
root 89692 0.0 0.0 227368 14504 0 IJ 13:30 0:00.03 | | `-- /usr/local/bin/qemu-aarch64-static wc //dev/null
root 89694 0.0 0.0 227424 14596 0 IJ 13:30 0:00.01 | | `-- /usr/local/bin/qemu-aarch64-static wc //dev/null
root 89695 0.0 0.0 227584 14720 0 IJ 13:30 0:00.01 | | `-- wc: zygote (qemu-aarch64-static)
So it appears that:
/usr/local/bin/qemu-aarch64-static wc //dev/null
is hanging-up (again).
Given that these are hangups I'll note that this is a Ryzen
Threadripper 1950X context and is running under Hyper-V from
Windows 10's 1809 update. I gave it 28 logical processors and
have it to have the virtual NUMA topology match the topology of
the physical hardware: "Use Hardware Topology". (Processors
28, NUMA nodes 2, Sockets 1, Hardware threads per core 2.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
More information about the freebsd-current
mailing list