PRs for manpage 'make(1)'
This is an experimental report containing PRs for manpage 'make(1)' as of Fri May 30 07:37:59 2014 UTC. See notes.
PRs for manpage 'make(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/05/22 | bin/190100 | [patch] make(1): fix core dumps at syntax error | |
| o | 2013/11/07 | bin/183762 | make(1) .undef does not work with variables set to a value | |
| o | 2013/06/22 | bin/179833 | [patch] make(1): contrib/bmake: port easter egg from pmake | |
| o | 2011/12/23 | bin/163567 | make(1): add option to disable object directory | |
| o | 2011/08/12 | bin/159730 | make(1) in parallel mode fails report failure of @-prefixed recipe using "set +e" | |
| o | 2011/04/29 | bin/156729 | make(1) does not respect.ORDER in non-parallel mode | |
| o | 2011/02/24 | bin/155000 | make(1) doesn't handle .POSIX: correctly | |
| o | 2011/02/14 | bin/154769 | make(1): :L modifier broken in quoted strings | |
| o | 2011/02/06 | bin/154562 | make(1): corrupted stack access when provided invalid identifiers | |
| o | 2010/03/01 | bin/144388 | [patch] different behavior of make(1) between command line argument and .MAKEFLAGS special target | |
| o | 2009/10/14 | bin/139601 | [patch] make(1): variable substitution for $@ in dependency source fails | |
| o | 2007/06/10 | bin/113518 | [patch] make(1): Prevent execution when command is a comment | |
| o | 2005/12/20 | bin/90680 | [patch] make(1) thinks "^.for.o:" is a directive (".for something in ...") | |
| o | 2004/03/16 | bin/64327 | [patch] make(1): document surprising behaviour of assign with expansion | |
| o | 2003/07/17 | bin/54594 | [patch] make(1) apply regexps to the entire variable -- a new variable modifier | |
| o | 2002/03/05 | bin/35568 | make(1) declares target out of date, but $? is empty | |
| o | 1999/08/09 | bin/13042 | make(1) doesn't handle wildcards in subdirectory paths | |
| s | 1999/04/13 | bin/11114 | make(1) does not work as documented with .POSIX: target |
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.