Your message dated Wed, 30 Apr 2014 17:52:36 +0000
with message-id <[email protected]>
has caused the   report #746443,
regarding make: New make behaviour confuses dpkg-buildpackages' test for make 
targets
to be marked as having been forwarded to the upstream software
author(s) 

(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 [email protected]
immediately.)


-- 
746443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
URL:
  <http://savannah.gnu.org/bugs/?42249>

                 Summary: error GNU make 4.0 in handling -q -- exits with 2 if
something needs to be updated
                 Project: make
            Submitted by: srivasta
            Submitted on: Wed 30 Apr 2014 12:52:35 PM CDT
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: 4.0
        Operating System: POSIX-Based
           Fixed Release: None
           Triage Status: None

    _______________________________________________________

Details:

[Please retain the CC to [email protected] so that updates to
this report are also recorded in the Debian BTS]

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

This is definitely a bug in GNU make 4.0 in handling -q.  The docs are clear
on what the exit codes should be, and with -q make should exit with 1 if
something needs to be updated and no error was detected.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42249>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/

--- End Message ---

Reply via email to