| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
problem with broken in-tree builds (which are used far more
pervasively than I'd known outside the tree). However, weird results
may now happen if at any point in the tree above you there happens to
be a directory that has subdirectory of share/mk, as unpredictable
results will follow. This was considered the lessor of the two evils,
at least for now. In the future this will be removed again when the
underlying issues are resolved.
|
|
|
|
|
|
|
| |
in SUBDIRS having tests added to it, which fails. Work around this by
checking to make sure tests exists before adding it to subdirs and
work to get the generated file fixed so we can rename Makefile.inc to
something else so it isn't automatically included by subdirs...
|
|
|
|
|
| |
location, including updating the test to work in the more-fragile
fmake -> bmake bootstrap environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This first step is mostly to prevent the code from rotting even further
and to ensure these do not get wiped when fmake's code is removed from
the tree.
These tests are currently being skipped because they detect the underlying
make is not fmake and thus disable themselves -- and the reason is that
some of the tests fail, possibly due to legitimate bugs. Enabling them to
run against bmake will come separately.
Lastly, it would be ideal if these tests were fed upstream but they are
not ready for that yet. In the interim, just put them under usr.bin/bmake/
while we sort things out. The existence of a different unit-tests directory
within here makes me feel less guilty about this.
Change confirmed working with a clean amd64 build.
|
|
|
|
|
| |
to fail and falling back on the conservative testing of variables
already in place. This should stop the tide of tinderbox mail.
|
| |
|
|
|
|
|
|
|
|
| |
instead of from /usr/share/mk.
I'm not sure that this will let buildworld complete on a system with
no installed src.opts.mk (make buildworld is still running), but the
tinderbox builds are all failing earlyon without this patch.
|
|
|
|
|
|
|
|
| |
build world, so it is the only make we build or install. fmake is
still in the tree, but disconnected, and upgrades from older systems
that still have bmake has not been removed, but its state has not been
tested (it should work given how minimal the work to upgrade to bmake
is).
|
|
|
|
| |
from the latter.
|
| |
|
|
|
|
|
| |
Reviewed by: obrien
Approved by: re
|
| |
|
|
|
|
|
| |
Consume up to next newline, and issue a parse warning.
If no newline found before P_end, carry on as before.
|
|
|
|
|
| |
Main feature of interest is .MAKE.JOB.PREFIX=
to suppress --- job --- tokens.
|
| |
|
| |
|
|
|
|
|
|
| |
we could be on an old system that knows noting of MK_BMAKE
or on an almost up to date one that is defaulting it to "no"
neither of which will work.
|
|
|
|
|
| |
correct options are set.
Also defined NO_PWD_OVERRIDE to match behavior of fmake.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
allow FreeBSD make to do 'obj'.
Approved by: marcel (mentor)
|
|
|
|
| |
Approved by: marcel (mentor)
|
|
|
|
|
|
| |
Also pay attention to MK_SHARED_TOOLCHAIN.
Approved by: marcel (mentor)
|
|
|
|
| |
Approved by: marcel (mentor)
|
|
|
|
|
|
|
|
|
| |
make) ended up being built with -DFORCE_MACHINE. This broke the lib32
built for amd64 & powerpc64.
This fix is comes with the next import of bmake, but is committed here
and now to minimize the exposure to the bug.
Submitted by: Simon Gerraty <sjg@juniper.net>
|
| |
|
|
of FreeBSD's make by setting WITH_BMAKE. The WITH_BMAKE build makes it
easy for people to switch while working out the kinks -- think ports
tree here. The option will be removed in due time.
Submitted by: Simon Gerraty (sjg@juniper.net)
|