Re: [bug #51311] Checking search retries for implicit make rules

[Philip Guenther]

On Sun, 25 Jun 2017, Mike Gran wrote:
> Follow-up Comment #1, bug #51311 (project make): You've opened this as a 
> bug. I believe it is not a bug.  Again. I'm not a maintainer.
> 
> Please note two things.
> 
> 1. while "MOTD%.log: MOTD%.txt" is a pattern rule, "MOTD%.log: MOTD%.txt
> MOTD%.in" is not a pattern rule, because it has two entries after the colon. 

This is incorrect.  To quote the make info pages, section 10.5.1
"Introduction to Pattern Rules":
-
A pattern rule contains the character `%' (exactly one of them) in the
target; otherwise, it looks exactly like an ordinary rule.  The target
is a pattern for matching file names; the `%' matches any nonempty
substring, while other characters match only themselves.  
-

There's no restriction in the documention on the number of prequisites on 
the rule and they may contain any mix of pattern and non-pattern names.  
See that page and the others in that section for further details.



> 2. The '%' (the stem) in a pattern rule doesn't, if I recall correctly, match
> a null string.  It needs to match at least a single character, so building
> MOTD.log won't work.

This is correct, as per the documentation quoted above.


Philip Guenther

___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

[bug #51311] Checking search retries for implicit make rules

[Mike Gran]

Follow-up Comment #1, bug #51311 (project make):

Markus,

You've opened this as a bug. I believe it is not a bug.  Again. I'm not a
maintainer.

Please note two things.

1. while "MOTD%.log: MOTD%.txt" is a pattern rule, "MOTD%.log: MOTD%.txt
MOTD%.in" is not a pattern rule, because it has two entries after the colon. 
So your interpretation is incorrect.

2. The '%' (the stem) in a pattern rule doesn't, if I recall correctly, match
a null string.  It needs to match at least a single character, so building
MOTD.log won't work.

___

Reply to this item at:

  

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


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

[bug #49841] flavor() function incorrectly shows function parameters as defined.

[Michael Builov]

Follow-up Comment #1, bug #49841 (project make):

> It appears that the scope of the parameters in the outer function intrudes
into the inner function for the flavor() function but not for the value of the
parameter. 

The origin() function is also affected.


When inner function takes less arguments than the outer one, make hides
"extra" arguments of outer scope by defining them with empty values in the
scope of inner function.

Moreover, these "hidden" arguments are automatic, so can't be redefined, for
example by $(eval 2:=aaa)

This looks like inconsistency - behavior of inner function depends on the
number of arguments of outer one.

May be better solution will be - instead of defining fake arguments in context
of inner function, just forbid looking up arguments in outer scope?

The patch (against git repository) is attached.

(file #41043)
___

Additional Item Attachment:

File name: gnu-make-git-49841.patch   Size:7 KB


___

Reply to this item at:

  

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


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

[bug #51309] Determination of a file list from a single folder without changing the working directory

[Markus Elfring]

URL:
  

 Summary: Determination of a file list from a single folder
without changing the working directory
 Project: make
Submitted by: elfring
Submitted on: Sun 25 Jun 2017 07:53:27 PM CEST
Severity: 3 - Normal
  Item Group: Enhancement
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: 4.2.1
Operating System: Any
   Fixed Release: None
   Triage Status: None

___

Details:

The function “wildcard”

is supported by the make software.
Corresponding file patterns work also in combination with directory names.
Such combinations are occasionally useful. The query result will contain them
as usual.

I came along the need to query a single folder without changing the working
directory

so that only file names (without folder names) will be in the result.
Can another software extension become useful for the function library to make
such data processing more efficient?




___

Reply to this item at:

  

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


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make