Your message dated Fri, 17 Aug 2018 09:38:32 +0000
with message-id
<20180817093832.5g7ntoydkateojwe@fbd7c150-3361-11e8-8c11-5badabdd4a8d>
and subject line Re: Bug#906321: Acknowledgement (mk-configure FTBFS: bmake[3]:
don't know how to make w)
has caused the Debian Bug report #906321,
regarding mk-configure FTBFS: bmake[3]: don't know how to make w
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
906321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mk-configure
Version: 0.29.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
mk-configure fails to build in current sid using schroot-based sbuild:
bmake cleandir-presentation
bmake[3]: bmake[3]: don't know how to make w. Stop
bmake[3]: stopped in /<<PKGBUILDDIR>>
*** [w] Error code 2
bmake[2]: stopped in /<<PKGBUILDDIR>>
1 error
bmake[2]: stopped in /<<PKGBUILDDIR>>
make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 2
Full build log attached.
-- dam
mk-configure_amd64-2018-08-17T00:03:39Z.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.29.1-2
Sorry, this turned out to be bad interaction of the build environment
with debhelper's bmake support.
Passing -j 1 messed with the code that tested whether a given makefile
target exists.
-- dam
--- End Message ---
