Hi!
On Wed, 2014-04-30 at 16:22:37 +0200, Guillem Jover wrote:
> I think we should first understand why the detection is failing with
> the newer make. I'm taking a look now. Once that's done we might just
> be able to fix (or workaround) one of:
>
> * make
> * dpkg-buildpackage
> * affected packages
It would appear to me that make is the culprit (if the behaviour
change was not intentional, that is).
Here's the minimal makefile needed to reproduce it, and a transcript:
,--- detect.mk ---
build-stamp:
echo $@
build-arch: build-stamp
`---
$ make --version | head -n1
GNU Make 3.81
$ make -f detect.mk -qn build-arch; echo $?
1
$ make --version | head -n1
GNU Make 4.0
$ make -f detect.mk -qn build-arch; echo $?
2
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140430161908.ga3...@gaara.hadrons.org
