The rework of GetBooleanVar to GetBooleanExpr requires we add "${" and ":U}" around the expression so it can be directly evaluated. Reported by: mjg MFC after: 1 week # # 72 columns --| # # Uncomment and complete these metadata fields, as appropriate: # # PR: <If and which Problem Report is related.> # Reported by: <If someone else reported the issue.> # Reviewed by: <If someone else reviewed your modification.> # Approved by: <If you needed approval for this commit.> # Obtained from: <If the change is from a third party.> # MFC after: <N [day[s]|week[s]|month[s]]. Request a reminder email> # MFH: <Ports tree branch name. Request approval for merge.> # Relnotes: <Set to 'yes' for mention in release notes.> # Security: <Vulnerability reference (one per line) or description.> # Sponsored by: <If the change was sponsored by an organization.> # Pull Request: <https://github.com/freebsd/<repo>/pull/###> # Differential Revision: <https://reviews.freebsd.org/D###> # # "Pull Request" and "Differential Revision" require the *full* GitHub or # Phabricator URL. The commit author should be set appropriately, using # `git commit --author` if someone besides the committer sent in the change. # # Uncomment and complete these metadata fields, as appropriate: # # PR: # Reported by: <If someone else reported the issue.> # Reviewed by: <If someone else reviewed your modification.> # Approved by: <If you needed approval for this commit.> # Obtained from: <If the change is from a third party.> # MFC after: <N [day[s]|week[s]|month[s]]. Request a reminder email> # MFH: <Ports tree branch name. Request approval for merge.> # Relnotes: <Set to 'yes' for mention in release notes.> # Security: <Vulnerability reference (one per line) or description.> # Sponsored by: <If the change was sponsored by an organization.> # Pull Request: <https://github.com/freebsd/<repo>/pull/###> # Differential Revision: <https://reviews.freebsd.org/D###> # # "Pull Request" and "Differential Revision" require the *full* GitHub or # Phabricator URL. The commit author should be set appropriately, using # `git commit --author` if someone besides the committer sent in the change. # |
||
---|---|---|
.. | ||
filemon | ||
missing/sys | ||
mk | ||
PSD.doc | ||
unit-tests | ||
aclocal.m4 | ||
arch.c | ||
bmake.1 | ||
bmake.cat1 | ||
boot-strap | ||
bsd.after-import.mk | ||
buf.c | ||
buf.h | ||
ChangeLog | ||
compat.c | ||
cond.c | ||
config.h.in | ||
configure | ||
configure.in | ||
dir.c | ||
dir.h | ||
dirname.c | ||
enum.c | ||
enum.h | ||
FILES | ||
find_lib.sh | ||
for.c | ||
getopt.c | ||
hash.c | ||
hash.h | ||
import.sh | ||
install-sh | ||
job.c | ||
job.h | ||
LICENSE | ||
lst.c | ||
lst.h | ||
machine.sh | ||
main.c | ||
make_malloc.c | ||
make_malloc.h | ||
make-bootstrap.sh.in | ||
make-conf.h | ||
make.1 | ||
make.c | ||
make.h | ||
Makefile | ||
Makefile.config.in | ||
makefile.in | ||
meta.c | ||
meta.h | ||
metachar.c | ||
metachar.h | ||
mkdeps.sh | ||
nonints.h | ||
os.sh | ||
parse.c | ||
pathnames.h | ||
ranlib.h | ||
README | ||
realpath.c | ||
setenv.c | ||
sigcompat.c | ||
str.c | ||
str.h | ||
stresep.c | ||
strlcpy.c | ||
suff.c | ||
targ.c | ||
trace.c | ||
trace.h | ||
util.c | ||
var.c | ||
VERSION | ||
wait.h |
bmake ***** This directory contains a port of the BSD make tool (from NetBSD). Since 1993 I have run it on AIX, BSDi, Darwin, FreeBSD, HP-UX, IRIX, Linux, Minix, OSF, Solaris, SunOS and even UTS. Others have run it on many more systems. Currently each release is tested on NetBSD, FreeBSD, Solaris and Linux. Since 2003 bmake switched to a date based version (first was 20030714) which generally represents the date it was last merged with NetBSD's make. Since then, NetBSD's make is imported within a week of any interesting changes, so that bmake tracks it very closely. Building ======== The preferred way to bootstrap bmake is:: ./bmake/boot-strap there are a number of args - most of which get passed to configure, eg. :: ./bmake/boot-strap --prefix=/opt see the boot-strap script for details. For folk that hate to read anything, since 20121212 you can also use the GNU standard process of:: ./configure; make; make install To make much use of bmake you will need the bsd.*.mk macros or my portable *.mk macros which are included with bmake since 20121212 and separately available from http://www.crufty.net/ftp/pub/sjg/mk.tar.gz which will be links to the latest versions. Porting ======= If you encounter a system that bmake does not build or work on *out of the box*, I welcome patches. If you can provide access to a suitable machine - even better. More info can be found at http://www.crufty.net/help/sjg/bmake.htm --sjg <sjg@crufty.net>