src-test2/Makefile, branch release/5.2.0FreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.2.02003-11-07T08:36:55ZDon't allow the 'make' target (which rebuilds make for bootstrapping)2003-11-07T08:36:55ZKris Kennawaykris@FreeBSD.org2003-11-07T08:36:55Zurn:sha1:2a6e9f885cabfcfa316b08785f2bc3cf96d2ba5b
to become confused by a file called 'make' in /usr/src
Submitted by: ru
Retired the "most" and "installmost" targets -- they just2003-10-04T18:53:38ZRuslan Ermilovru@FreeBSD.org2003-10-04T18:53:38Zurn:sha1:829340b175aab9ea365b5ff4cd5720a5c82aaacb
do not have a chance to work nowadays as we have a lot of
internal libraries in lib/.
Discussed with: marcel, wollman
Cosmetics: folded BITGTS into TGTS.2003-08-30T13:33:41ZRuslan Ermilovru@FreeBSD.org2003-08-30T13:33:41Zurn:sha1:b797df80b950c8dfd5ab7c2545ecec9d160fb043Limit testing for an up-to-date version of make(1) to the world and2003-08-28T04:03:13ZMarcel Moolenaarmarcel@FreeBSD.org2003-08-28T04:03:13Zurn:sha1:d911f786ab7c711235b2e883bd05895313e95c92
buildworld targets by default, but allow it to be done for all user
targets by introducing a boolean option, named ALWAYS_CHECK_MAKE.
This change is by no means perfect and I don't even want to claim
this to be a solution. It does however address the fact that not
everybody likes to see make(1) rebuilt simply because the regression
test failed for some reason or other, including pilot error. It
therefore serves the purpose of keeping the crowd happy until we
have something better or simply reached a compromise.
The reasons for changing the default behaviour are:
o It avoids a negative, possibly non-intuitive option,
o It's according to POLA and fond of feet,
o Only buildworld is documented to do its best to be
successful at reasonably cost.
Reviewed by: gad, imp, obrien, peter
- Don't print "elf" before printing "make world" (aout support has been2003-08-06T11:06:38ZRuslan Ermilovru@FreeBSD.org2003-08-06T11:06:38Zurn:sha1:5ab778118b32eecd69e897614e153aafcc3a5b63
removed).
- Avoid using printf(1) where a simple shell's built-in echo is enough.
The `mk' target is long dead.2003-07-20T12:38:29ZRuslan Ermilovru@FreeBSD.org2003-07-20T12:38:29Zurn:sha1:9d1086a65ba9f145055f2a3a90bd9449944b8631Use an up-to-date make binary in the upgrade_checks target if2003-07-19T23:17:08ZRuslan Ermilovru@FreeBSD.org2003-07-19T23:17:08Zurn:sha1:ef2c779bf9e182c9dc4f2eae0dafe56fdaac898e
one is already available. This avoids sometimes unnecessary
step of attempting to rebuild the make binary again which may
fail at all if, for example, one has removed his /usr/include
before doing an installworld (to keep /usr/include tidied up).
Pointed out by: kris, marcel
Don't hardcore PATH into BINMAKE; the latter should only be2003-07-04T17:35:26ZRuslan Ermilovru@FreeBSD.org2003-07-04T17:35:26Zurn:sha1:ead4296edbd4b6c72c4e0b0cb8d89a0bd82a2477
comprised of the path to a make(1) binary (possibly the one
built by the "make" target in this Makefile), and a path to
a fresh share/mk. The idea is to allow "make release" pick
up the right "make" binary, if one exists.
This fixes release.5 I broke with the last commit here; the
second PATH here was overriding the right one from WMAKEENV
while rebuilding the "build-tools" for crunched binaries.
Fixed style bugs related to parentheses in Makefile.inc1.2003-07-04T14:27:06ZRuslan Ermilovru@FreeBSD.org2003-07-04T14:27:06Zurn:sha1:5dc6311712e646a85f63f99a8c3000d1a0dd0142
Submitted by: bde
Fixed nearby bug: propagate the root Makefile's idea of
the appropriate "make" binary down to release/Makefile.
Do the upgrade checks quietly.2003-06-22T21:56:22ZRuslan Ermilovru@FreeBSD.org2003-06-22T21:56:22Zurn:sha1:b31745f59978785062d93b77f80027841c73b1e3