Date: Mon, 13 Jul 2015 17:24:34 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no>, vbox@FreeBSD.org Subject: Re: oddity in virtualbox-ose-additions Message-ID: <55A42C92.3050404@FreeBSD.org> In-Reply-To: <86k2u454q7.fsf@nine.des.no> References: <86k2u454q7.fsf@nine.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 07/13/2015 13:48, Dag-Erling Smørgrav wrote:
> While trying to build $subj on 10.2, I noticed an oddity in the
> Makefile:
>
> cd ${WRKSRC} && ${SH} env.sh && \ ${KMK_CONFIG}
> ${LOCALBASE}/bin/kmk ${KMK_FLAGS}
>
> the last two lines are wrong - env.sh sets environment variables
> and needs to be sourced into the shell before kmk is invoked, like
> virtualbox-ose des:
>
> cd ${WRKSRC} && \ ${SH} -c '. env.sh && ${KMK_CONFIG}
> ${LOCALBASE}/bin/kmk ${KMK_FLAGS}'
>
> although I don't think it will fix the problem, which is that kmk
> just hangs on wait channel umtxn. I changed the Makefile so it
> reads:
>
> cd ${WRKSRC} && (. env.sh && ktrace -di env \ ${KMK_CONFIG}
> ${LOCALBASE}/bin/kmk ${KMK_FLAGS})
No, it does not make any difference but fixed.
https://svnweb.freebsd.org/changeset/ports/391963
> "make build" now shows:
>
> ===> Building for virtualbox-ose-additions-4.3.30 cd
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.30
> && (. env.sh && ktrace -di env VBOX_LIBPATH_X11=/usr/local
> /usr/local/bin/kmk ) Config.kmk:2463:
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.30/o
ut/freebsd.amd64/release/DynamicConfig.kmk:
> No such file or directory Config.kmk:5741:
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.30/o
ut/freebsd.amd64/release/revision.kmk:
> No such file or directory
>
> ktracing kmk shows:
...
> It ignores the SIGINT and remains stuck in the backgrounf until I
> SIGKILL it (pkill -9 kmk).
There maybe a bug in kmk as it is relatively old fork of GNU make
3.82. However, I can't reproduce the problem. Probably there's a
libthr issue for you?
Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVpCyLAAoJEHyflib82/FGSb0IAJK8J3c/NpHXsKy4b5yBRzcH
SCKwRTcbhHHLOorQSULKbxwQZWQSkVFU2qb3aTzHgxiDzVC2yY5yyf0Ma6kqtq0S
QAAqn4rQ5e0AbgFjK/1RmuxaXZUSrnuU0wGcPMg8nrAMt6Ye5djNh1HDkos9g1QP
n73RXnyYLZoFwyoIjEs86MaU9hZ2YePS18fOQw0CLyvoTnjCypyD8NUpTufNnVFo
46GcG+Qz7829DFy3OQzKuftFD8ZJKeSkwFS67K3uf548v8tDKsdmPB8UTBQ78eE0
guSQKbtJKMtUmOfNWQNC05B+2D6vpmCPe3+jcq0S4wxz4wxLdOKTkEiHEhazjsw=
=s+12
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A42C92.3050404>