summaryrefslogtreecommitdiffstats
path: root/tools/build
Commit message (Collapse)AuthorAgeFilesLines
* A version of <sys/endian.h> in RELENG_4 doesn't have 64-bit functions.ru2003-04-151-1/+1
| | | | Spotted by: simokawa
* Make sure legacy stuff comes last. Some tools that useru2003-04-123-10/+12
| | | | | | | | | | | legacy stuff (binutils) depend on this order. For this to work, provide (and use) specialized versions of bsd.prog.mk and bsd.lib.mk that include the standard versions first, then augment CFLAGS, DPADD, LDADD, and LDFLAGS as necessary, with the legacy stuff. Tested on: 4.0-RELEASE
* libc_gen/basename.c depends on include/libgen.h.ru2003-04-111-3/+3
|
* -legacy and /.../legacy/... looks better than build or bootstrap inimp2003-04-062-5/+5
| | | | | | the logs, so use that instead. Submitted by: obrien.
* We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. Thisimp2003-04-061-3/+5
| | | | | | | | | | | is because we populate these directories later, and a subsequent -DNOCLEAN build may fail. So, we put them in ${WORLDTMP}/build/usr/{include,lib} instead and adjust Makefile.boot. Again, this works on -stable and -current, but might break older versions. Submitted by: ru@
* Don't need the gccism include_next since we won't create this fileimp2003-04-061-6/+1
| | | | | | when a real sys/endian.h exists. Submitted by: ru@
* Migrate to a new way of dealing with building from old revisions ofimp2003-04-056-0/+180
| | | | | | | | | | | | | | | | | FreeBSD. This method attempts to centralize all the necessary hacks or work arounds in one of two places in the tree (src/Makefile.inc1 and src/tools/build). We build a small compatibility library (libbuild.a) as well as selectively installing necessary include files. We then include this directory when building host binaries. This removes all the past release compatibilty hacks from various places in the tree. We still build on tip of stable and current. I will work with those that want to support more, although I anticipate it will just work. Many thanks to ru@, obrien@ and jhb@ for providing valuable input at various stage of implementation, as well as for working together to positively effect a change for the better.
* The regression-tests for 'make' *expect* to trigger make's warning:gad2003-02-101-1/+1
| | | | | | | | | | warning: duplicate script for target "double" ignored The regression-tests do try to hide that message, but the message does still appear when using -j (eg: 'make -j5 buildworld'). This changes the regression-test so the expected warning message will not be seen even when -j is specified. Reviewed by: jmallett ru
* Add a test for what was fixed in revisions 1.39 and 1.50 ofru2002-11-281-0/+9
| | | | | | make/parse.c (allow embedded `:' and `!' in target names). Approved by: re
* Moved make(1) regression tests from src/Makefile to where theyru2002-11-281-1/+25
| | | | | | | belong (src/tools/regression/usr.bin/make), and use the latter to test if make(1) is adequate for building the world. Approved by: re
* Hide the test in <target> under '.if make(<target>)' so as to not get anyjmallett2002-10-251-0/+4
| | | | errors/warnings related to crud in said test block.
* As of revision 1.38 of make/parse.c, our make(1) will warn too. Note thatjmallett2002-07-281-2/+3
| | | | | this isn't just for the sake of testing behaviour, and that things really do break if this regression occurs.
* Grrr, make the test for embedded variables in the left-hand-side actually dojmallett2002-06-201-2/+2
| | | | the right thing in every case. Yuck.
* Add a test for what was fixed in revision 1.27 and 1.28 of make(1)'s var.c,jmallett2002-06-191-0/+17
| | | | | | expansion of embedded variables in the left-hand-side of an assignment expression, using the simplest case - hiding recursion using nil-expanded variables.
* Add a regression test for bin/5297, regarding sysv substitution with a niljmallett2002-05-052-0/+10
| | | | left-hand-side.
* Prefix tests with PASS and FAIL, to make grepping easier, and note this injmallett2002-04-271-3/+3
| | | | | | the README. This affects only the base-system regression tests, of course.
* Check to see if make(1)'s handling of doubly-defined targets is busted orjmallett2002-04-211-0/+11
| | | | not. A lot relies on this.
* Add a test of variable evaluation and substitution for make(1), as a startjmallett2002-04-202-0/+21
of tests for it.
OpenPOWER on IntegriCloud