|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001660 |
[Issue 8 drafts] Shell and Utilities |
Comment |
Error |
2023-04-06 08:44 |
2024-06-11 09:12 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
Product Version |
Draft 3 |
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
make |
|
Page Number |
3128 |
|
Line Number |
105558 |
|
Final Accepted Text |
|
|
|
Summary |
0001660: Out of date make rationale about -n and $(MAKE) |
|
Description |
Bug 0001436 added the requirement that command lines which expand the MAKE macro are still executed when -n is used, and removed some old rationale about this feature, but missed some later rationale that should also have been either removed or changed.
|
|
Desired Action |
Change:However, the System V convention of forcing command execution with -n when the command line of a target contains either of the strings "$(MAKE)" or "${MAKE}" has not been adopted. This functionality appeared in early proposals, but the danger of this approach was pointed out with the following example of a portion of a makefile:subdir:
cd subdir; rm all_the_files; $(MAKE) The loss of the System V behavior in this case is well-balanced by the safety afforded to other makefiles that were not aware of this situation. In any event, the command line <plus-sign> prefix can provide the desired functionality. to:The System V convention of forcing command execution with -n when the command line of a target expands the MAKE macro was not adopted in earlier versions of this standard, but it is now required because it has become widespread existing practice.
|
| Tags |
applied_after_i8d3, issue8 |
|
|
Attached Files |
|
|
|
Relationships 
