Hi With CURRENT post base r316946 `devel/py-pykde4` fails to build with -- Build files have been written to: /wrkdirs/usr/ports/devel/py-pykde4/work/.build /usr/local/bin/cmake -E cmake_progress_start /wrkdirs/usr/ports/devel/py-pykde4/work/.build/CMakeFiles /wrkdirs/usr/ports/devel/py-pykde4/work/.build/CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: cannot open CMakeFiles/Makefile2. make[2]: stopped in /wrkdirs/usr/ports/devel/py-pykde4/work/.build/wrkdirs/usr/ports/devel/py-pykde4/work/.build *** [all] Error code 2 make[1]: stopped in /wrkdirs/usr/ports/devel/py-pykde4/work/.build 1 error make[1]: stopped in /wrkdirs/usr/ports/devel/py-pykde4/work/.build ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/devel/py-pykde4 switching it to use `USES=gmake` fixes the issue as a work-around. I verified, that it works with base r316946 and does not with base r316949: > bmake_316946 head@316946: [01:42:16] ====>> [01][00:03:20] Finished build of devel/py-pykde4: Success > bmake_316949 head@316949: [00:03:41] ====>> [01][00:01:41] Finished build of devel/py-pykde4: Failed: build Maybe some other ports are affected by this too. mfg Tobias
There seems to be a problem with the working directory: -- Build files have been written to: /wrkdirs/usr/ports/devel/py-pykde4/work/.build /usr/local/bin/cmake -E cmake_progress_start /wrkdirs/usr/ports/devel/py-pykde4/work/.build/CMakeFiles /wrkdirs/usr/ports/devel/py-pykde4/work/.build/CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: cannot open CMakeFiles/Makefile2. make[2]: stopped in /wrkdirs/usr/ports/devel/py-pykde4/work/.build/wrkdirs/usr/ports/devel/py-pykde4/work/.build *** Error code 2 Stop. make[1]: stopped in /wrkdirs/usr/ports/devel/py-pykde4/work/.build *** Error code 1 The "/wrkdirs/usr/ports/devel/py-pykde4/work/.build/wrkdirs/usr/ports/devel/py-pykde4/work/.build" looks suspicious.
There are a couple of known bugs in bmake-20170413, so it is being updated (as I type). It is quite possible that that will fix this issue - I don't build ports enough to be sure what the issue here is, but will ask you to retry once bmake-20170420 is in the tree.
r317239 updates bmake to 20170420, can you retry with that pls
I tested it against r317245. It seems to work again. Thanks.