summaryrefslogtreecommitdiffstats
path: root/Makefile.inc1
Commit message (Collapse)AuthorAgeFilesLines
* Set AR=gnu-ar and RANLIB=gnu-ranlib on systems where we are forcedru2008-03-021-4/+3
| | | | | | to use GNU tools. Remove the _WITH_GNUAR knob. Prodded by: obrien
* Sort.ru2008-02-251-5/+5
| | | | Prodded by: obrien
* Make again BSD ar(1) the default system ar(1), now properly handlingru2008-02-251-0/+9
| | | | | | | | | | | | | source upgrades by falling back to GNU ar(1) as necessary. Option WITH_BSDAR is gone. Option _WITH_GNUAR to aid in upgrades is *not* supposed to be set by the user. Stop bootstrapping BSD ar(1) on the next __FreeBSD_version bump, as there are no known bugs in it. Bump __FreeBSD_version to anticipate this and to flag the switch to BSD ar(1), should it be needed for something. Input from: obrien, des, kaiw
* Satisfy a particularly obstinate nit-picker :)des2008-02-051-1/+1
|
* Give usr.bin/kdump/kdump_subr.c the same treatment as usr.bin/kdump/ioctl.cdes2008-02-051-0/+1
| | | | | | | | | and usr.bin/truss/ioctl.c. This is the correct way to address the problem that arises when doing an incremental build after a header used by kdump has been removed (cf. i4b disconnect a while ago) Explained by: ru MFC after: 2 weeks
* Support source upgrades from at least 6.0-RELEASE.ru2008-01-231-0/+4
| | | | Reviewed by: imp, obrien
* Conditionally add mklocale to bootstrap-toolsache2008-01-231-0/+5
|
* Cleanup after last commit (remove undefined variables).ru2008-01-221-7/+1
|
* Remove 5.x and 6.x cruft - source upgrades to RELENG_8 from versions priorobrien2008-01-211-28/+0
| | | | to RELENG_7 are not supported.
* Remove WITHOUT_FORTRAN from the XMAKE target, it doesn't exist anymore.brueffer2008-01-161-1/+1
| | | | | | Reviewed by: imp, kan Approved by: rwatson (mentor) MFC after: 3 days
* - Explicitly verify if all needed libs were found by ldd(1). Do soyar2007-12-041-6/+14
| | | | | | | | | | | | | | | | | through scanning its output as ldd(1) returns a non-zero status only for really abnormal conditions such as an improper file format. Now cp(1) won't get bogus "not" and "found" arguments if a lib is missing. [1] - Don't guess if an element of a complex pipeline is assigned to the main shell or a sub-shell. Namely use stdio, not vars, to pass lists out from loops. If using vars, there's the risk that a loop will run in a sub-shell and the list won't make it to the main shell. It appears that braces and parens give only limited control over the issue while stdio always works as intended. Apply this solution to both $progs and $libs for consistency, although I've failed to go without it only in the $libs part. Requested by: emaste [1]
* Decouple the install tools from the main system as much as possible.yar2007-10-311-14/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | I.e., not only copy them to a scratch dir, but also make them use saved copies of libraries and locale files. That gives us several benefits: 1) ABI breakages should no longer affect installworld over the live system. 2) It becomes safe to run installworld while still running the old kernel. However, it can be reasonable to save the old /rescue before that to be able to run the old reboot(8), as the new binaries are rather likely to fail with the old kernel. Anyhow, it's now possible to upgrade a system in a single reboot _reliably_. 3) With a bit of hackery around rtld(8), it becomes possible to do destructive cross-installs, e.g., i386->amd64 over the live system. The only shared item left between the old and new systems is rtld(8), which cannot be run from a saved copy easily because its full pathname is stored in the respective field of each ELF executable. (In theory, that field could be overridden, e.g., from the environment, but this can lead to security issues.) That's why a destructive cross-install isn't possible w/o hackery yet. Fruitful ideas by: ru Reviewed by: ru Tested with: audit(4)
* If a required install tool is missing, provide a more friendly erroremaste2007-10-151-1/+6
| | | | message (instead of cp's usage info).
* Tweak the handling of "WITHOUT_LIBPTHREAD". Also remove the accidentalobrien2007-10-091-1/+1
| | | | | | | treatment of 'LIBKSE' as an "old style" knob. Submitted by: ru Approved by: re(kensmith)
* Repo copy libpthreads to libkse.obrien2007-10-091-3/+3
| | | | | | This introduces the WITHOUT_LIBKSE nob, and changes WITHOUT_LIBPTHREADS to mean with neither threading libs. Approved by: re(kensmith)
* Revise the list of directories we manually create underru2007-10-011-5/+2
| | | | | | | ${WORLDTMP} and ${LIB32TMP}; some of them are no longer needed, and some were never needed. Approved by: re (kensmith)
* Always install libpthread.* symlinks if at least one ofru2007-10-011-1/+9
| | | | | | | | | | | | the threading libraries is built. This simplifies the logic in makefiles that need to check if the pthreads support is present. It also fixes a bug where we would build a threading library that we shouldn't have built: for example, building with WITHOUT_LIBTHR and the default value of DEFAULT_THREADING_LIB (libthr) would mistakenly build the libthr library, but not install it. Approved by: re (kensmith)
* Add sed(1) to cross tools. We do want newly built version duringdelphij2007-07-101-0/+1
| | | | | | buildworld. Approved by: re (rwatson)
* lex(1) no longer installs headers into GCC-internal dirsru2007-05-261-3/+3
| | | | (since src/usr.bin/lex/Makefile,v 1.20).
* Revision 1.576 removed too much. I didn't notice because my /usr is ondes2007-05-191-0/+2
| | | | ZFS, which doesn't support flags...
* GCC will now properly link libc with all shared objects in order to recordkan2007-05-191-3/+26
| | | | | | their dependency on libc and its versioned symbols. For that to work, libc needs to be built before any other shared library that might depend on it. Add necessary glue to make that happen.
* Don't use a subshell where it isn't needed.des2007-05-161-12/+12
| | | | Noticed by: John E Hein <jhein@timing.com>
* Expose all of {check,delete}-old{,-dirs,-files,-libs}.des2007-05-161-1/+4
| | | | MFC after: 3 weeks
* Remove stray comment which broke delete-old-dirs.des2007-05-161-1/+0
|
* Partially revert the check-old / delete-old modifications to clarify thedes2007-05-161-26/+20
| | | | | | | logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
* Restore previous behaviour of aborting delete-old* if rm failed.des2007-05-141-2/+2
| | | | | Pointed out by: netchild MFC after: 3 weeks
* Greatly speed up {check,delete}-old* by replacing make loops with sh loops.des2007-05-131-28/+20
| | | | MFC after: 3 weeks
* Enable symbol versioning by default. Use WITHOUT_SYMVER to disable it.deischen2007-05-131-1/+1
| | | | | | | | | | Warning, after symbol versioning is enabled, going back is not easy (use WITHOUT_SYMVER at your own risk). Change the default thread library to libthr. There most likely still needs to be a version bump for at least the thread libraries. If necessary, this will happen later.
* Link libzpool, ztest and zdb against libpthread.pjd2007-04-171-2/+2
| | | | Requested by: ru
* Connect ZFS to the build.pjd2007-04-061-2/+12
|
* Enable ncurses wide character supportrafan2007-03-091-2/+4
| | | | | Approved by: delphij (mentor) Tested by: kris on pointyhat (early version), current@
* Bump the bootstrapping requirements for gensnmptree(1) and removeru2007-03-011-1/+1
| | | | | | | a note in UPDATING that tried to work around the build breakage. Tested by: jhb OK'ed by: njl
* Resurrect one of the patches from attic and refine theru2007-02-281-31/+18
| | | | | | | | | | lib32 build somewhat. Specifically, instead of spamming ${CC} et al with -I${LIB32TMP}/usr/include which can be harmful (as has been demonstrated by the ncursesw WIP), use slightly different approach to achieve the same goal. This also simplifies things a bit. Prodded by: rafan
* Clean the lib32 object directory with cleandir rather than rm -rf.des2007-02-271-1/+2
| | | | | Discussed with: ru MFC after: 2 weeks
* Switch to new ncurses build gluerafan2007-01-201-3/+3
| | | | Approved by: delphij
* There was a timeframe where crunchgen(1) was broken; forceru2006-11-271-1/+1
| | | | | an upgrade during the build so those who are affected can build world again.
* There doesn't seem to be a real reason for include/ to be installedru2006-11-131-6/+9
| | | | so early.
* Add sun4v to the TARGET_ARCH when just TARGET is set (like pc98 is done).jb2006-10-161-1/+1
| | | | This is required for 'make universe'.
* buildworld fixes for sun4vkmacy2006-10-091-1/+1
| | | | | | | not sure why pmap.c is included as it is unchanged Approved by: rwatson (mentor) Reviewed by: jmg
* Shuffle _*_libs assigments (no functional changes).ru2006-10-071-29/+28
|
* - Prebuild libgssapi only if building with Kerberos support.ru2006-10-071-3/+6
| | | | | | | | | - Remove libnetgraph from the list of prebuilt libraries as no other library depends on it (snmp_netgraph.so does not count as we don't build it in the "libraries" target). - Restore libssh dependencies when compiling with Kerberos support.
* Previous revision wasn't enough for "make TARGET=<machine> build*"ru2006-09-081-0/+1
| | | | | | to work. Some build-tools that are part of cross-tools (cc_tools) also need to know the proper values of TARGET_ARCH and TARGET, so tell them.
* While experimenting with cross-building by specifying just TARGET,ru2006-09-071-0/+1
| | | | | | | | I found one bug. Pass our idea of TARGET_ARCH and TARGET down to XMAKE, the cross-tools make. Previously it worked because usually TARGET_ARCH was specified on the initial make's command line. This should also allow us to simplify the "universe" target, which I'm currently testing.
* Added timestamping to buildworld, similar to buildkernel.ru2006-09-071-2/+12
|
* - Rewrite logic to guess TARGET_ARCH/TARGET to be more readable,ru2006-09-071-6/+25
| | | | | | but without changes in behavior. - Add sanity checking for TARGET_ARCH/TARGET.
* make "make TARGET=foo" work correctly. Before, it would fail to setimp2006-09-071-1/+4
| | | | | | | | | | | | | | | | | | | TARGET_ARCH correctly. Now it does, even for pc98. We should suggest TARGET=foo in preference to TARGET_ARCH because the former is unambiguous and the latter isn't, so update the docs. This means that a long standing gripe I've had with this comes to a close. I can build pc98 w/o specify both things. make TARGET=arm works (rather than trying to build a arm:amd64 image and dying badly in the attempt). If you specify only TARGET_ARCH, then you get the old behavior. # we can likely simplify the UNIVERSE target now to use this, but I'm not # up for breaking that tonight :-). # We should consider adding some kind of sanity check for TARGET_ARCH # and TARGET.
* Always make obj when building the libraries. This never hurts, andimp2006-08-241-2/+4
| | | | | helps some cross-architecture building tool installation patches that I'm developing.
* Remove alpha left-overs.ru2006-08-221-4/+0
|
* Remove sade from build-tools, the tinderbox problem should be fixed now.netchild2006-08-091-1/+0
|
* Add the sade to build-tools list. This fixes a tinderbox.nyan2006-08-091-0/+1
|
OpenPOWER on IntegriCloud