Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'make(1)'

This is an experimental report containing PRs for manpage 'make(1)' as of Mon Apr 21 07:37:55 2014 UTC. See notes.


PRs for manpage 'make(1)':
SSubmittedTrackerResp.Description
o2013/11/07bin/183762make(1) .undef does not work with variables set to a value
o2011/12/23bin/163567make(1): add option to disable object directory
o2011/08/12bin/159730make(1) in parallel mode fails report failure of @-prefixed recipe using "set +e"
o2011/04/29bin/156729make(1) does not respect.ORDER in non-parallel mode
o2011/02/24bin/155000make(1) doesn't handle .POSIX: correctly
o2011/02/14bin/154769make(1): :L modifier broken in quoted strings
o2011/02/06bin/154562make(1): corrupted stack access when provided invalid identifiers
o2010/03/01bin/144388[patch] different behavior of make(1) between command line argument and .MAKEFLAGS special target
o2009/10/14bin/139601[patch] make(1): variable substitution for $@ in dependency source fails
o2007/06/10bin/113518[patch] make(1): Prevent execution when command is a comment
o2005/12/20bin/90680[patch] make(1) thinks "^.for.o:" is a directive (".for something in ...")
o2004/03/16bin/64327[patch] make(1): document surprising behaviour of assign with expansion
o2003/07/17bin/54594[patch] make(1) apply regexps to the entire variable -- a new variable modifier
o2002/03/05bin/35568make(1) declares target out of date, but $? is empty
o1999/08/09bin/13042make(1) doesn't handle wildcards in subdirectory paths
s1999/04/13bin/11114make(1) does not work as documented with .POSIX: target
16 problems total.


Notes

GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.