| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
be opened, to avoid trying to read standard input after already closing
it, which resulted in EBADF errors.
|
|
|
|
|
|
| |
the MFLAGS target. Document that variable assignments from the MAKEFLAGS
environment variable and the .MAKEFLAGS and .MFLAGS target have the
same precedence as command line variable assignments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
variable as required by POSIX. This causes such variables to be
pushed into all sub-makes called by the make (except when the MAKEFLAGS
variable is explicitely changed in the sub-make's environment).
This makes them also mostly un-overrideable in sub-makes except on the
sub-make's command line. Therefor specifying 'make CC=icc' will cause
icc to be used as C compiler in all sub-makes no matter what the Makefiles
itself try to do to the CC variable.
This patch also corrects the handling of the MFLAGS variable. MFLAGS
contains all the command line flags but not the command line variable
assignments. The evaluation of the .MFLAGS or .MAKEFLAGS target now
changes both MFLAGS and MAKEFLAGS (they used to change MAKEFLAGS only).
Makefiles can use MFLAGS for their own purposes given that they do not
except MFLAGS to be undefined at the beginning and that they don't evaluate
.MFLAGS or .MAKEFLAGS. MFLAGS should be removed for POSIX compliance,
but it is unfortunately heavily used by the X makefiles.
This has been extensively tested by port builds (thanks to portmgr), new
worlds and kernels.
PR: standards/57295 (1st part above)
Submitted by: James E. Flemer <jflemer@alum.rpi.edu>
Approved by: portmgr
Obtained from: NetBSD (1st part above)
MFC after: 4 weeks
|
|
|
|
| |
as unused, so that make can be compiled with WARNS=3 again.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For -l, upset everyone by breaking it. Specifically, -l now produces
a lengthy error message that suggests --check-links (POSIX -l) or
--one-file-system (GNU -l) instead. However, if POSIXLY_CORRECT is set,
use the POSIX interpretation.
For -o, please everyone by making it work both ways:
* -xo uses POSIX behavior
* -co uses "almost GNU" behavior (as close as we can get until
libarchive implements a true V7 tar format)
|
|
|
|
| |
still potentially useful.
|
|
|
|
| |
to discourage people from using them.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
replace the version we currently have in src/gnu/usr.bin/patch/.
Among other things, this version includes a --posix option for strict
POSIX conformance.
This version is the current source from OpenBSD as of today. It is
their 3.5-release, plus a few updates to patch.c and pch.c that they
made about three weeks ago.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Thanks to: Pav Lucistnik
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
work in the util-linux packages, but with some minor fixes.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
(downloaded file(s) are created inside the directory).
MFC after: 3 days
|
| |
| |
| |
| | |
Thanks to: Barry Bouwsma
|
| |
| |
| |
| | |
Thanks to: Johan Karlsson
|
| | |
|
| |
| |
| |
| | |
Install FlexLexer.h into /usr/include directly.
|
| |
| |
| |
| | |
in the util-linux package.
|
| |
| |
| |
| |
| |
| | |
PR: misc/69768
Submitted by: bronek
MFC after: 1 week
|
| |
| |
| |
| | |
Requested by: ru
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to be executed even when -n is given on the command line to make. This is
very handy for calls to submakes.
This is slightly changed from the original patch as obtained from NetBSD.
The NetBSD variant prints lines which have both '+' and '@' when -n
is specified. The commited version always obeys '@'.
Bump MAKE_VERSION so Makefiles can use this conditionally.
PR: standards/66357 (partly)
Submitted by: Mark Baushke <mdb@juniper.net>
Obtained from: NetBSD
|
| | |
|
| |
| |
| |
| |
| | |
character straddles the "start" or "stop" columns, but this should be
quite uncommon.
|
| | |
|
| |
| |
| |
| | |
previous commit.
|
| |
| |
| |
| | |
work in the util-linux package.
|
| |
| |
| |
| | |
since + is also a valid way to terminate -exec.
|
| | |
|
| |
| |
| |
| | |
entry from BUGS section that said otherwise.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
output on bare ethernet and vlan interfaces the same.
PR: bin/69674
Submitted by: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
Reviewed by: ru
Approved by: julian (mentor)
MFC after: 1 week
|
| | |
|
| |
| |
| |
| | |
both GCC builtin and system declared ones.
|
| |
| |
| |
| | |
a warning with gcc 3.4.x.
|
| |
| |
| |
| | |
Pointed out by: simon
|
| |
| |
| |
| |
| |
| | |
options even though they look like primaries. (This is already documented
in the options themselves, but is sufficiently astonishing that I think it
deserves a BUGS entry as well.)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
section.
Move the HISTORY section to place it before BUGS rather than after BUGS,
in order to minimize the chance of this error being reproduced in the
future. (Both mdoc(7) and 63% of manual pages have these sections listed
in this order.)
|
| |
| |
| |
| | |
MFC after: 2 weeks
|
| | |
|