bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #54675] avoid redundant recipe warning for identical recipes


From: David Boyce
Subject: [bug #54675] avoid redundant recipe warning for identical recipes
Date: Mon, 17 Sep 2018 21:23:11 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?54675>

                 Summary: avoid redundant recipe warning for identical recipes
                 Project: make
            Submitted by: boyski
            Submitted on: Tue 18 Sep 2018 01:23:09 AM UTC
                Severity: 3 - Normal
              Item Group: Enhancement
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: SCM
        Operating System: None
           Fixed Release: None
           Triage Status: None

    _______________________________________________________

Details:

I'm wondering whether it might be reasonable to skip the redundant-recipe
warnings if the recipes are identical anyway. Test case:

% cat makefile
.PHONY: all
all:
foo:; touch $@
foo:; touch $@

% make
makefile:5: warning: overriding recipe for target 'foo'
makefile:4: warning: ignoring old recipe for target 'foo'
make: Nothing to be done for 'all'.

It looks like this might be avoidable with a strcmp in read.c around line 2113
(in current SCM) though I'm not in a position to try it now.

This comes up because I have various macros and helper makefiles which
generate rules to create directory paths. The recipe to create a directory
will in all cases be "mkdir $@" in my use case but when multiple macros end up
generating identical rules these spurious warnings are still printed. Of
course it can be programmed around but I wonder whether it's worth giving the
warning at all here.






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54675>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]