Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Don't stop other legs of a parallel build due to a failure in make_check.The whole point is to see if there's any failure, which is handled bybuilding a newer version of make.
Following r226271, allow disabling lzma support with "WITHOUT_LZMA_SUPPORT".Correct r226271 which should have used WITHOUT_BZIP2_SUPPORT per r166255.Obtained from: Juniper Networks
Add support for bmake. This includes:1. Don't do upgrade_checks when using bmake. As long as we have WITH_BMAKE, there's a bootstrap complication in ths respect. Avoid it. Make the necessar
Add support for bmake. This includes:1. Don't do upgrade_checks when using bmake. As long as we have WITH_BMAKE, there's a bootstrap complication in ths respect. Avoid it. Make the necessary changes to have upgrade_checks work wth bmake anyway.2. Remove the use of -E. It's not needed in our build because we use ?= for the respective variables, which means that we'll take the environment value (if any) anyway.3. Properly declare phony targets as phony as bmake is a lot smarter (and thus agressive) about build avoidance.4. Make sure CLEANFILES is complete and use it on .NOPATH. bmake is a lot smarter about build avoidance and should not find files we generate in the source tree. We should not have files in the repository we want to generate, but this is an easier way to cross this hurdle.5. Have behavior under bmake the same as it is under make with respect to halting when sub-commands fail. Add "set -e" to compound commands so that bmake is informed when sub-commands fail.6. Make sure crunchgen uses the same make as the rest of the build. This is important when the make utility isn't called make (but bmake for example).7. While here, add support for using MAKEOBJDIR to set the object tree location. It's the second alternative bmake looks for when determining the actual object directory (= .OBJDIR).Submitted by: Simon Gerraty <[email protected]>Submitted by: John Van Horne <[email protected]>
show more ...
Remove the "funny targets" make check. We no longer need embedded :: targetsto build FreeBSD (they are used in Perl man pages). We never needed embedded"!" in targets that I can find.We got thi
Remove the "funny targets" make check. We no longer need embedded :: targetsto build FreeBSD (they are used in Perl man pages). We never needed embedded"!" in targets that I can find.We got this from OpenBSD and I cannot find any other make that supportssuch things -- contrary to their commit message claim: "This behaviouris also consistent with other versions of make.".
make it easier to check newly-built make
+ Tighten up (and simplify) the pass_cmd_vars_1 "variable definition arrived from the calling make" test.+ Be more tolerant of newlines in the plus_flag "supports the '+' flag" test.
The shell_1_sh test was failing with "make -jX".Approved by: re (kensmith)
Fix builds with a read-only directory and a make upgrade. This is doneby forcing the creation of an object directory for the make regressiontests. Let make handle the tracking of the dependency and
Fix builds with a read-only directory and a make upgrade. This is doneby forcing the creation of an object directory for the make regressiontests. Let make handle the tracking of the dependency and installationof test_shell script.Submitted by: ru
Make this work under debugging, e.g., "make -dl".
Make the tests runnable on a read-only src. To do this you must make surethat you create one of the object directories make knows (see make(1)).This uses the -C flag, so add a test that checks that
Make the tests runnable on a read-only src. To do this you must make surethat you create one of the object directories make knows (see make(1)).This uses the -C flag, so add a test that checks that make actually accepts-C. Also fix the test that selects csh via the .SHELL target to work fortcsh users too.This commit renames shell_test to shell_test.sh. There is no historyto preserve so go without a repo-copy.Reviewed by: ru
Chmod the shell testscript to be executable if it isn't already. Accordingto the CVS-Meisters x-mode just happens to work, but is not guaranteed todo so. Try to be on the safe side.
Add some regression tests for the .SHELL target. I'm not sure that theoutput of shell_2j is actually correct - it just tests what make currentlydoes. Make should switch on echoing for the second li
Add some regression tests for the .SHELL target. I'm not sure that theoutput of shell_2j is actually correct - it just tests what make currentlydoes. Make should switch on echoing for the second line, shouldn't it?
Switch over to a different, more flexible test output protocol that'sunderstood by Perl's Test::Harness module and prove(1) commands.Update README to describe the new protocol. The work's broken
Switch over to a different, more flexible test output protocol that'sunderstood by Perl's Test::Harness module and prove(1) commands.Update README to describe the new protocol. The work's broken down intotwo main sets of changes.First, update the existing test programs (shell scripts and C programs)to produce output in the ok/not ok format, and to, where possible, alsoproduce a header describing the number of tests that are expected to berun.Second, provide the .t files that actually run the tests. In some casesthese are copies of, or very similar too, scripts that already existed.I've kept the old scripts around so that it's possible to verify thatbehaviour under this new system (in terms of whether or not a test fails)is identical to the behaviour under the old system.Add a TODO file.
Add a regression test for the alternate shell specification.
Now that make more correctly handles variable assignmentsin .MAKEFLAGS targets enable the regression test for this.
Back out something I'm working on that crept in with the last commit.Spotted by: ru
Remove extra spaces. Remove double quotes around error messages -they are not needed and will actually be printed.Submitted by: ru
Add another test that checks for a working '+' command flag.
Add a regression test for the passing of command linevariable assignments via the MAKEFLAGS environment variable.
Add a test for what was broken in rev. 1.28 and fixed in rev. 1.29of make/str.c.
Add a test for what was fixed in revs. 1.28 and 1.29 of make/str.c.
Fix a bug that prevented exists() from finding "foo/", "foo/."and "foo/.." when ".PATH: foo" was also given.PR: bin/34062
Fixed broken arithmetic expression parser.Reminded by: bdeIn memory of: alane
The regression-tests for 'make' *expect* to trigger make's warning: warning: duplicate script for target "double" ignoredThe regression-tests do try to hide that message, but the message does
The regression-tests for 'make' *expect* to trigger make's warning: warning: duplicate script for target "double" ignoredThe regression-tests do try to hide that message, but the message doesstill appear when using -j (eg: 'make -j5 buildworld'). This changes theregression-test so the expected warning message will not be seen evenwhen -j is specified.Reviewed by: jmallett ru
12