d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a6c55c35fa
freebsd-skq/Makefile.inc1

2210 lines
67 KiB
Makefile
Raw Normal View History

E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
$Id$ -> $FreeBSD$
1999-08-28 01:35:59 +00:00
# $FreeBSD$
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# Make command line options:
NOCLEAN -> NO_CLEAN NOCLEANDIR -> NO_CLEANDIR
2004-12-21 12:21:26 +00:00
# -DNO_CLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir
# -DNO_CLEAN do not clean at all
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
# -DDB_FROM_SRC use the user/group databases in src/etc instead of
# the system database when installing.
NOSHARE -> NO_SHARE
2004-12-21 12:13:23 +00:00
# -DNO_SHARE do not go into share subdir
Add NO_KERNELOBJ flag, similar to NO_KERNEL{CONFIG,DEPEND,CLEAN}, which disables doing a make obj. Use it when you know it will work only. KERNFAST now implies NO_KERNELOBJ, since you don't need to keep doing obj when doing incremental kernel builds.
2009-12-16 02:54:34 +00:00
# -DKERNFAST define NO_KERNEL{CONFIG,CLEAN,DEPEND,OBJ}
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
# -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
Sigh, I thought we still had the rm -rf objdir stuff in make world, which would have taken care of the possibility of buildkernel crossing over from one binutils set to another. Back out the part about turning off 'make clean' if the 'make depend' is still active, but add a NO_KERNELCLEAN target instead that works like NOCLEAN but just for the kernel.
2001-01-22 23:29:13 +00:00
# -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
# -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
Add NO_KERNELOBJ flag, similar to NO_KERNEL{CONFIG,DEPEND,CLEAN}, which disables doing a make obj. Use it when you know it will work only. KERNFAST now implies NO_KERNELOBJ, since you don't need to keep doing obj when doing incremental kernel builds.
2009-12-16 02:54:34 +00:00
# -DNO_KERNELOBJ do not run ${MAKE} obj in ${MAKE} buildkernel
Make the update target consistent; both ports and doc are updated if their SUPFILE variables are defined _and_ NO_PORTSUPDATE and NO_DOCUPDATE respectively are not defined. Previously, only ports was updated and there was no way to prevent this without undefining its SUPFILE variable. PR: 17514 Reported by: Udo Erdelhoff <ue@nathan.ruhr.de>
2000-08-07 14:35:49 +00:00
# -DNO_PORTSUPDATE do not update ports in ${MAKE} update
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
# -DNO_ROOT install without using root privilege
Make the update target consistent; both ports and doc are updated if their SUPFILE variables are defined _and_ NO_PORTSUPDATE and NO_DOCUPDATE respectively are not defined. Previously, only ports was updated and there was no way to prevent this without undefining its SUPFILE variable. PR: 17514 Reported by: Udo Erdelhoff <ue@nathan.ruhr.de>
2000-08-07 14:35:49 +00:00
# -DNO_DOCUPDATE do not update doc in ${MAKE} update
Remove NO_CTF, exccept as an undocumented compatibility option. Convert all other uses to MK_CTF=no. Set MK_CTF=no rather than the indirect WITHOUT_CDDL in filemon regression. It is expected that NO_CTF will be removed in FreeBSD 12 entirely.
2014-04-25 19:25:00 +00:00
# -DWITHOUT_CTF do not run the DTrace CTF conversion tools on built objects
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
# LOCAL_DIRS="list of dirs" to add additional dirs to the SUBDIR list
- Add a LOCAL_ITOOLS to allow adding additional tools required for the installworld and distributeworld targets PR: 179562 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> MFC after: 1 week
2014-06-17 22:23:36 +00:00
# LOCAL_ITOOLS="list of tools" to add additional tools to the ITOOLS list
Minor wording change. The previous commit message should have included: Sponsored by: DARPA, AFRL
2012-06-15 19:42:49 +00:00
# LOCAL_LIB_DIRS="list of dirs" to add additional dirs to libraries target
Allow LOCAL_(DIRS,LIBS) to install files in directories not found in the system mtree files via a LOCAL_MTREE variable which contains a list of mtree files to be applyed along with the base mtree files to the tmp root and DESTDIR.
2012-10-18 12:32:51 +00:00
# LOCAL_MTREE="list of mtree files" to process to allow local directories
# to be created before files are installed
Allow extra directories to be added to the build-tools target. Things such as "sh" require local tools to be built before cross-compiling. This allows for extra software (that's built via LOCAL_DIRS) to also have a build-tools target where required.
2012-01-05 21:50:50 +00:00
# LOCAL_TOOL_DIRS="list of dirs" to add additional dirs to the build-tools
# list
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
# METALOG="path to metadata log" to write permission and ownership
# when NO_ROOT is set. (default: ${DESTDIR}/METALOG)
- Rewrite logic to guess TARGET_ARCH/TARGET to be more readable, but without changes in behavior. - Add sanity checking for TARGET_ARCH/TARGET.
2006-09-07 16:41:30 +00:00
# TARGET="machine" to crossbuild world for a different machine type
Add note about TARGET_ARCH
2010-04-14 18:56:07 +00:00
# TARGET_ARCH= may be required when a TARGET supports multiple endians
Allow specification of build shell for the buildenv target. Submitted by: ian lepore
2012-01-30 20:19:28 +00:00
# BUILDENV_SHELL= shell to launch for the buildenv target (def:/bin/sh)
- Add CHECKSUM.* support in Makefile[1]. - Use ln -fs to create a symlink. - Remove pkgadd for docports. - Use WITHOUT_JADETEX=yes instead of WITH_JADETEX=no. - Add {WORLD,KERNEL}_FLAGS to [BTWK]MAKE. - Use makefs(8) and gpart(8) for sparc64 ISO image[2]. - Add publisher option to makefs(8)[2]. Based on work by: gjb[1] Discussed with: marius, nwhitehorn[2]
2013-02-03 10:26:24 +00:00
# WORLD_FLAGS= additional flags to pass to make(1) during buildworld
# KERNEL_FLAGS= additional flags to pass to make(1) during buildkernel
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# The intended user-driven targets are:
# buildworld - rebuild *everything*, including glue to help do upgrades
# installworld- install everything built by "buildworld"
Connect the kernel subsystem API documentation generation framework to the build infrastructure: "make doxygen" Changes to the man pages will be made when some defaults are revisited. Requested by: gnn
2006-05-26 18:10:06 +00:00
# doxygen - build API documentation of the kernel
Update comments to reflect use of svn/svnup to keep the src/ tree up to date. MFC after: 3 days
2013-05-28 21:57:55 +00:00
# update - convenient way to update your source tree (eg: svn/svnup)
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# Standard targets (not defined here) are documented in the makefiles in
# /usr/share/mk. These include:
# obj depend all install clean cleandepend cleanobj
You are now *REQUIRED* to pass both TARGET and TARGET_ARCH to any invocations of Makefile.inc1 (since that's supposed to be an internal interface for world and related targets). Document this with a .error message. For a transition period, support passing in just TARGET, but give a .warning for that case: I plan on removing it in 9.0...
2011-02-10 19:58:21 +00:00
.if !defined(TARGET) || !defined(TARGET_ARCH)
.error "Both TARGET and TARGET_ARCH must be defined."
.endif
Document src.opts.mk changes and the decoupling of /etc/src.conf from anything but the source tree.
2014-05-06 04:22:29 +00:00
.include "share/mk/src.opts.mk"
Merge from TBEMD: Rather than having arch specific code in Makefile.inc1, generalize so that we can control the settings of different options on a per architecutre basis. Reviewed by: arch@ (twice)
2010-06-24 16:28:52 +00:00
.include <bsd.arch.inc.mk>
Introduce a new make variable COMPILER_TYPE that specifies what type of compiler is being used (currently clang or gcc). COMPILER_TYPE is set in the new bsd.compiler.mk file based on the value of the CC variable or, should it prove informative, by running ${CC} --version and examining the output. To avoid negative performance impacts in the default case and correct value for COMPILER_TYPE type is determined and passed in the environment of submake instances while building world. Replace adhoc attempts at determining the compiler type by examining CC or MK_CLANG_IS_CC with checks of COMPILER_TYPE. This eliminates bootstrapping complications when first setting WITH_CLANG_IS_CC. Sponsored by: DARPA, AFRL Reviewed by: Yamaya Takashi <yamayan@kbh.biglobe.ne.jp>, imp, linimon (with some modifications post review) MFC after: 2 weeks
2012-09-13 16:00:46 +00:00
.include <bsd.compiler.mk>
Rescue is "not yet" for MIPS.
2008-09-19 16:14:42 +00:00
There doesn't seem to be a real reason for include/ to be installed so early.
2006-11-13 05:52:11 +00:00
# We must do lib/ and libexec/ before bin/, because if installworld
Fix a problem where 'make installworld' will fail and leave the system in a messy state *if* the user is upgrading from a system which has no /libexec to a system which builds a DYNAMICROOT, and if that user has set DISTDIR (as documented for ports, but it turns out that the same variable name is used for a completely unrelated purpose in 'make release'). There are other possible fixes for this issue, and ru@ may later decide to commit one of those fixes. I just wanted some fix in ASAP, and this is the fix that I have tested. Reviewed by: bde, imp, and ru
2003-12-09 00:42:44 +00:00
# installs a new /bin/sh, the 'make' command will *immediately*
# use that new version. And the new (dynamically-linked) /bin/sh
# will expect to find appropriate libraries in /lib and /libexec.
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
#
Fix build host pollution by avoiding calling 'uname -srp' to determine values for 'VERSION'. Looked at by: cperciva
2013-10-24 22:55:15 +00:00
SRCDIR?= ${.CURDIR}
Optimize SUBDIR_OVERRIDE such that SUBDIR isn't automatically defined if SUBDIR_OVERRIDE is defined. PR: conf/174071 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> Sponsored by: EMC / Isilon Storage Division
2013-05-01 09:56:09 +00:00
.if defined(SUBDIR_OVERRIDE)
SUBDIR= ${SUBDIR_OVERRIDE}
.else
Remove remnant from texinfo
2015-02-11 08:26:36 +00:00
SUBDIR= lib libexec
There doesn't seem to be a real reason for include/ to be installed so early.
2006-11-13 05:52:11 +00:00
SUBDIR+=bin
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_GAMES} != "no"
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=games
Just to be pedantic and more aesthetically pleasing, move the secure/ top-level subdirectory prior to share/ so that the top-level directories are processed in alphabetical order.
2001-12-06 07:44:47 +00:00
.endif
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
.if ${MK_CDDL} != "no"
SUBDIR+=cddl
.endif
There doesn't seem to be a real reason for include/ to be installed so early.
2006-11-13 05:52:11 +00:00
SUBDIR+=gnu include
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_KERBEROS} != "no"
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=kerberos5
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_RESCUE} != "no"
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=rescue
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.endif
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=sbin
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_CRYPT} != "no"
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=secure
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.endif
NOSHARE -> NO_SHARE
2004-12-21 12:13:23 +00:00
.if !defined(NO_SHARE)
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=share
Back out part of the revision 1.261: "etc" indeed needs to be last for "distribute" to succeed -- the "make makedb" part of the etc/Makefile:distribution target should be the last thing made.
2002-04-30 11:46:49 +00:00
.endif
There doesn't seem to be a real reason for include/ to be installed so early.
2006-11-13 05:52:11 +00:00
SUBDIR+=sys usr.bin usr.sbin
Set up the /usr/tests hierarchy. Populate /usr/tests with the only test programs that currently live in the tree (those in lib/libcrypt/tests/) and add all the build machinery to accompany this change. In particular: - Add a WITHOUT_TESTS variable that users can define to request that no tests be put in /usr/tests. - Add a top-level Kyuafile for /usr/tests and a way to create similar Kyuafiles in top-level subdirectories. - Add a BSD.tests.dist file to define the directory layout of /usr/tests. Submitted by: Julio Merino jmmv google.com Reviewed by: sjg MFC after: 2 weeks
2013-10-25 05:25:19 +00:00
.if ${MK_TESTS} != "no"
SUBDIR+= tests
.endif
- Merge in OFED 1.5.3 from projects/ofed/head
2011-03-21 09:58:24 +00:00
.if ${MK_OFED} != "no"
SUBDIR+=contrib/ofed
.endif
There doesn't seem to be a real reason for include/ to be installed so early.
2006-11-13 05:52:11 +00:00
#
# We must do etc/ last for install/distribute to work.
#
SUBDIR+=etc
Back out part of the revision 1.261: "etc" indeed needs to be last for "distribute" to succeed -- the "make makedb" part of the etc/Makefile:distribution target should be the last thing made.
2002-04-30 11:46:49 +00:00
Slightly alter the handling of LOCAL_LIB_DIRS to skip addition of directories in LOCAL_LIB_DIRS if they are subdirectories of directories listed in LOCAL_DIRS. This allows a hierarchy like: foo foo/lib foo/usr.bin foo/usr.sbin to be supported with LOCAL_DIRS=foo LOCAL_DIRS=foo/lib. MFC after: 1 week Sponsored by: DARPA, AFRL
2014-11-21 18:35:48 +00:00
# Local directories are last, since it is nice to at least get the base
# system rebuilt before you do them.
.for _DIR in ${LOCAL_DIRS}
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if exists(${.CURDIR}/${_DIR}/Makefile)
Slightly alter the handling of LOCAL_LIB_DIRS to skip addition of directories in LOCAL_LIB_DIRS if they are subdirectories of directories listed in LOCAL_DIRS. This allows a hierarchy like: foo foo/lib foo/usr.bin foo/usr.sbin to be supported with LOCAL_DIRS=foo LOCAL_DIRS=foo/lib. MFC after: 1 week Sponsored by: DARPA, AFRL
2014-11-21 18:35:48 +00:00
SUBDIR+= ${_DIR}
.endif
.endfor
# Add LOCAL_LIB_DIRS, but only if they will not be picked up as a SUBDIR
# of a LOCAL_DIRS directory. This allows LOCAL_DIRS=foo and
# LOCAL_LIB_DIRS=foo/lib to behave as expected.
.for _DIR in ${LOCAL_DIRS:M*/} ${LOCAL_DIRS:N*/:S|$|/|}
_REDUNDENT_LIB_DIRS+= ${LOCAL_LIB_DIRS:M${_DIR}*}
.endfor
.for _DIR in ${LOCAL_LIB_DIRS}
.if empty(_REDUNDENT_LIB_DIRS:M${_DIR}) && exists(${.CURDIR}/${_DIR}/Makefile)
SUBDIR+= ${_DIR}
Add an UPDATING entry and warning about the change in r274807 to help users transition to the new behavior. Discussed with: jmallett Sponsored by: DARPA, AFRL
2014-12-16 20:45:17 +00:00
.else
.warning ${_DIR} not added to SUBDIR list. See UPDATING 20141121.
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.endif
.endfor
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
.endif
Accept the old user interface for NO_CLEAN as it is a POLA violation as we've eventually changed the user interface of a common command.
2005-02-28 09:23:38 +00:00
.if defined(NOCLEAN)
NO_CLEAN= ${NOCLEAN}
.endif
NOCLEAN -> NO_CLEAN NOCLEANDIR -> NO_CLEANDIR
2004-12-21 12:21:26 +00:00
.if defined(NO_CLEANDIR)
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
CLEANDIR= clean cleandepend
.else
CLEANDIR= cleandir
.endif
Fix the broken non-cross compile build. Oops! Another pointy hat to: adrian, for stirring up more trouble.
2012-01-06 00:34:27 +00:00
LOCAL_TOOL_DIRS?=
Allow extra directories to be added to the build-tools target. Things such as "sh" require local tools to be built before cross-compiling. This allows for extra software (that's built via LOCAL_DIRS) to also have a build-tools target where required.
2012-01-05 21:50:50 +00:00
Allow specification of build shell for the buildenv target. Submitted by: ian lepore
2012-01-30 20:19:28 +00:00
BUILDENV_SHELL?=/bin/sh
r245757 introduced warning output if update method is set to CVS_UPDATE or SUP_UPDATE. CVS exporter for head/ is turned off for nearly one month now. It is finally time to swing the ax at these update methods. Reviewed by: eadler MFC after: 1 month
2013-05-28 23:43:47 +00:00
SVN?= /usr/local/bin/svn
Allow "make update" work with SVN, if you take the time to set up your /etc/make.conf properly. Only one SCM? I do not think this is right. Now I have fixed it.
2009-06-14 15:16:24 +00:00
SVNFLAGS?= -r HEAD
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
MAKEOBJDIRPREFIX?= /usr/obj
Many developers run with userland != to kernel. While this isn't supported, it usually works for months at a time. Allow these people to override the OSRELDATE of their installed world when things don't match and the exact OSRELDATE matters and is different than the kernel. Now that Makefile.inc1 depends more and more about which date you have to optimize the pieces it builds, it may be necessary to pessimize things if its guesses are wrong. If OSRELDATE is already set, we won't fork the sysctl to find out what the kernel's date is. Developers on IRC suggested that they run mismatches all the time as well. Reviewed by: obrien
2003-05-04 04:14:10 +00:00
.if !defined(OSRELDATE)
Fall back to using the kernel version for the OSRELDATE when /usr/include/osreldate.h doesn't exist on the system. While this could be worked around by saying something like 'make includes OSLRELDATE=0' when this file doesn't exist, it is just as easy to provide a fallback when the file we know we depend on doesn't exist. While this doesn't make all targets work w/o a /usr/include/osreldate.h, because some of the FreeBSD bootstrap tools use this file. 'make includes' however does work. Noticed by: peter, obrien (and likely others) Pointy hat to: imp (for suggesting a method that depended on /usr/include)
2003-08-25 17:48:25 +00:00
.if exists(/usr/include/osreldate.h)
Use the installed world's idea of OSRELDATE rather than the kernel. This was the initial intent anyway, and it became clear that it is really necessary to treat it this way, as many people happen to run with kernel newer than the installed world. Submitted by: imp, ru Approved by: re (scottl)
2003-05-15 17:59:32 +00:00
OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \
/usr/include/osreldate.h
Fall back to using the kernel version for the OSRELDATE when /usr/include/osreldate.h doesn't exist on the system. While this could be worked around by saying something like 'make includes OSLRELDATE=0' when this file doesn't exist, it is just as easy to provide a fallback when the file we know we depend on doesn't exist. While this doesn't make all targets work w/o a /usr/include/osreldate.h, because some of the FreeBSD bootstrap tools use this file. 'make includes' however does work. Noticed by: peter, obrien (and likely others) Pointy hat to: imp (for suggesting a method that depended on /usr/include)
2003-08-25 17:48:25 +00:00
.else
OSRELDATE should fallback to 'unknown' rather than the kernel that's booted on this machine. This is a slightly better default to use. Requested by: ru
2003-08-27 04:49:43 +00:00
OSRELDATE= 0
Fall back to using the kernel version for the OSRELDATE when /usr/include/osreldate.h doesn't exist on the system. While this could be worked around by saying something like 'make includes OSLRELDATE=0' when this file doesn't exist, it is just as easy to provide a fallback when the file we know we depend on doesn't exist. While this doesn't make all targets work w/o a /usr/include/osreldate.h, because some of the FreeBSD bootstrap tools use this file. 'make includes' however does work. Noticed by: peter, obrien (and likely others) Pointy hat to: imp (for suggesting a method that depended on /usr/include)
2003-08-25 17:48:25 +00:00
.endif
Many developers run with userland != to kernel. While this isn't supported, it usually works for months at a time. Allow these people to override the OSRELDATE of their installed world when things don't match and the exact OSRELDATE matters and is different than the kernel. Now that Makefile.inc1 depends more and more about which date you have to optimize the pieces it builds, it may be necessary to pessimize things if its guesses are wrong. If OSRELDATE is already set, we won't fork the sysctl to find out what the kernel's date is. Developers on IRC suggested that they run mismatches all the time as well. Reviewed by: obrien
2003-05-04 04:14:10 +00:00
.endif
- Rewrite logic to guess TARGET_ARCH/TARGET to be more readable, but without changes in behavior. - Add sanity checking for TARGET_ARCH/TARGET.
2006-09-07 16:41:30 +00:00
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
.if !defined(VERSION)
Use ${MAKE} so that we always use the same version/implementation of make.
2014-03-02 00:14:57 +00:00
REVISION!= ${MAKE} -C ${SRCDIR}/release -V REVISION
BRANCH!= ${MAKE} -C ${SRCDIR}/release -V BRANCH
Fix build host pollution by avoiding calling 'uname -srp' to determine values for 'VERSION'. Looked at by: cperciva
2013-10-24 22:55:15 +00:00
SRCRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \
${SRCDIR}/sys/sys/param.h
Strip the -pN patch level from the VERSION string which gets encoded into CTF data. Otherwise FreeBSD Update builds think every kernel file has changed every time there's a security advisory, since the FreeBSD Update build code isn't smart enough to look inside CTF data to ignore those changes. Pointy hat to: cperciva MFC after: 1 day, or before the next BETA
2013-11-13 08:08:56 +00:00
VERSION= FreeBSD ${REVISION}-${BRANCH:C/-p[0-9]+$//} ${TARGET_ARCH} ${SRCRELDATE}
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
.endif
Start to import support for the AArch64 architecture from ARM. This change only adds support for kernel-toolchain, however it is expected further changes to add kernel and userland support will be committed as they are reviewed. As our copy of binutils is too old the devel/aarch64-binutils port needs to be installed to pull in a linker. To build either TARGET needs to be set to arm64, or TARGET_ARCH set to aarch64. The latter is set so uname -p will return aarch64 as existing third party software expects this. Differential Revision: https://reviews.freebsd.org/D2005 Relnotes: Yes Sponsored by: The FreeBSD Foundation
2015-03-19 13:53:47 +00:00
KNOWN_ARCHES?= aarch64/arm64 amd64 arm armeb/arm armv6/arm armv6hf/arm i386 i386/pc98 mips mipsel/mips mips64el/mips mips64/mips mipsn32el/mips mipsn32/mips powerpc powerpc64/powerpc sparc64
- Rewrite logic to guess TARGET_ARCH/TARGET to be more readable, but without changes in behavior. - Add sanity checking for TARGET_ARCH/TARGET.
2006-09-07 16:41:30 +00:00
.if ${TARGET} == ${TARGET_ARCH}
_t= ${TARGET}
.else
_t= ${TARGET_ARCH}/${TARGET}
.endif
.for _t in ${_t}
.if empty(KNOWN_ARCHES:M${_t})
.error Unknown target ${TARGET_ARCH}:${TARGET}.
.endif
.endfor
.if ${TARGET} == ${MACHINE}
TARGET_CPUTYPE should exist solely in Makefile.inc1, similar to TARGET_ARCH and TARGET. This is problematic when one has the = (unconditional) type of assigment for CPUTYPE in /etc/make.conf. (This would override what was set on the command line to "make buildworld".) Add a (horrible) kludge to Makefile.inc1 to check the type of assignment for CPUTYPE (only for those who attempts to set it to a different value). Fix an example make.conf. Fix the kernel's build-tools target (aicasm only at the moment) to catch up with bsd.cpu.mk,v 1.15 (BOOTSTRAPPING replaced with NO_CPU_CFLAGS in Makefile.inc1's BMAKE). Reviewed by: jhb
2002-08-02 18:04:22 +00:00
TARGET_CPUTYPE?=${CPUTYPE}
Don't special case i386/pc98, replace it with the smarter logic of setting ${TARGET} -- make it default to ${MACHINE} if we are not cross-building, and ${TARGET_ARCH} otherwise. Set MAKEOBJDIREPREFIX based on ${TARGET}, not on ${TARGET_ARCH}. This is useful if you want to cross-build pc98 worlds on i386.
2002-04-11 13:43:50 +00:00
.else
- Define NO_CPU_CFLAGS during BMAKE and TMAKE (and thus XMAKE) so that bsd.cpu.mk doesn't have to worry about compilers other than the current version. - Allow TARGET_CPUTYPE to override CPUTYPE in bsd.cpu.mk. - Treat an empty CPUTYPE the same as an undefined CPUTYPE. - For buildworld, buildkernel, etc., define TARGET_CPUTYPE to CPUTYPE for native builds and define it to be empty for cross-builds. TARGET_CPUTYPE is only defined if it is not already defined via the commandline or environment.
2002-07-31 03:56:03 +00:00
TARGET_CPUTYPE?=
Don't special case i386/pc98, replace it with the smarter logic of setting ${TARGET} -- make it default to ${MACHINE} if we are not cross-building, and ${TARGET_ARCH} otherwise. Set MAKEOBJDIREPREFIX based on ${TARGET}, not on ${TARGET_ARCH}. This is useful if you want to cross-build pc98 worlds on i386.
2002-04-11 13:43:50 +00:00
.endif
- Rewrite logic to guess TARGET_ARCH/TARGET to be more readable, but without changes in behavior. - Add sanity checking for TARGET_ARCH/TARGET.
2006-09-07 16:41:30 +00:00
The intent in rev. 1.299 was to make the CPUTYPE assignment type check bother "only those who attempts to set it to a different value". This got broken in rev. 1.300 (that fixed another race). Reported by: ache
2002-08-08 15:43:23 +00:00
.if !empty(TARGET_CPUTYPE)
_TARGET_CPUTYPE=${TARGET_CPUTYPE}
.else
_TARGET_CPUTYPE=dummy
.endif
Further fix the case mentioned in rev. 1.302. The intent was (and still is) that if a user has say CPUTYPE=i686 set in /etc/make.conf, we don't print the assignment type warning unless TARGET_CPUTYPE is overridden. Unfortunately, the implementation was buggy, and only recent changes to bsd.cpu.mk that swapped canonical and alias values of some CPU types made the bug apparent. Here's what happens here. - CPUTYPE=i686 is set in /etc/make.conf, - bsd.cpu.mk reset it to "pentiumpro", - Makefile.inc1 compares this canonical value with the result of the following test, make -f /dev/null CPUTYPE=pentiumpro -V CPUTYPE and expects the result to be "pentiumpro" too, but "i686" is returned, here's why. We have two CPUTYPE variables, global, set to "i686" in /etc/make.conf, and command-line (of a higher precedence), set to "pentiumpro". The following part of bsd.cpu.mk, . elif ${CPUTYPE} == "i686" CPUTYPE = pentiumpro which is responsible for converting aliases to canonical values, sees the value of the CPUTYPE command-line variable first, "pentiumpro", and no conversion is done -- the net effect is that CPUTYPE global stays with its old value "i686", and "make -V CPUTYPE" (which prints variables in the global context) returns "i686". The fix was to pass the CPUTYPE in the test above as an environment variable instead of as a command line variable, i.e., CPUTYPE=pentiumpro make -f /dev/null -V CPUTYPE This time, CPUTYPE global is still set to "i686" initially (by /etc/make.conf), and an envieronment variable CPUTYPE (of a lower precedence) is set to "pentiumpro". The .elif sees it's set to "i686" and resets it to "pentiumpro", and so "make -V" returns "pentiumpro". NB: these various types of make(1) variables can be very painful, especially when combined with "make -V".
2004-12-22 22:00:01 +00:00
_CPUTYPE!= MAKEFLAGS= CPUTYPE=${_TARGET_CPUTYPE} ${MAKE} \
-f /dev/null -m ${.CURDIR}/share/mk -V CPUTYPE
The intent in rev. 1.299 was to make the CPUTYPE assignment type check bother "only those who attempts to set it to a different value". This got broken in rev. 1.300 (that fixed another race). Reported by: ache
2002-08-08 15:43:23 +00:00
.if ${_CPUTYPE} != ${_TARGET_CPUTYPE}
TARGET_CPUTYPE should exist solely in Makefile.inc1, similar to TARGET_ARCH and TARGET. This is problematic when one has the = (unconditional) type of assigment for CPUTYPE in /etc/make.conf. (This would override what was set on the command line to "make buildworld".) Add a (horrible) kludge to Makefile.inc1 to check the type of assignment for CPUTYPE (only for those who attempts to set it to a different value). Fix an example make.conf. Fix the kernel's build-tools target (aicasm only at the moment) to catch up with bsd.cpu.mk,v 1.15 (BOOTSTRAPPING replaced with NO_CPU_CFLAGS in Makefile.inc1's BMAKE). Reviewed by: jhb
2002-08-02 18:04:22 +00:00
.error CPUTYPE global should be set with ?=.
.endif
Fix cross-building, etc: 1. To cross-build, one now needs to set TARGET_ARCH, and not the MACHINE_ARCH. MACHINE_ARCH should never be changed manually! 2. Initialize DESTDIR= explicitly for bootstrap-tools, build-tools, and cross-tools stages. This fixes broken header and library dependencies problem. We build them in the host environment, and obviously want them to depend on host headers and libraries. The problem with broken header dependencies for bootstrap-tools and cross-tools was already partially solved (see BOOTSTRAPPING tests in bsd.prog.mk and bsd.lib.mk), but it was still there for build-tools if the user ran "make world DESTDIR=/foo". Also, for all of these stages, the library dependencies were broken because of how bsd.libnames.mk define DPADD members. We still provide a glue to install bootstrap- and cross-tools under the ${WORLDTMP}. Removed PATH overrides for bootstrap-, build-, and cross-tools stages. There is just no reason why we would need to override it, and the hacks to clean up the ${WORLDTMP} in the -DNOCLEAN case are no longer needed with fixes from this step. That is, we now never use ${WORLDTMP} headers and libraries, and we don't use any ${WORLDTMP} installed binaries during these stages. Again, these stages depend solely on the host environment, including compiler, headers, and libraries. 3. Moved "miniperl" back from cross-tools (it has nothing to do with a cross-compiler) to build-tools where it belongs. The change from step 1 let to do this. Also, to make this work, build-tools targets of "cc_tools" and "miniperl" were modified to call "depend". Here follow the detailed explanations. There are two categories of build tools, for now. In the first category there are "cc_tools" and "miniperl". They occupy the whole (sub)directory, and nothing needs to be done in this subdirectory later during the "all" stage. They are also constructed using system makefiles. We must build the .depend early in the build-tools stage because: 1) They use (and depend on) the host environment. 2) If we don't do this in build-tools, the "depend" stage of buildworld will do this for us; wrong library and header dependencies will be recorded (DESTDIR=${WORLDTMP}) and, what's worse, the "all" stage may then clobber the build-architecture format tools (that we built in the build-tools stage) with the target-architecture format ones, breaking cross build. In the second category there are all other build-tools. They share their directory with the "main" module that needs them in the "all" stage, and they don't show up themselves in the .depend file. The portion of this fix was already committed in gnu/usr.bin/cc/cc_tools/Makefile,v 1.52. 4. "libperl" is no longer a build tool, and "miniperl" is the stand-alone application. I had to make this change because build-tools and "all" stages share the same object directory. Without this change, if we cross compile, libperl.a is first built for the build architecture during the build-tools stage (for the purposes of immediate linkage with "miniperl"). Later on, the "all" stage sees this library as up-to-date, and doesn't rebuild it. The effect is that the wrong format static libperl library is installed with installworld. 5. Fixed "includes" to install secure/lib/libtelnet headers if required. Reviewed by: bde
2001-09-29 13:17:54 +00:00
.if make(buildworld)
Switch BUILD_ARCH in Makefile to use uname -p suggested by ru. Switch strncpy to strlcpy suggested by gad and issue found by pjd. Add to uname(3) man page describing: UNAME_s UNAME_r UNAME_v UNAME_m Add to getosreldate(3) man page describing: OSVERSION Submitted by: ru, pjd/gad Reviewed by: ru (man pages)
2005-12-03 05:11:07 +00:00
BUILD_ARCH!= uname -p
Fix cross-building, etc: 1. To cross-build, one now needs to set TARGET_ARCH, and not the MACHINE_ARCH. MACHINE_ARCH should never be changed manually! 2. Initialize DESTDIR= explicitly for bootstrap-tools, build-tools, and cross-tools stages. This fixes broken header and library dependencies problem. We build them in the host environment, and obviously want them to depend on host headers and libraries. The problem with broken header dependencies for bootstrap-tools and cross-tools was already partially solved (see BOOTSTRAPPING tests in bsd.prog.mk and bsd.lib.mk), but it was still there for build-tools if the user ran "make world DESTDIR=/foo". Also, for all of these stages, the library dependencies were broken because of how bsd.libnames.mk define DPADD members. We still provide a glue to install bootstrap- and cross-tools under the ${WORLDTMP}. Removed PATH overrides for bootstrap-, build-, and cross-tools stages. There is just no reason why we would need to override it, and the hacks to clean up the ${WORLDTMP} in the -DNOCLEAN case are no longer needed with fixes from this step. That is, we now never use ${WORLDTMP} headers and libraries, and we don't use any ${WORLDTMP} installed binaries during these stages. Again, these stages depend solely on the host environment, including compiler, headers, and libraries. 3. Moved "miniperl" back from cross-tools (it has nothing to do with a cross-compiler) to build-tools where it belongs. The change from step 1 let to do this. Also, to make this work, build-tools targets of "cc_tools" and "miniperl" were modified to call "depend". Here follow the detailed explanations. There are two categories of build tools, for now. In the first category there are "cc_tools" and "miniperl". They occupy the whole (sub)directory, and nothing needs to be done in this subdirectory later during the "all" stage. They are also constructed using system makefiles. We must build the .depend early in the build-tools stage because: 1) They use (and depend on) the host environment. 2) If we don't do this in build-tools, the "depend" stage of buildworld will do this for us; wrong library and header dependencies will be recorded (DESTDIR=${WORLDTMP}) and, what's worse, the "all" stage may then clobber the build-architecture format tools (that we built in the build-tools stage) with the target-architecture format ones, breaking cross build. In the second category there are all other build-tools. They share their directory with the "main" module that needs them in the "all" stage, and they don't show up themselves in the .depend file. The portion of this fix was already committed in gnu/usr.bin/cc/cc_tools/Makefile,v 1.52. 4. "libperl" is no longer a build tool, and "miniperl" is the stand-alone application. I had to make this change because build-tools and "all" stages share the same object directory. Without this change, if we cross compile, libperl.a is first built for the build architecture during the build-tools stage (for the purposes of immediate linkage with "miniperl"). Later on, the "all" stage sees this library as up-to-date, and doesn't rebuild it. The effect is that the wrong format static libperl library is installed with installworld. 5. Fixed "includes" to install secure/lib/libtelnet headers if required. Reviewed by: bde
2001-09-29 13:17:54 +00:00
.if ${MACHINE_ARCH} != ${BUILD_ARCH}
.error To cross-build, set TARGET_ARCH.
.endif
.endif
Check TARGET_ARCH as well as TARGET to determine if we are doing a cross build. This is necessary to be able to cross-build 32-bit PowerPC from a 64-bit PowerPC host. Reviewed by: imp
2010-09-08 19:53:16 +00:00
.if ${MACHINE} == ${TARGET} && ${MACHINE_ARCH} == ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING)
Don't add MACHINE_ARCH to MAKEOBJDIRPREFIX when not cross-building. This should fix make release. Reported by: jhay, phk
1999-12-11 17:05:36 +00:00
OBJTREE= ${MAKEOBJDIRPREFIX}
.else
Merge from tbemd: change the name of the object tree from ${TARGET} to ${TARGET}.${TARGET_ARCH} so we can do both big and little endian builds in the same tree. Reviewed by: arch@ (twice)
2010-06-24 16:32:20 +00:00
OBJTREE= ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH}
Don't add MACHINE_ARCH to MAKEOBJDIRPREFIX when not cross-building. This should fix make release. Reported by: jhay, phk
1999-12-11 17:05:36 +00:00
.endif
Add hacks that I use to test cross-builds (by building on native and foreign architectures and comparing products). They eliminate most of the differences caused by different object directory paths, timestamping, and identification. (Note WORLDTMP was renamed to ${OBJTREE}${.CURDIR}/tmp.)
2005-03-02 16:40:51 +00:00
WORLDTMP= ${OBJTREE}${.CURDIR}/tmp
Step 1 of eliminating the "games" distribution: Move binaries to /usr/bin; update paths; and include everything in the "base" distribution. The "games" distribution being optional made sense when there were more games and we had small disks; but the "games-like" games were moved into the ports tree a dozen years ago and the remaining "utility-like" games occupy less than 0.001% of my laptop's small hard drive. Meanwhile every new user is confronted by the question "do you want games installed" when they they try to install FreeBSD. The next steps will be: 2. Removing punch card (bcd, ppt), phase-of-moon (pom), clock (grdc), and caesar cipher (caesar, rot13) utilities. I intend to keep fortune, factor, morse, number, primes, and random, since there is evidence that those are still being used. 3. Merging src/games into src/usr.bin. This change will not be MFCed. Reviewed by: jmg Discussed at: EuroBSDCon Approved by: gjb (release-affecting changes)
2015-02-12 05:35:00 +00:00
BPATH= ${WORLDTMP}/legacy/usr/sbin:${WORLDTMP}/legacy/usr/bin:${WORLDTMP}/legacy/bin
XPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin
Install bootstrap-tools into a separate subtree of ${WORLDTMP}. This allows us to use them as early as possible while building bootstrap-, build-, and cross-tools. Some cleanups to follow. This change resolves the gperf(1) bootstrapping issue (missing -E option) in gnu/usr.bin/cc/cc1plus while in the cross-tools stage when upgrading from 4.0-RELEASE.
2003-04-13 11:42:55 +00:00
STRICTTMPPATH= ${BPATH}:${XPATH}
Don't add /usr/games to $PATH. Adding it here can only work for the `make world' case, and only made a difference for the evil NOTOOLS case of `make world' since games tools are installed in ${TOOLROOT}/usr/bin if they are built, but the PR was for normal builds. This is fixed in rev.1.14 of src/games/fortune/datfiles/Makefile. PR: 7936
1998-10-17 11:56:20 +00:00
TMPPATH= ${STRICTTMPPATH}:${PATH}
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
#
# Avoid running mktemp(1) unless actually needed.
# It may not be functional, e.g., due to new ABI
# when in the middle of installing over this system.
#
.if make(distributeworld) || make(installworld)
Specify the full path to mktemp
2001-12-23 22:49:06 +00:00
INSTALLTMP!= /usr/bin/mktemp -d -u -t install
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
.endif
Save any binaries we use by installworld, so that we won't use the binaries we just installed. This allows a future upgrade target to install a new system without intermediate reboots and also prevents conflicts for parallel make runs where we might exec a binary that's being installed at the same time.
2000-07-19 04:41:59 +00:00
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
#
# Building a world goes through the following stages
#
-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien.
2003-04-06 21:46:44 +00:00
# 1. legacy stage [BMAKE]
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# This stage is responsible for creating compatibility
# shims that are needed by the bootstrap-tools,
Add some more explanation to the different phases of the build.
2015-03-25 21:59:36 +00:00
# build-tools and cross-tools stages. These are generally
# APIs that tools from one of those three stages need to
# build that aren't present on the host.
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# 1. bootstrap-tools stage [BMAKE]
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# This stage is responsible for creating programs that
# are needed for backward compatibility reasons. They
# are not built as cross-tools.
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# 2. build-tools stage [TMAKE]
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# This stage is responsible for creating the object
# tree and building any tools that are needed during
# the build process.
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# 3. cross-tools stage [XMAKE]
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# This stage is responsible for creating any tools that
Add some more explanation to the different phases of the build.
2015-03-25 21:59:36 +00:00
# are needed for building the system. A cross-compiler is one
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# of them.
Number the stages in the documentation to match what is printed out when running.
2000-10-13 01:19:36 +00:00
# 4. world stage [WMAKE]
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# This stage actually builds the world.
Number the stages in the documentation to match what is printed out when running.
2000-10-13 01:19:36 +00:00
# 5. install stage (optional) [IMAKE]
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# This stage installs a previously built world.
#
elf2aout.c,v 1.6 and onwards have no known backward compatibility issues.
2003-04-13 15:43:29 +00:00
BOOTSTRAPPING?= 0
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# Common environment for world related stages
CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \
Fix cross-building, etc: 1. To cross-build, one now needs to set TARGET_ARCH, and not the MACHINE_ARCH. MACHINE_ARCH should never be changed manually! 2. Initialize DESTDIR= explicitly for bootstrap-tools, build-tools, and cross-tools stages. This fixes broken header and library dependencies problem. We build them in the host environment, and obviously want them to depend on host headers and libraries. The problem with broken header dependencies for bootstrap-tools and cross-tools was already partially solved (see BOOTSTRAPPING tests in bsd.prog.mk and bsd.lib.mk), but it was still there for build-tools if the user ran "make world DESTDIR=/foo". Also, for all of these stages, the library dependencies were broken because of how bsd.libnames.mk define DPADD members. We still provide a glue to install bootstrap- and cross-tools under the ${WORLDTMP}. Removed PATH overrides for bootstrap-, build-, and cross-tools stages. There is just no reason why we would need to override it, and the hacks to clean up the ${WORLDTMP} in the -DNOCLEAN case are no longer needed with fixes from this step. That is, we now never use ${WORLDTMP} headers and libraries, and we don't use any ${WORLDTMP} installed binaries during these stages. Again, these stages depend solely on the host environment, including compiler, headers, and libraries. 3. Moved "miniperl" back from cross-tools (it has nothing to do with a cross-compiler) to build-tools where it belongs. The change from step 1 let to do this. Also, to make this work, build-tools targets of "cc_tools" and "miniperl" were modified to call "depend". Here follow the detailed explanations. There are two categories of build tools, for now. In the first category there are "cc_tools" and "miniperl". They occupy the whole (sub)directory, and nothing needs to be done in this subdirectory later during the "all" stage. They are also constructed using system makefiles. We must build the .depend early in the build-tools stage because: 1) They use (and depend on) the host environment. 2) If we don't do this in build-tools, the "depend" stage of buildworld will do this for us; wrong library and header dependencies will be recorded (DESTDIR=${WORLDTMP}) and, what's worse, the "all" stage may then clobber the build-architecture format tools (that we built in the build-tools stage) with the target-architecture format ones, breaking cross build. In the second category there are all other build-tools. They share their directory with the "main" module that needs them in the "all" stage, and they don't show up themselves in the .depend file. The portion of this fix was already committed in gnu/usr.bin/cc/cc_tools/Makefile,v 1.52. 4. "libperl" is no longer a build tool, and "miniperl" is the stand-alone application. I had to make this change because build-tools and "all" stages share the same object directory. Without this change, if we cross compile, libperl.a is first built for the build architecture during the build-tools stage (for the purposes of immediate linkage with "miniperl"). Later on, the "all" stage sees this library as up-to-date, and doesn't rebuild it. The effect is that the wrong format static libperl library is installed with installworld. 5. Fixed "includes" to install secure/lib/libtelnet headers if required. Reviewed by: bde
2001-09-29 13:17:54 +00:00
MACHINE_ARCH=${TARGET_ARCH} \
Fix cross-building further. Introduce ${TARGET} defaulting to ${MACHINE} which should be set to whatever your target ${MACHINE} is, and use that with world-related stages. That is, to build pc98 on alpha, one now needs to set both TARGET_ARCH=i386 and TARGET=pc98. The scope of ${TARGET} is limited to Makefile.inc1 and cross-tools. In particular, this change was tested to fix: 1. Cross building of "alpha" on i386. The breakage was introduced by rev. 1.10 to sbin/i386/Makefile (missing <machine/cronyx.h>). 2. Descending into machine-specific subdirs for a different arch. Previously, sbin/i386 and usr.sbin/boot0cfg were descended into when cross-building "alpha" or pc98 on i386. 3. Fixes pc98 cross-building which was horribly broken, caused by not setting MACHINE correctly (most ${MACHINE} == pc98 checking Makefiles put -DPC98 to CFLAGS).
2001-10-25 07:28:55 +00:00
MACHINE=${TARGET} \
Flesh out WITHOUT_GROFF support to DTRT. A full featured groff is required during buildworld, so build it always and don't rely on it being present on the host system. vgrind(1) is tightly coupled to a roff processor and will not be built/installed when groff is disabled. Also much of the roff'ed documentation under share/doc will not be built/installed when WITHOUT_GROFF is defined. Reviewed by: ru (partial)
2011-02-22 08:13:49 +00:00
CPUTYPE=${TARGET_CPUTYPE}
.if ${MK_GROFF} != "no"
CROSSENV+= GROFF_BIN_PATH=${WORLDTMP}/legacy/usr/bin \
GROFF_FONT_PATH=${WORLDTMP}/legacy/usr/share/groff_font \
GROFF_TMAC_PATH=${WORLDTMP}/legacy/usr/share/tmac
.endif
With the more generous footprints today, it makes little sense to use UFS1 by default any more. Switch to UFS2.
2014-03-14 19:45:40 +00:00
.if defined(TARGET_CFLAGS)
CROSSENV+= ${TARGET_CFLAGS}
.endif
Don't make gdb, objc and f77 when building tools.
1999-12-09 16:40:27 +00:00
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# bootstrap-tools stage
Fix "make world DESTDIR=/mnt" to work again. A recent change to make(1) that causes command-line variables to be passed as command-line variables to sub-processes that make(1) executes broke it. By changing the type of all DESTDIR variables used internally in Makefile.inc1, from environment to command-line variables of the highest priority, I was able to "make world" with success, with the command-line variable DESTDIR set.
2004-08-25 22:06:29 +00:00
BMAKEENV= INSTALL="sh ${.CURDIR}/tools/install.sh" \
Install bootstrap-tools into a separate subtree of ${WORLDTMP}. This allows us to use them as early as possible while building bootstrap-, build-, and cross-tools. Some cleanups to follow. This change resolves the gperf(1) bootstrapping issue (missing -E option) in gnu/usr.bin/cc/cc1plus while in the cross-tools stage when upgrading from 4.0-RELEASE.
2003-04-13 11:42:55 +00:00
PATH=${BPATH}:${PATH} \
Make sure legacy stuff comes last. Some tools that use 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
2003-04-12 15:07:46 +00:00
WORLDTMP=${WORLDTMP} \
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
VERSION="${VERSION}" \
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}"
Migrate to a new way of dealing with building from old revisions of 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.
2003-04-05 20:30:30 +00:00
BMAKE= MAKEOBJDIRPREFIX=${WORLDTMP} \
- Add CHECKSUM.* support in Makefile[1]. - Use ln -fs to create a symlink. - Remove pkgadd for docports. - Use WITHOUT_JADETEX=yes instead of WITH_JADETEX=no. - Add {WORLD,KERNEL}_FLAGS to [BTWK]MAKE. - Use makefs(8) and gpart(8) for sparc64 ISO image[2]. - Add publisher option to makefs(8)[2]. Based on work by: gjb[1] Discussed with: marius, nwhitehorn[2]
2013-02-03 10:26:24 +00:00
${BMAKEENV} ${MAKE} ${WORLD_FLAGS} -f Makefile.inc1 \
Fix "make world DESTDIR=/mnt" to work again. A recent change to make(1) that causes command-line variables to be passed as command-line variables to sub-processes that make(1) executes broke it. By changing the type of all DESTDIR variables used internally in Makefile.inc1, from environment to command-line variables of the highest priority, I was able to "make world" with success, with the command-line variable DESTDIR set.
2004-08-25 22:06:29 +00:00
DESTDIR= \
Take __FreeBSD_version into account when BOOTSTRAPPING.
2002-11-13 13:49:29 +00:00
BOOTSTRAPPING=${OSRELDATE} \
Revert r267233 for now. PIE support needs to be reworked. 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
2014-08-19 15:04:32 +00:00
SSP_CFLAGS= \
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
MK_HTML=no NO_LINT=yes MK_MAN=no \
Spell NO_PROFILE= as MK_PROFILE=no.
2014-04-25 19:25:26 +00:00
-DNO_PIC MK_PROFILE=no -DNO_SHARED \
Eliminate EARLY_BUILD flag. It is redundant and means MK_CLANG_FULL=no and MK_LLDB=no, so set those explicitly (now that we can do that). Simplify tests for these variables as well, since we know they will always be defined regardless of the phase of the build.
2014-05-10 16:38:03 +00:00
-DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no \
Don't build full clang toolchain or clang extras in stages 1-3 of buildworld MFC after: 1 week Reviewed by: dim (as part of a "larger" diff) Phabric: D1336 Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:26:10 +00:00
MK_CLANG_EXTRAS=no MK_CLANG_FULL=no \
Force MK_INCLUDES for the legacy stage As legacy executes "make installincludes" we don't want it to be disabled by a src.conf setting. Reviewed by: imp MFC after: 1 month Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D2143
2015-03-25 20:57:08 +00:00
MK_LLDB=no MK_TESTS=no \
MK_INCLUDES=yes
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# build-tools stage
Migrate to a new way of dealing with building from old revisions of 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.
2003-04-05 20:30:30 +00:00
TMAKE= MAKEOBJDIRPREFIX=${OBJTREE} \
- Add CHECKSUM.* support in Makefile[1]. - Use ln -fs to create a symlink. - Remove pkgadd for docports. - Use WITHOUT_JADETEX=yes instead of WITH_JADETEX=no. - Add {WORLD,KERNEL}_FLAGS to [BTWK]MAKE. - Use makefs(8) and gpart(8) for sparc64 ISO image[2]. - Add publisher option to makefs(8)[2]. Based on work by: gjb[1] Discussed with: marius, nwhitehorn[2]
2013-02-03 10:26:24 +00:00
${BMAKEENV} ${MAKE} ${WORLD_FLAGS} -f Makefile.inc1 \
Previous revision wasn't enough for "make TARGET=<machine> build*" 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.
2006-09-08 10:09:02 +00:00
TARGET=${TARGET} TARGET_ARCH=${TARGET_ARCH} \
Fix "make world DESTDIR=/mnt" to work again. A recent change to make(1) that causes command-line variables to be passed as command-line variables to sub-processes that make(1) executes broke it. By changing the type of all DESTDIR variables used internally in Makefile.inc1, from environment to command-line variables of the highest priority, I was able to "make world" with success, with the command-line variable DESTDIR set.
2004-08-25 22:06:29 +00:00
DESTDIR= \
+ DTrace as a bootstrap tool is only needed on certain older systems. + Be more consistent between BMAKE and TMAKE. + Add NO_CTF to crosstools as is done for bootstrap and build tools. Reviewed by: marcel
2011-05-11 17:50:19 +00:00
BOOTSTRAPPING=${OSRELDATE} \
Revert r267233 for now. PIE support needs to be reworked. 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
2014-08-19 15:04:32 +00:00
SSP_CFLAGS= \
+ DTrace as a bootstrap tool is only needed on certain older systems. + Be more consistent between BMAKE and TMAKE. + Add NO_CTF to crosstools as is done for bootstrap and build tools. Reviewed by: marcel
2011-05-11 17:50:19 +00:00
-DNO_LINT \
Don't build full clang toolchain or clang extras in stages 1-3 of buildworld MFC after: 1 week Reviewed by: dim (as part of a "larger" diff) Phabric: D1336 Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:26:10 +00:00
-DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no \
MK_CLANG_EXTRAS=no MK_CLANG_FULL=no \
MK_LLDB=no MK_TESTS=no
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
Fixed buildworld stages names in comments.
2003-04-06 21:23:02 +00:00
# cross-tools stage
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
XMAKE= TOOLS_PREFIX=${WORLDTMP} ${BMAKE} \
While experimenting with cross-building by specifying just TARGET, 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.
2006-09-07 20:27:56 +00:00
TARGET=${TARGET} TARGET_ARCH=${TARGET_ARCH} \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
MK_GDB=no MK_TESTS=no
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
This change builds kernel tools based on the same assumption as building the kernel itself: If building for the same architecture as the build host, the kernel build assumes that the host toolchain is capable of building the kernel. If it's not, "make kernel-toolchain" will bootstrap a new set of tools that will work. With this change the same assumptions are made for building kernel tools, and the existing host toolchain is used to do the build (notably, the build doesn't link the tools with the legacy libraries, which may not even exist). If ever for some reason the host toolchain isn't capable of building the kernel tools, then doing a "make kernel-toolchain" will bootstrap newer tools to get the job done. So when built as part of buildworld or kernel-toolchain, the kernel tools are built using the XMAKE (via BMAKE) commands and environment. When built as part of building just the kernel on a same-target host, the tools are built using the new KTMAKE commands and environment. What doesn't jump out at you in the diffs is that the difference between BMAKE and KTMAKE is that BMAKE contains this magic line which changes how the build is done because it changes what files get included for .include <bsd.prog.mk> and other standard includes: MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}" and KTMAKE doesn't, and contains this instead: TOOLS_PREFIX=${WORLDTMP} Hopefully this brings the "how to build aicasm with the right toolchain" saga to a conclusion that works in all usage scenarios that have historically been supported.
2013-11-09 00:15:36 +00:00
# kernel-tools stage
KTMAKEENV= INSTALL="sh ${.CURDIR}/tools/install.sh" \
PATH=${BPATH}:${PATH} \
WORLDTMP=${WORLDTMP} \
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
VERSION="${VERSION}"
This change builds kernel tools based on the same assumption as building the kernel itself: If building for the same architecture as the build host, the kernel build assumes that the host toolchain is capable of building the kernel. If it's not, "make kernel-toolchain" will bootstrap a new set of tools that will work. With this change the same assumptions are made for building kernel tools, and the existing host toolchain is used to do the build (notably, the build doesn't link the tools with the legacy libraries, which may not even exist). If ever for some reason the host toolchain isn't capable of building the kernel tools, then doing a "make kernel-toolchain" will bootstrap newer tools to get the job done. So when built as part of buildworld or kernel-toolchain, the kernel tools are built using the XMAKE (via BMAKE) commands and environment. When built as part of building just the kernel on a same-target host, the tools are built using the new KTMAKE commands and environment. What doesn't jump out at you in the diffs is that the difference between BMAKE and KTMAKE is that BMAKE contains this magic line which changes how the build is done because it changes what files get included for .include <bsd.prog.mk> and other standard includes: MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}" and KTMAKE doesn't, and contains this instead: TOOLS_PREFIX=${WORLDTMP} Hopefully this brings the "how to build aicasm with the right toolchain" saga to a conclusion that works in all usage scenarios that have historically been supported.
2013-11-09 00:15:36 +00:00
KTMAKE= TOOLS_PREFIX=${WORLDTMP} MAKEOBJDIRPREFIX=${WORLDTMP} \
${KTMAKEENV} ${MAKE} ${WORLD_FLAGS} -f Makefile.inc1 \
DESTDIR= \
BOOTSTRAPPING=${OSRELDATE} \
Revert r267233 for now. PIE support needs to be reworked. 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
2014-08-19 15:04:32 +00:00
SSP_CFLAGS= \
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
MK_HTML=no -DNO_LINT MK_MAN=no \
Spell NO_PROFILE= as MK_PROFILE=no.
2014-04-25 19:25:26 +00:00
-DNO_PIC MK_PROFILE=no -DNO_SHARED \
Eliminate EARLY_BUILD flag. It is redundant and means MK_CLANG_FULL=no and MK_LLDB=no, so set those explicitly (now that we can do that). Simplify tests for these variables as well, since we know they will always be defined regardless of the phase of the build.
2014-05-10 16:38:03 +00:00
-DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no
This change builds kernel tools based on the same assumption as building the kernel itself: If building for the same architecture as the build host, the kernel build assumes that the host toolchain is capable of building the kernel. If it's not, "make kernel-toolchain" will bootstrap a new set of tools that will work. With this change the same assumptions are made for building kernel tools, and the existing host toolchain is used to do the build (notably, the build doesn't link the tools with the legacy libraries, which may not even exist). If ever for some reason the host toolchain isn't capable of building the kernel tools, then doing a "make kernel-toolchain" will bootstrap newer tools to get the job done. So when built as part of buildworld or kernel-toolchain, the kernel tools are built using the XMAKE (via BMAKE) commands and environment. When built as part of building just the kernel on a same-target host, the tools are built using the new KTMAKE commands and environment. What doesn't jump out at you in the diffs is that the difference between BMAKE and KTMAKE is that BMAKE contains this magic line which changes how the build is done because it changes what files get included for .include <bsd.prog.mk> and other standard includes: MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}" and KTMAKE doesn't, and contains this instead: TOOLS_PREFIX=${WORLDTMP} Hopefully this brings the "how to build aicasm with the right toolchain" saga to a conclusion that works in all usage scenarios that have historically been supported.
2013-11-09 00:15:36 +00:00
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# world stage
WMAKEENV= ${CROSSENV} \
- No need to create libfoo.so -> libfoo.so.X symlinks in /lib, as it was decided that our toolchain will revert to looking for libraries in /usr/lib only. - Make /usr/lib/libfoo.so -> /lib/libfoo.so.X symlinks absolute so that they still work if /usr is symlinked. - Remove stale /usr/lib/libfoo.so.X libraries during install. Discussed with: gordon, obrien, peter
2003-09-07 14:15:40 +00:00
_SHLIBDIRPREFIX=${WORLDTMP} \
Introduce the ${SHLIB_LDSCRIPT} variable to have an ld(1) script instead of a symlink for .so files. Reviewed by: kib, kan (previous version), dim Approved by: kib (mentor) Silence from: -hackers@ MFC after: 1 week
2012-05-07 09:00:30 +00:00
_LDSCRIPTROOT= \
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
VERSION="${VERSION}" \
Revert gratuitous change in rev. 1.123 which broke building world as non-root. Breakage caused by: green
2000-01-11 16:23:51 +00:00
INSTALL="sh ${.CURDIR}/tools/install.sh" \
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
PATH=${TMPPATH}
Simplify the hierarchy target's logic. [0] Run hierarchy with WORLDTMP in the path so it works when it is invoked directly. Such use is nearly alwasy wrong but appears to be common.[1] PR: conf/178209 [0], conf/178547 [1] Submitted by: Garrett Cooper <yaneurabeya@gmail.com> [0] MFC after: 5 days
2013-06-14 22:32:47 +00:00
# make hierarchy
- Fix LOCAL_MTREE so it properly handles multiple files and quotes its value into submakes PR: conf/179466 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> Approved by: bapt MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2013-08-30 01:32:47 +00:00
HMAKE= PATH=${TMPPATH} ${MAKE} LOCAL_MTREE=${LOCAL_MTREE:Q}
Simplify the hierarchy target's logic. [0] Run hierarchy with WORLDTMP in the path so it works when it is invoked directly. Such use is nearly alwasy wrong but appears to be common.[1] PR: conf/178209 [0], conf/178547 [1] Submitted by: Garrett Cooper <yaneurabeya@gmail.com> [0] MFC after: 5 days
2013-06-14 22:32:47 +00:00
.if defined(NO_ROOT)
HMAKE+= PATH=${TMPPATH} METALOG=${METALOG} -DNO_ROOT
.endif
Remove explicit setting of NO_CTF in WMAKEENV and in the make call for the buildkernel. This way makeoptions WITH_CTF=yes not only works when compiling the tradtitional way, but also when using buildkernel. This does not enable the CTF part of the world, it still defaults to without CTF info. The cross/build-tools/bootstrap targets are not affected by this, they still have and should keep the explicit NO_CTF. Notified by: np
2010-04-22 09:30:02 +00:00
.if ${MK_CDDL} == "no"
Remove NO_CTF, exccept as an undocumented compatibility option. Convert all other uses to MK_CTF=no. Set MK_CTF=no rather than the indirect WITHOUT_CDDL in filemon regression. It is expected that NO_CTF will be removed in FreeBSD 12 entirely.
2014-04-25 19:25:00 +00:00
WMAKEENV+= MK_CTF=no
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
.endif
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
Add CROSS_TOOLCHAIN macro select pre seeded external toolchain configuration files The goal is to provide pre seeded toolchain configurations withing the ports tree to allow the use of an external toolchain in a simple way: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc TARGET_ARCH=powerpc64 buildworld This will look for the external toolchain definition in /usr/local/share/mk/powerpc64-gcc.mk While here add the notion of X_COMPILER_TYPE to the external toolchain framework to allow to deal with differences between gcc and clang in regards of cross building
2014-10-09 09:04:01 +00:00
.if defined(CROSS_TOOLCHAIN)
LOCALBASE?= /usr/local
.include "${LOCALBASE}/share/toolchains/${CROSS_TOOLCHAIN}.mk"
.endif
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.if defined(CROSS_TOOLCHAIN_PREFIX)
CROSS_COMPILER_PREFIX?=${CROSS_TOOLCHAIN_PREFIX}
CROSS_BINUTILS_PREFIX?=${CROSS_TOOLCHAIN_PREFIX}
.endif
Provide automatic cross-binutils path if no BINUTILS_BOOTSTRAP The in-tree binutils does not support arm64, so will not work for the forthcoming FreeBSD arm64 port. BROKEN_OPTIONS will include BINUTILS_BOOTSTRAP, so provide a default CROSS_BINUTILS_PREFIX for this case. Reviewed by: imp Sponsored by: The FreeBSD Foundation
2015-03-12 08:40:32 +00:00
# If we do not have a bootstrap binutils (because the in-tree one does not
# support the target architecture), provide a default cross-binutils prefix.
# This allows aarch64 builds, for example, to automatically use the
# aarch64-binutils port or package.
.if !empty(BROKEN_OPTIONS:MBINUTILS_BOOTSTRAP) && \
!defined(CROSS_BINUTILS_PREFIX)
CROSS_BINUTILS_PREFIX=/usr/local/${TARGET_ARCH}-freebsd/bin/
.if !exists(${CROSS_BINUTILS_PREFIX})
.error In-tree binutils does not support the ${TARGET_ARCH} architecture. Install the ${TARGET_ARCH}-binutils port or package or set CROSS_BINUTILS_PREFIX.
.endif
.endif
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
XCOMPILERS= CC CXX CPP
.for COMPILER in ${XCOMPILERS}
.if defined(CROSS_COMPILER_PREFIX)
X${COMPILER}?= ${CROSS_COMPILER_PREFIX}${${COMPILER}}
.else
X${COMPILER}?= ${${COMPILER}}
.endif
.endfor
Add size(1) to the cross build toolchain
2014-10-09 15:52:01 +00:00
XBINUTILS= AS AR LD NM OBJCOPY OBJDUMP RANLIB SIZE STRINGS
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.for BINUTIL in ${XBINUTILS}
Only use the CROSS_BINUTILS_PREFIX tool if it exists. Reviewed by: emaste Sponsored by: The FreeBSD Foundation
2015-04-02 17:03:02 +00:00
.if defined(CROSS_BINUTILS_PREFIX) && \
exists(${CROSS_BINUTILS_PREFIX}${${BINUTIL}})
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
X${BINUTIL}?= ${CROSS_BINUTILS_PREFIX}${${BINUTIL}}
.else
X${BINUTIL}?= ${${BINUTIL}}
.endif
.endfor
Rename XFLAGS to XCFLAGS and XXFLAGS to XCXXFLAGS This is less confusing names and actually more reflexting what they are intended to. Discussed with: brooks
2014-10-27 23:31:07 +00:00
WMAKEENV+= CC="${XCC} ${XCFLAGS}" CXX="${XCXX} ${XCFLAGS} ${XCXXFLAGS}" \
Make the external toolchain support grows to the knowleged of XXFLAGS for C++ dedicated flags and DEPFLAGS for mkdep flags Pass the path to the libc++ headers in both, enforce the gnu++11 standard in the XXFLAGS to satisfy libc++ requirements pass the libc++ objectdir as a location where to find libraries so it can find libstdc++.so and libstdc++.A Reviewed by: imp
2014-10-21 20:07:15 +00:00
DEPFLAGS="${DEPFLAGS}" \
Rename XFLAGS to XCFLAGS and XXFLAGS to XCXXFLAGS This is less confusing names and actually more reflexting what they are intended to. Discussed with: brooks
2014-10-27 23:31:07 +00:00
CPP="${XCPP} ${XCFLAGS}" \
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
AS="${XAS}" AR="${XAR}" LD="${XLD}" NM=${XNM} \
Fix typo
2014-10-09 12:20:00 +00:00
OBJDUMP=${XOBJDUMP} OBJCOPY="${XOBJCOPY}" \
Add size(1) to the cross build toolchain
2014-10-09 15:52:01 +00:00
RANLIB=${XRANLIB} STRINGS=${XSTRINGS} \
SIZE="${XSIZE}"
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.if ${XCC:M/*}
.if defined(CROSS_BINUTILS_PREFIX)
# In the case of xdev-build tools, CROSS_BINUTILS_PREFIX won't be a
# directory, but the compiler will look in the right place for it's
# tools so we don't need to tell it where to look.
.if exists(${CROSS_BINUTILS_PREFIX})
Restore the ability to use clang as an external compiler. This was inadvertently removed when support for external GCC was added. Deprecate XFLAGS in favour of the newer XCFLAGS/XCXXFLAGS. Tested with: make universe, make CROSS_COMPILER_PREFIX=/usr/bin/ buildworld Reviewed by: imp, bapt
2015-02-18 19:27:51 +00:00
BFLAGS+= -B${CROSS_BINUTILS_PREFIX}
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.endif
.else
Restore the ability to use clang as an external compiler. This was inadvertently removed when support for external GCC was added. Deprecate XFLAGS in favour of the newer XCFLAGS/XCXXFLAGS. Tested with: make universe, make CROSS_COMPILER_PREFIX=/usr/bin/ buildworld Reviewed by: imp, bapt
2015-02-18 19:27:51 +00:00
BFLAGS+= -B${WORLDTMP}/usr/bin
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.endif
Remove MK_ARM_EABI, the armeb issues have been fixed. The code to support the oabi is still in the tree, but it is expected this will be removed as developers work on surrounding code. With this commit the ARM EABI is the only supported supported ABI by FreeBSD on ARMa 32-bit processors. X-MFC after: never Relnotes: yes Differential Revision: https://reviews.freebsd.org/D876
2014-10-01 08:26:51 +00:00
.if ${TARGET} == "arm"
Fix the TARGET_ABI value clang uses. It shpuld be gnueabi on all ARM soft-float architectures, and gnueabihf for hard-float.
2014-10-01 12:47:25 +00:00
.if ${TARGET_ARCH:M*hf*} != ""
Add a new ARM TARGET_ARCH, armv6hf. This is considered experimental. This targets the existing ARMv6 and ARMv7 SoCs that contain a VFP unit. This is an optional coprocessors may not be present in all devices, however it appears to be in all current SoCs we support. armv6hf targets the VFP variant of the ARM EABI and our copy of gcc is too old to support this. Because of this there are a number of WITH/WITHOUT options that are unsupported and must be left as the default value. The options and their required value are: * WITH_ARM_EABI * WITHOUT_GCC * WITHOUT_GNUCXX In addition, without an external toolchain, the following need to be left as their default: * WITH_CLANG * WITH_CLANG_IS_CC As there is a different method of passing float and double values to functions the ABI is incompatible with existing armv6 binaries. To use this a full rebuild of world is required. Because no floating point values are passed into the kernel an armv6 kernel with VFP enabled will work with an armv6hf userland and vice versa.
2014-03-23 12:49:25 +00:00
TARGET_ABI= gnueabihf
Fix the TARGET_ABI value clang uses. It shpuld be gnueabi on all ARM soft-float architectures, and gnueabihf for hard-float.
2014-10-01 12:47:25 +00:00
.else
TARGET_ABI= gnueabi
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.endif
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
.endif
Fix build when XCC is defined and X_COMPILER_TYPE is not
2014-10-09 09:46:44 +00:00
.if defined(X_COMPILER_TYPE) && ${X_COMPILER_TYPE} == gcc
Rename XFLAGS to XCFLAGS and XXFLAGS to XCXXFLAGS This is less confusing names and actually more reflexting what they are intended to. Discussed with: brooks
2014-10-27 23:31:07 +00:00
XCFLAGS+= -isystem ${WORLDTMP}/usr/include -L${WORLDTMP}/usr/lib
XCXXFLAGS+= -I${WORLDTMP}/usr/include/c++/v1 -std=gnu++11 -L${WORLDTMP}/../lib/libc++
Make the external toolchain support grows to the knowleged of XXFLAGS for C++ dedicated flags and DEPFLAGS for mkdep flags Pass the path to the libc++ headers in both, enforce the gnu++11 standard in the XXFLAGS to satisfy libc++ requirements pass the libc++ objectdir as a location where to find libraries so it can find libstdc++.so and libstdc++.A Reviewed by: imp
2014-10-21 20:07:15 +00:00
DEPFLAGS+= -I${WORLDTMP}/usr/include/c++/v1
Add CROSS_TOOLCHAIN macro select pre seeded external toolchain configuration files The goal is to provide pre seeded toolchain configurations withing the ports tree to allow the use of an external toolchain in a simple way: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc TARGET_ARCH=powerpc64 buildworld This will look for the external toolchain definition in /usr/local/share/mk/powerpc64-gcc.mk While here add the notion of X_COMPILER_TYPE to the external toolchain framework to allow to deal with differences between gcc and clang in regards of cross building
2014-10-09 09:04:01 +00:00
.else
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
TARGET_ABI?= unknown
Bump OS versions in the toolchain triples to 11.0, and bump the __FreeBSD_cc_version predefined macros in clang and gcc. Approved by: re (gjb)
2013-10-10 20:47:11 +00:00
TARGET_TRIPLE?= ${TARGET_ARCH:C/amd64/x86_64/}-${TARGET_ABI}-freebsd11.0
Rename XFLAGS to XCFLAGS and XXFLAGS to XCXXFLAGS This is less confusing names and actually more reflexting what they are intended to. Discussed with: brooks
2014-10-27 23:31:07 +00:00
XCFLAGS+= -target ${TARGET_TRIPLE}
Add --sysroot to the compiler flags for clang or gcc external toolchains Before this fix, --sysroot was only added to the compiler flags if a clang external toolchain was used. Reviewed by: imp
2015-03-26 23:37:03 +00:00
.endif
Restore the ability to use clang as an external compiler. This was inadvertently removed when support for external GCC was added. Deprecate XFLAGS in favour of the newer XCFLAGS/XCXXFLAGS. Tested with: make universe, make CROSS_COMPILER_PREFIX=/usr/bin/ buildworld Reviewed by: imp, bapt
2015-02-18 19:27:51 +00:00
XCFLAGS+= --sysroot=${WORLDTMP} ${BFLAGS}
XCXXFLAGS+= --sysroot=${WORLDTMP} ${BFLAGS}
Support CROSS_BINUTILS_PREFIX with in-tree compiler Reviewed by: bapt, imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1974
2015-02-26 20:02:29 +00:00
.else
.if defined(CROSS_BINUTILS_PREFIX) && exists(${CROSS_BINUTILS_PREFIX})
BFLAGS+= -B${CROSS_BINUTILS_PREFIX}
XCFLAGS+= ${BFLAGS}
XCXXFLAGS+= ${BFLAGS}
Add CROSS_TOOLCHAIN macro select pre seeded external toolchain configuration files The goal is to provide pre seeded toolchain configurations withing the ports tree to allow the use of an external toolchain in a simple way: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc TARGET_ARCH=powerpc64 buildworld This will look for the external toolchain definition in /usr/local/share/mk/powerpc64-gcc.mk While here add the notion of X_COMPILER_TYPE to the external toolchain framework to allow to deal with differences between gcc and clang in regards of cross building
2014-10-09 09:04:01 +00:00
.endif
Support CROSS_BINUTILS_PREFIX with in-tree compiler Reviewed by: bapt, imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1974
2015-02-26 20:02:29 +00:00
.endif # ${XCC:M/*}
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
- Add CHECKSUM.* support in Makefile[1]. - Use ln -fs to create a symlink. - Remove pkgadd for docports. - Use WITHOUT_JADETEX=yes instead of WITH_JADETEX=no. - Add {WORLD,KERNEL}_FLAGS to [BTWK]MAKE. - Use makefs(8) and gpart(8) for sparc64 ISO image[2]. - Add publisher option to makefs(8)[2]. Based on work by: gjb[1] Discussed with: marius, nwhitehorn[2]
2013-02-03 10:26:24 +00:00
WMAKE= ${WMAKEENV} ${MAKE} ${WORLD_FLAGS} -f Makefile.inc1 DESTDIR=${WORLDTMP}
Restore the upgrade path from -stable to -current and prepare for non-root cross-building. o Makefile.inc0 is not used anymore. o The legacy aout build has been removed. o Selectively build tools *before* building includes/libraries. o Avoid using mtree to populate the obj tree.
1999-12-08 13:45:11 +00:00
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "powerpc64"
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
# 32 bit world
Root the lib32 object tree under the overall object tree. This enables a common root directory for all object files for a given tree, which eases sharing a common MAKEOBJDIRPREFIX, and cleaning up of object trees. In particular, one can simply (from the source directory) rm -rf /usr/obj$(pwd) to destroy all object files for it. Or to copy/sync files, etc. Reviewed by: bdrewery CR: https://reviews.freebsd.org/D796 MFC after: 1 month Sponsored by: Spectra Logic
2014-09-18 01:57:36 +00:00
LIB32_OBJTREE= ${OBJTREE}${.CURDIR}/world32
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
LIB32TMP= ${OBJTREE}${.CURDIR}/lib32
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if ${TARGET_ARCH} == "amd64"
Use cross-compile friendly spelling of CPUTYPE. Submitted by: ru
2005-12-07 22:55:29 +00:00
.if empty(TARGET_CPUTYPE)
If a CPUTYPE isn't specified, then don't use -march=k8 when compiling 32-bit compat libs on amd64 since -march=k8 may generate instructions that are not implemented on Intel EM64T processors. Instead, use a simpler set of default flags that should work on all amd64-capable CPUs. PR: amd64/113111 Submitted by: NIIMI Satoshi sa2c of sa2c.net MFC after: 1 week
2008-08-19 14:23:26 +00:00
LIB32CPUFLAGS= -march=i686 -mmmx -msse -msse2
Default to producing 'k8' COMPAT_32BIT bits, but allow override.
2005-12-07 17:41:10 +00:00
.else
If a CPUTYPE isn't specified, then don't use -march=k8 when compiling 32-bit compat libs on amd64 since -march=k8 may generate instructions that are not implemented on Intel EM64T processors. Instead, use a simpler set of default flags that should work on all amd64-capable CPUs. PR: amd64/113111 Submitted by: NIIMI Satoshi sa2c of sa2c.net MFC after: 1 week
2008-08-19 14:23:26 +00:00
LIB32CPUFLAGS= -march=${TARGET_CPUTYPE}
Default to producing 'k8' COMPAT_32BIT bits, but allow override.
2005-12-07 17:41:10 +00:00
.endif
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
LIB32WMAKEENV= MACHINE=i386 MACHINE_ARCH=i386 \
Fix 32-bit library builds after the removal of adding -E to make for AS, CC, CXX and LD. This fix implements the intended as it should have been implemented all along: by passing AS, CC, CXX and LD on the commandline of the sub-make instead of in the environment of the sub-make. Breakage pointed-out by: dim@
2012-10-07 16:45:38 +00:00
MACHINE_CPU="i686 mmx sse sse2"
LIB32WMAKEFLAGS= \
Ensure the cross assembler, linker and objcopy are used for the build32 stage, just like for the regular world stage. Reviewed by: rodrigc, imp, bapt, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D2187
2015-04-02 06:58:17 +00:00
AS="${XAS} --32" \
LD="${XLD} -m elf_i386_fbsd -Y P,${LIB32TMP}/usr/lib32" \
OBJCOPY="${XOBJCOPY}"
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.elif ${TARGET_ARCH} == "powerpc64"
.if empty(TARGET_CPUTYPE)
LIB32CPUFLAGS= -mcpu=powerpc
.else
LIB32CPUFLAGS= -mcpu=${TARGET_CPUTYPE}
.endif
Fix 32-bit library builds after the removal of adding -E to make for AS, CC, CXX and LD. This fix implements the intended as it should have been implemented all along: by passing AS, CC, CXX and LD on the commandline of the sub-make instead of in the environment of the sub-make. Breakage pointed-out by: dim@
2012-10-07 16:45:38 +00:00
LIB32WMAKEENV= MACHINE=powerpc MACHINE_ARCH=powerpc
LIB32WMAKEFLAGS= \
Ensure the cross assembler, linker and objcopy are used for the build32 stage, just like for the regular world stage. Reviewed by: rodrigc, imp, bapt, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D2187
2015-04-02 06:58:17 +00:00
LD="${XLD} -m elf32ppc_fbsd" \
OBJCOPY="${XOBJCOPY}"
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.endif
LIB32FLAGS= -m32 ${LIB32CPUFLAGS} -DCOMPAT_32BIT \
Replace -iprefix with -isystem. We only need alternative header files search path and thus -isystem is sufficient. -iprefix is meant to do something entirely different. Approved by: ed (mentor) OKed by: ru, kan Tested by: make universe
2009-11-01 08:20:30 +00:00
-isystem ${LIB32TMP}/usr/include/ \
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
-L${LIB32TMP}/usr/lib32 \
-B${LIB32TMP}/usr/lib32
Restore the ability to build on systems with 32-bit compat when the system compiler is not clang. clang and gcc appear to differ signficantly in their interpretation of -isystem and --sysroot. Further work is likely required to support an external gcc. Reported by: andreast, fidaj@ukr.net, sergey.dyatko@gmail.com
2013-05-21 16:58:23 +00:00
.if ${XCC:M/*}
LIB32FLAGS+= --sysroot=${WORLDTMP}
.endif
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
# Yes, the flags are redundant.
Root the lib32 object tree under the overall object tree. This enables a common root directory for all object files for a given tree, which eases sharing a common MAKEOBJDIRPREFIX, and cleaning up of object trees. In particular, one can simply (from the source directory) rm -rf /usr/obj$(pwd) to destroy all object files for it. Or to copy/sync files, etc. Reviewed by: bdrewery CR: https://reviews.freebsd.org/D796 MFC after: 1 month Sponsored by: Spectra Logic
2014-09-18 01:57:36 +00:00
LIB32WMAKEENV+= MAKEOBJDIRPREFIX=${LIB32_OBJTREE} \
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
_SHLIBDIRPREFIX=${LIB32TMP} \
Introduce the ${SHLIB_LDSCRIPT} variable to have an ld(1) script instead of a symlink for .so files. Reviewed by: kib, kan (previous version), dim Approved by: kib (mentor) Silence from: -hackers@ MFC after: 1 week
2012-05-07 09:00:30 +00:00
_LDSCRIPTROOT=${LIB32TMP} \
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
VERSION="${VERSION}" \
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
INSTALL="sh ${.CURDIR}/tools/install.sh" \
PATH=${TMPPATH} \
LIBDIR=/usr/lib32 \
Introduce a new make variable COMPILER_TYPE that specifies what type of compiler is being used (currently clang or gcc). COMPILER_TYPE is set in the new bsd.compiler.mk file based on the value of the CC variable or, should it prove informative, by running ${CC} --version and examining the output. To avoid negative performance impacts in the default case and correct value for COMPILER_TYPE type is determined and passed in the environment of submake instances while building world. Replace adhoc attempts at determining the compiler type by examining CC or MK_CLANG_IS_CC with checks of COMPILER_TYPE. This eliminates bootstrapping complications when first setting WITH_CLANG_IS_CC. Sponsored by: DARPA, AFRL Reviewed by: Yamaya Takashi <yamayan@kbh.biglobe.ne.jp>, imp, linimon (with some modifications post review) MFC after: 2 weeks
2012-09-13 16:00:46 +00:00
SHLIBDIR=/usr/lib32 \
Run dtrace in 32-bit mode when compiling 32-bit libraries. MFC after: 3 days
2014-08-08 23:55:22 +00:00
LIBPRIVATEDIR=/usr/lib32/private \
DTRACE="${DTRACE} -32"
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
LIB32WMAKEFLAGS+= CC="${XCC} ${LIB32FLAGS}" \
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
CXX="${XCXX} ${LIB32FLAGS}" \
Fix 32-bit library builds after the removal of adding -E to make for AS, CC, CXX and LD. This fix implements the intended as it should have been implemented all along: by passing AS, CC, CXX and LD on the commandline of the sub-make instead of in the environment of the sub-make. Breakage pointed-out by: dim@
2012-10-07 16:45:38 +00:00
DESTDIR=${LIB32TMP} \
-DCOMPAT_32BIT \
Add a new LIBRARIES_ONLY make variable to disable the build and install of files other than the actual libraries. Use LIBRARIES_ONLY to supress the inclusion of files in the lib32 distribution that are duplicates of files in base. Sponsored by: DARPA, AFRL Reviewed by: emaste
2013-01-17 17:27:10 +00:00
-DLIBRARIES_ONLY \
Fix 32-bit library builds after the removal of adding -E to make for AS, CC, CXX and LD. This fix implements the intended as it should have been implemented all along: by passing AS, CC, CXX and LD on the commandline of the sub-make instead of in the environment of the sub-make. Breakage pointed-out by: dim@
2012-10-07 16:45:38 +00:00
-DNO_CPU_CFLAGS \
Remove NO_CTF, exccept as an undocumented compatibility option. Convert all other uses to MK_CTF=no. Set MK_CTF=no rather than the indirect WITHOUT_CDDL in filemon regression. It is expected that NO_CTF will be removed in FreeBSD 12 entirely.
2014-04-25 19:25:00 +00:00
MK_CTF=no \
Fix the build so -DNO_TESTS is passed in various phases that don't require tests in order to build or install. Crucially, don't try to install tests during the lib32 install phase. This commit supersedes r261081, which fixed the lib32 install phase problem, but didn't fix other phases. Submitted by: Garrett Cooper Reviewed by: sjg MFC after: 13 days
2014-01-24 18:01:46 +00:00
-DNO_LINT \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
MK_TESTS=no
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
Fix 32-bit library builds after the removal of adding -E to make for AS, CC, CXX and LD. This fix implements the intended as it should have been implemented all along: by passing AS, CC, CXX and LD on the commandline of the sub-make instead of in the environment of the sub-make. Breakage pointed-out by: dim@
2012-10-07 16:45:38 +00:00
LIB32WMAKE= ${LIB32WMAKEENV} ${MAKE} ${LIB32WMAKEFLAGS} \
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
MK_MAN=no MK_HTML=no
Eliminate NO_INCS. It is used one place, and MK_TOOLCHAIN=no will handle the job just as well. Opt for simplicity rather than one more option.
2014-04-25 19:25:45 +00:00
LIB32IMAKE= ${LIB32WMAKE:NINSTALL=*:NDESTDIR=*:N_LDSCRIPTROOT=*} \
MK_TOOLCHAIN=no ${IMAKE_INSTALL}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endif
Introduce the ${SHLIB_LDSCRIPT} variable to have an ld(1) script instead of a symlink for .so files. Reviewed by: kib, kan (previous version), dim Approved by: kib (mentor) Silence from: -hackers@ MFC after: 1 week
2012-05-07 09:00:30 +00:00
IMAKEENV= ${CROSSENV:N_LDSCRIPTROOT=*}
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1 \
There's no need to guess at the COMPILER_TYPE to pass it down. We guess wrong for buildkernel when CC=gcc49, say. Eliminate all the guessing. COMPILER_TYPE propigates properly on its own, if specified, and we guess it correctly otherwise lower in the build. Also, fix conditionals for armv6hf when using an external compiler chain. They were broken before, but unused. Also, prefer checking the compiler type over CLANG_IS_CC since the latter is only supposed to be used to determine what symlinks to install (more fixes to follow).
2014-03-30 23:43:30 +00:00
${IMAKE_INSTALL} ${IMAKE_MTREE}
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
.if empty(.MAKEFLAGS:M-n)
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
IMAKEENV+= PATH=${STRICTTMPPATH}:${INSTALLTMP} \
LD_LIBRARY_PATH=${INSTALLTMP} \
PATH_LOCALE=${INSTALLTMP}/locale
IMAKE+= __MAKE_SHELL=${INSTALLTMP}/sh
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
.else
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
IMAKEENV+= PATH=${TMPPATH}:${INSTALLTMP}
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
.endif
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.if defined(DB_FROM_SRC)
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
INSTALLFLAGS+= -N ${.CURDIR}/etc
MTREEFLAGS+= -N ${.CURDIR}/etc
.endif
Always define INSTALL_DDIR and define it such that it contains no extra / characters rather than removing them later on. This should fix release builds. PR: conf/178963 Reviewed by: gjb, hrs
2013-05-30 14:09:58 +00:00
_INSTALL_DDIR= ${DESTDIR}/${DISTDIR}
INSTALL_DDIR= ${_INSTALL_DDIR:S://:/:g:C:/$::}
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.if defined(NO_ROOT)
METALOG?= ${DESTDIR}/${DISTDIR}/METALOG
IMAKE+= -DNO_ROOT METALOG=${METALOG}
Always define INSTALL_DDIR and define it such that it contains no extra / characters rather than removing them later on. This should fix release builds. PR: conf/178963 Reviewed by: gjb, hrs
2013-05-30 14:09:58 +00:00
INSTALLFLAGS+= -U -M ${METALOG} -D ${INSTALL_DDIR}
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
MTREEFLAGS+= -W
.endif
.if defined(DB_FROM_SRC) || defined(NO_ROOT)
IMAKE_INSTALL= INSTALL="install ${INSTALLFLAGS}"
Merge from CheriBSD: commit 1b41f6de7ca09e04fdc6f66bc478ea6c981a41b9 Author: Brooks Davis <brooks@one-eyed-alien.net> Date: Mon Jan 27 22:59:02 2014 +0000 Now that mtree is always nmtree use it as mtree Tested on: ref9-amd64 X-MFC after: never Sponsored by: DARPA, AFRL
2014-01-30 22:26:51 +00:00
IMAKE_MTREE= MTREE_CMD="mtree ${MTREEFLAGS}"
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.endif
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
As threatened in hackers@ on Friday, obviate the need for a buildworld to preceed a buildkernel. The buildworld is still required when upgrading across major releases, across binutil upgrades and when config changes version. If buildkernel breaks, and you haven't done a buildworld, then do not complain unless you do a buildworld and it still breaks.
2001-01-22 08:07:58 +00:00
# kernel stage
Initiate deorbit burn for the i386-only a.out related support. Moves are under way to move the remnants of the a.out toolchain to ports. As the comment in src/Makefile said, this stuff is deprecated and one should not expect this to remain beyond 4.0-REL. It has already lasted WAY beyond that. Notable exceptions: gcc - I have not touched the a.out generation stuff there. ldd/ldconfig - still have some code to interface with a.out rtld. old as/ld/etc - I have not removed these yet, pending their move to ports. some includes - necessary for ldd/ldconfig for now. Tested on: i386 (extensively), alpha
2002-09-17 01:49:00 +00:00
KMAKEENV= ${WMAKEENV}
Upgrade our copy of llvm/clang to trunk r178860, in preparation of the upcoming 3.3 release (branching and freezing expected in a few weeks). Preliminary release notes can be found at the usual location: <http://llvm.org/docs/ReleaseNotes.html> An MFC is planned once the actual 3.3 release is finished.
2013-04-12 17:57:40 +00:00
KMAKE= ${KMAKEENV} ${MAKE} ${.MAKEFLAGS} ${KERNEL_FLAGS} KERNEL=${INSTKERNNAME}
As threatened in hackers@ on Friday, obviate the need for a buildworld to preceed a buildkernel. The buildworld is still required when upgrading across major releases, across binutil upgrades and when config changes version. If buildkernel breaks, and you haven't done a buildworld, then do not complain unless you do a buildworld and it still breaks.
2001-01-22 08:07:58 +00:00
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# buildworld
#
# Attempt to rebuild the entire system, with reasonable chance of
# success, regardless of how old your existing system is.
#
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_worldtmp:
Don't attempt buildworld if the path to the source-tree contains a comma. Can be removed if the underlying issue is fixed. Submitted by: Flemming Jacobsen <fj@batmule.dk>
2003-02-04 08:15:30 +00:00
.if ${.CURDIR:C/[^,]//g} != ""
# The m4 build of sendmail files doesn't like it if ',' is used
# anywhere in the path of it's files.
@echo
@echo "*** Error: path to source tree contains a comma ','"
@echo
Improved the description of the installkernel targets. Don't hide what we do to force failures for the installkernel targets or other targets.
2004-03-04 09:14:30 +00:00
false
Don't attempt buildworld if the path to the source-tree contains a comma. Can be removed if the underlying issue is fixed. Submitted by: Flemming Jacobsen <fj@batmule.dk>
2003-02-04 08:15:30 +00:00
.endif
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
@echo ">>> Rebuilding the temporary build tree"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
NOCLEAN -> NO_CLEAN NOCLEANDIR -> NO_CLEANDIR
2004-12-21 12:21:26 +00:00
.if !defined(NO_CLEAN)
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
rm -rf ${WORLDTMP}
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP)
- clean ${LIB32TMP} in _worldtmp - clean ${OBJTREE}/lib32 in _cleanobj - ensure that ${WORLDTMP} exists in build32
2005-08-05 23:48:58 +00:00
rm -rf ${LIB32TMP}
.endif
I now don't seem to be able to reproduce the -DNOCLEAN buildworld breakage with ioctl.c. The .depend file should track dependencies just fine, and the worst we can have is to miss new ioctls. But I still think it's a good idea to have -DNOCLEAN build produce the same ioctl.c as it would without -DNOCLEAN. Prodded for a long time by: bde
2002-04-11 14:49:32 +00:00
.else
Put back parts of 1.335 and 1.336 that 1.337 accidentally backed out. Submitted by: ru
2003-04-06 23:46:02 +00:00
rm -rf ${WORLDTMP}/legacy/usr/include
Satisfy a particularly obstinate nit-picker :)
2008-02-05 15:41:58 +00:00
# XXX - These three can depend on any header file.
I now don't seem to be able to reproduce the -DNOCLEAN buildworld breakage with ioctl.c. The .depend file should track dependencies just fine, and the worst we can have is to miss new ioctls. But I still think it's a good idea to have -DNOCLEAN build produce the same ioctl.c as it would without -DNOCLEAN. Prodded for a long time by: bde
2002-04-11 14:49:32 +00:00
rm -f ${OBJTREE}${.CURDIR}/usr.bin/kdump/ioctl.c
Give usr.bin/kdump/kdump_subr.c the same treatment as usr.bin/kdump/ioctl.c 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
2008-02-05 08:56:18 +00:00
rm -f ${OBJTREE}${.CURDIR}/usr.bin/kdump/kdump_subr.c
I now don't seem to be able to reproduce the -DNOCLEAN buildworld breakage with ioctl.c. The .depend file should track dependencies just fine, and the worst we can have is to miss new ioctls. But I still think it's a good idea to have -DNOCLEAN build produce the same ioctl.c as it would without -DNOCLEAN. Prodded for a long time by: bde
2002-04-11 14:49:32 +00:00
rm -f ${OBJTREE}${.CURDIR}/usr.bin/truss/ioctl.c
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
.endif
Only create directories that are really needed.
2003-04-13 14:34:17 +00:00
.for _dir in \
Log the addition of login.conf.db, passwd, pwd.db, and spwd.db via cat -l. Make cat a bootstrap tool to facilitate this.
2013-01-29 22:17:58 +00:00
lib usr legacy/bin legacy/usr
Only create directories that are really needed.
2003-04-13 14:34:17 +00:00
mkdir -p ${WORLDTMP}/${_dir}
Restore the upgrade path from -stable to -current and prepare for non-root cross-building. o Makefile.inc0 is not used anymore. o The legacy aout build has been removed. o Selectively build tools *before* building includes/libraries. o Avoid using mtree to populate the obj tree.
1999-12-08 13:45:11 +00:00
.endfor
- Create the buildworld object directories with mtree instead of various mkdir calls - Remove the ugly workaroung from libc NLS, which was to create some of these directories
2009-03-15 13:14:06 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${WORLDTMP}/legacy/usr >/dev/null
Flesh out WITHOUT_GROFF support to DTRT. A full featured groff is required during buildworld, so build it always and don't rely on it being present on the host system. vgrind(1) is tightly coupled to a roff processor and will not be built/installed when groff is disabled. Also much of the roff'ed documentation under share/doc will not be built/installed when WITHOUT_GROFF is defined. Reviewed by: ru (partial)
2011-02-22 08:13:49 +00:00
.if ${MK_GROFF} != "no"
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.groff.dist \
-p ${WORLDTMP}/legacy/usr >/dev/null
.endif
- Create the buildworld object directories with mtree instead of various mkdir calls - Remove the ugly workaroung from libc NLS, which was to create some of these directories
2009-03-15 13:14:06 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${WORLDTMP}/usr >/dev/null
Unbreak parallel make of _includes after revision 1.356 changes. Spotted by: bde Approved by: re (scottl)
2003-05-18 20:22:26 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
Don't scare non-root users attempting to build world.
2004-03-14 16:44:27 +00:00
-p ${WORLDTMP}/usr/include >/dev/null
Enhancement to 1.99 -> 1.100. Avoid EPERM from ln(1) in a different (proper) way.
2001-03-22 09:54:25 +00:00
ln -sf ${.CURDIR}/sys ${WORLDTMP}
Add a new knob WITH_DEBUG_FILES to control the building of standalone debug files for userland programs and libraries. The "-g" debug flag is automatically applied when WITH_DEBUG_FILES is set. The debug files are now named ${prog}.debug and ${shlib}.debug for consistency with other systems and documentation. In addition they are installed under /usr/lib/debug, to simplify the process of installing them if needed after a crash. Users of bsd.{prog,lib}.mk outside of the base system place the standalone debug files in a .debug subdirectory. GDB automatically searches both of these directories for standalone debug files. Thanks to everyone who contributed changes, review, and testing during development.
2013-06-07 21:40:02 +00:00
.if ${MK_DEBUG_FILES} != "no"
# We could instead disable debug files for these build stages
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.debug.dist \
-p ${WORLDTMP}/legacy/usr/lib >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.debug.dist \
-p ${WORLDTMP}/usr/lib >/dev/null
.endif
Set up the /usr/tests hierarchy. Populate /usr/tests with the only test programs that currently live in the tree (those in lib/libcrypt/tests/) and add all the build machinery to accompany this change. In particular: - Add a WITHOUT_TESTS variable that users can define to request that no tests be put in /usr/tests. - Add a top-level Kyuafile for /usr/tests and a way to create similar Kyuafiles in top-level subdirectories. - Add a BSD.tests.dist file to define the directory layout of /usr/tests. Submitted by: Julio Merino jmmv google.com Reviewed by: sjg MFC after: 2 weeks
2013-10-25 05:25:19 +00:00
.if ${MK_TESTS} != "no"
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
mkdir -p ${WORLDTMP}${TESTSBASE}
Set up the /usr/tests hierarchy. Populate /usr/tests with the only test programs that currently live in the tree (those in lib/libcrypt/tests/) and add all the build machinery to accompany this change. In particular: - Add a WITHOUT_TESTS variable that users can define to request that no tests be put in /usr/tests. - Add a top-level Kyuafile for /usr/tests and a way to create similar Kyuafiles in top-level subdirectories. - Add a BSD.tests.dist file to define the directory layout of /usr/tests. Submitted by: Julio Merino jmmv google.com Reviewed by: sjg MFC after: 2 weeks
2013-10-25 05:25:19 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.tests.dist \
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
-p ${WORLDTMP}${TESTSBASE} >/dev/null
Set up the /usr/tests hierarchy. Populate /usr/tests with the only test programs that currently live in the tree (those in lib/libcrypt/tests/) and add all the build machinery to accompany this change. In particular: - Add a WITHOUT_TESTS variable that users can define to request that no tests be put in /usr/tests. - Add a top-level Kyuafile for /usr/tests and a way to create similar Kyuafiles in top-level subdirectories. - Add a BSD.tests.dist file to define the directory layout of /usr/tests. Submitted by: Julio Merino jmmv google.com Reviewed by: sjg MFC after: 2 weeks
2013-10-25 05:25:19 +00:00
.endif
Allow LOCAL_(DIRS,LIBS) to install files in directories not found in the system mtree files via a LOCAL_MTREE variable which contains a list of mtree files to be applyed along with the base mtree files to the tmp root and DESTDIR.
2012-10-18 12:32:51 +00:00
.for _mtree in ${LOCAL_MTREE}
mtree -deU -f ${.CURDIR}/${_mtree} -p ${WORLDTMP} > /dev/null
.endfor
-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien.
2003-04-06 21:46:44 +00:00
_legacy:
We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. This 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@
2003-04-06 03:50:28 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 1.1: legacy release compatibility shims"
We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. This 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@
2003-04-06 03:50:28 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${BMAKE} legacy
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_bootstrap-tools:
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 1.2: bootstrap tools"
More cross-building related changes: o Build tools before doing anything in or with the object tree. o Tools don't use the object tree any more, but have there object tree located in the temp. world. o Use the proper make env. for cleaning and building the object tree. o Don't create kernel include subdirectories in the temp. world. These are removed later on and replaced by symlinks. o Change the layout of the object tree: The temp. world now is /usr/obj/${MACHINE_ARCH}${.CURDIR}/${BUILD_ARCH}. /usr/obj can be set/changed by using MAKEOBJDIRPREFIX, and {.CURDIR} obviously depends on where the source tree is located. MACHINE_ARCH is the arch. for which the world is to be build and BUILD_ARCH is the arch. on which we are building. The object tree now is /usr/obj/${MACHINE_ARCH}${.CURDIR}. This allows concurrent cross-builds and allows the object tree to be shared on different archs., each doing the same cross-build. This of course assumes that the output on Alpha (for example) is the same as the output of an Alpha cross-build on i386 (for example). The use of NOCLEAN is is still dangerous, but should be usable in many more situations than before. It should now be possible to safely restart an interrupted build with NOCLEAN without side-effects. Because the tools don't share the object tree with the normal (cross-build), no tools have to be rebuild.
1999-12-10 10:48:20 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${BMAKE} bootstrap-tools
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_cleanobj:
NOCLEAN -> NO_CLEAN NOCLEANDIR -> NO_CLEANDIR
2004-12-21 12:21:26 +00:00
.if !defined(NO_CLEAN)
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 2.1: cleaning up the object tree"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${WMAKE} ${CLEANDIR:S/^/par-/}
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP)
Resurrect one of the patches from attic and refine the 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
2007-02-28 20:06:21 +00:00
${_+_}cd ${.CURDIR}; ${LIB32WMAKE} -f Makefile.inc1 ${CLEANDIR:S/^/par-/}
- clean ${LIB32TMP} in _worldtmp - clean ${OBJTREE}/lib32 in _cleanobj - ensure that ${WORLDTMP} exists in build32
2005-08-05 23:48:58 +00:00
.endif
Backed out rev.1.49. It broke bootstrapping from 2.1.5 2.2.7 and probably other versions by spamming ${DESTDIR}/usr/include in much the same way as `make includes'. Details for 2.2.7: the bootstrap target has always done a weak spam of ${DESTDIR}/usr/include; we depend on it not installing any significant anachronisms (it probably shouldn't touch the headers at all; however, we may be depending on it for things like the renaming of ts_nsec to ts_sec in <sys/time.h>). Rev.1.49 strengthens the spam to everything in src/include. For 2.2.7, this is not immediately fatal. However, the `make all' step in src/includes is not followed by a `make clean' step, so new rpc headers are not generated after we've bootstrapped rpcgen. This causes a fatal error much later when the old (generated) rpc headers are used with the current headers (sys/types.h and/or the non-generated rpc headers). Details for 2.1.x: the bug is immediately fatal. It gives definition of errno that is not supported by 2.1.x's libc. The weak spam in the restored version avoids this problem by not installing errno.h. (Bootstrapping from 2.1.5 actually breaks much earlier.) I think the header problems supposedly fixed by rev.1.49 were caused by using NOCLEAN and having the build fall over when the weakly spammed headers are active. Minor differences in the layout will then cause the .depend files to point to nonexistent headers. It is a feature for symlinks like errno.h -> sys/errno.h to not exist early. The other change in rev.1.49 breaks building obj directories if NOCLEAN is set. It is only safe for _re_building with NOCLEAN set.
1999-01-04 12:05:59 +00:00
.endif
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_obj:
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 2.2: rebuilding the object tree"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${WMAKE} par-obj
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_build-tools:
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 2.3: build tools"
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${TMAKE} build-tools
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_cross-tools:
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
@echo
@echo "--------------------------------------------------------------"
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
@echo ">>> stage 3: cross tools"
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${XMAKE} cross-tools
Build kernel tools along with other tools during world build, as well as during kernel build (if they didn't get done with world). This will make -DMODULES_WITH_WORLD work, and it ensures the kernel tools are built as part of 'make kernel-toolchain'.
2013-11-08 05:11:32 +00:00
${_+_}cd ${.CURDIR}; ${XMAKE} kernel-tools
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_includes:
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Don't be so chatty about building includes.
2003-11-03 21:09:47 +00:00
@echo ">>> stage 4.1: building includes"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Restore (at least temporarily) SHARED=symlinks in the build includes stage of buildworld. This was accidentally included in r251140. Reported by: jhb
2013-05-30 15:25:54 +00:00
${_+_}cd ${.CURDIR}; ${WMAKE} SHARED=symlinks par-includes
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_libraries:
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 4.2: building libraries"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; \
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
${WMAKE} -DNO_FSCHG MK_HTML=no -DNO_LINT MK_MAN=no \
My previous commit exposed an issue as it fixed a different issue. lib/atf isn't a prereq_lib, since it isn't required for other libraries to build. Remove it. The old kludge of always building it had effectively been retired. Since we don't want to build the libraries with the tests when we're bootstrapping, invent MK_TESTS_SUPPORT which normally defaults to the current MK_TESTS value, except when explicitly defined. Make lib/atf depend on it being yes. When building the libraries set MK_TESTS to no, and MK_TESTS_SUPPORT to the current value of MK_TESTS so that later stages of the build work correctly. This should fix (and does for me) people's issues with parallel builds racing between lib/atf and libexec/atf. Since lib/atf is built during the libraries phase, the race disappears.
2014-10-22 03:39:11 +00:00
MK_PROFILE=no MK_TESTS=no MK_TESTS_SUPPORT=${MK_TESTS} libraries
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
_depend:
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Clarify the numbering of some of the build stages.
2003-09-01 06:43:24 +00:00
@echo ">>> stage 4.3: make dependencies"
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${WMAKE} par-depend
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
everything:
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
@echo
@echo "--------------------------------------------------------------"
Removed 3x2 dots I don't like. ;)
2004-03-19 17:57:07 +00:00
@echo ">>> stage 4.4: building everything"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${WMAKE} par-all
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP)
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
build32:
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 5.1: building 32 bit shim libraries"
@echo "--------------------------------------------------------------"
Add the BSD-licensed Citrus iconv to the base system with default off setting. It can be built by setting the WITH_ICONV knob. While this knob is unset, the library part, the binaries, the header file and the metadata files will not be built or installed so it makes no impact on the system if left turned off. This work is based on the iconv implementation in NetBSD but a great number of improvements and feature additions have been included: - Some utilities have been added. There is a conversion table generator, which can compare conversion tables to reference data generated by GNU libiconv. This helps ensuring conversion compatibility. - UTF-16 surrogate support and some endianness issues have been fixed. - The rather chaotic Makefiles to build metadata have been refactored and cleaned up, now it is easy to read and it is also easier to add support for new encodings. - A bunch of new encodings and encoding aliases have been added. - Support for 1->2, 1->3 and 1->4 mappings, which is needed for transliterating with flying accents as GNU does, like "u. - Lots of warnings have been fixed, the major part of the code is now WARNS=6 clean. - New section 1 and section 5 manual pages have been added. - Some GNU-specific calls have been implemented: iconvlist(), iconvctl(), iconv_canonicalize(), iconv_open_into() - Support for GNU's //IGNORE suffix has been added. - The "-" argument for stdin is now recognized in iconv(1) as per POSIX. - The Big5 conversion module has been fixed. - The iconv.h header files is supposed to be compatible with the GNU version, i.e. sources should build with base iconv.h and GNU libiconv. It also includes a macro magic to deal with the char ** and const char ** incompatibility. - GNU compatibility: "" or "char" means the current local encoding in use - Various cleanups and style(9) fixes. Approved by: delphij (mentor) Obtained from: The NetBSD Project Sponsored by: Google Summer of Code 2009
2011-02-25 00:04:39 +00:00
mkdir -p ${LIB32TMP}/usr/include
- Create the buildworld object directories with mtree instead of various mkdir calls - Remove the ugly workaroung from libc NLS, which was to create some of these directories
2009-03-15 13:14:06 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${LIB32TMP}/usr >/dev/null
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
-p ${LIB32TMP}/usr/include >/dev/null
Add a new knob WITH_DEBUG_FILES to control the building of standalone debug files for userland programs and libraries. The "-g" debug flag is automatically applied when WITH_DEBUG_FILES is set. The debug files are now named ${prog}.debug and ${shlib}.debug for consistency with other systems and documentation. In addition they are installed under /usr/lib/debug, to simplify the process of installing them if needed after a crash. Users of bsd.{prog,lib}.mk outside of the base system place the standalone debug files in a .debug subdirectory. GDB automatically searches both of these directories for standalone debug files. Thanks to everyone who contributed changes, review, and testing during development.
2013-06-07 21:40:02 +00:00
.if ${MK_DEBUG_FILES} != "no"
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.debug.dist \
-p ${LIB32TMP}/usr/lib >/dev/null
.endif
- clean ${LIB32TMP} in _worldtmp - clean ${OBJTREE}/lib32 in _cleanobj - ensure that ${WORLDTMP} exists in build32
2005-08-05 23:48:58 +00:00
mkdir -p ${WORLDTMP}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
ln -sf ${.CURDIR}/sys ${WORLDTMP}
.for _t in obj includes
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/include; ${LIB32WMAKE} DIRPRFX=include/ ${_t}
cd ${.CURDIR}/lib; ${LIB32WMAKE} DIRPRFX=lib/ ${_t}
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
.if ${MK_CDDL} != "no"
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/cddl/lib; ${LIB32WMAKE} DIRPRFX=cddl/lib/ ${_t}
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
.endif
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/gnu/lib; ${LIB32WMAKE} DIRPRFX=gnu/lib/ ${_t}
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_CRYPT} != "no"
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/secure/lib; ${LIB32WMAKE} DIRPRFX=secure/lib/ ${_t}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_KERBEROS} != "no"
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/kerberos5/lib; ${LIB32WMAKE} DIRPRFX=kerberos5/lib ${_t}
Oops, all my test boxes have NO_KERBEROS set, so I didn't hit the kerberos5 build tools problem. I'd missed the kerberos5/tools stuff entirely. Add the missing bits.
2004-11-15 05:59:10 +00:00
.endif
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endfor
Send the pcvt(4) driver off to retirement.
2006-05-17 09:33:15 +00:00
.for _dir in usr.bin/lex/lib
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/${_dir}; ${LIB32WMAKE} DIRPRFX=${_dir}/ obj
Do not leave build droppings in /usr/src for usr.sbin/pcvt/keycap and usr.bin/lex/lib for the 32 bit libraries on amd64. Add an explicit obj for these two directories that are built in for the "libraries" target.
2004-12-01 23:23:14 +00:00
.endfor
Enable ncurses wide character support Approved by: delphij (mentor) Tested by: kris on pointyhat (early version), current@
2007-03-09 12:11:58 +00:00
.for _dir in lib/ncurses/ncurses lib/ncurses/ncursesw lib/libmagic
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
cd ${.CURDIR}/${_dir}; \
The build-tools step during build32 also needs the -legacy magic. Approved by: marcel (mentor)
2012-11-30 20:50:34 +00:00
WORLDTMP=${WORLDTMP} \
MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}" \
Root the lib32 object tree under the overall object tree. This enables a common root directory for all object files for a given tree, which eases sharing a common MAKEOBJDIRPREFIX, and cleaning up of object trees. In particular, one can simply (from the source directory) rm -rf /usr/obj$(pwd) to destroy all object files for it. Or to copy/sync files, etc. Reviewed by: bdrewery CR: https://reviews.freebsd.org/D796 MFC after: 1 month Sponsored by: Spectra Logic
2014-09-18 01:57:36 +00:00
MAKEOBJDIRPREFIX=${LIB32_OBJTREE} ${MAKE} SSP_CFLAGS= DESTDIR= \
Migrate NO_WARN to MK_WARN. Support legacy NO_WARN usage. Remove a check for EARLY_BUILD because it isn't necessary (MK_WARN=no will always be defined for that).
2014-05-10 16:37:53 +00:00
DIRPRFX=${_dir}/ -DNO_LINT -DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no \
Eliminate EARLY_BUILD flag. It is redundant and means MK_CLANG_FULL=no and MK_LLDB=no, so set those explicitly (now that we can do that). Simplify tests for these variables as well, since we know they will always be defined regardless of the phase of the build.
2014-05-10 16:38:03 +00:00
build-tools
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endfor
cd ${.CURDIR}; \
Resurrect one of the patches from attic and refine the 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
2007-02-28 20:06:21 +00:00
${LIB32WMAKE} -f Makefile.inc1 libraries
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.for _t in obj depend all
Use a suitable DIRPRFX for each invocation of make in the build32 and install32 targets so that the full path to each program or library is displayed in the make output. MFC after: 1 week
2011-03-01 14:53:36 +00:00
cd ${.CURDIR}/libexec/rtld-elf; PROG=ld-elf32.so.1 ${LIB32WMAKE} \
DIRPRFX=libexec/rtld-elf/ ${_t}
cd ${.CURDIR}/usr.bin/ldd; PROG=ldd32 ${LIB32WMAKE} \
DIRPRFX=usr.bin/ldd ${_t}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endfor
Provide 32-bit runtime support on amd64 as a separate distribution, lib32. Prodded by: obrien Nodded by: peter Approved by: re
2005-06-16 18:16:14 +00:00
distribute32 install32:
- Remove duplicate setting from LIB32MAKE definition. - Install lib32 bits using the real install(1) program.
2005-08-03 20:27:06 +00:00
cd ${.CURDIR}/lib; ${LIB32IMAKE} ${.TARGET:S/32$//}
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
.if ${MK_CDDL} != "no"
cd ${.CURDIR}/cddl/lib; ${LIB32IMAKE} ${.TARGET:S/32$//}
.endif
- Remove duplicate setting from LIB32MAKE definition. - Install lib32 bits using the real install(1) program.
2005-08-03 20:27:06 +00:00
cd ${.CURDIR}/gnu/lib; ${LIB32IMAKE} ${.TARGET:S/32$//}
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_CRYPT} != "no"
- Remove duplicate setting from LIB32MAKE definition. - Install lib32 bits using the real install(1) program.
2005-08-03 20:27:06 +00:00
cd ${.CURDIR}/secure/lib; ${LIB32IMAKE} ${.TARGET:S/32$//}
Add the kerberos5 libs to the install32 target. (we've been building the all along, but never installing them)
2008-11-12 04:43:55 +00:00
.endif
.if ${MK_KERBEROS} != "no"
cd ${.CURDIR}/kerberos5/lib; ${LIB32IMAKE} ${.TARGET:S/32$//}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endif
Various style fixes in the build32 rules. Submitted by: bde (mostly)
2008-08-02 12:14:22 +00:00
cd ${.CURDIR}/libexec/rtld-elf; \
PROG=ld-elf32.so.1 ${LIB32IMAKE} ${.TARGET:S/32$//}
Tweak the support for using ldd on 32-bit objects a bit further. Specifically, build a 32-bit /usr/bin/ldd32 on amd64 which handles 32-bit objects. Since it is a 32-bit binary, it can fork a child process which can dlopen() a 32-bit shared library. The current 32-bit support in ldd can't do this because it does the dlopen() from a 64-bit process. In order to preserve an intuitive interface for users, the ldd binary automatically execs /usr/bin/ldd32 for 32-bit objects. The end result is that ldd on amd64 now transparently handles 32-bit shared libraries in addition to 32-bit binaries. Submitted by: ps (indirectly)
2008-08-01 21:52:41 +00:00
cd ${.CURDIR}/usr.bin/ldd; PROG=ldd32 ${LIB32IMAKE} ${.TARGET:S/32$//}
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
.endif
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
WMAKE_TGTS=
Remove local patch that crept in.
2002-05-18 18:17:13 +00:00
.if !defined(SUBDIR_OVERRIDE)
-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien.
2003-04-06 21:46:44 +00:00
WMAKE_TGTS+= _worldtmp _legacy _bootstrap-tools
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
.endif
WMAKE_TGTS+= _cleanobj _obj _build-tools
Remove local patch that crept in.
2002-05-18 18:17:13 +00:00
.if !defined(SUBDIR_OVERRIDE)
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
WMAKE_TGTS+= _cross-tools
.endif
WMAKE_TGTS+= _includes _libraries _depend everything
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP) && ${MK_LIB32} != "no"
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
WMAKE_TGTS+= build32
.endif
Milestone #1 in cross-arch make releases. Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
2002-04-26 17:55:27 +00:00
Added timestamping to buildworld, similar to buildkernel.
2006-09-07 19:36:16 +00:00
buildworld: buildworld_prologue ${WMAKE_TGTS} buildworld_epilogue
.ORDER: buildworld_prologue ${WMAKE_TGTS} buildworld_epilogue
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
Added timestamping to buildworld, similar to buildkernel.
2006-09-07 19:36:16 +00:00
buildworld_prologue:
@echo "--------------------------------------------------------------"
@echo ">>> World build started on `LC_ALL=C date`"
@echo "--------------------------------------------------------------"
buildworld_epilogue:
@echo
@echo "--------------------------------------------------------------"
@echo ">>> World build completed on `LC_ALL=C date`"
@echo "--------------------------------------------------------------"
Create a new target 'buildenvvars'. This target reports the build environment for cross building (the same one you'd get interactively in make buildenv). This cannot be a simple make -f Makefile.inc1 -V WMAKEENV because in PATH is not set correctly unless one takes a trip through the Makefile/Makefile.inc1 indirection, the logic of which is too large to reproduce outside of Makefiles.
2006-06-06 16:24:54 +00:00
#
# We need to have this as a target because the indirection between Makefile
# and Makefile.inc1 causes the correct PATH to be used, rather than a
Also need to quote values so they can be passed on correctly.
2006-06-06 18:07:58 +00:00
# modification of the current environment's PATH. In addition, we need
# to quote multiword values.
lex(1) no longer installs headers into GCC-internal dirs (since src/usr.bin/lex/Makefile,v 1.20).
2007-05-26 20:17:19 +00:00
#
Create a new target 'buildenvvars'. This target reports the build environment for cross building (the same one you'd get interactively in make buildenv). This cannot be a simple make -f Makefile.inc1 -V WMAKEENV because in PATH is not set correctly unless one takes a trip through the Makefile/Makefile.inc1 indirection, the logic of which is too large to reproduce outside of Makefiles.
2006-06-06 16:24:54 +00:00
buildenvvars:
Also need to quote values so they can be passed on correctly.
2006-06-06 18:07:58 +00:00
@echo ${WMAKEENV:Q}
Create a new target 'buildenvvars'. This target reports the build environment for cross building (the same one you'd get interactively in make buildenv). This cannot be a simple make -f Makefile.inc1 -V WMAKEENV because in PATH is not set correctly unless one takes a trip through the Makefile/Makefile.inc1 indirection, the logic of which is too large to reproduce outside of Makefiles.
2006-06-06 16:24:54 +00:00
Add a guard against attempting to invoke the buildenv target with -j# as that silently exits rather than doing something useful. MFC after: 1 week Sponsored by: DARPA, AFRL
2014-11-21 18:18:37 +00:00
.if ${.TARGETS:Mbuildenv}
.if ${.MAKEFLAGS:M-j}
.error The buildenv target is incompatible with -j
.endif
.endif
Added the "buildenv" target, for developers only! CAVEAT: if you run tcsh(1) from within this target, this will reset your PATH making this target mostly useless. Careful! Submitted by: jmg, ru
2005-02-26 22:02:18 +00:00
buildenv:
@echo Entering world for ${TARGET_ARCH}:${TARGET}
Allow specification of build shell for the buildenv target. Submitted by: ian lepore
2012-01-30 20:19:28 +00:00
@cd ${.CURDIR} && env ${WMAKEENV} ${BUILDENV_SHELL} || true
Added the "buildenv" target, for developers only! CAVEAT: if you run tcsh(1) from within this target, this will reset your PATH making this target mostly useless. Careful! Submitted by: jmg, ru
2005-02-26 22:02:18 +00:00
Exclude build32 target from the list of toolchain and kernel-toolchain dependencies. We do not need to build 32bit compat tools to compile a kernel. Approved by: re (scottl) Reported by: jhb
2005-07-07 00:58:41 +00:00
TOOLCHAIN_TGTS= ${WMAKE_TGTS:N_depend:Neverything:Nbuild32}
Add a kernel-toolchain target which only builds the bits required to build a kernel. This is essentially the same as the toolchain target, except that it does not build headers and libraries. Submitted by: ru
2004-04-13 13:42:01 +00:00
toolchain: ${TOOLCHAIN_TGTS}
kernel-toolchain: ${TOOLCHAIN_TGTS:N_includes:N_libraries}
Added the `toolchain' top-level target, which builds enough of buildworld, up to and including libraries, except for actually building the world. Requested by: many
2004-03-24 08:26:22 +00:00
Commit the first set of files for changing time_t on freebsd/sparc64 from a 32-bit value to a 64-bit value. This commit does not actually change anything. It merely provides instructions, scripts, and a safety measure in Makefile.inc1 for people who want to make the change. The real change to 64-bit time_t's on sparc64 is scheduled to happen on March 10th, assuming that so major problems are found between now and then by early-adopters. Reviewed by: freebsd-sparc64
2004-03-03 19:36:20 +00:00
#
Get rid of SPECIAL_INSTALLCHECKS variable that isn't settable by a user. Instead, add individual checks as dependencies to the main "installcheck" target. Make sure that installkernel etc. depend on it (including the UID/GID checks).
2005-11-22 12:02:41 +00:00
# installcheck
#
# Checks to be sure system is ready for installworld/installkernel.
Commit the first set of files for changing time_t on freebsd/sparc64 from a 32-bit value to a 64-bit value. This commit does not actually change anything. It merely provides instructions, scripts, and a safety measure in Makefile.inc1 for people who want to make the change. The real change to 64-bit time_t's on sparc64 is scheduled to happen on March 10th, assuming that so major problems are found between now and then by early-adopters. Reviewed by: freebsd-sparc64
2004-03-03 19:36:20 +00:00
#
Fix 'make installcheck' to check for missing UID/GID as well, broken since r249893, by adding a separate _installcheck_world and _installcheck_kernel so the destination targets can be more explicit on which they are needed for. installcheck will call both, while installworld only calls _installcheck_world and installkernel only calls _installcheck_kernel While here, mark the internal targets as starting with _. Reported by: des Reviewed by: des Pointyhat to: bdrewery Approved by: re (delphij)
2013-09-18 00:33:24 +00:00
installcheck: _installcheck_world _installcheck_kernel
_installcheck_world:
_installcheck_kernel:
Commit the first set of files for changing time_t on freebsd/sparc64 from a 32-bit value to a 64-bit value. This commit does not actually change anything. It merely provides instructions, scripts, and a safety measure in Makefile.inc1 for people who want to make the change. The real change to 64-bit time_t's on sparc64 is scheduled to happen on March 10th, assuming that so major problems are found between now and then by early-adopters. Reviewed by: freebsd-sparc64
2004-03-03 19:36:20 +00:00
Require DESTDIR to be set when installing for a different architecture.
2005-11-07 15:03:04 +00:00
#
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
# Require DESTDIR to be set if installing for a different architecture or
# using the user/group database in the source tree.
Require DESTDIR to be set when installing for a different architecture.
2005-11-07 15:03:04 +00:00
#
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.if ${TARGET_ARCH} != ${MACHINE_ARCH} || ${TARGET} != ${MACHINE} || \
defined(DB_FROM_SRC)
Don't check DESTDIR when making distributeworld; the latter expects DISTDIR. Reported by: nyan
2005-11-12 19:28:46 +00:00
.if !make(distributeworld)
Fix 'make installcheck' to check for missing UID/GID as well, broken since r249893, by adding a separate _installcheck_world and _installcheck_kernel so the destination targets can be more explicit on which they are needed for. installcheck will call both, while installworld only calls _installcheck_world and installkernel only calls _installcheck_kernel While here, mark the internal targets as starting with _. Reported by: des Reviewed by: des Pointyhat to: bdrewery Approved by: re (delphij)
2013-09-18 00:33:24 +00:00
_installcheck_world: __installcheck_DESTDIR
_installcheck_kernel: __installcheck_DESTDIR
__installcheck_DESTDIR:
Require DESTDIR to be set when installing for a different architecture.
2005-11-07 15:03:04 +00:00
.if !defined(DESTDIR) || empty(DESTDIR)
@echo "ERROR: Please set DESTDIR!"; \
false
.endif
.endif
Don't check DESTDIR when making distributeworld; the latter expects DISTDIR. Reported by: nyan
2005-11-12 19:28:46 +00:00
.endif
Require DESTDIR to be set when installing for a different architecture.
2005-11-07 15:03:04 +00:00
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.if !defined(DB_FROM_SRC)
Revert r245316. Systems with non-standard uids/gids are more prevalent that I'd feared. Discussion is ongoing about the scope of a safer solution.
2013-01-11 23:44:35 +00:00
#
# Check for missing UIDs/GIDs.
#
CHECK_UIDS= auditdistd
CHECK_GIDS= audit
.if ${MK_SENDMAIL} != "no"
CHECK_UIDS+= smmsp
CHECK_GIDS+= smmsp
.endif
.if ${MK_PF} != "no"
CHECK_UIDS+= proxy
CHECK_GIDS+= proxy authpf
.endif
Add unbound to the list of UIDs / GIDs to check fore before installing. Approved by: re (blanket)
2013-09-17 12:59:37 +00:00
.if ${MK_UNBOUND} != "no"
CHECK_UIDS+= unbound
CHECK_GIDS+= unbound
.endif
Fix 'make installcheck' to check for missing UID/GID as well, broken since r249893, by adding a separate _installcheck_world and _installcheck_kernel so the destination targets can be more explicit on which they are needed for. installcheck will call both, while installworld only calls _installcheck_world and installkernel only calls _installcheck_kernel While here, mark the internal targets as starting with _. Reported by: des Reviewed by: des Pointyhat to: bdrewery Approved by: re (delphij)
2013-09-18 00:33:24 +00:00
_installcheck_world: __installcheck_UGID
__installcheck_UGID:
Revert r245316. Systems with non-standard uids/gids are more prevalent that I'd feared. Discussion is ongoing about the scope of a safer solution.
2013-01-11 23:44:35 +00:00
.for uid in ${CHECK_UIDS}
@if ! `id -u ${uid} >/dev/null 2>&1`; then \
echo "ERROR: Required ${uid} user is missing, see /usr/src/UPDATING."; \
false; \
fi
.endfor
.for gid in ${CHECK_GIDS}
@if ! `find / -prune -group ${gid} >/dev/null 2>&1`; then \
echo "ERROR: Required ${gid} group is missing, see /usr/src/UPDATING."; \
false; \
fi
.endfor
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.endif
Revert r245316. Systems with non-standard uids/gids are more prevalent that I'd feared. Discussion is ongoing about the scope of a safer solution.
2013-01-11 23:44:35 +00:00
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
#
# Required install tools to be saved in a scratch dir for safety.
#
Now that the zoneinfo data is automatically updated when a new world is installed, we should at least have the tzsetup tool available! Suggested by: Andriy Gapon <avg@freebsd.org> Noticed by: Ben Kaduk <minimarmot@gmail.com> MFC after: 1 week
2009-10-28 07:05:32 +00:00
.if ${MK_ZONEINFO} != "no"
Use find -exec to install zoneinfo instead of requiring xargs to be an install tool. Suggested by: delphij
2013-01-11 18:37:51 +00:00
_zoneinfo= zic tzsetup
Now that the zoneinfo data is automatically updated when a new world is installed, we should at least have the tzsetup tool available! Suggested by: Andriy Gapon <avg@freebsd.org> Noticed by: Ben Kaduk <minimarmot@gmail.com> MFC after: 1 week
2009-10-28 07:05:32 +00:00
.endif
Don't put "install-info" to the list of install-tools if we're installing with -DWITHOUT_INFO, otherwise one can experience a failure trying to installworld on a system that is built with -DWITHOUT_INFO (i.e., without /usr/bin/install-info). Reported by: bland MFC after: 3 days
2009-03-13 10:09:08 +00:00
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
ITOOLS= [ awk cap_mkdb cat chflags chmod chown \
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
date echo egrep find grep id install ${_install-info} \
Merge from CheriBSD: commit 1b41f6de7ca09e04fdc6f66bc478ea6c981a41b9 Author: Brooks Davis <brooks@one-eyed-alien.net> Date: Mon Jan 27 22:59:02 2014 +0000 Now that mtree is always nmtree use it as mtree Tested on: ref9-amd64 X-MFC after: never Sponsored by: DARPA, AFRL
2014-01-30 22:26:51 +00:00
ln lockf make mkdir mtree mv pwd_mkdb \
Fix sporadic build failures due to race when running make installworld when strip gets replaced at install time by adding it to ITOOLS for the default usr.bin/xinstall STRIP_CMD This will fix the failure noted in this Jenkins build step: https://jenkins.freebsd.org/job/Build-UFS-image/688/ This will also fix the issue reported by alfred@ dealing with installing on targets that differ from build hosts (e.g. installing on i386/i386 when built on amd64/amd64) MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
2014-12-17 20:02:07 +00:00
rm sed services_mkdb sh strip sysctl test true uname wc ${_zoneinfo} \
- Add a LOCAL_ITOOLS to allow adding additional tools required for the installworld and distributeworld targets PR: 179562 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> MFC after: 1 week
2014-06-17 22:23:36 +00:00
${LOCAL_ITOOLS}
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
Add makewhatis to ITOOLS if MK_MAN != no This will fix installation with differing host targets in installworld, so one can build i386/i386 on an amd64 host, then install to an i386/i386 target Reported by: alfred Phabric: D1280 MFC after: 1 week
2014-12-08 18:29:20 +00:00
# Needed for share/man
.if ${MK_MAN} != "no"
ITOOLS+=makewhatis
.endif
Restore comment that got lost in revision 1.265.
2002-05-14 08:30:40 +00:00
#
# distributeworld
#
# Distributes everything compiled by a `buildworld'.
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# installworld
#
# Installs everything compiled by a 'buildworld'.
#
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
# Non-base distributions produced by the base system
Fix 'distributeworld' target when WITHOUT_GAMES is set. Reviewed by: des Approved by: des MFC after: 3 days X-MFC-To: 9-only
2012-09-03 18:17:21 +00:00
EXTRA_DISTRIBUTIONS= doc
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.if defined(LIB32TMP) && ${MK_LIB32} != "no"
EXTRA_DISTRIBUTIONS+= lib32
.endif
Put the test suite in its own tests.txz distribution file. Force all the contents of /usr/tests to go into a separate distribution file so that users of binary releases can easily choose to not install it. To make this possible, we need two fixes: - bsd.subdir.mk needs to properly honor NO_SUBDIR in all cases so that we do not recurse into 'tests' subdirectories when we needn't. Otherwise, we end up with some Kyuafiles in base.txz. - etc/Makefile needs to skip installing tests in its 'distribute' target so that a Kyuafile doesn't leak into base.txz. Approved by: gjb
2014-06-10 17:04:30 +00:00
.if ${MK_TESTS} != "no"
EXTRA_DISTRIBUTIONS+= tests
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
DEBUG_DISTRIBUTIONS=
.if ${MK_DEBUG_FILES} != "no"
Exclude 'tests' from DEBUG_DISTRIBUTIONS. Sponsored by: The FreeBSD Foundation
2015-02-10 01:35:26 +00:00
DEBUG_DISTRIBUTIONS+= base ${EXTRA_DISTRIBUTIONS:S,doc,,:S,tests,,}
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
.endif
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
MTREE_MAGIC?= mtree 2.0
Fix 'make installcheck' to check for missing UID/GID as well, broken since r249893, by adding a separate _installcheck_world and _installcheck_kernel so the destination targets can be more explicit on which they are needed for. installcheck will call both, while installworld only calls _installcheck_world and installkernel only calls _installcheck_kernel While here, mark the internal targets as starting with _. Reported by: des Reviewed by: des Pointyhat to: bdrewery Approved by: re (delphij)
2013-09-18 00:33:24 +00:00
distributeworld installworld: _installcheck_world
Save any binaries we use by installworld, so that we won't use the binaries we just installed. This allows a future upgrade target to install a new system without intermediate reboots and also prevents conflicts for parallel make runs where we might exec a binary that's being installed at the same time.
2000-07-19 04:41:59 +00:00
mkdir -p ${INSTALLTMP}
- Explicitly verify if all needed libs were found by ldd(1). Do so 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]
2007-12-04 12:55:27 +00:00
progs=$$(for prog in ${ITOOLS}; do \
If a required install tool is missing, provide a more friendly error message (instead of cp's usage info).
2007-10-15 13:50:46 +00:00
if progpath=`which $$prog`; then \
- Explicitly verify if all needed libs were found by ldd(1). Do so 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]
2007-12-04 12:55:27 +00:00
echo $$progpath; \
If a required install tool is missing, provide a more friendly error message (instead of cp's usage info).
2007-10-15 13:50:46 +00:00
else \
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
echo "Required tool $$prog not found in PATH." >&2; \
If a required install tool is missing, provide a more friendly error message (instead of cp's usage info).
2007-10-15 13:50:46 +00:00
exit 1; \
fi; \
- Explicitly verify if all needed libs were found by ldd(1). Do so 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]
2007-12-04 12:55:27 +00:00
done); \
libs=$$(ldd -f "%o %p\n" -f "%o %p\n" $$progs 2>/dev/null | sort -u | \
while read line; do \
set -- $$line; \
if [ "$$2 $$3" != "not found" ]; then \
echo $$2; \
else \
echo "Required library $$1 not found." >&2; \
exit 1; \
fi; \
done); \
cp $$libs $$progs ${INSTALLTMP}
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
cp -R $${PATH_LOCALE:-"/usr/share/locale"} ${INSTALLTMP}/locale
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.if defined(NO_ROOT)
echo "#${MTREE_MAGIC}" > ${METALOG}
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.if make(distributeworld)
.for dist in ${EXTRA_DISTRIBUTIONS}
-mkdir ${DESTDIR}/${DISTDIR}/${dist}
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.root.dist \
-p ${DESTDIR}/${DISTDIR}/${dist} >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${DESTDIR}/${DISTDIR}/${dist}/usr >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
-p ${DESTDIR}/${DISTDIR}/${dist}/usr/include >/dev/null
Add a new knob WITH_DEBUG_FILES to control the building of standalone debug files for userland programs and libraries. The "-g" debug flag is automatically applied when WITH_DEBUG_FILES is set. The debug files are now named ${prog}.debug and ${shlib}.debug for consistency with other systems and documentation. In addition they are installed under /usr/lib/debug, to simplify the process of installing them if needed after a crash. Users of bsd.{prog,lib}.mk outside of the base system place the standalone debug files in a .debug subdirectory. GDB automatically searches both of these directories for standalone debug files. Thanks to everyone who contributed changes, review, and testing during development.
2013-06-07 21:40:02 +00:00
.if ${MK_DEBUG_FILES} != "no"
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.debug.dist \
-p ${DESTDIR}/${DISTDIR}/${dist}/usr/lib >/dev/null
.endif
Put the test suite in its own tests.txz distribution file. Force all the contents of /usr/tests to go into a separate distribution file so that users of binary releases can easily choose to not install it. To make this possible, we need two fixes: - bsd.subdir.mk needs to properly honor NO_SUBDIR in all cases so that we do not recurse into 'tests' subdirectories when we needn't. Otherwise, we end up with some Kyuafiles in base.txz. - etc/Makefile needs to skip installing tests in its 'distribute' target so that a Kyuafile doesn't leak into base.txz. Approved by: gjb
2014-06-10 17:04:30 +00:00
.if ${MK_TESTS} != "no" && ${dist} == "tests"
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
-mkdir -p ${DESTDIR}/${DISTDIR}/${dist}${TESTSBASE}
Put the test suite in its own tests.txz distribution file. Force all the contents of /usr/tests to go into a separate distribution file so that users of binary releases can easily choose to not install it. To make this possible, we need two fixes: - bsd.subdir.mk needs to properly honor NO_SUBDIR in all cases so that we do not recurse into 'tests' subdirectories when we needn't. Otherwise, we end up with some Kyuafiles in base.txz. - etc/Makefile needs to skip installing tests in its 'distribute' target so that a Kyuafile doesn't leak into base.txz. Approved by: gjb
2014-06-10 17:04:30 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.tests.dist \
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
-p ${DESTDIR}/${DISTDIR}/${dist}${TESTSBASE} >/dev/null
Put the test suite in its own tests.txz distribution file. Force all the contents of /usr/tests to go into a separate distribution file so that users of binary releases can easily choose to not install it. To make this possible, we need two fixes: - bsd.subdir.mk needs to properly honor NO_SUBDIR in all cases so that we do not recurse into 'tests' subdirectories when we needn't. Otherwise, we end up with some Kyuafiles in base.txz. - etc/Makefile needs to skip installing tests in its 'distribute' target so that a Kyuafile doesn't leak into base.txz. Approved by: gjb
2014-06-10 17:04:30 +00:00
.endif
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.if defined(NO_ROOT)
Merge from CheriBSD: commit 1b41f6de7ca09e04fdc6f66bc478ea6c981a41b9 Author: Brooks Davis <brooks@one-eyed-alien.net> Date: Mon Jan 27 22:59:02 2014 +0000 Now that mtree is always nmtree use it as mtree Tested on: ref9-amd64 X-MFC after: never Sponsored by: DARPA, AFRL
2014-01-30 22:26:51 +00:00
${IMAKEENV} mtree -C -f ${.CURDIR}/etc/mtree/BSD.root.dist | \
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
sed -e 's#^\./#./${dist}/#' >> ${METALOG}
Merge from CheriBSD: commit 1b41f6de7ca09e04fdc6f66bc478ea6c981a41b9 Author: Brooks Davis <brooks@one-eyed-alien.net> Date: Mon Jan 27 22:59:02 2014 +0000 Now that mtree is always nmtree use it as mtree Tested on: ref9-amd64 X-MFC after: never Sponsored by: DARPA, AFRL
2014-01-30 22:26:51 +00:00
${IMAKEENV} mtree -C -f ${.CURDIR}/etc/mtree/BSD.usr.dist | \
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
sed -e 's#^\./#./${dist}/usr/#' >> ${METALOG}
Merge from CheriBSD: commit 1b41f6de7ca09e04fdc6f66bc478ea6c981a41b9 Author: Brooks Davis <brooks@one-eyed-alien.net> Date: Mon Jan 27 22:59:02 2014 +0000 Now that mtree is always nmtree use it as mtree Tested on: ref9-amd64 X-MFC after: never Sponsored by: DARPA, AFRL
2014-01-30 22:26:51 +00:00
${IMAKEENV} mtree -C -f ${.CURDIR}/etc/mtree/BSD.include.dist | \
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
sed -e 's#^\./#./${dist}/usr/include/#' >> ${METALOG}
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endfor
-mkdir ${DESTDIR}/${DISTDIR}/base
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
cd ${.CURDIR}/etc; ${CROSSENV} PATH=${TMPPATH} ${MAKE} \
METALOG=${METALOG} ${IMAKE_INSTALL} ${IMAKE_MTREE} \
DISTBASE=/base DESTDIR=${DESTDIR}/${DISTDIR}/base \
- Fix LOCAL_MTREE so it properly handles multiple files and quotes its value into submakes PR: conf/179466 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> Approved by: bapt MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2013-08-30 01:32:47 +00:00
LOCAL_MTREE=${LOCAL_MTREE:Q} distrib-dirs
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endif
Decouple the install tools from the main system as much as possible. 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)
2007-10-31 09:26:42 +00:00
${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}; \
${IMAKEENV} rm -rf ${INSTALLTMP}
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.if make(distributeworld)
.for dist in ${EXTRA_DISTRIBUTIONS}
release: Allow empty extra distributions. For example, WITHOUT_SHAREDOCS= in src.conf creates an empty doc distribution. Submitted by: Kurt Lidl Tested by: Kurt Lidl Discussed with: gjb MFC after: 1 week
2013-06-05 22:27:49 +00:00
find ${DESTDIR}/${DISTDIR}/${dist} -mindepth 1 -empty -delete
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endfor
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.if defined(NO_ROOT)
.for dist in base ${EXTRA_DISTRIBUTIONS}
@# For each file that exists in this dist, print the corresponding
@# line from the METALOG. This relies on the fact that
@# a line containing only the filename will sort immediatly before
@# the relevant mtree line.
cd ${DESTDIR}/${DISTDIR}; \
find ./${dist} | sort -u ${METALOG} - | \
awk 'BEGIN { print "#${MTREE_MAGIC}" } !/ type=/ { file = $$1 } / type=/ { if ($$1 == file) { sub(/^\.\/${dist}\//, "./"); print } }' > \
${DESTDIR}/${DISTDIR}/${dist}.meta
.endfor
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
.for dist in ${DEBUG_DISTRIBUTIONS}
Generate debug data release dist sets If WITH_DEBUG_FILES is set the standalone debug data will be excluded from each ${dist}.txz and placed in a ${dist}.debug.txz. Submitted by: gjb Reviewed by: brooks
2013-07-23 19:34:09 +00:00
@# For each file that exists in this dist, print the corresponding
@# line from the METALOG. This relies on the fact that
@# a line containing only the filename will sort immediatly before
@# the relevant mtree line.
cd ${DESTDIR}/${DISTDIR}; \
find ./${dist}/usr/lib/debug | sort -u ${METALOG} - | \
awk 'BEGIN { print "#${MTREE_MAGIC}" } !/ type=/ { file = $$1 } / type=/ { if ($$1 == file) { sub(/^\.\/${dist}\//, "./"); print } }' > \
${DESTDIR}/${DISTDIR}/${dist}.debug.meta
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
.endfor
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endif
packageworld:
.for dist in base ${EXTRA_DISTRIBUTIONS}
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.if defined(NO_ROOT)
${_+_}cd ${DESTDIR}/${DISTDIR}/${dist}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - --exclude usr/lib/debug \
@${DESTDIR}/${DISTDIR}/${dist}.meta | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/${dist}.txz
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.else
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
${_+_}cd ${DESTDIR}/${DISTDIR}/${dist}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - --exclude usr/lib/debug . | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/${dist}.txz
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endfor
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
.for dist in ${DEBUG_DISTRIBUTIONS}
. if defined(NO_ROOT)
Generate debug data release dist sets If WITH_DEBUG_FILES is set the standalone debug data will be excluded from each ${dist}.txz and placed in a ${dist}.debug.txz. Submitted by: gjb Reviewed by: brooks
2013-07-23 19:34:09 +00:00
${_+_}cd ${DESTDIR}/${DISTDIR}/${dist}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - @${DESTDIR}/${DISTDIR}/${dist}.debug.meta | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/${dist}-dbg.txz
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
. else
Generate debug data release dist sets If WITH_DEBUG_FILES is set the standalone debug data will be excluded from each ${dist}.txz and placed in a ${dist}.debug.txz. Submitted by: gjb Reviewed by: brooks
2013-07-23 19:34:09 +00:00
${_+_}cd ${DESTDIR}/${DISTDIR}/${dist}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvLf - usr/lib/debug | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/${dist}-dbg.txz
Merge ^/projects/release-debugdist into ^/head: r262491, r262493, r262516, r267345, r267397: r262491: Add DEBUG_DISTRIBUTIONS, and set it to include base and EXTRA_DISTRIBUTIONS, excluding 'doc', since the documentation distribution does not have corresponding debug information. Use DEBUG_DISTRIBUTIONS in the 'distributeworld installworld' and 'packageworld' targets, to reduce the number of occurances of excluding distributions that do not have .debug files. r262493: In release/Makefile, explicitly set WITHOUT_DEBUG_FILES=1 for dvdrom and cdrom targets. (Later reverted.) Exclude the *.debug.txz distributions from dvdrom and cdrom images, but include them for ftp distribution. r262516: Rename ${dist}.debug.txz to ${dist}-dbg.txz to prevent the following output: eval: ${base....}: Bad substitution eval: ${doc....}: Bad substitution eval: ${games....}: Bad substitution eval: ${lib32....}: Bad substitution This also follows other naming conventions seen in the wild. r267345: Explicitly set MK_DEBUG_FILES=no, which overrides the WITH_DEBUG_FILES=1 and WITHOUT_DEBUG_FILES=1 collisions previously experienced. This change allows us to create the {base,kernel}_debug.txz distributions without accidentally installing the *.debug files on the medium itself. r267397: Remove evaluations of MK_DEBUG_FILES where not needed. If DEBUG_DISTRIBUTIONS is empty, which is true if MK_DEBUG_FILES evaluates to 'no' above, the loop does nothing. MFC after: 1 month Tested on: head@r267801 Reviewed by: brooks [1], emaste, imp [1] [1] earlier version Sponsored by: The FreeBSD Foundation
2014-07-01 19:04:04 +00:00
. endif
.endfor
Generate debug data release dist sets If WITH_DEBUG_FILES is set the standalone debug data will be excluded from each ${dist}.txz and placed in a ${dist}.debug.txz. Submitted by: gjb Reviewed by: brooks
2013-07-23 19:34:09 +00:00
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# reinstall
#
# If you have a build server, you can NFS mount the source and obj directories
# and do a 'make reinstall' on the *client* to install new binaries from the
# most recent server build.
#
Have distrib-dirs, distribution, hier, hierarchy, redistribute, and reinstall depend on the .MAKE special target This will allow users to do something like the following to print out the results of the running the simulated make target with bmake, like some of the other top-level make targets in Makefile.inc1: % make -f Makefile.inc1 -n distribution TARGET=i386 TARGET_ARCH=i386 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2014-09-24 04:06:54 +00:00
reinstall: .MAKE
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Purely cosmetic but useful change. Make output of make world more readable for grep. Now a grep '>>>' world.log shows you the single stages through which the bootstrap process went as discussed on -current. Could be used to debug the bootstrap mechanism in case of trouble more easily. Would be fine if any further @echo "..." messages containing a description, what's going on, could use the new format: @echo ">>> ..."
1998-09-17 16:32:00 +00:00
@echo ">>> Making hierarchy"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Allow LOCAL_(DIRS,LIBS) to install files in directories not found in the system mtree files via a LOCAL_MTREE variable which contains a list of mtree files to be applyed along with the base mtree files to the tmp root and DESTDIR.
2012-10-18 12:32:51 +00:00
${_+_}cd ${.CURDIR}; ${MAKE} -f Makefile.inc1 \
- Fix LOCAL_MTREE so it properly handles multiple files and quotes its value into submakes PR: conf/179466 Submitted by: Garrett Cooper <yaneurabeya@gmail.com> Approved by: bapt MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2013-08-30 01:32:47 +00:00
LOCAL_MTREE=${LOCAL_MTREE:Q} hierarchy
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo
@echo "--------------------------------------------------------------"
Removed 3x2 dots I don't like. ;)
2004-03-19 17:57:07 +00:00
@echo ">>> Installing everything"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${MAKE} -f Makefile.inc1 install
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP) && ${MK_LIB32} != "no"
Convert tools/lib32/build.sh into world connectable hooks. This still rates pretty high on the "hack!" scale, but it works for me. Adding -DWANT_LIB32 to the world build command line, or 'WANT_LIB32=yes' to /etc/make.conf will include the 32 bit libraries with the build. I have not made this default behavior. Cross compiling this stuff is an adventure I have not investigated. This is still a WIP. We needed this at work so that we could install from a readonly obj tree - lib32/build.sh wasn't up to that.
2004-11-06 03:14:26 +00:00
${_+_}cd ${.CURDIR}; ${MAKE} -f Makefile.inc1 install32
.endif
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
Have distrib-dirs, distribution, hier, hierarchy, redistribute, and reinstall depend on the .MAKE special target This will allow users to do something like the following to print out the results of the running the simulated make target with bmake, like some of the other top-level make targets in Makefile.inc1: % make -f Makefile.inc1 -n distribution TARGET=i386 TARGET_ARCH=i386 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2014-09-24 04:06:54 +00:00
redistribute: .MAKE
Milestone #2 in cross-arch make releases. They now work! You need to set TARGET_ARCH and possibly TARGET, the same way you normally do it for a cross build(7). Renamed `distribworld' to a more natutal `distributeworld'. Put pwd_mkdb(8) under ${INSTALLTMP}; for `distributeworld'.
2002-04-30 11:50:01 +00:00
@echo "--------------------------------------------------------------"
Removed 3x2 dots I don't like. ;)
2004-03-19 17:57:07 +00:00
@echo ">>> Distributing everything"
Milestone #2 in cross-arch make releases. They now work! You need to set TARGET_ARCH and possibly TARGET, the same way you normally do it for a cross build(7). Renamed `distribworld' to a more natutal `distributeworld'. Put pwd_mkdb(8) under ${INSTALLTMP}; for `distributeworld'.
2002-04-30 11:50:01 +00:00
@echo "--------------------------------------------------------------"
Make make recurse into sub-directories and sub-makes when given two -n flags. If only one -n flag is given the old behaviour is retained (POLA). In order to make this working for installworld change the IMAKEENV in this case so that the tools are found (we have no temporary installation environment in this case). Submitted by: ru (IMAKEENV part)
2004-08-09 11:38:41 +00:00
${_+_}cd ${.CURDIR}; ${MAKE} -f Makefile.inc1 distribute
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if defined(LIB32TMP) && ${MK_LIB32} != "no"
Various style fixes in the build32 rules. Submitted by: bde (mostly)
2008-08-02 12:14:22 +00:00
${_+_}cd ${.CURDIR}; ${MAKE} -f Makefile.inc1 distribute32 \
DISTRIBUTION=lib32
Provide 32-bit runtime support on amd64 as a separate distribution, lib32. Prodded by: obrien Nodded by: peter Approved by: re
2005-06-16 18:16:14 +00:00
.endif
Fix release, broken by the perl cross-build fixes. The distribute target is basicly the same as an install. For perl, this means that miniperl is needed. Since miniperl is only present in the object directory, we need to make sure the path is set correctly. To do this, we have make release use a new distribworld target that sets the path before doing a make distribute.
2000-11-21 04:37:30 +00:00
Have distrib-dirs, distribution, hier, hierarchy, redistribute, and reinstall depend on the .MAKE special target This will allow users to do something like the following to print out the results of the running the simulated make target with bmake, like some of the other top-level make targets in Makefile.inc1: % make -f Makefile.inc1 -n distribution TARGET=i386 TARGET_ARCH=i386 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2014-09-24 04:06:54 +00:00
distrib-dirs distribution: .MAKE
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
cd ${.CURDIR}/etc; ${CROSSENV} PATH=${TMPPATH} ${MAKE} \
Introduce a new option -DNO_ROOT that allows install and distribution targets to be run without root privilege. Information about ownership, group, flags, and suid bits are stored in the file specified by METALOG which defaults to ${DESTDIR}/METALOG. This file can be used in conjunction with bsdtar or makefs to generate archives or file system images with correct permissions. The packageworld target has been altered to use this metadata allowing non-root releases (subject to further changes in release/Makefile.) Sponsored by: DARPA, AFRL Reviewed by: ian, ray
2013-01-22 21:10:03 +00:00
${IMAKE_INSTALL} ${IMAKE_MTREE} METALOG=${METALOG} ${.TARGET}
Added the convenience "distribution" target which calls the target of the same name from src/etc/Makefile with a proper environment, suitable to be used during upgrades and cross- builds.
2005-02-27 12:11:35 +00:00
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
#
# buildkernel and installkernel
#
# Which kernels to build and/or install is specified by setting
Using "KERNEL" for buildkernel was a very very bad mistake. $KERNEL is already used by the kernel makefiles themselves, and this leads to a lot of trouble when people put "KERNEL=MYKERNEL" in make.conf. Bite the bullet and change it to KERNCONF instead, before it gets too far entrenched. The kernel Makefiles use ${KERNEL} as the name of what to install the kernel as, eg: /boot/${KERNEL}/kernel or /${KERNEL}. This leads to much unhappiness with things like /LOCAL instead of /kernel. buildkernel is severely limited as it is only useful directly after a buildworld. Reviewed by: jhb
2001-01-22 07:29:48 +00:00
# KERNCONF. If not defined a GENERIC kernel is built/installed.
Fix cross-building further. Introduce ${TARGET} defaulting to ${MACHINE} which should be set to whatever your target ${MACHINE} is, and use that with world-related stages. That is, to build pc98 on alpha, one now needs to set both TARGET_ARCH=i386 and TARGET=pc98. The scope of ${TARGET} is limited to Makefile.inc1 and cross-tools. In particular, this change was tested to fix: 1. Cross building of "alpha" on i386. The breakage was introduced by rev. 1.10 to sbin/i386/Makefile (missing <machine/cronyx.h>). 2. Descending into machine-specific subdirs for a different arch. Previously, sbin/i386 and usr.sbin/boot0cfg were descended into when cross-building "alpha" or pc98 on i386. 3. Fixes pc98 cross-building which was horribly broken, caused by not setting MACHINE correctly (most ${MACHINE} == pc98 checking Makefiles put -DPC98 to CFLAGS).
2001-10-25 07:28:55 +00:00
# Only the existing (depending TARGET) config files are used
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
# for building kernels and only the first of these is designated
# as the one being installed.
#
Fix cross-building further. Introduce ${TARGET} defaulting to ${MACHINE} which should be set to whatever your target ${MACHINE} is, and use that with world-related stages. That is, to build pc98 on alpha, one now needs to set both TARGET_ARCH=i386 and TARGET=pc98. The scope of ${TARGET} is limited to Makefile.inc1 and cross-tools. In particular, this change was tested to fix: 1. Cross building of "alpha" on i386. The breakage was introduced by rev. 1.10 to sbin/i386/Makefile (missing <machine/cronyx.h>). 2. Descending into machine-specific subdirs for a different arch. Previously, sbin/i386 and usr.sbin/boot0cfg were descended into when cross-building "alpha" or pc98 on i386. 3. Fixes pc98 cross-building which was horribly broken, caused by not setting MACHINE correctly (most ${MACHINE} == pc98 checking Makefiles put -DPC98 to CFLAGS).
2001-10-25 07:28:55 +00:00
# Note that we have to use TARGET instead of TARGET_ARCH when
Fix cross-building, etc: 1. To cross-build, one now needs to set TARGET_ARCH, and not the MACHINE_ARCH. MACHINE_ARCH should never be changed manually! 2. Initialize DESTDIR= explicitly for bootstrap-tools, build-tools, and cross-tools stages. This fixes broken header and library dependencies problem. We build them in the host environment, and obviously want them to depend on host headers and libraries. The problem with broken header dependencies for bootstrap-tools and cross-tools was already partially solved (see BOOTSTRAPPING tests in bsd.prog.mk and bsd.lib.mk), but it was still there for build-tools if the user ran "make world DESTDIR=/foo". Also, for all of these stages, the library dependencies were broken because of how bsd.libnames.mk define DPADD members. We still provide a glue to install bootstrap- and cross-tools under the ${WORLDTMP}. Removed PATH overrides for bootstrap-, build-, and cross-tools stages. There is just no reason why we would need to override it, and the hacks to clean up the ${WORLDTMP} in the -DNOCLEAN case are no longer needed with fixes from this step. That is, we now never use ${WORLDTMP} headers and libraries, and we don't use any ${WORLDTMP} installed binaries during these stages. Again, these stages depend solely on the host environment, including compiler, headers, and libraries. 3. Moved "miniperl" back from cross-tools (it has nothing to do with a cross-compiler) to build-tools where it belongs. The change from step 1 let to do this. Also, to make this work, build-tools targets of "cc_tools" and "miniperl" were modified to call "depend". Here follow the detailed explanations. There are two categories of build tools, for now. In the first category there are "cc_tools" and "miniperl". They occupy the whole (sub)directory, and nothing needs to be done in this subdirectory later during the "all" stage. They are also constructed using system makefiles. We must build the .depend early in the build-tools stage because: 1) They use (and depend on) the host environment. 2) If we don't do this in build-tools, the "depend" stage of buildworld will do this for us; wrong library and header dependencies will be recorded (DESTDIR=${WORLDTMP}) and, what's worse, the "all" stage may then clobber the build-architecture format tools (that we built in the build-tools stage) with the target-architecture format ones, breaking cross build. In the second category there are all other build-tools. They share their directory with the "main" module that needs them in the "all" stage, and they don't show up themselves in the .depend file. The portion of this fix was already committed in gnu/usr.bin/cc/cc_tools/Makefile,v 1.52. 4. "libperl" is no longer a build tool, and "miniperl" is the stand-alone application. I had to make this change because build-tools and "all" stages share the same object directory. Without this change, if we cross compile, libperl.a is first built for the build architecture during the build-tools stage (for the purposes of immediate linkage with "miniperl"). Later on, the "all" stage sees this library as up-to-date, and doesn't rebuild it. The effect is that the wrong format static libperl library is installed with installworld. 5. Fixed "includes" to install secure/lib/libtelnet headers if required. Reviewed by: bde
2001-09-29 13:17:54 +00:00
# we're in kernel-land. Since only TARGET_ARCH is (expected) to
Fix cross-building further. Introduce ${TARGET} defaulting to ${MACHINE} which should be set to whatever your target ${MACHINE} is, and use that with world-related stages. That is, to build pc98 on alpha, one now needs to set both TARGET_ARCH=i386 and TARGET=pc98. The scope of ${TARGET} is limited to Makefile.inc1 and cross-tools. In particular, this change was tested to fix: 1. Cross building of "alpha" on i386. The breakage was introduced by rev. 1.10 to sbin/i386/Makefile (missing <machine/cronyx.h>). 2. Descending into machine-specific subdirs for a different arch. Previously, sbin/i386 and usr.sbin/boot0cfg were descended into when cross-building "alpha" or pc98 on i386. 3. Fixes pc98 cross-building which was horribly broken, caused by not setting MACHINE correctly (most ${MACHINE} == pc98 checking Makefiles put -DPC98 to CFLAGS).
2001-10-25 07:28:55 +00:00
# be set to cross-build, we have to make sure TARGET is set
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
# properly.
Add KERNFAST define. When defined, it skips all the config, depends and clean steps. KERNFAST was selected to complement KERNCONF which is typically used in these scenarios (especially with cross building). Reviewed by: arch@
2009-01-15 04:19:03 +00:00
.if defined(KERNFAST)
NO_KERNELCLEAN= t
NO_KERNELCONFIG= t
NO_KERNELDEPEND= t
Add NO_KERNELOBJ flag, similar to NO_KERNEL{CONFIG,DEPEND,CLEAN}, which disables doing a make obj. Use it when you know it will work only. KERNFAST now implies NO_KERNELOBJ, since you don't need to keep doing obj when doing incremental kernel builds.
2009-12-16 02:54:34 +00:00
NO_KERNELOBJ= t
Implement an idea from Sam Leffler: make KERNFAST=blah buildkernel is now a short cut for make KERNCONF=blah -DKERNFAST buildkernel This change works for all kernel config files not named "1". I did that to make sure that make -DKERNFAST buildkernel remains the same as make -DKERNFAST KERNCONF=GENERIC buildkernel rather than trying to build and configure "1". I've never seen a kernel config file named "1," so I think this is a good compromise.
2009-01-23 18:23:16 +00:00
# Shortcut for KERNCONF=Blah -DKERNFAST is now KERNFAST=Blah
.if !defined(KERNCONF) && ${KERNFAST} != "1"
KERNCONF=${KERNFAST}
.endif
Add KERNFAST define. When defined, it skips all the config, depends and clean steps. KERNFAST was selected to complement KERNCONF which is typically used in these scenarios (especially with cross building). Reviewed by: arch@
2009-01-15 04:19:03 +00:00
.endif
Connect powerpc64 to the build. It is not presently part of make universe, which will be added soon. Reviewed by: imp
2010-07-13 21:19:59 +00:00
.if ${TARGET_ARCH} == "powerpc64"
KERNCONF?= GENERIC64
.else
Using "KERNEL" for buildkernel was a very very bad mistake. $KERNEL is already used by the kernel makefiles themselves, and this leads to a lot of trouble when people put "KERNEL=MYKERNEL" in make.conf. Bite the bullet and change it to KERNCONF instead, before it gets too far entrenched. The kernel Makefiles use ${KERNEL} as the name of what to install the kernel as, eg: /boot/${KERNEL}/kernel or /${KERNEL}. This leads to much unhappiness with things like /LOCAL instead of /kernel. buildkernel is severely limited as it is only useful directly after a buildworld. Reviewed by: jhb
2001-01-22 07:29:48 +00:00
KERNCONF?= GENERIC
Provide backwards compatable recognition of ${KERNEL}. You should be able to use KERNEL= again with buildkernel, but it will point you at KERNCONF= and press on regardless.
2001-01-23 09:52:50 +00:00
.endif
Allow one to specify what the installed kernel's name is by setting "INSTKERNNAME". Reviewed by: marcel
2000-09-03 02:58:39 +00:00
INSTKERNNAME?= kernel
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
Rename KRNLSRCDIR to KERNSRCDIR and allow it to be overridden. The name change was to be consistent with other overridable variables such as KERNCONFDIR and KERNCONF.
2003-04-16 21:05:06 +00:00
KERNSRCDIR?= ${.CURDIR}/sys
KRNLCONFDIR= ${KERNSRCDIR}/${TARGET}/conf
KRNLOBJDIR= ${OBJTREE}${KERNSRCDIR}
Change the name of KRNLDEFDIR to KERNCONFDIR. Suggested by Bruce, since the latter is more acceptable for a variable that is externally visible. Fix a style nit with a long line.
2001-08-27 12:01:46 +00:00
KERNCONFDIR?= ${KRNLCONFDIR}
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
BUILDKERNELS=
INSTALLKERNEL=
Using "KERNEL" for buildkernel was a very very bad mistake. $KERNEL is already used by the kernel makefiles themselves, and this leads to a lot of trouble when people put "KERNEL=MYKERNEL" in make.conf. Bite the bullet and change it to KERNCONF instead, before it gets too far entrenched. The kernel Makefiles use ${KERNEL} as the name of what to install the kernel as, eg: /boot/${KERNEL}/kernel or /${KERNEL}. This leads to much unhappiness with things like /LOCAL instead of /kernel. buildkernel is severely limited as it is only useful directly after a buildworld. Reviewed by: jhb
2001-01-22 07:29:48 +00:00
.for _kernel in ${KERNCONF}
Change the name of KRNLDEFDIR to KERNCONFDIR. Suggested by Bruce, since the latter is more acceptable for a variable that is externally visible. Fix a style nit with a long line.
2001-08-27 12:01:46 +00:00
.if exists(${KERNCONFDIR}/${_kernel})
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
BUILDKERNELS+= ${_kernel}
.if empty(INSTALLKERNEL)
INSTALLKERNEL= ${_kernel}
.endif
.endif
.endfor
Move stray targets out of the xdev section.
2014-03-30 22:25:01 +00:00
buildkernel ${WMAKE_TGTS} ${.ALLTARGETS:M_*}: .MAKE
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
#
# buildkernel
#
# Builds all kernels defined by BUILDKERNELS.
#
buildkernel:
Fail the 'buildkernel' target if not even one of the specified kernel configuration files was found. Reviewed by: obrien
2000-10-25 04:31:32 +00:00
.if empty(BUILDKERNELS)
Add missing continuation.
2005-02-27 11:48:45 +00:00
@echo "ERROR: Missing kernel configuration file(s) (${KERNCONF})."; \
Improved the description of the installkernel targets. Don't hide what we do to force failures for the installkernel targets or other targets.
2004-03-04 09:14:30 +00:00
false
Fail the 'buildkernel' target if not even one of the specified kernel configuration files was found. Reviewed by: obrien
2000-10-25 04:31:32 +00:00
.endif
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
@echo
Also add some timing information for kernel builds so that it's easy to do "make world kernel |grep -e '^>>>'" and get a complete event log.
2001-01-21 23:44:41 +00:00
.for _kernel in ${BUILDKERNELS}
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
@echo "--------------------------------------------------------------"
setlocale(3) has been fixed to match POSIX standard: LC_ALL takes precedence over other LC_* envariables.
2001-03-02 16:52:14 +00:00
@echo ">>> Kernel build for ${_kernel} started on `LC_ALL=C date`"
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
@echo "--------------------------------------------------------------"
@echo "===> ${_kernel}"
Create ${KRNLOBJDIR} before running config(8), since config(8) does not create required parent directories of the kernel compile directory specified with its -d option.
2000-04-27 09:20:18 +00:00
mkdir -p ${KRNLOBJDIR}
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
.if !defined(NO_KERNELCONFIG)
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 1: configuring the kernel"
@echo "--------------------------------------------------------------"
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
cd ${KRNLCONFDIR}; \
PATH=${TMPPATH} \
Change the name of KRNLDEFDIR to KERNCONFDIR. Suggested by Bruce, since the latter is more acceptable for a variable that is externally visible. Fix a style nit with a long line.
2001-08-27 12:01:46 +00:00
config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} \
Add appropriate quoting to allow building with a KERNCONFDIR containing spaces. PR: kern/162736 MFC after: 1 week
2014-05-03 09:24:20 +00:00
-I '${KERNCONFDIR}' '${KERNCONFDIR}/${_kernel}'
Use 'make clean' instead of 'config -r', and only if the 'depend' step has been skipped. We went to a lot of trouble to make the 'blow away' stage unneeded, and it has not been needed for quite some time.
2001-01-22 23:10:01 +00:00
.endif
NOCLEAN -> NO_CLEAN NOCLEANDIR -> NO_CLEANDIR
2004-12-21 12:21:26 +00:00
.if !defined(NO_CLEAN) && !defined(NO_KERNELCLEAN)
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 2.1: cleaning up the object tree"
@echo "--------------------------------------------------------------"
Fold some common stuff into a macro ${KMAKE}.
2005-11-22 11:31:03 +00:00
cd ${KRNLOBJDIR}/${_kernel}; ${KMAKE} ${CLEANDIR}
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
.endif
Add NO_KERNELOBJ flag, similar to NO_KERNEL{CONFIG,DEPEND,CLEAN}, which disables doing a make obj. Use it when you know it will work only. KERNFAST now implies NO_KERNELOBJ, since you don't need to keep doing obj when doing incremental kernel builds.
2009-12-16 02:54:34 +00:00
.if !defined(NO_KERNELOBJ)
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 2.2: rebuilding the object tree"
@echo "--------------------------------------------------------------"
Fold some common stuff into a macro ${KMAKE}.
2005-11-22 11:31:03 +00:00
cd ${KRNLOBJDIR}/${_kernel}; ${KMAKE} obj
Add NO_KERNELOBJ flag, similar to NO_KERNEL{CONFIG,DEPEND,CLEAN}, which disables doing a make obj. Use it when you know it will work only. KERNFAST now implies NO_KERNELOBJ, since you don't need to keep doing obj when doing incremental kernel builds.
2009-12-16 02:54:34 +00:00
.endif
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 2.3: build tools"
@echo "--------------------------------------------------------------"
This change builds kernel tools based on the same assumption as building the kernel itself: If building for the same architecture as the build host, the kernel build assumes that the host toolchain is capable of building the kernel. If it's not, "make kernel-toolchain" will bootstrap a new set of tools that will work. With this change the same assumptions are made for building kernel tools, and the existing host toolchain is used to do the build (notably, the build doesn't link the tools with the legacy libraries, which may not even exist). If ever for some reason the host toolchain isn't capable of building the kernel tools, then doing a "make kernel-toolchain" will bootstrap newer tools to get the job done. So when built as part of buildworld or kernel-toolchain, the kernel tools are built using the XMAKE (via BMAKE) commands and environment. When built as part of building just the kernel on a same-target host, the tools are built using the new KTMAKE commands and environment. What doesn't jump out at you in the diffs is that the difference between BMAKE and KTMAKE is that BMAKE contains this magic line which changes how the build is done because it changes what files get included for .include <bsd.prog.mk> and other standard includes: MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}" and KTMAKE doesn't, and contains this instead: TOOLS_PREFIX=${WORLDTMP} Hopefully this brings the "how to build aicasm with the right toolchain" saga to a conclusion that works in all usage scenarios that have historically been supported.
2013-11-09 00:15:36 +00:00
${_+_}cd ${.CURDIR}; ${KTMAKE} kernel-tools
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
.if !defined(NO_KERNELDEPEND)
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 3.1: making dependencies"
@echo "--------------------------------------------------------------"
Fold some common stuff into a macro ${KMAKE}.
2005-11-22 11:31:03 +00:00
cd ${KRNLOBJDIR}/${_kernel}; ${KMAKE} depend -DNO_MODULES_OBJ
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
.endif
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo
@echo "--------------------------------------------------------------"
Temporarily revert r251058 - it breaks documented use of makeoptions including the tinderbox. http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-i386.full make: don't know how to make modules-all. Stop make: stopped in /obj/i386.i386/src/sys/PAE *** Error code 2
2013-05-28 21:29:05 +00:00
@echo ">>> stage 3.2: building everything"
Comment various stages of buildkernel, symmetrical to buildworld.
2004-03-18 10:17:03 +00:00
@echo "--------------------------------------------------------------"
Temporarily revert r251058 - it breaks documented use of makeoptions including the tinderbox. http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-i386.full make: don't know how to make modules-all. Stop make: stopped in /obj/i386.i386/src/sys/PAE *** Error code 2
2013-05-28 21:29:05 +00:00
cd ${KRNLOBJDIR}/${_kernel}; ${KMAKE} all -DNO_MODULES_OBJ
Also add some timing information for kernel builds so that it's easy to do "make world kernel |grep -e '^>>>'" and get a complete event log.
2001-01-21 23:44:41 +00:00
@echo "--------------------------------------------------------------"
setlocale(3) has been fixed to match POSIX standard: LC_ALL takes precedence over other LC_* envariables.
2001-03-02 16:52:14 +00:00
@echo ">>> Kernel build for ${_kernel} completed on `LC_ALL=C date`"
Also add some timing information for kernel builds so that it's easy to do "make world kernel |grep -e '^>>>'" and get a complete event log.
2001-01-21 23:44:41 +00:00
@echo "--------------------------------------------------------------"
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
.endfor
#
Improved the description of the installkernel targets. Don't hide what we do to force failures for the installkernel targets or other targets.
2004-03-04 09:14:30 +00:00
# installkernel, etc.
Add a buildkernel and an installkernel target. With these targets users can more easily upgrade. buildworld now makes usr.sbin/config in bootstrap-tools so that when you first make buildworld, buildkernel will use config(8) from the temp. world tree (and of course also the compiler). Which kernel to built is determined by the KERNEL variable. You can have as many kernels listed as you like. When a config file exists for the given MACHINE it will be built. When KERNEL has not been defined it will be set to "GENERIC GENERIC98". The first valid kernel named in the list will be used by the installkernel target. When NOCLEAN is defined the kernel object directory is *not* removed by config first. This is in line with normal buildworld behaviour. The buildkernel target makes aicasm in sys/dev/aic7xxx first and unconditionally. This hack allows us to cross-build kernels and can go away when the problem is solved in a structural way.
2000-01-09 17:56:40 +00:00
#
# Install the kernel defined by INSTALLKERNEL
#
Commit the first set of files for changing time_t on freebsd/sparc64 from a 32-bit value to a 64-bit value. This commit does not actually change anything. It merely provides instructions, scripts, and a safety measure in Makefile.inc1 for people who want to make the change. The real change to 64-bit time_t's on sparc64 is scheduled to happen on March 10th, assuming that so major problems are found between now and then by early-adopters. Reviewed by: freebsd-sparc64
2004-03-03 19:36:20 +00:00
installkernel installkernel.debug \
Fix 'make installcheck' to check for missing UID/GID as well, broken since r249893, by adding a separate _installcheck_world and _installcheck_kernel so the destination targets can be more explicit on which they are needed for. installcheck will call both, while installworld only calls _installcheck_world and installkernel only calls _installcheck_kernel While here, mark the internal targets as starting with _. Reported by: des Reviewed by: des Pointyhat to: bdrewery Approved by: re (delphij)
2013-09-18 00:33:24 +00:00
reinstallkernel reinstallkernel.debug: _installcheck_kernel
Catch typos in the kernel name specified for an "installkernel" invocation early on, rather than failing later with an obscure error message. Make error messages appear consistent.
2003-02-07 07:29:57 +00:00
.if empty(INSTALLKERNEL)
Add missing continuation.
2005-02-27 11:48:45 +00:00
@echo "ERROR: No kernel \"${KERNCONF}\" to install."; \
Improved the description of the installkernel targets. Don't hide what we do to force failures for the installkernel targets or other targets.
2004-03-04 09:14:30 +00:00
false
Catch typos in the kernel name specified for an "installkernel" invocation early on, rather than failing later with an obscure error message. Make error messages appear consistent.
2003-02-07 07:29:57 +00:00
.endif
Create hierarchy before installing a new kernel. This is needed because we require that a new kernel be installed prior to a new world, and we may need some new directories to succeed. Once MFCed, this will also help those poor souls who redundantly ``mv /modules /modules.old'' in RELENG_4 before an installkernel. Requested by: many MFC after: 3 days
2004-03-13 15:46:34 +00:00
@echo "--------------------------------------------------------------"
Correct the kernel config name printed out during install. PR: 156579 Submitted by: dhw
2011-05-05 00:43:55 +00:00
@echo ">>> Installing kernel ${INSTALLKERNEL}"
Create hierarchy before installing a new kernel. This is needed because we require that a new kernel be installed prior to a new world, and we may need some new directories to succeed. Once MFCed, this will also help those poor souls who redundantly ``mv /modules /modules.old'' in RELENG_4 before an installkernel. Requested by: many MFC after: 3 days
2004-03-13 15:46:34 +00:00
@echo "--------------------------------------------------------------"
Add reinstallkernel target. Does same thing as installkernel, but executes the reinstall target rather than the install target that installkernel does.
2000-09-17 21:02:58 +00:00
cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
For installkernel, use the fresh tools (if we've built them with buildworld). Reviewed by: imp, marcel Approved by: re (rwatson)
2002-12-02 14:03:40 +00:00
${CROSSENV} PATH=${TMPPATH} \
Fix installworld when nmtree is not on the host by only adding it to ITOOLS when we will be using the host copy. Fix installkernel when -DNO_ROOT is set.
2013-01-29 21:48:10 +00:00
${MAKE} ${IMAKE_INSTALL} KERNEL=${INSTKERNNAME} ${.TARGET:S/kernel//}
Allow one to specify what the installed kernel's name is by setting "INSTKERNNAME". Reviewed by: marcel
2000-09-03 02:58:39 +00:00
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
distributekernel distributekernel.debug:
.if empty(INSTALLKERNEL)
@echo "ERROR: No kernel \"${KERNCONF}\" to install."; \
false
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.endif
mkdir -p ${DESTDIR}/${DISTDIR}
.if defined(NO_ROOT)
echo "#${MTREE_MAGIC}" > ${DESTDIR}/${DISTDIR}/kernel.premeta
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
.endif
cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
${IMAKEENV} ${IMAKE_INSTALL:S/METALOG/kernel.premeta/} \
${IMAKE_MTREE} PATH=${TMPPATH} ${MAKE} KERNEL=${INSTKERNNAME} \
Always define INSTALL_DDIR and define it such that it contains no extra / characters rather than removing them later on. This should fix release builds. PR: conf/178963 Reviewed by: gjb, hrs
2013-05-30 14:09:58 +00:00
DESTDIR=${INSTALL_DDIR}/kernel \
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
${.TARGET:S/distributekernel/install/}
Fix distributekernel in the non NO_ROOT case. PR: conf/178775 Submitted by: Garrett Cooper <yaneurabeya@gmail.com>
2013-05-20 21:16:38 +00:00
.if defined(NO_ROOT)
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
sed -e 's|^./kernel|.|' ${DESTDIR}/${DISTDIR}/kernel.premeta > \
${DESTDIR}/${DISTDIR}/kernel.meta
Fix distributekernel in the non NO_ROOT case. PR: conf/178775 Submitted by: Garrett Cooper <yaneurabeya@gmail.com>
2013-05-20 21:16:38 +00:00
.endif
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
.for _kernel in ${BUILDKERNELS:S/${INSTALLKERNEL}//}
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.if defined(NO_ROOT)
echo "#${MTREE_MAGIC}" > ${DESTDIR}/${DISTDIR}/kernel.${_kernel}.premeta
.endif
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
cd ${KRNLOBJDIR}/${_kernel}; \
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
${IMAKEENV} ${IMAKE_INSTALL:S/METALOG/kernel.${_kernel}.premeta/} \
${IMAKE_MTREE} PATH=${TMPPATH} ${MAKE} \
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
KERNEL=${INSTKERNNAME}.${_kernel} \
Always define INSTALL_DDIR and define it such that it contains no extra / characters rather than removing them later on. This should fix release builds. PR: conf/178963 Reviewed by: gjb, hrs
2013-05-30 14:09:58 +00:00
DESTDIR=${INSTALL_DDIR}/kernel.${_kernel} \
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
${.TARGET:S/distributekernel/install/}
Don't parse NO_ROOT metadata for extra kernels if NO_ROOT isn't defined. Approved by: re (gjb) MFC after: 1 week
2013-09-24 19:09:21 +00:00
.if defined(NO_ROOT)
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
sed -e 's|^./kernel|.|' \
${DESTDIR}/${DISTDIR}/kernel.${_kernel}.premeta > \
${DESTDIR}/${DISTDIR}/kernel.${_kernel}.meta
Don't parse NO_ROOT metadata for extra kernels if NO_ROOT isn't defined. Approved by: re (gjb) MFC after: 1 week
2013-09-24 19:09:21 +00:00
.endif
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
.endfor
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
packagekernel:
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.if defined(NO_ROOT)
cd ${DESTDIR}/${DISTDIR}/kernel; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - @${DESTDIR}/${DISTDIR}/kernel.meta | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/kernel.txz
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.for _kernel in ${BUILDKERNELS:S/${INSTALLKERNEL}//}
cd ${DESTDIR}/${DISTDIR}/kernel.${_kernel}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - @${DESTDIR}/${DISTDIR}/kernel.${_kernel}.meta | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/kernel.${_kernel}.txz
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.endfor
.else
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
cd ${DESTDIR}/${DISTDIR}/kernel; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - . | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/kernel.txz
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
.for _kernel in ${BUILDKERNELS:S/${INSTALLKERNEL}//}
cd ${DESTDIR}/${DISTDIR}/kernel.${_kernel}; \
release: use xz via pipe when compressing the tarballs. libarchive(3) doesn't support the new liblzma API yet, but this change allows us to enable multi-threaded xz compression. ``make release'' should now finish in half the time on a machine with several cores and fast disks (our typical build server). This behaviour only applies when building a release and it doesn't affect buildworld/installworld. To disable threaded xz compression, set XZ_THREADS=1. Reviewed by: gjb Tested by: gjb
2015-02-17 23:13:45 +00:00
tar cvf - . | \
${XZ_CMD} > ${DESTDIR}/${DISTDIR}/kernel.${_kernel}.txz
Restore functionality to pack several kernels into release. All kernels specified by KERNCONF are built and packed into release. The first one is packed into kernel.txz, all others to kernel.CONFIG.txz. The first one is installed on bootables in /boot.
2012-01-15 08:36:25 +00:00
.endfor
Implement NO_ROOT support for distributekernel and packagekernel.
2013-05-16 18:37:14 +00:00
.endif
Improve the distributeworld target in Makefile.inc1 and update the release infrastructure to use it. make distributeworld can now be used without preparing its environment first and installs games into its distribution using the regular make distribute logic instead of post-processing with a script. Also add two new targets, packageworld and packagekernel, that tar up the results of distributeworld and distributekernel (also new), respectively.
2011-03-02 14:39:26 +00:00
Connect the kernel subsystem API documentation generation framework to the build infrastructure: "make doxygen" Changes to the man pages will be made when some defaults are revisited. Requested by: gnn
2006-05-26 18:10:06 +00:00
#
# doxygen
#
# Build the API documentation with doxygen
#
doxygen:
@if [ ! -x `/usr/bin/which doxygen` ]; then \
echo "You need doxygen (devel/doxygen) to generate the API documentation of the kernel." | /usr/bin/fmt; \
exit 1; \
fi
Fix doxygen target. Submitted by: "Alexander Mogilny" <sg@astral.ntu-kpi.kiev.ua> Pointy hat to: netchild
2006-08-02 15:26:15 +00:00
cd ${.CURDIR}/tools/kerneldoc/subsys && ${MAKE} obj all
Connect the kernel subsystem API documentation generation framework to the build infrastructure: "make doxygen" Changes to the man pages will be made when some defaults are revisited. Requested by: gnn
2006-05-26 18:10:06 +00:00
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
# update
#
Update comments to reflect use of svn/svnup to keep the src/ tree up to date. MFC after: 3 days
2013-05-28 21:57:55 +00:00
# Update the source tree(s), by running svn/svnup to update to the
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
# latest copy.
#
update:
r245757 introduced warning output if update method is set to CVS_UPDATE or SUP_UPDATE. CVS exporter for head/ is turned off for nearly one month now. It is finally time to swing the ax at these update methods. Reviewed by: eadler MFC after: 1 month
2013-05-28 23:43:47 +00:00
.if (defined(CVS_UPDATE) || defined(SUP_UPDATE)) && !defined(SVN_UPDATE)
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
r245757 introduced warning output if update method is set to CVS_UPDATE or SUP_UPDATE. CVS exporter for head/ is turned off for nearly one month now. It is finally time to swing the ax at these update methods. Reviewed by: eadler MFC after: 1 month
2013-05-28 23:43:47 +00:00
@echo "CVS_UPDATE and SUP_UPDATE are no longer supported."
@echo "Please see: https://wiki.freebsd.org/CvsIsDeprecated"
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
@echo "--------------------------------------------------------------"
r245757 introduced warning output if update method is set to CVS_UPDATE or SUP_UPDATE. CVS exporter for head/ is turned off for nearly one month now. It is finally time to swing the ax at these update methods. Reviewed by: eadler MFC after: 1 month
2013-05-28 23:43:47 +00:00
@exit 1
Allow "make update" work with SVN, if you take the time to set up your /etc/make.conf properly. Only one SCM? I do not think this is right. Now I have fixed it.
2009-06-14 15:16:24 +00:00
.endif
.if defined(SVN_UPDATE)
r245757 introduced warning output if update method is set to CVS_UPDATE or SUP_UPDATE. CVS exporter for head/ is turned off for nearly one month now. It is finally time to swing the ax at these update methods. Reviewed by: eadler MFC after: 1 month
2013-05-28 23:43:47 +00:00
@echo "--------------------------------------------------------------"
@echo ">>> Updating ${.CURDIR} using Subversion"
@echo "--------------------------------------------------------------"
@(cd ${.CURDIR} && ${SVN} update ${SVNFLAGS})
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.endif
#
# ------------------------------------------------------------------------
#
# From here onwards are utility targets used by the 'make world' and
# related targets. If your 'world' breaks, you may like to try to fix
# the problem and manually run the following targets to attempt to
# complete the build. Beware, this is *not* guaranteed to work, you
# need to have a pretty good grip on the current state of the system
# to attempt to manually finish it. If in doubt, 'make world' again.
#
#
Add some more explanation to the different phases of the build.
2015-03-25 21:59:36 +00:00
# legacy: Build compatibility shims for the next three targets. This is a minimal
# set of tools and shims necessary to compensate for older systems which don't have
# the APIs that the targets built in bootstrap-tools, build-tools or cross-tools.
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien.
2003-04-06 21:46:44 +00:00
legacy:
Up the minimum system to build FreeBSD current to 8.0-RELEASE. The issues with vendors that needed 7.x support have been resolved. Many vendors are still using 8.x build platforms, however, so bumping this up to 9.0 will have to wait until that is resolved. Actual support for building from 8.x still relies on those vendors fixing bugs that are present as most developers have moved onto 9.x or newer platforms. Reviewed by: marcel@
2014-04-13 05:21:30 +00:00
.if ${BOOTSTRAPPING} < 800107 && ${BOOTSTRAPPING} != 0
@echo "ERROR: Source upgrades from versions prior to 8.0 not supported."; \
Support source upgrades from at least 6.0-RELEASE. Reviewed by: imp, obrien
2008-01-23 22:21:36 +00:00
false
.endif
We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. This 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@
2003-04-06 03:50:28 +00:00
.for _tool in tools/build
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,includes,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX}/legacy includes && \
${MAKE} DIRPRFX=${_tool}/ depend && \
${MAKE} DIRPRFX=${_tool}/ all && \
-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien.
2003-04-06 21:46:44 +00:00
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX}/legacy install
We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. This 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@
2003-04-06 03:50:28 +00:00
.endfor
Moved libbuild target to where it belongs. Added a comment.
2003-04-06 21:33:49 +00:00
#
Add some more explanation to the different phases of the build.
2015-03-25 21:59:36 +00:00
# bootstrap-tools: Build tools needed for compatibility. These are binaries that
# are built to build other binaries in the system. However, the focus of these
# binaries is usually quite narrow. Bootstrap tools use the host's compiler and
# libraries, augmented by -legacy.
Moved libbuild target to where it belongs. Added a comment.
2003-04-06 21:33:49 +00:00
#
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
_bt= _bootstrap-tools
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_GAMES} != "no"
Moved libbuild target to where it belongs. Added a comment.
2003-04-06 21:33:49 +00:00
_strfile= games/fortune/strfile
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_CXX} != "no"
As threatened, drop support for source upgrades from pre-5.3. Inspired by: obrien
2005-02-27 11:22:58 +00:00
_gperf= gnu/usr.bin/gperf
Groff after 2002/10/15 has no known backward compatibility issues, but we always want the latest macro files.
2003-04-30 10:58:52 +00:00
.endif
Flesh out WITHOUT_GROFF support to DTRT. A full featured groff is required during buildworld, so build it always and don't rely on it being present on the host system. vgrind(1) is tightly coupled to a roff processor and will not be built/installed when groff is disabled. Also much of the roff'ed documentation under share/doc will not be built/installed when WITHOUT_GROFF is defined. Reviewed by: ru (partial)
2011-02-22 08:13:49 +00:00
.if ${MK_GROFF} != "no"
Replace groff's soelim by soeliminate(1) renamed soelim(1)
2015-05-01 20:08:25 +00:00
_groff= gnu/usr.bin/groff \
usr.bin/soelim
Wrap gperf & groff wth NO_CXX.
2003-05-31 21:29:38 +00:00
.endif
Groff after 2002/10/15 has no known backward compatibility issues, but we always want the latest macro files.
2003-04-30 10:58:52 +00:00
Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT The _SUPPORT knobs have a consistent meaning which differs from the behaviour controlled by this knob. As the knob is opt-out and has not appeared in a release the impact should be low. Suggested by: imp, wblock MFC after: 1 week
2014-06-30 00:20:12 +00:00
.if ${MK_VT} != "no"
Build vt(4) fonts during buildworld vtfontcvt(8) is now built during buildworld, so can be used as a bootstrap tool to create vt(4) fonts from source .hex or .bdf font files, rather than having uuencoded binary fonts in the tree. Sponsored by: The FreeBSD Foundation
2014-06-12 18:31:32 +00:00
_vtfontcvt= usr.bin/vtfontcvt
.endif
Move sed(1) from cross-tools to bootstrap-tools.
2009-10-21 19:39:34 +00:00
.if ${BOOTSTRAPPING} < 900002
_sed= usr.bin/sed
.endif
Connect flex 2.5.37 to the build and bump __FreeBSD_version.
2013-05-21 19:32:35 +00:00
.if ${BOOTSTRAPPING} < 1000002
m4 now requires libohash, ensure it gets built when bootstrapping.
2014-08-07 21:37:03 +00:00
_m4= lib/libohash \
usr.bin/m4
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
${_bt}-usr.bin/m4: ${_bt}-lib/libohash
Connect flex 2.5.37 to the build and bump __FreeBSD_version.
2013-05-21 19:32:35 +00:00
.endif
Always bootstrap nmtree if it is not available on the host. It is fairly small and it is quite annoying to get all the way through buildworld only to discover that you forgot the DB_FROM_SRC (or soon NO_ROOT) option.
2013-01-21 23:12:50 +00:00
.if ${BOOTSTRAPPING} < 1000026
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
_nmtree= lib/libnetbsd \
usr.sbin/nmtree
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
${_bt}-usr.sbin/nmtree: ${_bt}-lib/libnetbsd
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
.endif
Log the addition of login.conf.db, passwd, pwd.db, and spwd.db via cat -l. Make cat a bootstrap tool to facilitate this.
2013-01-29 22:17:58 +00:00
.if ${BOOTSTRAPPING} < 1000027
_cat= bin/cat
.endif
10 has a new flex (2.5.37) and the config.h for unbound has been updated to take this into account. Alas it breaks source upgrade from any version of 9 because flex is not built as a bootstrap-tools (it would be for older versions). That means "libunbound/configlexer.c" is built with the old flex but using config.h for the new one. Build is thus broken going from 9.* to 10. Make flex a bootstrap-tools entry if host is less than 1000033 to take into account the flex update in 10. Tested on both 9.2-RC3 and 9.3 by myself and dim@. Running buildworld in head but as both 10 and 11 has the new flex, it will not matter. Reviewed by: imp Approved by: des, imp MFC after: 1 week Phabric: D554
2014-08-07 11:44:30 +00:00
.if ${BOOTSTRAPPING} < 1000033
_lex= usr.bin/lex
.endif
Bump crunch BOOTSTRAPPING for ELF header offset fix in r277557
2015-04-17 16:02:49 +00:00
.if ${BOOTSTRAPPING} < 1001507
_crunch= usr.sbin/crunch
.endif
- Merged awk upstream that includes a fix for a bug exposed by kmod_syms.mk. - Provide a build aid for those who already have a buggy awk(1) installed. Approved by: re (kib)
2011-08-11 10:29:10 +00:00
.if ${BOOTSTRAPPING} >= 900040 && ${BOOTSTRAPPING} < 900041
_awk= usr.bin/awk
.endif
Fix bootstrap on systems with old yacc with small MAXTABLE.
2015-02-18 23:10:15 +00:00
_yacc= lib/liby \
usr.bin/yacc
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
${_bt}-usr.bin/yacc: ${_bt}-lib/liby
Fix bootstrap on systems with old yacc with small MAXTABLE.
2015-02-18 23:10:15 +00:00
Fix atmconfig compilation when MK_ATM == yes and MK_BSNMP == no Makefile.inc1: Always compile gensnmptree with bootstrap-tools when MK_BSNMP != no instead of depending on a potentially stale tool installed on the build host sbin/atm/atmconfig/Makefile: - Always remove oid.h to avoid cluttering up the build/src tree. - Consolidate all of the RESCUE/MK_BSNMP != no logic under one conditional to improve readability - Remove unnecessary ${.OBJDIR} prefixing for oid.h and use ${.TARGET} instead of spelling out oid.h - Add a missing DPADD for ${LIBCRYPTO} when compiled MK_BSNMP == yes and MK_OPENSSL == yes and not compiling for /rescue/rescue sbin/atm/atmconfig/main.c: Change #ifndef RESCUE to #ifdef WITH_BSNMP in main.c to make it clear that we're compiling bsnmp support into atmconfig Approved by: jmmv (mentor) Phabric: D579 PR: 143830 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2014-08-15 21:22:49 +00:00
.if ${MK_BSNMP} != "no"
Sort bootstrap-tools entries.
2006-03-31 14:10:35 +00:00
_gensnmptree= usr.sbin/bsnmpd/gensnmptree
.endif
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
# We need to build tblgen when we're building clang either as
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
# the bootstrap compiler, or as the part of the normal build.
.if ${MK_CLANG_BOOTSTRAP} != "no" || ${MK_CLANG} != "no"
Revert r227403 for now. Since the cross-tools stage purposefully doesn't have ${WORLDTMP}/usr/bin in its PATH, if you build world with CC=clang, tblgen tools from /usr/bin will be used instead of the ones built under ${WORLDTMP}. This can lead to various errors, especially if you upgrade from an older clang. Note that building world with gcc would not experience these problems, because it only uses the tblgen tools in the world stage, where PATH does contain ${WORLDTMP}/usr/bin. Pointy hat to: dim
2011-11-10 20:15:35 +00:00
_clang_tblgen= \
lib/clang/libllvmsupport \
lib/clang/libllvmtablegen \
usr.bin/clang/tblgen \
usr.bin/clang/clang-tblgen
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
${_bt}-usr.bin/clang/clang-tblgen: ${_bt}-lib/clang/libllvmtablegen ${_bt}-lib/clang/libllvmsupport
${_bt}-usr.bin/clang/tblgen: ${_bt}-lib/clang/libllvmtablegen ${_bt}-lib/clang/libllvmsupport
Revert r227403 for now. Since the cross-tools stage purposefully doesn't have ${WORLDTMP}/usr/bin in its PATH, if you build world with CC=clang, tblgen tools from /usr/bin will be used instead of the ones built under ${WORLDTMP}. This can lead to various errors, especially if you upgrade from an older clang. Note that building world with gcc would not experience these problems, because it only uses the tblgen tools in the world stage, where PATH does contain ${WORLDTMP}/usr/bin. Pointy hat to: dim
2011-11-10 20:15:35 +00:00
.endif
Fix bootstrap on systems with old libdwarf and WITHOUT_CDDL ELF Tool Chain tools need libelf and libdwarf. Submitted by: jmallett (earlier version) Reviewed by: jmallett Sponsored by: The FreeBSD Foundation
2015-01-21 21:49:03 +00:00
# ELF Tool Chain libraries are needed for ELF tools and dtrace tools.
Build CTF tools as a part of toolchain for cross-compilation case
2012-03-24 05:30:13 +00:00
# dtrace tools are required for older bootstrap env and cross-build
When libelf and libdwarf were updated, we didn't bump the minimal version needed for CTF tools, so sometimes we'd use the host's CTF tools that didn't work. Be sure to bootstrap in that case.
2014-05-23 00:20:48 +00:00
# pre libdwarf
Fix bootstrap on systems with old libdwarf and WITHOUT_CDDL ELF Tool Chain tools need libelf and libdwarf. Submitted by: jmallett (earlier version) Reviewed by: jmallett Sponsored by: The FreeBSD Foundation
2015-01-21 21:49:03 +00:00
.if ${BOOTSTRAPPING} < 1100006 || (${MACHINE} != ${TARGET} || \
${MACHINE_ARCH} != ${TARGET_ARCH})
_elftoolchain_libs= lib/libelf lib/libdwarf
.if ${MK_CDDL} != "no"
_dtrace_tools= cddl/usr.bin/sgsmsg cddl/lib/libctf cddl/usr.bin/ctfconvert \
cddl/usr.bin/ctfmerge
Fill in missing dependencies for dtrace related tools so the bootstrap-tools compiles properly on older hosts Pointyhat to: me X-MFC with: r279197 MFC after: 2 weeks
2015-02-23 06:46:04 +00:00
${_bt}-cddl/usr.bin/ctfconvert: ${_bt}-lib/libelf ${_bt}-lib/libdwarf ${_bt}-cddl/lib/libctf
${_bt}-cddl/usr.bin/ctfmerge: ${_bt}-lib/libelf ${_bt}-lib/libdwarf ${_bt}-cddl/lib/libctf
Fix bootstrap on systems with old libdwarf and WITHOUT_CDDL ELF Tool Chain tools need libelf and libdwarf. Submitted by: jmallett (earlier version) Reviewed by: jmallett Sponsored by: The FreeBSD Foundation
2015-01-21 21:49:03 +00:00
.endif
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
.endif
Integrate device-tree upstream files into the build process: (1) Invoke cpp to bring in files via #include (although the old /include/ stuff is supported still). (2) bring in files from either vendor tree or freebsd-custom files when building. (3) move all dts* files from sys/boot/fdt/dts to sys/boot/fdt/dts/${MACHINE} as appropriate. (4) encode all the magic to do the build in sys/tools/fdt/make_dtb.sh so that the different places in the tree use the exact same logic. (5) switch back to gpl dtc by default. the bsdl one in the tree has significant issues not easily addressed by those unfamiliar with the code.
2014-02-28 18:29:09 +00:00
# Default to building the GPL DTC, but build the BSDL one if users explicitly
Import new (BSDL) device tree compiler. Now built by default, so that it can't be used on the host system (and not installed on the device, if required). The GPL'd one is still available if there are any devices that need it (make universe passes with it, including kernels that use fdt, but there may be some out-of-tree ones). WITH_GPL_DTC can be used to select the old one, for now. Probably won't be MFC'd, but we'll remove the GPL'd version in head after the new one has had a lot more testing and ship it in 10.0.
2013-01-22 17:49:51 +00:00
# request it.
Fix spurious leading / on dtc path in Makefile.inc1. Spotted by jhb.
2013-01-22 19:40:26 +00:00
_dtc= usr.bin/dtc
Import new (BSDL) device tree compiler. Now built by default, so that it can't be used on the host system (and not installed on the device, if required). The GPL'd one is still available if there are any devices that need it (make universe passes with it, including kernels that use fdt, but there may be some out-of-tree ones). WITH_GPL_DTC can be used to select the old one, for now. Probably won't be MFC'd, but we'll remove the GPL'd version in head after the new one has had a lot more testing and ship it in 10.0.
2013-01-22 17:49:51 +00:00
.if ${MK_GPL_DTC} != "no"
Connect FDT infrastructure to the build system. Reviewed by: imp Sponsored by: The FreeBSD Foundation
2010-06-13 13:02:43 +00:00
_dtc= gnu/usr.bin/dtc
.endif
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
.if ${MK_KERBEROS} != "no"
_kerberos5_bootstrap_tools= \
kerberos5/tools/make-roken \
kerberos5/lib/libroken \
kerberos5/lib/libvers \
kerberos5/tools/asn1_compile \
Add compile_et to kerberos bootstrap tools. This makes it possible to build a regular world on a host without kerberos. PR: conf/178421 Submitted by: Garrett Cooper MFC after: 1 month
2013-05-11 13:44:11 +00:00
kerberos5/tools/slc \
usr.bin/compile_et
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
Serialize all of _kerberos5_bootstrap_tools to avoid build failures involving make bootstrap-tools On the plus side, this also greatly reduces complexity MFC after: 1 week Pointyhat to: ngie Reported by: Willem Jan Withagen <wjw@digiware.nl>
2015-04-21 10:17:25 +00:00
.ORDER: ${_kerberos5_bootstrap_tools:C/^/${_bt}-/g}
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
.endif
Unbreak build following rev. 282726 (Makefile.inc1): add dependency of xinstall on libmd to avoid failure of parallel bootstrap. (lib/libmd/*.h): do not redefine symbols if already defined as macros (libcrypt uses the same sources internally, redefining symbols with a prefix of its own). Fixes build failures caused by previous change to libmd. Reported by: ian Pointy hat to: thomas
2015-05-10 21:21:52 +00:00
# Rebuild up-to-date libmd for xinstall
${_bt}-usr.bin/xinstall: ${_bt}-lib/libmd
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
bootstrap-tools: .PHONY
+ DTrace as a bootstrap tool is only needed on certain older systems. + Be more consistent between BMAKE and TMAKE. + Add NO_CTF to crosstools as is done for bootstrap and build tools. Reviewed by: marcel
2011-05-11 17:50:19 +00:00
# Please document (add comment) why something is in 'bootstrap-tools'.
# Try to bound the building of the bootstrap-tool to just the
# FreeBSD versions that need the tool built at this stage of the build.
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
.for _tool in \
Revert r227403 for now. Since the cross-tools stage purposefully doesn't have ${WORLDTMP}/usr/bin in its PATH, if you build world with CC=clang, tblgen tools from /usr/bin will be used instead of the ones built under ${WORLDTMP}. This can lead to various errors, especially if you upgrade from an older clang. Note that building world with gcc would not experience these problems, because it only uses the tblgen tools in the world stage, where PATH does contain ${WORLDTMP}/usr/bin. Pointy hat to: dim
2011-11-10 20:15:35 +00:00
${_clang_tblgen} \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
${_kerberos5_bootstrap_tools} \
Fix bootstrap on systems with old libdwarf and WITHOUT_CDDL ELF Tool Chain tools need libelf and libdwarf. Submitted by: jmallett (earlier version) Reviewed by: jmallett Sponsored by: The FreeBSD Foundation
2015-01-21 21:49:03 +00:00
${_elftoolchain_libs} \
Add the DTrace build tools to the list of tools and pass NO_CTF to all the stages of the build which don't require CTF conversion.
2008-05-23 04:22:14 +00:00
${_dtrace_tools} \
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
${_strfile} \
${_gperf} \
${_groff} \
Connect FDT infrastructure to the build system. Reviewed by: imp Sponsored by: The FreeBSD Foundation
2010-06-13 13:02:43 +00:00
${_dtc} \
- Merged awk upstream that includes a fix for a bug exposed by kmod_syms.mk. - Provide a build aid for those who already have a buggy awk(1) installed. Approved by: re (kib)
2011-08-11 10:29:10 +00:00
${_awk} \
Log the addition of login.conf.db, passwd, pwd.db, and spwd.db via cat -l. Make cat a bootstrap tool to facilitate this.
2013-01-29 22:17:58 +00:00
${_cat} \
Add lorder(1) to the list of bootstrap-tools.
2005-02-19 10:25:42 +00:00
usr.bin/lorder \
Revert r208353. It did not work as I expected because WITHOUT_MAN is set for bootstrap-tools target and WITHOUT_MAN_UTILS was implied by default. Pointy hat: jkim
2010-05-20 20:15:56 +00:00
usr.bin/makewhatis \
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
usr.bin/rpcgen \
Move sed(1) from cross-tools to bootstrap-tools.
2009-10-21 19:39:34 +00:00
${_sed} \
Disable K&R style function definitions for WARNS=6. Unfortunately there are two slight problems with that: - Yacc and lex might generate code that generates warnings because of this. Require yacc and lex to be rebuilt during bootstrap. I'm not incrementing __FreeBSD_version here, because I assume someone else will do this eventually. - When running `make buildkernel', it uses share/mk from the source treeo to build aicasm. Because aicasm also depends on lex, this would break. Lower WARNS to 5 for now. We should just increment it to 6 again somewhere in the very far future.
2009-12-31 00:07:26 +00:00
${_yacc} \
Connect flex 2.5.37 to the build and bump __FreeBSD_version.
2013-05-21 19:32:35 +00:00
${_m4} \
Bump __FreeBSD_version for the byacc import, and update _bootstrap_tools.
2012-05-22 15:59:07 +00:00
${_lex} \
- Fix libmd dependency. It is needed in the bootstrap library list because usr.bin/xinstall depends on it. - Remove libutil from usr.bin/xinstall/Makefile. No symbol was actually used. Reviewed by: brooks
2013-02-14 08:32:07 +00:00
lib/libmd \
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
usr.bin/xinstall \
After revision 1.4 of `src/usr.sbin/bsnmpd/bsnmpd/Makefile' the gensnmptree utility is required at "make depend" time, because it is used to generate `oid.h' for bsnmpd. This means that all versions of HEAD before 2004/01/23 16:22:49 need gensnmptree as a bootstrap util when it's not already installed as part of the base system. The first __FreeBSD_version that we can assume this can work is 700014 which happened after the gensnmptree change (in -r 1.263 of `src/sys/sys/param.h', at 2006/02/17 14:14:15). For __FreeBSD_version values before 700014 add gensnmptree to the bootstrap tools, to allow upgrades from versions of FreeBSD before that date. Approved by: ru, harti
2006-03-09 12:55:02 +00:00
${_gensnmptree} \
Add an option DB_FROM_SRC to use src/etc's user/group databases when installing. This allows things like running installworld for 10-CURRENT on a 9.0-RELEASE system without adding extra users and groups to the passwd and group files. To prevent potentially risky uid/gid mismatches on systems with non-standard local values, require that DESTDIR be set if DB_FROM_SRC is set. Sponsored by: DARPA, AFRL Reviewed by: peter
2013-01-15 00:12:34 +00:00
usr.sbin/config \
Fix building on slightly older -current and stable systems after the switch to bmake. The rescue bits are built via crunchgen, which didn't respect the MAKE environment variable until r237574 (i.e. ~11 months ago). This resulted in a failure due to bmake's internal -J flag being passed around and not being understood by the standard (i.e. host's) make. Note that the failure is conditional upon having the jobServer feature enabled within bmake.
2013-05-24 15:53:13 +00:00
${_crunch} \
Build vt(4) fonts during buildworld vtfontcvt(8) is now built during buildworld, so can be used as a bootstrap tool to create vt(4) fonts from source .hex or .bdf font files, rather than having uuencoded binary fonts in the tree. Sponsored by: The FreeBSD Foundation
2014-06-12 18:31:32 +00:00
${_nmtree} \
${_vtfontcvt}
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
${_bt}-${_tool}: .PHONY .MAKE
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
${MAKE} DIRPRFX=${_tool}/ depend && \
${MAKE} DIRPRFX=${_tool}/ all && \
Install bootstrap-tools into a separate subtree of ${WORLDTMP}. This allows us to use them as early as possible while building bootstrap-, build-, and cross-tools. Some cleanups to follow. This change resolves the gperf(1) bootstrapping issue (missing -E option) in gnu/usr.bin/cc/cc1plus while in the cross-tools stage when upgrading from 4.0-RELEASE.
2003-04-13 11:42:55 +00:00
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX}/legacy install
Parallelize building bootstrap-tools Differential Revision: https://reviews.freebsd.org/D1901 MFC after: 2 weeks Reviewed by: ian No serious objections from: imp
2015-02-23 05:28:17 +00:00
bootstrap-tools: ${_bt}-${_tool}
Restore the upgrade path from -stable to -current and prepare for non-root cross-building. o Makefile.inc0 is not used anymore. o The legacy aout build has been removed. o Selectively build tools *before* building includes/libraries. o Avoid using mtree to populate the obj tree.
1999-12-08 13:45:11 +00:00
.endfor
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
#
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
# build-tools: Build special purpose build tools
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
#
NOSHARE -> NO_SHARE
2004-12-21 12:13:23 +00:00
.if !defined(NO_SHARE)
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
_share= share/syscons/scrnmaps
.endif
Unbreak amd64 cross-build where amd64 is the target. While clang may be installed as cc and we don't need to build gcc as a cross-tools, we still build gcc and thus need cc_tools built as a build tool. Not doing this results in building gengenrtl with the target compiler while we need to run it on the build machine.
2012-11-20 03:21:26 +00:00
.if ${MK_GCC} != "no"
Add a WITH_CLANG_IS_CC option for src.conf(5), disabled by default, that installs clang as /usr/bin/cc, /usr/bin/c++ and /usr/bin/cpp. Note this does *not* disable building and installing gcc, which will still be available as /usr/bin/gcc, /usr/bin/g++ and /usr/bin/gcpp. If you want to disable gcc completely, you must use WITHOUT_GCC. MFC after: 2 weeks
2012-02-29 22:58:51 +00:00
_gcc_tools= gnu/usr.bin/cc/cc_tools
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_RESCUE} != "no"
Forgot that the rescue subdir needs to be a conditional for the build-tools bit.
2003-07-11 17:01:58 +00:00
_rescue= rescue/rescue
.endif
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
build-tools: .MAKE
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
.for _tool in \
bin/csh \
bin/sh \
Forgot that the rescue subdir needs to be a conditional for the build-tools bit.
2003-07-11 17:01:58 +00:00
${_rescue} \
Allow extra directories to be added to the build-tools target. Things such as "sh" require local tools to be built before cross-compiling. This allows for extra software (that's built via LOCAL_DIRS) to also have a build-tools target where required.
2012-01-05 21:50:50 +00:00
${LOCAL_TOOL_DIRS} \
Switch to new ncurses build glue Approved by: delphij
2007-01-20 07:48:10 +00:00
lib/ncurses/ncurses \
Enable ncurses wide character support Approved by: delphij (mentor) Tested by: kris on pointyhat (early version), current@
2007-03-09 12:11:58 +00:00
lib/ncurses/ncursesw \
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
${_share} \
usr.bin/awk \
The file(1) related build-tool moved to libmagic.
2004-08-09 10:51:01 +00:00
lib/libmagic \
Add the BSD-licensed Citrus iconv to the base system with default off setting. It can be built by setting the WITH_ICONV knob. While this knob is unset, the library part, the binaries, the header file and the metadata files will not be built or installed so it makes no impact on the system if left turned off. This work is based on the iconv implementation in NetBSD but a great number of improvements and feature additions have been included: - Some utilities have been added. There is a conversion table generator, which can compare conversion tables to reference data generated by GNU libiconv. This helps ensuring conversion compatibility. - UTF-16 surrogate support and some endianness issues have been fixed. - The rather chaotic Makefiles to build metadata have been refactored and cleaned up, now it is easy to read and it is also easier to add support for new encodings. - A bunch of new encodings and encoding aliases have been added. - Support for 1->2, 1->3 and 1->4 mappings, which is needed for transliterating with flying accents as GNU does, like "u. - Lots of warnings have been fixed, the major part of the code is now WARNS=6 clean. - New section 1 and section 5 manual pages have been added. - Some GNU-specific calls have been implemented: iconvlist(), iconvctl(), iconv_canonicalize(), iconv_open_into() - Support for GNU's //IGNORE suffix has been added. - The "-" argument for stdin is now recognized in iconv(1) as per POSIX. - The Big5 conversion module has been fixed. - The iconv.h header files is supposed to be compatible with the GNU version, i.e. sources should build with base iconv.h and GNU libiconv. It also includes a macro magic to deal with the char ** and const char ** incompatibility. - GNU compatibility: "" or "char" means the current local encoding in use - Various cleanups and style(9) fixes. Approved by: delphij (mentor) Obtained from: The NetBSD Project Sponsored by: Google Summer of Code 2009
2011-02-25 00:04:39 +00:00
usr.bin/mkesdb_static \
Update nvi-1.79 to 2.1.1-4334a8297f This is the gsoc-2011 project to clean up and backport multibyte support from other nvi forks in a form we can use. USE_WIDECHAR is on unless building for the rescue crunchgen. This should allow editing in the native locale encoding. USE_ICONV depends on make.conf having 'WITH_ICONV=YES' for now. This adds the ability to do things like edit a KOI8-R file while having $LANG set to (say) en_US.UTF-8. iconv is used to transcode the characters for display. Other points: * It uses gencat and catopen/etc instead of homegrown msg catalog stuff. * A lot of stuff has been trimmed out, eg: the perl and tcl bindings which we could never use in base anyway. * It uses ncursesw when in widechar mode. This could be interesting. GSoC info: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1 Repo at: https://github.com/lichray/nvi2 Obtained from: Zhihao Yuan <lichray@gmail.com>
2013-08-11 20:03:12 +00:00
usr.bin/mkcsmapper_static \
usr.bin/vi/catalog
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,build-tools)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
Ensure that build-tools end up in the object directory different from the source directory. (This mostly affects the RELENG_4's ``make release'' release.5 target, where "rtermcap" build-tool for release/sysinstall ends up in the source directory and later steps of release.5 wipe it out.) Spotted by: jhay
2003-02-24 20:09:16 +00:00
${MAKE} DIRPRFX=${_tool}/ build-tools
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
.endfor
Overhaul of kerberos5/ makefiles. Most significant changes are: - Dropped support for standalone builds, this was only partially supported anyway, and required so much magic in makefiles that made life dangerous (e.g., by using the custom yacc rules). - Got rid of .OBJDIR in makefiles -- makes building of individual files possible again. - Made the .x.c transformations -j safe. - Reprogrammed LDADD to fix static build of some utilities that was broken. - Fixed LDFLAGS and DPADD in the WITH_OPENLDAP case -- positively affects the contents of .depend files. - Removed redundant .h's from SRCS, only kept those that are generated. - libkrb5/ INCS were bogusly installed again with libgssapi/. - Made build-tools real tools with their own makefiles in separate directories. This allows us to properly track their dependencies, etc. - Faster build, 21% less of makefile code! Approved by: nectar Reviewed by: markm Silence on: arch
2004-01-31 08:15:57 +00:00
.for _tool in \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
${_gcc_tools}
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
${MAKE} DIRPRFX=${_tool}/ depend && \
Overhaul of kerberos5/ makefiles. Most significant changes are: - Dropped support for standalone builds, this was only partially supported anyway, and required so much magic in makefiles that made life dangerous (e.g., by using the custom yacc rules). - Got rid of .OBJDIR in makefiles -- makes building of individual files possible again. - Made the .x.c transformations -j safe. - Reprogrammed LDADD to fix static build of some utilities that was broken. - Fixed LDFLAGS and DPADD in the WITH_OPENLDAP case -- positively affects the contents of .depend files. - Removed redundant .h's from SRCS, only kept those that are generated. - libkrb5/ INCS were bogusly installed again with libgssapi/. - Made build-tools real tools with their own makefiles in separate directories. This allows us to properly track their dependencies, etc. - Faster build, 21% less of makefile code! Approved by: nectar Reviewed by: markm Silence on: arch
2004-01-31 08:15:57 +00:00
${MAKE} DIRPRFX=${_tool}/ all
.endfor
o Add games/caesar to the list of bootstrap-tools so that a buildworld doesn't break because the host doesn't have any games installed, o Add a new build stage: TMAKE. TMAKE builds all the build-tools targets in the respective makefiles. Note that these targets don't use the bootstrap tools, o Add elf2exe to the bootstrap-tools when cross-building Alpha on other platforms, o Add ${WORLDTMP}/usr/games to TMPPATH, o Remove ${WORLDTMP}/usr/bin even when NOCLEAN is defined. This prevents using any bootstrap-tools previously installed. Most importantly, it prevents using the cross-compiler when we still need the native compiler. The current stages are BMAKE, TMAKE, XMAKE and IMAKE in that order. BMAKE builds bootstrap-tools that either solve compatibility problems or are needed as cross-tools, TMAKE builds the support tools necessary by some parts in the source tree and also performs the cleandir and par-obj targets, XMAKE builds the includes, libraries and everything (resp.), and IMAKE installs the world. This stage needs further work if it's to be used to install -current over -stable for example. This is the last major update towards cross-building.
1999-12-16 13:47:34 +00:00
Do not build aicasm with the cross-tools/kernel-toolchain, instead add a proper kernel-tools step/target modeled after the world build-tools stuff. This is a re-do of r257730 which was backed out in r257734, but this time it's one byte smaller... a leftover trailing backslash resulted in a .for loop with no rules, so no compiler stuff got built and later steps built with the wrong toolset.
2013-11-07 04:31:21 +00:00
#
# kernel-tools: Build kernel-building tools
#
kernel-tools: .MAKE
Instead of modeling the kernel-tools build after the bootstrap tools, build kernel tools the way cross-tools get built. This seems to result in the tool getting installed in the right place. It also seems more correct in retrospect, because if a tool emitted code or binary data as part of building the kernel, it should do so in target-specific ways (endianess, architecture, whatever). That issue is moot for aicasm, our only current tool, but it still seems to be more correct in principle.
2013-11-07 22:50:42 +00:00
mkdir -p ${MAKEOBJDIRPREFIX}/usr
Do not build aicasm with the cross-tools/kernel-toolchain, instead add a proper kernel-tools step/target modeled after the world build-tools stuff. This is a re-do of r257730 which was backed out in r257734, but this time it's one byte smaller... a leftover trailing backslash resulted in a .for loop with no rules, so no compiler stuff got built and later steps built with the wrong toolset.
2013-11-07 04:31:21 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
Instead of modeling the kernel-tools build after the bootstrap tools, build kernel tools the way cross-tools get built. This seems to result in the tool getting installed in the right place. It also seems more correct in retrospect, because if a tool emitted code or binary data as part of building the kernel, it should do so in target-specific ways (endianess, architecture, whatever). That issue is moot for aicasm, our only current tool, but it still seems to be more correct in principle.
2013-11-07 22:50:42 +00:00
-p ${MAKEOBJDIRPREFIX}/usr >/dev/null
Do not build aicasm with the cross-tools/kernel-toolchain, instead add a proper kernel-tools step/target modeled after the world build-tools stuff. This is a re-do of r257730 which was backed out in r257734, but this time it's one byte smaller... a leftover trailing backslash resulted in a .for loop with no rules, so no compiler stuff got built and later steps built with the wrong toolset.
2013-11-07 04:31:21 +00:00
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
#
Add some more explanation to the different phases of the build.
2015-03-25 21:59:36 +00:00
# cross-tools: All the tools needed to build the rest of the system after
# we get done with the earlier stages. It is the last set of tools needed
# to begin building the target binaries.
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
#
Up the minimum system to build FreeBSD current to 8.0-RELEASE. The issues with vendors that needed 7.x support have been resolved. Many vendors are still using 8.x build platforms, however, so bumping this up to 9.0 will have to wait until that is resolved. Actual support for building from 8.x still relies on those vendors fixing bugs that are present as most developers have moved onto 9.x or newer platforms. Reviewed by: marcel@
2014-04-13 05:21:30 +00:00
.if ${TARGET_ARCH} != ${MACHINE_ARCH}
Style, no functional changes.
2005-12-07 20:01:12 +00:00
.if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "i386"
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
_btxld= usr.sbin/btxld
.endif
Bootstrap the build of btxld.
2008-04-15 05:14:42 +00:00
.endif
.if ${TARGET_ARCH} != ${MACHINE_ARCH}
RELEASEDIR was removed in FreeBSD 9.x, at the same time /boot/loader stopped using kgzip in the release process. We no longer need to build kgzip as a cross tool, and tests for RELEASEDIR are obsolete, so remove both. Differential Revision: https://reviews.freebsd.org/D2313
2015-04-17 15:55:13 +00:00
.if ${MK_RESCUE} != "no"
Only bootstrap crunchide(1) and build crunchgen(1) when necessary. The latter needs to be built either if it's used as a cross-tool (${TARGET_ARCH} != ${MACHINE_ARCH}) or if it has backward compat issues, like e.g. lack of the AMD64 support.
2003-07-01 12:25:11 +00:00
_crunchide= usr.sbin/crunch/crunchide
.endif
Style, no functional changes.
2005-12-07 20:01:12 +00:00
.endif
Make lint(1) a cross-tool. (See commit log for usr.bin/xlint/Makefile,v 1.11 for what was wrong with enabling build of lint libraries in rev. 1.12.) This fixes cross-arch compiles (running binaries for a different arch when generating lint.7 and lint libraries) and cross-branch compiles (4.x -> 5.0 buildworld should be working again).
2002-03-20 18:25:50 +00:00
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
# If we're given an XAS, don't build binutils.
Use BINUTILS_BOOTSTRAP knob for binutils only Previously it also disabled building elftoolchain bootstrap tools such as strip(1). Differential Revision: https://reviews.freebsd.org/D1398 Reviewed by: imp Sponsored by: The FreeBSD Foundation
2014-12-30 18:42:53 +00:00
.if ${XAS:M/*} == ""
.if ${MK_BINUTILS_BOOTSTRAP} != "no"
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
_binutils= gnu/usr.bin/binutils
Use BINUTILS_BOOTSTRAP knob for binutils only Previously it also disabled building elftoolchain bootstrap tools such as strip(1). Differential Revision: https://reviews.freebsd.org/D1398 Reviewed by: imp Sponsored by: The FreeBSD Foundation
2014-12-30 18:42:53 +00:00
.endif
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
.if ${MK_ELFTOOLCHAIN_TOOLS} != "no"
_elftctools= lib/libelftc \
usr.bin/elfcopy \
usr.bin/nm \
usr.bin/size \
usr.bin/strings
Restore addr2line to cross tools Addr2line is not required for the build, and a per-arch binary is no longer required with the switch to the ELF Tool Chain. However, building these tools during the cross tools stage can be useful for developers who cross build HEAD from stable/10, and adds very little to the build time. Reviewed by: ian, imp Differential Revision: https://reviews.freebsd.org/D1583
2015-01-23 21:34:08 +00:00
# These are not required by the build, but can be useful for developers who
# cross-build on a FreeBSD 10 host:
_elftctools+= usr.bin/addr2line
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
.endif
When cross-building with an external toolchain we still need a target strip It is used by at least crunchide(1).
2015-03-17 19:35:50 +00:00
.elif ${TARGET_ARCH} != ${MACHINE_ARCH} && ${MK_ELFTOOLCHAIN_TOOLS} != "no"
# If cross-building with an external binutils we still need to build strip for
# the target (for at least crunchide).
_elftctools= lib/libelftc \
usr.bin/elfcopy
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
.endif
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
# If an full path to an external cross compiler is given, don't build
# a cross compiler.
.if ${XCC:M/*} == "" && ${MK_CROSS_COMPILER} != "no"
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
.if ${MK_CLANG_BOOTSTRAP} != "no"
Move building of clang's tblgen tools (and required libraries) from the bootstrap-tools stage to the cross-tools stage. These tools are only needed for generating llvm/clang include files, and are not necessary for bootstrapping the build itself. This shaves off some build time, because the required libraries are now just built twice (during the cross-tools and world stages), instead of three times. Also, if you build world using WITHOUT_CLANG= in src.conf(5), no llvm or clang code will be compiled at all anymore. MFC after: 1 week
2011-11-09 19:00:27 +00:00
_clang= usr.bin/clang
Revert r227403 for now. Since the cross-tools stage purposefully doesn't have ${WORLDTMP}/usr/bin in its PATH, if you build world with CC=clang, tblgen tools from /usr/bin will be used instead of the ones built under ${WORLDTMP}. This can lead to various errors, especially if you upgrade from an older clang. Note that building world with gcc would not experience these problems, because it only uses the tblgen tools in the world stage, where PATH does contain ${WORLDTMP}/usr/bin. Pointy hat to: dim
2011-11-10 20:15:35 +00:00
_clang_libs= lib/clang
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
.endif
Separate out enabling building clang and/or gcc for the system and building clang and/or gcc as the bootstrap compiler. Normally, the default compiler is used. WITH_CLANG_BOOTSTRAP and/or WITH_GCC_BOOTSTRAP will enable building these compilers as part bootstrap phase. WITH/WITHOUT_CLANG_IS_CC controls which compiler is used by default for the bootstrap phase, as well as which compiler is installed as cc. buildworld now successfully completes building the cross compiler with WITHOUT_CLANG=t and WITHOUT_GCC=t and produces a built system with neither of these included. Similarlly, MK_BINUTILS_BOOTSTRAP controls whether binutils is built during this phase. WITHOUT_CROSS_COMPILER will now force MK_BINUTILS_BOOTSTRAP=no, MK_CLANG_BOOTSTRAP=no and MK_GCC_BOOTSTRAP=no. BOOTSTRAP_COMPILER was considered, but rejected, since pc98 needs both clang and gcc to bootstrap still. It should be revisisted in the future if this requirement goes away. Values should be gcc, clang or none. It could also be a list. The odd interaction with Xfoo cross/external tools needs work, but is beyond the scope of this change as well.
2014-04-18 17:03:58 +00:00
.if ${MK_GCC_BOOTSTRAP} != "no"
Fix build. Both clang and gcc are required on pc98. X-MFC with: r256915
2013-10-29 12:34:11 +00:00
_cc= gnu/usr.bin/cc
.endif
Add support for an external cross compiler. The cross compiler is specified by passing the XCC, XCXX, and XCPP variables (corresponding to CC, CXX, and CPP) to buildworld/buildkernel. The compiler must be clang or be configured to target the appropriate architecture. To speed build times, if XCC is an absolute path or WITHOUT_CROSS_COMPILER is defined then no cross compiler will be built during the cross-tools stage. Limited documentation of this feature can currently be found at: https://wiki.freebsd.org/ExternalToolchain This functionality should be considered experimental and is subject to change without notice. Sponsored by: DARPA, AFRL Discussed with: imp, sjg
2013-05-15 14:30:03 +00:00
.endif
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
cross-tools: .MAKE
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
.for _tool in \
Add clang to the cross-tools build stage. Submitted by: Dimitry Andric <dimitry at andric.com>
2010-08-21 15:39:06 +00:00
${_clang_libs} \
${_clang} \
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
${_binutils} \
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
${_elftctools} \
Implement WITH{,OUT}_{GCC,BINUTILS} to provide finer-grained control over building gcc and binutils. They default to true, unless MK_TOOLCHAIN is no. Reviewed by: ru@
2011-05-19 05:13:25 +00:00
${_cc} \
Put rescue/ into a correct slot in the SUBDIR list. Sort bootstrap-, build-, and cross-tools lists, reformat lists for easier maintenance. Submitted by: bde, ru
2003-07-01 12:57:53 +00:00
${_btxld} \
${_crunchide} \
Merge from CheriBSD: Make the sysinit tool a build tool rather than building in with /usr/bin/cc and running it from OBJDIR. (It will be moved to usr.bin once a manpage is written and a few style cleanups are done.) Split the makefile bits for Hans' kernel shim layer into their own includable kshim.mk. Move USB support into a .mk file so loaders can include it.
2014-08-04 23:00:13 +00:00
sys/boot/usb/tools
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
${MAKE} DIRPRFX=${_tool}/ depend && \
${MAKE} DIRPRFX=${_tool}/ all && \
Added new bsd.incs.mk which handles installing of header files via INCS. Implemented INCSLINKS (equivalent to SYMLINKS) to handle symlinking include files. Allow for multiple groups of include files to be installed, with the powerful INCSGROUPS knob. Documentation to follow. Added standard `includes' and `incsinstall' targets, use them in Makefile.inc1. Headers from the following makefiles were not installed before (during `includes' in Makefile.inc1): kerberos5/lib/libtelnet/Makefile lib/libbz2/Makefile lib/libdevinfo/Makefile lib/libform/Makefile lib/libisc/Makefile lib/libmenu/Makefile lib/libmilter/Makefile lib/libpanel/Makefile Replaced all `beforeinstall' targets for installing includes with the INCS stuff. Renamed INCDIR to INCSDIR, for consistency with FILES and SCRIPTS, and for compatibility with NetBSD. Similarly for INCOWN, INCGRP, and INCMODE. Consistently use INCLUDEDIR instead of /usr/include. gnu/lib/libstdc++/Makefile and gnu/lib/libsupc++/Makefile changes were only lightly tested due to the missing contrib/libstdc++-v3. I fully tested the pre-WIP_GCC31 version of this patch with the contrib/libstdc++.295 stuff. These changes have been tested on i386 with the -DNO_WERROR "make world" and "make release".
2002-05-12 16:01:00 +00:00
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX} install
o make SHARED=symlinks a caller defined instead of a callee defined property. This fixes the includes target when DESTDIR is empty. o Do not make build-tools for f771 when NO_FORTRAN is defined. o Add new build stage. See below. o Change banners so that staging information is displayed. The addition of the build-tools target broke the upgrade path because we couldn't make use of previously built tools that were made for compatibility reasons. Doing so would also result in the cross-compiler being used and that is exactly what had to be avoided. This is solved by designating the bootstrap-tools stage for building anything that is needed for compatibility only and to create a new stage (started after the build-tools stage) that handles cross-tools building. We now have the following stages: 1. bootstrap-tools (for compatibility issues only) 2. build-tools 3. cross-tools (what it says) 4. world 5. install Stages 1-4 (inclusive) are handled by buildworld. Stage 5 is handled by installworld. Any more stages and I'll join Nik in his quest for the holy grail^W^Wworld :-)
1999-12-20 10:32:11 +00:00
.endfor
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
NXBENV= MAKEOBJDIRPREFIX=${OBJTREE}/nxb \
INSTALL="sh ${.CURDIR}/tools/install.sh" \
Setting PATH to anything is useless as a bare command. Its only relevant if its set in the environement of each command seperately. Move the PATH setting to the NXBMAKE variable so its picked up to find the one-off gperf build for the native-xtools target. Pointed Out by: ngie
2015-04-30 02:08:36 +00:00
VERSION="${VERSION}" \
PATH=${PATH}:${OBJTREE}/gperf_for_gcc/usr/bin
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
NXBMAKE= ${NXBENV} ${MAKE} \
TBLGEN=${OBJTREE}/nxb-bin/usr/bin/tblgen \
CLANG_TBLGEN=${OBJTREE}/nxb-bin/usr/bin/clang-tblgen \
MACHINE=${TARGET} MACHINE_ARCH=${TARGET_ARCH} \
MK_GDB=no MK_TESTS=no \
Revert r267233 for now. PIE support needs to be reworked. 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
2014-08-19 15:04:32 +00:00
SSP_CFLAGS= \
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
MK_HTML=no NO_LINT=yes MK_MAN=no \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
-DNO_PIC MK_PROFILE=no -DNO_SHARED \
-DNO_CPU_CFLAGS MK_WARNS=no MK_CTF=no \
Don't build full clang toolchain or clang extras in stages 1-3 of buildworld MFC after: 1 week Reviewed by: dim (as part of a "larger" diff) Phabric: D1336 Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:26:10 +00:00
MK_CLANG_EXTRAS=no MK_CLANG_FULL=no \
Fix accidental MK_DEBUG_FILES=no addition to NXBMAKE in r275909 X-MFC with: r275909 Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:30:33 +00:00
MK_LLDB=no
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
Fix native-xtools breakage when building a gcc enabled target on a clang enabled host. Build a one-off gperf and put it in the PATH for the rest of the target so the ONE call to gperf by the gcc build picks it up and DTRT. Reviewed by: imp
2015-04-30 00:17:32 +00:00
# native-xtools is the current target for qemu-user cross builds of ports
# via poudriere and the imgact_binmisc kernel module.
# For non-clang enabled targets that are still using the in tree gcc
# we must build a gperf binary for one instance of its Makefiles. On
# clang-enabled systems, the gperf binary is obsolete.
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
native-xtools: .MAKE
Fix native-xtools breakage when building a gcc enabled target on a clang enabled host. Build a one-off gperf and put it in the PATH for the rest of the target so the ONE call to gperf by the gcc build picks it up and DTRT. Reviewed by: imp
2015-04-30 00:17:32 +00:00
.if ${MK_GCC_BOOTSTRAP} != "no"
mkdir -p ${OBJTREE}/gperf_for_gcc/usr/bin
${_+_}@${ECHODIR} "===> ${_gperf} (obj,depend,all,install)"; \
cd ${.CURDIR}/${_gperf} && \
${NXBMAKE} DIRPRFX=${_gperf}/ obj && \
${NXBMAKE} DIRPRFX=${_gperf}/ depend && \
${NXBMAKE} DIRPRFX=${_gperf}/ all && \
${NXBMAKE} DIRPRFX=${_gperf}/ DESTDIR=${OBJTREE}/gperf_for_gcc install
.endif
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
mkdir -p ${OBJTREE}/nxb-bin/bin
mkdir -p ${OBJTREE}/nxb-bin/sbin
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
mkdir -p ${OBJTREE}/nxb-bin/usr
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${OBJTREE}/nxb-bin/usr >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
-p ${OBJTREE}/nxb-bin/usr/include >/dev/null
.for _tool in \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
bin/cat \
bin/chmod \
bin/cp \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
bin/csh \
Add mv, echo and hostname to the native-xtools target. Missed these when profiling. MFC after: 2 weeks
2014-11-16 23:31:23 +00:00
bin/echo \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
bin/expr \
Add mv, echo and hostname to the native-xtools target. Missed these when profiling. MFC after: 2 weeks
2014-11-16 23:31:23 +00:00
bin/hostname \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
bin/ln \
bin/ls \
bin/mkdir \
Add mv, echo and hostname to the native-xtools target. Missed these when profiling. MFC after: 2 weeks
2014-11-16 23:31:23 +00:00
bin/mv \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
bin/ps \
bin/realpath \
bin/rm \
bin/rmdir \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
bin/sh \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
bin/sleep \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
${_clang_tblgen} \
usr.bin/ar \
${_binutils} \
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
${_elftctools} \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
${_cc} \
${_gcc_tools} \
${_clang_libs} \
${_clang} \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
sbin/md5 \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
sbin/sysctl \
gnu/usr.bin/diff \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
usr.bin/awk \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/basename \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
usr.bin/bmake \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/bzip2 \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/cmp \
usr.bin/dirname \
usr.bin/env \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/fetch \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/find \
usr.bin/grep \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/gzip \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/id \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
usr.bin/lex \
usr.bin/lorder \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/mktemp \
usr.bin/mt \
usr.bin/patch \
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
usr.bin/sed \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/sort \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/tar \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/touch \
usr.bin/tr \
usr.bin/true \
usr.bin/uniq \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/unzip \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/xargs \
usr.bin/xinstall \
Add more static binaries to the native-xtools target. These help speed up the cross builds significantly. adding: bin/sh bin/csh sbin/md5 usr.bin/bzip2 usr.bin/fetch usr.bin/gzip usr.bin/tar usr.bin/unzip usr.bin/xz Phabric: D1146 Reviewed by: imp bdrewery MFC after: 2 weeks
2014-11-13 22:25:22 +00:00
usr.bin/xz \
Flush out many more static binaries that can be used in a jail for building pkgs via poudriere. This removes a significant amount of emulation speeding up run times. Phabric: D1172 Reviewed by: imp MFC after: 2 weeks
2014-11-16 20:10:37 +00:00
usr.bin/yacc \
usr.sbin/chown
Create the native-xtools target. This target creates only the cross building toolchain for the host computer. This toolchain produces TARGET_ARCH and assumes the rest of the system contains libraries for the target. It is intended to be used in a "qemu-user jail" where all the binaries would otherwise be the target architecture's to build ports. However, emulation of the compilers is too slow, so we build native binaries for that. Rather than use the xdev produced binaries, with all their weird links and paths, these binaries use the native paths. They will not work unless installed into the qemu-user jail. Differential Revision: https://phabric.freebsd.org/D518 Reviewed by: sbruno@
2014-08-18 21:04:44 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
cd ${.CURDIR}/${_tool} && \
${NXBMAKE} DIRPRFX=${_tool}/ obj && \
${NXBMAKE} DIRPRFX=${_tool}/ depend && \
${NXBMAKE} DIRPRFX=${_tool}/ all && \
${NXBMAKE} DIRPRFX=${_tool}/ DESTDIR=${OBJTREE}/nxb-bin install
.endfor
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
#
Restore the upgrade path from -stable to -current and prepare for non-root cross-building. o Makefile.inc0 is not used anymore. o The legacy aout build has been removed. o Selectively build tools *before* building includes/libraries. o Avoid using mtree to populate the obj tree.
1999-12-08 13:45:11 +00:00
# hierarchy - ensure that all the needed directories are present
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
#
Have distrib-dirs, distribution, hier, hierarchy, redistribute, and reinstall depend on the .MAKE special target This will allow users to do something like the following to print out the results of the running the simulated make target with bmake, like some of the other top-level make targets in Makefile.inc1: % make -f Makefile.inc1 -n distribution TARGET=i386 TARGET_ARCH=i386 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2014-09-24 04:06:54 +00:00
hierarchy hier: .MAKE
Simplify the hierarchy target's logic. [0] Run hierarchy with WORLDTMP in the path so it works when it is invoked directly. Such use is nearly alwasy wrong but appears to be common.[1] PR: conf/178209 [0], conf/178547 [1] Submitted by: Garrett Cooper <yaneurabeya@gmail.com> [0] MFC after: 5 days
2013-06-14 22:32:47 +00:00
cd ${.CURDIR}/etc && ${HMAKE} distrib-dirs
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
Restore the upgrade path from -stable to -current and prepare for non-root cross-building. o Makefile.inc0 is not used anymore. o The legacy aout build has been removed. o Selectively build tools *before* building includes/libraries. o Avoid using mtree to populate the obj tree.
1999-12-08 13:45:11 +00:00
# libraries - build all libraries, and install them under ${DESTDIR}.
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
#
Add a tool (and the first application of it) that could be used to automate building of libraries. Prodded by: bde
2002-04-12 19:46:25 +00:00
# The list of libraries with dependents (${_prebuild_libs}) and their
# interdependencies (__L) are built automatically by the
# ${.CURDIR}/tools/make_libdeps.sh script.
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
#
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
libraries: .MAKE
cd ${.CURDIR} && \
${MAKE} -f Makefile.inc1 _prereq_libs && \
${MAKE} -f Makefile.inc1 _startup_libs && \
${MAKE} -f Makefile.inc1 _prebuild_libs && \
${MAKE} -f Makefile.inc1 _generic_libs
Add a tool (and the first application of it) that could be used to automate building of libraries. Prodded by: bde
2002-04-12 19:46:25 +00:00
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
#
# static libgcc.a prerequisite for shared libc
#
Replace libgcc.a by libcompiler_rt.a. libcompiler_rt.a is a BSD licensed C language runtime, which implements many routines which are linked into binaries on architectures where certain functionality is missing (e.g. 64 bits mul/div on i386). Unfortunately, libcompiler_rt cannot replace libgcc entirely. Certain features, such as an unwinder for exception handling, are missing. That's why only libgcc.a is replaced for now, because this one does seem to be complete. Tested by: rene (amd64), nwhitehorn (powerpc), droso (i386 exprun) and many others. Thanks! Obtained from: user/ed/compiler-rt
2010-11-11 15:48:27 +00:00
_prereq_libs= gnu/lib/libssp/libssp_nonshared gnu/lib/libgcc lib/libcompiler_rt
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
# These dependencies are not automatically generated:
#
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
# gnu/lib/csu, gnu/lib/libgcc, lib/csu and lib/libc must be built before
# all shared libraries for ELF.
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
#
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
_startup_libs= gnu/lib/csu
Remove redundant csu subdir logic The appropriate subdirectories are handled by lib/csu/Makefile. There's no need to duplicate this logic in Makefile.inc1 and lib/Makefile. Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D2523
2015-05-12 17:53:22 +00:00
_startup_libs+= lib/csu
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
_startup_libs+= gnu/lib/libgcc
Replace libgcc.a by libcompiler_rt.a. libcompiler_rt.a is a BSD licensed C language runtime, which implements many routines which are linked into binaries on architectures where certain functionality is missing (e.g. 64 bits mul/div on i386). Unfortunately, libcompiler_rt cannot replace libgcc entirely. Certain features, such as an unwinder for exception handling, are missing. That's why only libgcc.a is replaced for now, because this one does seem to be complete. Tested by: rene (amd64), nwhitehorn (powerpc), droso (i386 exprun) and many others. Thanks! Obtained from: user/ed/compiler-rt
2010-11-11 15:48:27 +00:00
_startup_libs+= lib/libcompiler_rt
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
_startup_libs+= lib/libc
Attempt to move the POSIX iconv* symbols out of runtime linker space. FreeBSD systems usually implemented this as a third party module and our implementation hasn't played as nicely with the old way as it could have. To that end: * Rename the iconv* symbols in libc.so.7 to have a __bsd_ prefix. * Provide .symver compatability with existing 10.x+ binaries that referenced the iconv symbols. All existing binaries should work. * Like on Linux/glibc systems, add a libc_nonshared.a to the ldscript at /usr/lib/libc.so. * Move the "iconv*" wrapper symbols to libc_nonshared.a This should solve the runtime ambiguity about which symbols resolve to where. If you compile against the iconv in libc, your runtime dependencies will be unambiguous. Old 9.x libraries and binaries will always resolve against their libiconv.so.3 like they did on 9.x. They won't resolve against libc. Old 10.x binaries will be satisified by the .symver helpers. This should allow ports to selectively compile against the libiconv port if needed and it should behave without ambiguity now. Discussed with: kib
2013-11-17 22:52:17 +00:00
_startup_libs+= lib/libc_nonshared
Fix breakage after r227983; lib/libcxxrt still got built, because it was not disabled in the usual way (by adding it to __DEFAULT_NO_OPTIONS in share/mk/bsd.own.mk), and because the test for MK_LIBCPLUSPLUS in Makefile.inc1 was incorrect. Pointy hat to: dim
2011-11-26 03:26:06 +00:00
.if ${MK_LIBCPLUSPLUS} != "no"
Import libc++ / libcxxrt into base. Not build by default yet (use MK_LIBCPLUSPLUS=yes to enable). This is a work-in-progress. It works for me, but is not guaranteed to work for anyone else and may eat your dog. To build C++ using libc++, add -stdlib=libc++ to your CXX and LD flags. Bug reports welcome, bug fixes even more welcome... Approved by: dim (mentor)
2011-11-25 20:59:04 +00:00
_startup_libs+= lib/libcxxrt
.endif
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
gnu/lib/libgcc__L: lib/libc__L
Attempt to move the POSIX iconv* symbols out of runtime linker space. FreeBSD systems usually implemented this as a third party module and our implementation hasn't played as nicely with the old way as it could have. To that end: * Rename the iconv* symbols in libc.so.7 to have a __bsd_ prefix. * Provide .symver compatability with existing 10.x+ binaries that referenced the iconv symbols. All existing binaries should work. * Like on Linux/glibc systems, add a libc_nonshared.a to the ldscript at /usr/lib/libc.so. * Move the "iconv*" wrapper symbols to libc_nonshared.a This should solve the runtime ambiguity about which symbols resolve to where. If you compile against the iconv in libc, your runtime dependencies will be unambiguous. Old 9.x libraries and binaries will always resolve against their libiconv.so.3 like they did on 9.x. They won't resolve against libc. Old 10.x binaries will be satisified by the .symver helpers. This should allow ports to selectively compile against the libiconv port if needed and it should behave without ambiguity now. Discussed with: kib
2013-11-17 22:52:17 +00:00
gnu/lib/libgcc__L: lib/libc_nonshared__L
Make sure libgcc_s is finished building in _startup_libs before building libcxxrt with high -j levels. The workaround in libc++/Makefile isn't necessary once that race is solved. Reviewed by: theravin
2012-03-17 22:12:09 +00:00
.if ${MK_LIBCPLUSPLUS} != "no"
lib/libcxxrt__L: gnu/lib/libgcc__L
.endif
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
_prebuild_libs= ${_kerberos5_lib_libasn1} \
${_kerberos5_lib_libhdb} \
${_kerberos5_lib_libheimbase} \
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
${_kerberos5_lib_libheimntlm} \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
${_kerberos5_lib_libheimsqlite} \
${_kerberos5_lib_libheimipcc} \
Regen the list of prebuild libraries using tools/make_libdeps.sh.
2010-01-26 10:00:26 +00:00
${_kerberos5_lib_libhx509} ${_kerberos5_lib_libkrb5} \
${_kerberos5_lib_libroken} \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
${_kerberos5_lib_libwind} \
- Do not build libcom_err and compile_et when kerberos is disabled. They depends on several heimdal libraries and not used by anything but kerberos tools.
2012-03-23 03:16:35 +00:00
lib/libbz2 ${_libcom_err} lib/libcrypt \
This should have been committed in r249666. MFC after: 1 month
2013-04-20 08:13:35 +00:00
lib/libelf lib/libexpat \
SUBDIR_DEPENDS__ in lib/Makefile is not working out so well for me. Add to using _prebuild_libs in (top-level) Makefile.inc1. NB: Unbreak build yet again (we'll get this right eventually) Reviewed by: markj, ngie Thanks to: ian, markj, ngie, Nikolai Lifanov <lifanov@mail.lifanov.com> MFC after: 21 days X-MFC-to: stable/10 stable/9 X-MFC-with: 274116 274120 274121 274123 274144 274146 274192
2014-11-06 22:53:50 +00:00
lib/libfigpar \
Remove IPX support. IPX was a network transport protocol in Novell's NetWare network operating system from late 80s and then 90s. The NetWare itself switched to TCP/IP as default transport in 1998. Later, in this century the Novell Open Enterprise Server became successor of Novell NetWare. The last release that claimed to still support IPX was OES 2 in 2007. Routing equipment vendors (e.g. Cisco) discontinued support for IPX in 2011. Thus, IPX won't be supported in FreeBSD 11.0-RELEASE.
2014-03-14 02:58:48 +00:00
${_lib_libgssapi} \
Please welcome casperd daemon. It (and its services) will be responsible for giving access to functionality that is not available in capability mode sandbox. The functionality can be precisely restricted. Start with the following services: - system.dns - provides API compatible to: - gethostbyname(3), - gethostbyname2(3), - gethostbyaddr(3), - getaddrinfo(3), - getnameinfo(3), - system.grp - provides getgrent(3)-compatible API, - system.pwd - provides getpwent(3)-compatible API, - system.random - allows to obtain entropy from /dev/random, - system.sysctl - provides sysctlbyname(3-compatible API. Sponsored by: The FreeBSD Foundation
2013-12-02 08:21:28 +00:00
lib/libkiconv lib/libkvm lib/liblzma lib/libmd lib/libnv \
${_lib_libcapsicum} \
Enable ncurses wide character support Approved by: delphij (mentor) Tested by: kris on pointyhat (early version), current@
2007-03-09 12:11:58 +00:00
lib/ncurses/ncurses lib/ncurses/ncursesw \
Revert r227841 and part of r227798. We still build libpam in two passes, but we use STATIC_CFLAGS instead of our own private .c.o rule. MFC after: 3 weeks
2011-11-24 13:18:58 +00:00
lib/libopie lib/libpam ${_lib_libthr} \
Conditionalize building radius support into libpam, ppp, etc via MK_RADIUS_SUPPORT MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
2015-02-04 06:53:45 +00:00
${_lib_libradius} lib/libsbuf lib/libtacplus \
Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
2014-10-03 20:36:09 +00:00
lib/libgeom \
Partial MFV (illumos-gate 13753:2aba784c276b) 2762 zpool command should have better support for feature flags References: https://www.illumos.org/issues/2762 MFC after: 2 weeks
2012-07-30 23:14:24 +00:00
${_cddl_lib_libumem} ${_cddl_lib_libnvpair} \
Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
2014-10-03 20:36:09 +00:00
${_cddl_lib_libuutil} \
Fix build: Build libavl as prebuild-lib. X-MFC-With: 266520
2014-05-22 05:33:50 +00:00
${_cddl_lib_libavl} \
WiP merge of libzfs_core (MFV r238590, r238592) not yet working, ioctl handling needs to be changed
2013-03-05 08:09:53 +00:00
${_cddl_lib_libzfs_core} \
Fix dependency errors when linking libproc. Reported by: Oliver Hartmann X-MFC-With: r272488
2014-10-05 22:13:13 +00:00
${_cddl_lib_libctf} \
Move my simple logging API to a separate library. It is now already used by hastctl(8), hastd(8) and auditdistd(8) and will soon be also used by casperd(8) and its services. There is no documentation and pjdlog.h header file is not installed in /usr/include/ to keep it private. Unfortunately we don't have /lib/private/ at this point, only /usr/lib/private/, so the library is installed in /lib/. Sponsored by: The FreeBSD Foundation
2013-12-01 09:41:06 +00:00
lib/libutil lib/libpjdlog ${_lib_libypclnt} lib/libz lib/msun \
Clean up the OpenSSH build. It is now possible to build most components as static binaries, if desired. The one exception is sshd, which runs into trouble due to libpam.a's includion of pam_ssh. Make OpenSSH use LDNS if available. This allows it to verify signed SSHFP records. Approved by: re (blanket)
2013-09-10 22:26:11 +00:00
${_secure_lib_libcrypto} ${_lib_libldns} \
For really fast machines, an edge-case may exist where dpv(3) may be built before contrib dependency, dialog(3). Add dialog(3) to the list of _prebuild_libs to ensure that this does not happen. Tested on: 11.0-CURRENT amd64 @ r274205 Thanks to: kargl, Larry Rosenman <ler@lerctr.org>, ngie, markj Recommended by: ngie Reviewed by: ngie, markj MFC after: 21 days X-MFC-to: stable/10 stable/9 X-MFC-with: 274116 274120 274121 274123 274144 274146 274192 274203
2014-11-07 00:59:40 +00:00
${_secure_lib_libssh} ${_secure_lib_libssl} \
gnu/lib/libdialog
Make MK_GNUCXX mean "build the libstdc++ and libsupc++ libraries" and nothing more. Force it to be "no" when MK_CXX is "no" to simplify usage. It no longer also means "build g++" since we no longer have a platform where that's interesting now that pc98 no longer needs clang and gcc, but not g++. pc98 now just uses clang after boot2 changes.
2014-07-10 21:11:48 +00:00
.if ${MK_GNUCXX} != "no"
When building g++, we need to build libsupc earlier to avoid a race with libproc. Not sure why people didn't see this before now, but I get it often for higher (20-30) -j builds, but never for -j1 builds.
2014-03-30 22:24:37 +00:00
_prebuild_libs+= gnu/lib/libstdc++ gnu/lib/libsupc++
Add dependency for libm to libstdc++. This fixes high -j value builds when not building with clang. Submitted by: ian@
2014-04-28 23:16:46 +00:00
gnu/lib/libstdc++__L: lib/msun__L
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
gnu/lib/libsupc++__L: gnu/lib/libstdc++__L
When building g++, we need to build libsupc earlier to avoid a race with libproc. Not sure why people didn't see this before now, but I get it often for higher (20-30) -j builds, but never for -j1 builds.
2014-03-30 22:24:37 +00:00
.endif
libufs does not need built before most things, after all. Submitted by: bde, ru
2002-07-01 17:51:43 +00:00
Add LIB_CXX so that C++ libraries will use CXX to link. This fixes C++ libraries not implicitly linking in libc++. This is generally not an issue because the final linking with the compiled binary will involve CXX via PROG_CXX or other means. It is however inconsistent with libraries implicitly linking in libc and problematic for trying to build libraries with '-z defs' to ensure all direct dependencies are linked in. libatf-c++ is currently the only consumer of this new feature. Differential Revision: https://reviews.freebsd.org/D2039 Reviewed by: imp Discussed with: bapt MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2015-03-17 15:16:36 +00:00
.if ${MK_LIBCPLUSPLUS} != "no"
_prebuild_libs+= lib/libc++
.endif
Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
2014-10-03 20:36:09 +00:00
lib/libgeom__L: lib/libexpat__L
Remove options MK_LIBKSE and DEFAULT_THREAD_LIB now that we no longer build libkse. This should fix WITHOUT_LIBTHR builds as a side effect.
2008-03-29 17:44:40 +00:00
.if ${MK_LIBTHR} != "no"
_lib_libthr= lib/libthr
Always install libpthread.* symlinks if at least one of 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)
2007-10-01 18:22:32 +00:00
.endif
Conditionalize building radius support into libpam, ppp, etc via MK_RADIUS_SUPPORT MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
2015-02-04 06:53:45 +00:00
.if ${MK_RADIUS_SUPPORT} != "no"
_lib_libradius= lib/libradius
.endif
- Merge in OFED 1.5.3 from projects/ofed/head
2011-03-21 09:58:24 +00:00
.if ${MK_OFED} != "no"
_ofed_lib= contrib/ofed/usr.lib/
.endif
Please welcome casperd daemon. It (and its services) will be responsible for giving access to functionality that is not available in capability mode sandbox. The functionality can be precisely restricted. Start with the following services: - system.dns - provides API compatible to: - gethostbyname(3), - gethostbyname2(3), - gethostbyaddr(3), - getaddrinfo(3), - getnameinfo(3), - system.grp - provides getgrent(3)-compatible API, - system.pwd - provides getpwent(3)-compatible API, - system.random - allows to obtain entropy from /dev/random, - system.sysctl - provides sysctlbyname(3-compatible API. Sponsored by: The FreeBSD Foundation
2013-12-02 08:21:28 +00:00
.if ${MK_CASPER} != "no"
_lib_libcapsicum=lib/libcapsicum
.endif
lib/libcapsicum__L: lib/libnv__L
Move my simple logging API to a separate library. It is now already used by hastctl(8), hastd(8) and auditdistd(8) and will soon be also used by casperd(8) and its services. There is no documentation and pjdlog.h header file is not installed in /usr/include/ to keep it private. Unfortunately we don't have /lib/private/ at this point, only /usr/lib/private/, so the library is installed in /lib/. Sponsored by: The FreeBSD Foundation
2013-12-01 09:41:06 +00:00
lib/libpjdlog__L: lib/libutil__L
Merge xz 5.2.0. This brings support for multi-threaded compression. This brings close N times faster compression where N is the number of CPU cores. Because of this, liblzma now depends on libthr. Soon libarchive will be modified to use the new lzma API. Thanks to antoine@ for the exp-run. Differential Revision: https://reviews.freebsd.org/D1786 Reviewed by: bapt
2015-02-09 06:20:34 +00:00
lib/liblzma__L: lib/libthr__L
Move my simple logging API to a separate library. It is now already used by hastctl(8), hastd(8) and auditdistd(8) and will soon be also used by casperd(8) and its services. There is no documentation and pjdlog.h header file is not installed in /usr/include/ to keep it private. Unfortunately we don't have /lib/private/ at this point, only /usr/lib/private/, so the library is installed in /lib/. Sponsored by: The FreeBSD Foundation
2013-12-01 09:41:06 +00:00
- Merge in OFED 1.5.3 from projects/ofed/head
2011-03-21 09:58:24 +00:00
_generic_libs= ${_cddl_lib} gnu/lib ${_kerberos5_lib} lib ${_secure_lib} usr.bin/lex/lib ${_ofed_lib}
MFP4: 212854, 212854 Add a LOCAL_LIB_DIRS variable to complement the existing LOCAL_DIRS and LOCAL_TOOL_DIRS variables. Directories in LOCAL_LIB_DIRS are built at the end of the _generic_libs target. Reviewed by: imp (212854)
2012-06-15 19:40:59 +00:00
.for _DIR in ${LOCAL_LIB_DIRS}
.if exists(${.CURDIR}/${_DIR}/Makefile)
_generic_libs+= ${_DIR}
.endif
.endfor
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
lib/libopie__L lib/libtacplus__L: lib/libmd__L
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
.if ${MK_CDDL} != "no"
Commit two more files missed in r219089. MFC after: 1 month
2011-02-27 19:44:10 +00:00
_cddl_lib_libumem= cddl/lib/libumem
Partial MFV (illumos-gate 13753:2aba784c276b) 2762 zpool command should have better support for feature flags References: https://www.illumos.org/issues/2762 MFC after: 2 weeks
2012-07-30 23:14:24 +00:00
_cddl_lib_libnvpair= cddl/lib/libnvpair
Fix build: Build libavl as prebuild-lib. X-MFC-With: 266520
2014-05-22 05:33:50 +00:00
_cddl_lib_libavl= cddl/lib/libavl
Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
2014-10-03 20:36:09 +00:00
_cddl_lib_libuutil= cddl/lib/libuutil
WiP merge of libzfs_core (MFV r238590, r238592) not yet working, ioctl handling needs to be changed
2013-03-05 08:09:53 +00:00
_cddl_lib_libzfs_core= cddl/lib/libzfs_core
Fix dependency errors when linking libproc. Reported by: Oliver Hartmann X-MFC-With: r272488
2014-10-05 22:13:13 +00:00
_cddl_lib_libctf= cddl/lib/libctf
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
_cddl_lib= cddl/lib
libzfs_core depends on libnvpair, explicitly say this in Makefile.inc1. This fixes build with make -j.
2013-03-05 22:51:11 +00:00
cddl/lib/libzfs_core__L: cddl/lib/libnvpair__L
Add dependencies to various libraries to libzfs and libzpool. Submitted by: sef
2014-10-03 20:36:09 +00:00
cddl/lib/libzfs__L: lib/libgeom__L
Fix dependency errors when linking libproc. Reported by: Oliver Hartmann X-MFC-With: r272488
2014-10-05 22:13:13 +00:00
cddl/lib/libctf__L: lib/libz__L
Connect ZFS to the build.
2007-04-06 02:13:30 +00:00
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_CRYPT} != "no"
.if ${MK_OPENSSL} != "no"
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
_secure_lib_libcrypto= secure/lib/libcrypto
_secure_lib_libssl= secure/lib/libssl
Add missing shared library interdependencies.
2005-11-10 18:07:07 +00:00
lib/libradius__L secure/lib/libssl__L: secure/lib/libcrypto__L
Clean up the OpenSSH build. It is now possible to build most components as static binaries, if desired. The one exception is sshd, which runs into trouble due to libpam.a's includion of pam_ssh. Make OpenSSH use LDNS if available. This allows it to verify signed SSHFP records. Approved by: re (blanket)
2013-09-10 22:26:11 +00:00
.if ${MK_LDNS} != "no"
_lib_libldns= lib/libldns
lib/libldns__L: secure/lib/libcrypto__L
.endif
Unbreak world: - WITHOUT_OPENSSH (and WITH_KERBEROS) - WITHOUT_KERBEROS and WITH_GSSAPI PR: 137483 Submitted by: bf MFC after: 2 weeks Note: this breaks harder world WITHOUT_GSSAPI (and WITH_KERBEROS), but well
2010-01-23 19:29:42 +00:00
.if ${MK_OPENSSH} != "no"
_secure_lib_libssh= secure/lib/libssh
secure/lib/libssh__L: lib/libz__L secure/lib/libcrypto__L lib/libcrypt__L
Clean up the OpenSSH build. It is now possible to build most components as static binaries, if desired. The one exception is sshd, which runs into trouble due to libpam.a's includion of pam_ssh. Make OpenSSH use LDNS if available. This allows it to verify signed SSHFP records. Approved by: re (blanket)
2013-09-10 22:26:11 +00:00
.if ${MK_LDNS} != "no"
secure/lib/libssh__L: lib/libldns__L
.endif
Unbreak world: - WITHOUT_OPENSSH (and WITH_KERBEROS) - WITHOUT_KERBEROS and WITH_GSSAPI PR: 137483 Submitted by: bf MFC after: 2 weeks Note: this breaks harder world WITHOUT_GSSAPI (and WITH_KERBEROS), but well
2010-01-23 19:29:42 +00:00
.if ${MK_KERBEROS_SUPPORT} != "no"
Regen the list of prebuild libraries using tools/make_libdeps.sh.
2010-01-26 10:00:26 +00:00
secure/lib/libssh__L: lib/libgssapi__L kerberos5/lib/libkrb5__L \
kerberos5/lib/libhx509__L kerberos5/lib/libasn1__L lib/libcom_err__L \
lib/libmd__L kerberos5/lib/libroken__L
Catch up with the current output of tools/make_libdeps.sh: - Removed the stale dependency of libypclnt on librpcsvc. - Fixed the dependency graph of libssh.
2004-05-12 07:02:17 +00:00
.endif
Don't build usr.sbin/pcvt/keycap on anything other than i386 when building the libraries target. pcvt is i386 specific.
1999-12-17 11:23:56 +00:00
.endif
Make NO_OPENSSL actually imply NO_OPENSSH, as documented in make.conf(5).
2002-06-21 08:54:03 +00:00
.endif
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
_secure_lib= secure/lib
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
.endif
Don't build usr.sbin/pcvt/keycap on anything other than i386 when building the libraries target. pcvt is i386 specific.
1999-12-17 11:23:56 +00:00
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
.if ${MK_KERBEROS} != "no"
kerberos5/lib/libasn1__L: lib/libcom_err__L kerberos5/lib/libroken__L
kerberos5/lib/libhdb__L: kerberos5/lib/libasn1__L lib/libcom_err__L \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
kerberos5/lib/libkrb5__L kerberos5/lib/libroken__L \
kerberos5/lib/libwind__L kerberos5/lib/libheimsqlite__L
kerberos5/lib/libheimntlm__L: secure/lib/libcrypto__L kerberos5/lib/libkrb5__L \
kerberos5/lib/libroken__L lib/libcom_err__L
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
kerberos5/lib/libhx509__L: kerberos5/lib/libasn1__L lib/libcom_err__L \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
secure/lib/libcrypto__L kerberos5/lib/libroken__L kerberos5/lib/libwind__L
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
kerberos5/lib/libkrb5__L: kerberos5/lib/libasn1__L lib/libcom_err__L \
lib/libcrypt__L secure/lib/libcrypto__L kerberos5/lib/libhx509__L \
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
kerberos5/lib/libroken__L kerberos5/lib/libwind__L \
kerberos5/lib/libheimbase__L kerberos5/lib/libheimipcc__L
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
kerberos5/lib/libroken__L: lib/libcrypt__L
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
kerberos5/lib/libwind__L: kerberos5/lib/libroken__L lib/libcom_err__L
kerberos5/lib/libheimbase__L: lib/libthr__L
kerberos5/lib/libheimipcc__L: kerberos5/lib/libroken__L kerberos5/lib/libheimbase__L lib/libthr__L
kerberos5/lib/libheimsqlite__L: lib/libthr__L
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
.endif
Unbreak world: - WITHOUT_OPENSSH (and WITH_KERBEROS) - WITHOUT_KERBEROS and WITH_GSSAPI PR: 137483 Submitted by: bf MFC after: 2 weeks Note: this breaks harder world WITHOUT_GSSAPI (and WITH_KERBEROS), but well
2010-01-23 19:29:42 +00:00
.if ${MK_GSSAPI} != "no"
_lib_libgssapi= lib/libgssapi
.endif
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
.if ${MK_KERBEROS} != "no"
_kerberos5_lib= kerberos5/lib
_kerberos5_lib_libasn1= kerberos5/lib/libasn1
- Add missing interdependencies to kerberos libraries. Some of the kerberos libraries were not linked properly (missing dependencies), which causes 3rd party applications linking to fail when --as-needed ld flag is used. I also added the --no-undefined ld(1) flag to make sure that there're no missing dependencies. MFC after: 3 days
2011-09-27 07:14:12 +00:00
_kerberos5_lib_libhdb= kerberos5/lib/libhdb
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
_kerberos5_lib_libheimbase= kerberos5/lib/libheimbase
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
_kerberos5_lib_libkrb5= kerberos5/lib/libkrb5
Fix conflicts after heimdal-1.1 import and add build infrastructure. Import all non-style changes made by heimdal to our own libgssapi.
2008-05-07 13:53:12 +00:00
_kerberos5_lib_libhx509= kerberos5/lib/libhx509
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
_kerberos5_lib_libroken= kerberos5/lib/libroken
Fix conflicts after heimdal-1.1 import and add build infrastructure. Import all non-style changes made by heimdal to our own libgssapi.
2008-05-07 13:53:12 +00:00
_kerberos5_lib_libheimntlm= kerberos5/lib/libheimntlm
- Update FreeBSD Heimdal distribution to version 1.5.1. This also brings several new kerberos related libraries and applications to FreeBSD: o kgetcred(1) allows one to manually get a ticket for a particular service. o kf(1) securily forwards ticket to another host through an authenticated and encrypted stream. o kcc(1) is an umbrella program around klist(1), kswitch(1), kgetcred(1) and other user kerberos operations. klist and kswitch are just symlinks to kcc(1) now. o kswitch(1) allows you to easily switch between kerberos credentials if you're running KCM. o hxtool(1) is a certificate management tool to use with PKINIT. o string2key(1) maps a password into key. o kdigest(8) is a userland tool to access the KDC's digest interface. o kimpersonate(8) creates a "fake" ticket for a service. We also now install manpages for some lirbaries that were not installed before, libheimntlm and libhx509. - The new HEIMDAL version no longer supports Kerberos 4. All users are recommended to switch to Kerberos 5. - Weak ciphers are now disabled by default. To enable DES support (used by telnet(8)), use "allow_weak_crypto" option in krb5.conf. - libtelnet, pam_ksu and pam_krb5 are now compiled with error on warnings disabled due to the function they use (krb5_get_err_text(3)) being deprecated. I plan to work on this next. - Heimdal's KDC now require sqlite to operate. We use the bundled version and install it as libheimsqlite. If some other FreeBSD components will require it in the future we can rename it to libbsdsqlite and use for these components as well. - This is not a latest Heimdal version, the new one was released while I was working on the update. I will update it to 1.5.2 soon, as it fixes some important bugs and security issues.
2012-03-22 08:48:42 +00:00
_kerberos5_lib_libheimsqlite= kerberos5/lib/libheimsqlite
_kerberos5_lib_libheimipcc= kerberos5/lib/libheimipcc
_kerberos5_lib_libwind= kerberos5/lib/libwind
- Do not build libcom_err and compile_et when kerberos is disabled. They depends on several heimdal libraries and not used by anything but kerberos tools.
2012-03-23 03:16:35 +00:00
_libcom_err= lib/libcom_err
- Added rad_demangle() for demangling user-passwords (needed for MS-CHAPv1 MPPE-keys). - Added rad_demangle_mppe_key() for demangling mppe-keys (needed for MPPE-keys). - Added some typecasts for avoiding compiler warnings. - Fix: better handle wrong usage of the lib (if the programmer has not called rad_create_request() but rad_put_*(), then a weird error message was returned). - Added a new function for putting the Message-Authenticator. - Verify the Message-Authenticator, if it was found inside a response packet and silently drop the packet, if the validation failed. - Implicitly put the Message-Authenticator, if the EAP-Message attribute was added. - Added some missing defines. Submitted by: Michael Bretterklieber PR: 46555
2004-04-27 15:00:29 +00:00
.endif
Reimplementation of world/kernel build options. For details, see: http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
2006-03-17 18:54:44 +00:00
.if ${MK_NIS} != "no"
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
_lib_libypclnt= lib/libypclnt
Add knob NO_NIS (fka NO_YP_LIBC) and make world compileable when set. If turned on no NIS support and related programs will be built. Lost parts rediscovered by: Danny Braniss <danny at cs.huji.ac.il> PR: bin/68303 No objections: des, gshapiro, nectar Reviewed by: ru Approved by: rwatson (mentor) MFC after: 2 weeks
2004-11-13 20:40:32 +00:00
.endif
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
.if ${MK_OPENSSL} == "no"
Backout libinstall.a -> libpkg commit. Discussed with: erwin, brooks, bapt
2011-05-17 19:11:47 +00:00
lib/libradius__L: lib/libmd__L
Shuffle _*_libs assigments (no functional changes).
2006-10-07 19:26:46 +00:00
.endif
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
Fix build race in Makefile.inc1 after r274226 by adding lib/libm__L dependency for gnu/lib/libdialog Sponsored by: EMC / Isilon Storage Division
2014-11-08 04:24:54 +00:00
gnu/lib/libdialog__L: lib/msun__L lib/ncurses/ncursesw__L
For really fast machines, an edge-case may exist where dpv(3) may be built before contrib dependency, dialog(3). Add dialog(3) to the list of _prebuild_libs to ensure that this does not happen. Tested on: 11.0-CURRENT amd64 @ r274205 Thanks to: kargl, Larry Rosenman <ler@lerctr.org>, ngie, markj Recommended by: ngie Reviewed by: ngie, markj MFC after: 21 days X-MFC-to: stable/10 stable/9 X-MFC-with: 274116 274120 274121 274123 274144 274146 274192 274203
2014-11-07 00:59:40 +00:00
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
.for _lib in ${_prereq_libs}
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
${_lib}__PL: .PHONY .MAKE
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
.if exists(${.CURDIR}/${_lib})
${_+_}@${ECHODIR} "===> ${_lib} (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_lib} && \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ obj && \
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ depend && \
Spell NO_PROFILE= as MK_PROFILE=no.
2014-04-25 19:25:26 +00:00
${MAKE} MK_TESTS=no MK_PROFILE=no -DNO_PIC \
Fix buildworld when WITH_TESTS is enabled. The addition of the TESTS knob and its enabling of the build of tests in lib/libcrypt/tests/ broke the build. The reason is that we cannot descend into tests/ subdirectories until all prerequisites have been built, which in the case of tests may be "a lot of things" (libatf-c in this case). Ensure that we do not walk tests/ directories during the bootstrapping of the libraries as part of buildworld. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
2013-11-08 14:20:22 +00:00
DIRPRFX=${_lib}/ all && \
Spell NO_PROFILE= as MK_PROFILE=no.
2014-04-25 19:25:26 +00:00
${MAKE} MK_TESTS=no MK_PROFILE=no -DNO_PIC \
Fix buildworld when WITH_TESTS is enabled. The addition of the TESTS knob and its enabling of the build of tests in lib/libcrypt/tests/ broke the build. The reason is that we cannot descend into tests/ subdirectories until all prerequisites have been built, which in the case of tests may be "a lot of things" (libatf-c in this case). Ensure that we do not walk tests/ directories during the bootstrapping of the libraries as part of buildworld. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
2013-11-08 14:20:22 +00:00
DIRPRFX=${_lib}/ install
GCC will now properly link libc with all shared objects in order to record 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.
2007-05-19 03:34:59 +00:00
.endif
.endfor
Revert r227841 and part of r227798. We still build libpam in two passes, but we use STATIC_CFLAGS instead of our own private .c.o rule. MFC after: 3 weeks
2011-11-24 13:18:58 +00:00
.for _lib in ${_startup_libs} ${_prebuild_libs:Nlib/libpam} ${_generic_libs}
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
${_lib}__L: .PHONY .MAKE
Revert to rev 1.91. Revs 1.9{2,3} were causing problems for people with pre-Aug 4.0-CURRENT worlds and those with pre-GCC 2.95.2 worlds. The problem with pre-Aug worlds is the installed Byacc and Bison doesn't have necessary changes to compile either GCC 2.95 or EGCS 1.1.x. The problem with pre-GCC 2.95 worlds is libgcc is built with the wrong compiler. See rev 1.17 of src/gnu/lib/libgcc/Makefile (which used to live in src/gnu/usr.bin/cc/libgcc) + commit messge for details of the requirements.
1999-11-24 06:04:11 +00:00
.if exists(${.CURDIR}/${_lib})
Always make obj when building the libraries. This never hurts, and helps some cross-architecture building tool installation patches that I'm developing.
2006-08-24 17:02:26 +00:00
${_+_}@${ECHODIR} "===> ${_lib} (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_lib} && \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ obj && \
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ depend && \
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ all && \
${MAKE} MK_TESTS=no DIRPRFX=${_lib}/ install
``Disable'' a.out 'make world', as per flag day notification on current and committers. A 'make aout-to-elf' is strongly encouraged. This isn't quite the end of the line for people who have a real problem with updating yet, but we've got to get this over and done with. Yes, it's bound to be a couple of bumpy couple of days.
1999-01-07 06:26:33 +00:00
.endif
Per requests from the community, commit rudimentary cross compilation support. I've been building world with these changes for months w/o ill effect. I've also managed to build the cross tool chain for MIPS with these patches. Please note that the extent to which these patches work is largely dictated by how well our tool chains support the cross compilation. Building alpha binaries on i386 doesn't work. Supposedly building i386 binaries on alpha does work, but I've not verified it with these patches, however.
1999-07-07 04:46:46 +00:00
.endfor
Add a target to check the consistency of the make OBJFORMAT variable with the object format determined by objformat. This prevents foot shooting (a form of boot scooting for hackers?) where local changes to /etc/make.conf or /etc/make.conf.local try to override OBJFORMAT in an incomplete way.
1998-09-01 00:39:02 +00:00
Revert r227841 and part of r227798. We still build libpam in two passes, but we use STATIC_CFLAGS instead of our own private .c.o rule. MFC after: 3 weeks
2011-11-24 13:18:58 +00:00
# libpam is special: we need to build static PAM modules before
# static PAM library, and dynamic PAM library before dynamic PAM
# modules.
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
lib/libpam__L: .PHONY .MAKE
Revert r227841 and part of r227798. We still build libpam in two passes, but we use STATIC_CFLAGS instead of our own private .c.o rule. MFC after: 3 weeks
2011-11-24 13:18:58 +00:00
${_+_}@${ECHODIR} "===> lib/libpam (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/lib/libpam && \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
${MAKE} MK_TESTS=no DIRPRFX=lib/libpam/ obj && \
${MAKE} MK_TESTS=no DIRPRFX=lib/libpam/ depend && \
${MAKE} MK_TESTS=no DIRPRFX=lib/libpam/ \
Fix buildworld when WITH_TESTS is enabled. The addition of the TESTS knob and its enabling of the build of tests in lib/libcrypt/tests/ broke the build. The reason is that we cannot descend into tests/ subdirectories until all prerequisites have been built, which in the case of tests may be "a lot of things" (libatf-c in this case). Ensure that we do not walk tests/ directories during the bootstrapping of the libraries as part of buildworld. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
2013-11-08 14:20:22 +00:00
-D_NO_LIBPAM_SO_YET all && \
Kill NO_TESTS and use MK_TESTS=no when we want to skip them.
2014-03-30 22:24:53 +00:00
${MAKE} MK_TESTS=no DIRPRFX=lib/libpam/ \
Fix buildworld when WITH_TESTS is enabled. The addition of the TESTS knob and its enabling of the build of tests in lib/libcrypt/tests/ broke the build. The reason is that we cannot descend into tests/ subdirectories until all prerequisites have been built, which in the case of tests may be "a lot of things" (libatf-c in this case). Ensure that we do not walk tests/ directories during the bootstrapping of the libraries as part of buildworld. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
2013-11-08 14:20:22 +00:00
-D_NO_LIBPAM_SO_YET install
Revert r227841 and part of r227798. We still build libpam in two passes, but we use STATIC_CFLAGS instead of our own private .c.o rule. MFC after: 3 weeks
2011-11-24 13:18:58 +00:00
lex(1) no longer installs headers into GCC-internal dirs (since src/usr.bin/lex/Makefile,v 1.20).
2007-05-26 20:17:19 +00:00
_prereq_libs: ${_prereq_libs:S/$/__PL/}
Add a tool (and the first application of it) that could be used to automate building of libraries. Prodded by: bde
2002-04-12 19:46:25 +00:00
_startup_libs: ${_startup_libs:S/$/__L/}
_prebuild_libs: ${_prebuild_libs:S/$/__L/}
_generic_libs: ${_generic_libs:S/$/__L/}
Parallelize (on the top-level SUBDIR list) the "all" stage of buildworld. This gives 5-11% percent gain in real buildworld times on various UP and SMP systems here. I used 4 * hw.ncpu as an argument to "make -j" in my tests.
2003-04-01 11:39:04 +00:00
.for __target in all clean cleandepend cleandir depend includes obj
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
.for entry in ${SUBDIR}
Sprinkle some .MAKE magic
2013-07-06 00:13:08 +00:00
${entry}.${__target}__D: .PHONY .MAKE
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
${_+_}@set -e; if test -d ${.CURDIR}/${entry}.${MACHINE_ARCH}; then \
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${ECHODIR} "===> ${DIRPRFX}${entry}.${MACHINE_ARCH} (${__target})"; \
MACHINE -> MACHINE_ARCH to allow PC98 to define MACHINE=pc98. Submitted by: Takahashi Yoshihiro <nyan@wyvern.cc.kogakuin.ac.jp>
1998-08-31 20:48:13 +00:00
edir=${entry}.${MACHINE_ARCH}; \
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
cd ${.CURDIR}/$${edir}; \
else \
Although 'Unanimous Consent' appears to be a well defined and used in the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
2004-09-07 15:19:40 +00:00
${ECHODIR} "===> ${DIRPRFX}${entry} (${__target})"; \
E-day build system changes. - Moved most of the guts of Makefile to Makefile.inc1 to become the backend for the build system. - The new Makefile doesn't suffer from problems including the wrong sys.mk because it doesn't use anything in there or bsd.own.mk. So, from now on, the proper build command is just `make world' (or buildworld). - The intermediate makefiles called Makefile.inc0 and Makefile.upgrade fiddle with the OBJFORMAT and MAKEOBJDIRPREFIX variables so that both aout and elf object trees can coexist. Makefile.upgrade contains the aout->elf transition build. - A cross build environment is now very close to reality. Specifying TOOLDIR, setting OBJFORMAT and MAKEOBJDIRPREFIX allow that. See the comments in Makefile for more info.
1998-08-31 01:08:08 +00:00
edir=${entry}; \
cd ${.CURDIR}/$${edir}; \
fi; \
${MAKE} ${__target} DIRPRFX=${DIRPRFX}$${edir}/
.endfor
par-${__target}: ${SUBDIR:S/$/.${__target}__D/}
.endfor
.include <bsd.subdir.mk>
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
Expose all of {check,delete}-old{,-dirs,-files,-libs}. MFC after: 3 weeks
2007-05-16 08:46:35 +00:00
.if make(check-old) || make(check-old-dirs) || \
make(check-old-files) || make(check-old-libs) || \
make(delete-old) || make(delete-old-dirs) || \
make(delete-old-files) || make(delete-old-libs)
- Only make the delete-old related parts visible if one of the 3 targets are called (wrapped in ".if make(...)"). This may reduce the amount of memory needed for all other targets (the file lists are already large and they will grow further). - Be verbose in the batch case of the delete-old part too.
2005-07-30 18:02:20 +00:00
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
#
# check for / delete old files section
#
.include "ObsoleteFiles.inc"
OLD_LIBS_MESSAGE="Please be sure no application still uses those libraries, \
else you can not start such an application. Consult UPDATING for more \
information regarding how to cope with the removal/revision bump of a \
specific library."
.if !defined(BATCH_DELETE_OLD_FILES)
RM_I=-i
- Only make the delete-old related parts visible if one of the 3 targets are called (wrapped in ".if make(...)"). This may reduce the amount of memory needed for all other targets (the file lists are already large and they will grow further). - Be verbose in the batch case of the delete-old part too.
2005-07-30 18:02:20 +00:00
.else
RM_I=-v
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
.endif
delete-old-files:
@echo ">>> Removing old files (only deletes safe to delete libs)"
# Ask for every old file if the user really wants to remove it.
Fix a couple of typos
2005-08-23 07:58:55 +00:00
# It's annoying, but better safe than sorry.
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
# NB: We cannot pass the list of OLD_FILES as a parameter because the
# argument list will get too long. Using .for/.endfor make "loops" will make
# the Makefile parser segfault.
@exec 3<&0; \
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
cd ${.CURDIR}; \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
Revert-and-redo r255955: the sort -r should be added to delete-old-dirs. Approved by: re (gjb)
2013-10-01 22:53:27 +00:00
-V OLD_FILES -V "OLD_FILES:Musr/share/*.gz:R" | xargs -n1 | \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
while read file; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -f "${DESTDIR}/$${file}" -o -L "${DESTDIR}/$${file}" ]; then \
Revision 1.576 removed too much. I didn't notice because my /usr is on ZFS, which doesn't support flags...
2007-05-19 20:34:29 +00:00
chflags noschg "${DESTDIR}/$${file}" 2>/dev/null || true; \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
rm ${RM_I} "${DESTDIR}/$${file}" <&3; \
A file can also be a link, so check not only for a file, but also for a link in the delete-old and check-old targets. We don't install a lib (libXY.so.Z) as a link, but an user may have created something like this. This is dangerous if this link points to a different version of the lib. So check for a link also in the *-lib targets (an annoyed user which absolutely wants this redirection of a lib should use libmap.conf instead of a link). A directory can also be a link, but in this case just echo a message to remove it by hand.
2006-02-18 16:58:21 +00:00
fi; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Remove cat-pages without corresponding man-pages.
2005-08-07 13:47:25 +00:00
# Remove catpages without corresponding manpages.
In 'make delete-old', use 'exec' to redirect an fd persistently. That is, write 'exec 3<&0' instead of '3<&0'. Due to an sh(1) bug fixed in r199953, the latter also persisted, provided that fd 3 was not open before. With newer sh or fd 3 open, it would not delete orphaned catpages. MFC after: 2 weeks
2010-01-14 23:27:23 +00:00
@exec 3<&0; \
Speed up stale catpages hunting by not running sed(1) for every catpage.
2005-11-12 19:31:30 +00:00
find ${DESTDIR}/usr/share/man/cat* ! -type d | \
sed -ep -e's:${DESTDIR}/usr/share/man/cat:${DESTDIR}/usr/share/man/man:' | \
while read catpage; do \
read manpage; \
if [ ! -e "$${manpage}" ]; then \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
rm ${RM_I} $${catpage} <&3; \
Speed up stale catpages hunting by not running sed(1) for every catpage.
2005-11-12 19:31:30 +00:00
fi; \
Remove cat-pages without corresponding man-pages.
2005-08-07 13:47:25 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
@echo ">>> Old files removed"
check-old-files:
@echo ">>> Checking for old files"
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
@cd ${.CURDIR}; \
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
-V OLD_FILES -V "OLD_FILES:Musr/share/*.gz:R" | xargs -n1 | \
while read file; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -f "${DESTDIR}/$${file}" -o -L "${DESTDIR}/$${file}" ]; then \
Greatly speed up {check,delete}-old* by replacing make loops with sh loops. MFC after: 3 weeks
2007-05-13 18:15:50 +00:00
echo "${DESTDIR}/$${file}"; \
fi; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Remove cat-pages without corresponding man-pages.
2005-08-07 13:47:25 +00:00
# Check for catpages without corresponding manpages.
Speed up stale catpages hunting by not running sed(1) for every catpage.
2005-11-12 19:31:30 +00:00
@find ${DESTDIR}/usr/share/man/cat* ! -type d | \
sed -ep -e's:${DESTDIR}/usr/share/man/cat:${DESTDIR}/usr/share/man/man:' | \
while read catpage; do \
read manpage; \
if [ ! -e "$${manpage}" ]; then \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
echo $${catpage}; \
Speed up stale catpages hunting by not running sed(1) for every catpage.
2005-11-12 19:31:30 +00:00
fi; \
Remove cat-pages without corresponding man-pages.
2005-08-07 13:47:25 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
delete-old-libs:
@echo ">>> Removing old libraries"
@echo "${OLD_LIBS_MESSAGE}" | fmt
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
@exec 3<&0; \
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
cd ${.CURDIR}; \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
-V OLD_LIBS | xargs -n1 | \
while read file; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -f "${DESTDIR}/$${file}" -o -L "${DESTDIR}/$${file}" ]; then \
Revision 1.576 removed too much. I didn't notice because my /usr is on ZFS, which doesn't support flags...
2007-05-19 20:34:29 +00:00
chflags noschg "${DESTDIR}/$${file}" 2>/dev/null || true; \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
rm ${RM_I} "${DESTDIR}/$${file}" <&3; \
A file can also be a link, so check not only for a file, but also for a link in the delete-old and check-old targets. We don't install a lib (libXY.so.Z) as a link, but an user may have created something like this. This is dangerous if this link points to a different version of the lib. So check for a link also in the *-lib targets (an annoyed user which absolutely wants this redirection of a lib should use libmap.conf instead of a link). A directory can also be a link, but in this case just echo a message to remove it by hand.
2006-02-18 16:58:21 +00:00
fi; \
Fix 'make delete-old-libs' and 'make check-libs' to delete .debug files created by WITH_DEBUG_FILES. Also cleanup .symbols files from the period between r244236 when .symbols were supported and r251512 when they were renamed to .debug. Only propose to delete a .debug file if the corresponding library itself was deleted already. Reported by: des Reviewed by: emaste (earlier version) Approved by: bapt MFC after: 3 days
2013-10-21 10:09:48 +00:00
for ext in debug symbols; do \
if ! [ -e "${DESTDIR}/$${file}" ] && [ -f \
"${DESTDIR}${DEBUGDIR}/$${file}.$${ext}" ]; then \
rm ${RM_I} "${DESTDIR}${DEBUGDIR}/$${file}.$${ext}" \
<&3; \
fi; \
done; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
@echo ">>> Old libraries removed"
check-old-libs:
@echo ">>> Checking for old libraries"
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
@cd ${.CURDIR}; \
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
-V OLD_LIBS | xargs -n1 | \
while read file; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -f "${DESTDIR}/$${file}" -o -L "${DESTDIR}/$${file}" ]; then \
Greatly speed up {check,delete}-old* by replacing make loops with sh loops. MFC after: 3 weeks
2007-05-13 18:15:50 +00:00
echo "${DESTDIR}/$${file}"; \
fi; \
Fix 'make delete-old-libs' and 'make check-libs' to delete .debug files created by WITH_DEBUG_FILES. Also cleanup .symbols files from the period between r244236 when .symbols were supported and r251512 when they were renamed to .debug. Only propose to delete a .debug file if the corresponding library itself was deleted already. Reported by: des Reviewed by: emaste (earlier version) Approved by: bapt MFC after: 3 days
2013-10-21 10:09:48 +00:00
for ext in debug symbols; do \
if [ -f "${DESTDIR}${DEBUGDIR}/$${file}.$${ext}" ]; then \
echo "${DESTDIR}${DEBUGDIR}/$${file}.$${ext}"; \
fi; \
done; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
delete-old-dirs:
@echo ">>> Removing old directories"
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
@cd ${.CURDIR}; \
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
Revert-and-redo r255955: the sort -r should be added to delete-old-dirs. Approved by: re (gjb)
2013-10-01 22:53:27 +00:00
-V OLD_DIRS | xargs -n1 | sort -r | \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
while read dir; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -d "${DESTDIR}/$${dir}" ]; then \
rmdir -v "${DESTDIR}/$${dir}" || true; \
elif [ -L "${DESTDIR}/$${dir}" ]; then \
echo "${DESTDIR}/$${dir} is a link, please remove everything manually."; \
A file can also be a link, so check not only for a file, but also for a link in the delete-old and check-old targets. We don't install a lib (libXY.so.Z) as a link, but an user may have created something like this. This is dangerous if this link points to a different version of the lib. So check for a link also in the *-lib targets (an annoyed user which absolutely wants this redirection of a lib should use libmap.conf instead of a link). A directory can also be a link, but in this case just echo a message to remove it by hand.
2006-02-18 16:58:21 +00:00
fi; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
@echo ">>> Old directories removed"
check-old-dirs:
@echo ">>> Checking for old directories"
In r257079, SRCDIR is pointed to ${.CURDIR} when not set. However, Makefile.inc1 is being called in sub-make's where make(1) would, by default, implicitly chdir(2) to ${.OBJDIR} before executing any targets. This would make some targets, like delete-old, when trying to derive various variables introduced by change r256921 using ``make -f Makefile.inc1'' that also rely on SRCDIR to fail. This changeset adds an explicit cd ${.CURDIR} before these unwrapped make calls, making them in line with the other ones that are already being wrapped with the explicit chdir's. Tested by: gjb MFC after: 5 days
2013-10-29 17:46:26 +00:00
@cd ${.CURDIR}; \
${MAKE} -f ${.CURDIR}/Makefile.inc1 ${.MAKEFLAGS} ${.TARGET} \
Fix the delete-old/check-old targets to work with arbitrarily long OLD_FILES/OLD_DIRS/OLD_LIBS lists. If you specify enough WITHOUT_FOO flags, the argument list passed to the shell will be too long. Using .for/.endfor make(1) "loop" will make the parser of the Makefile explode. Hack around this with good old pipes. No objections: netchild Reported by: b.f.
2011-04-01 20:59:23 +00:00
-V OLD_DIRS | xargs -n1 | \
while read dir; do \
Partially revert the check-old / delete-old modifications to clarify the logic. Apply similar modifications to {check,delete}-old-dirs, which I had overlooked.
2007-05-16 08:37:40 +00:00
if [ -d "${DESTDIR}/$${dir}" ]; then \
echo "${DESTDIR}/$${dir}"; \
elif [ -L "${DESTDIR}/$${dir}" ]; then \
echo "${DESTDIR}/$${dir} is a link, please remove everything manually."; \
A file can also be a link, so check not only for a file, but also for a link in the delete-old and check-old targets. We don't install a lib (libXY.so.Z) as a link, but an user may have created something like this. This is dangerous if this link points to a different version of the lib. So check for a link also in the *-lib targets (an annoyed user which absolutely wants this redirection of a lib should use libmap.conf instead of a link). A directory can also be a link, but in this case just echo a message to remove it by hand.
2006-02-18 16:58:21 +00:00
fi; \
Don't use a subshell where it isn't needed. Noticed by: John E Hein <jhein@timing.com>
2007-05-16 20:16:06 +00:00
done
Add delete-old and delete-old-libs targets: - removes obsolete files/dirs or libraries. - works in interactive (default) and batch mode - respects DISTDIR - documented in UPDATING and build(7) The head of the file ObsoleteFiles.inc contains instructions how to add obsolete files/dirs/libs to the list. Obviously one should add obsolete files to this list, when he removes a file/dir/lib from the basesystem. Additionally add check-old target: - allows re@ to check if a file on the obsolete list resurfaces Design goals: - allows full control by the user (default interactive mode) - possibility of scripted removal of obsolete files (batch mode) - opt-in removal of files (explicit list of files) - seperate removal of libs (2 delete targets) Important design decissions: - structured list of files to remove instead of a plain text file: * allows to remove additional files if a NO_foo knob is specified without the need to change the targets (no NO_foo knob is respected yet) - not using mtree like NetBSD does: * mtree doesn't has an interactive mode Discussed on: arch (long ago), current (this year) Additional input from: re (hrs) Approved by: mentor (joerg)
2005-07-23 14:23:30 +00:00
delete-old: delete-old-files delete-old-dirs
@echo "To remove old libraries run '${MAKE} delete-old-libs'."
check-old: check-old-files check-old-libs check-old-dirs
@echo "To remove old files and directories run '${MAKE} delete-old'."
@echo "To remove old libraries run '${MAKE} delete-old-libs'."
- Only make the delete-old related parts visible if one of the 3 targets are called (wrapped in ".if make(...)"). This may reduce the amount of memory needed for all other targets (the file lists are already large and they will grow further). - Be verbose in the batch case of the delete-old part too.
2005-07-30 18:02:20 +00:00
.endif
Add the new "showconfig" target that displays build configuration. Suggested by: phk
2006-03-18 14:30:23 +00:00
#
# showconfig - show build configuration.
#
showconfig:
Generate both userland and kernel option settings for showconfig. PR: 191920
2014-10-21 20:29:51 +00:00
@(${MAKE} -n -f ${.CURDIR}/sys/conf/kern.opts.mk -V dummy -dg1; \
${MAKE} -n -f ${.CURDIR}/share/mk/src.opts.mk -V dummy -dg1) 2>&1 | grep ^MK_ | sort -u
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
CPUTYPE is now a required define for calling Makefile.inc1 diretly, so make sure we define it for the xdev stuff. Move xdev stuff to be last again in this file. # xdev-build works now, but xdev-install appears to be broken though.
2011-02-11 02:37:47 +00:00
.if !empty(KRNLOBJDIR) && !empty(KERNCONF)
DTBOUTPUTPATH= ${KRNLOBJDIR}/${KERNCONF}/
.if !defined(FDT_DTS_FILE) || empty(FDT_DTS_FILE)
.if exists(${KERNCONFDIR}/${KERNCONF})
FDT_DTS_FILE!= awk 'BEGIN {FS="="} /^makeoptions[[:space:]]+FDT_DTS_FILE/ {print $$2}' \
Add appropriate quoting to allow building with a KERNCONFDIR containing spaces. PR: kern/162736 MFC after: 1 week
2014-05-03 09:24:20 +00:00
'${KERNCONFDIR}/${KERNCONF}' ; echo
CPUTYPE is now a required define for calling Makefile.inc1 diretly, so make sure we define it for the xdev stuff. Move xdev stuff to be last again in this file. # xdev-build works now, but xdev-install appears to be broken though.
2011-02-11 02:37:47 +00:00
.endif
.endif
.endif
.if !defined(DTBOUTPUTPATH) || !exists(${DTBOUTPUTPATH})
DTBOUTPUTPATH= ${.CURDIR}
.endif
#
# Build 'standalone' Device Tree Blob
#
builddtb:
Allow FDT_DTS_FILE to be a list, either in the makedtb target, or in a kernel config file. If you also want to have a static DTB compiled into your kernel, however, it cannot be a list. We have no mechanism in the kernel for picking one, so that doesn't make sense and will result in a compile-time error.
2014-04-30 18:02:04 +00:00
@PATH=${TMPPATH} MACHINE=${TARGET} \
Integrate device-tree upstream files into the build process: (1) Invoke cpp to bring in files via #include (although the old /include/ stuff is supported still). (2) bring in files from either vendor tree or freebsd-custom files when building. (3) move all dts* files from sys/boot/fdt/dts to sys/boot/fdt/dts/${MACHINE} as appropriate. (4) encode all the magic to do the build in sys/tools/fdt/make_dtb.sh so that the different places in the tree use the exact same logic. (5) switch back to gpl dtc by default. the bsdl one in the tree has significant issues not easily addressed by those unfamiliar with the code.
2014-02-28 18:29:09 +00:00
${.CURDIR}/sys/tools/fdt/make_dtb.sh ${.CURDIR}/sys \
Allow FDT_DTS_FILE to be a list, either in the makedtb target, or in a kernel config file. If you also want to have a static DTB compiled into your kernel, however, it cannot be a list. We have no mechanism in the kernel for picking one, so that doesn't make sense and will result in a compile-time error.
2014-04-30 18:02:04 +00:00
"${FDT_DTS_FILE}" ${DTBOUTPUTPATH}
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
###############
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
.if defined(TARGET) && defined(TARGET_ARCH)
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
.if ${TARGET} == ${MACHINE} && ${TARGET_ARCH} == ${MACHINE_ARCH}
CPUTYPE is now a required define for calling Makefile.inc1 diretly, so make sure we define it for the xdev stuff. Move xdev stuff to be last again in this file. # xdev-build works now, but xdev-install appears to be broken though.
2011-02-11 02:37:47 +00:00
XDEV_CPUTYPE?=${CPUTYPE}
.else
XDEV_CPUTYPE?=${TARGET_CPUTYPE}
.endif
Remove GNU texinfo from base along with all info pages. To be able to info pages consider installing texinfo from ports print/texinfo or via pkg: pkg install texinfo Differential Revision: https://reviews.freebsd.org/D1409 Reviewed by: emaste, imp (previous version) Relnotes: yes
2015-01-02 18:45:03 +00:00
NOFUN=-DNO_FSCHG MK_HTML=no -DNO_LINT \
Spell NO_PROFILE= as MK_PROFILE=no.
2014-04-25 19:25:26 +00:00
MK_MAN=no MK_NLS=no MK_PROFILE=no \
Migrate NO_WARN to MK_WARN. Support legacy NO_WARN usage. Remove a check for EARLY_BUILD because it isn't necessary (MK_WARN=no will always be defined for that).
2014-05-10 16:37:53 +00:00
MK_KERBEROS=no MK_RESCUE=no MK_TESTS=no MK_WARNS=no \
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
TARGET=${TARGET} TARGET_ARCH=${TARGET_ARCH} \
CPUTYPE is now a required define for calling Makefile.inc1 diretly, so make sure we define it for the xdev stuff. Move xdev stuff to be last again in this file. # xdev-build works now, but xdev-install appears to be broken though.
2011-02-11 02:37:47 +00:00
CPUTYPE=${XDEV_CPUTYPE}
Hmmm, specifying TARGET and TARGET_ARCH in the environment doesn't seem to work when building xdev anymore (most likely my changes lately moving the TARGET guessing stuff to Makefile from Makefile.inc1, but I really don't grok why). Fix make xdev by putting them on the command line. This will work either way while I try to figure it out.
2011-02-11 04:03:39 +00:00
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
XDDIR=${TARGET_ARCH}-freebsd
Prevent XDTP from being a relative path XDTP is used as the default SYSROOT for clang and thus should be an absolute path. PR: arm/188249 Submitted by: Edgar Martinez <wink15987@gmail.com> Reviewed by: imp
2014-04-04 17:58:33 +00:00
XDTP?=/usr/${XDDIR}
.if ${XDTP:N/*}
.error XDTP variable should be an absolute path
.endif
Fix xdev by using the install shell script as it knows about the -l argument thile the local version install may not.
2013-02-04 09:34:25 +00:00
CDBENV=MAKEOBJDIRPREFIX=${MAKEOBJDIRPREFIX}/${XDDIR} \
INSTALL="sh ${.CURDIR}/tools/install.sh"
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
CDENV= ${CDBENV} \
Fix xdev-install when installing to a location other than /
2013-03-31 08:54:04 +00:00
_SHLIBDIRPREFIX=${XDDESTDIR} \
Some xdev fixes: - if TARGET_ARCH is not defined and XDEV_ARCH is defined then early define TARGET_ARCH to the valud of XDEV_ARCH: This allow the xdev-build target to be able to correctly chose the compiler it needs to build - Allow overwriting XDTP to allow a user to not chose where the xdev env will live in - Fix build for gcc only xdev (like ia64) by providing the proper -B to the toolchain and not relying on gcc being installed already in base - Fix TOOLS_PREFIX so the generated toolchain has the right default sysroot when installed intead of getting the DESTDIR one - Fix supporting DESTDIR - Also overwrite CXX (needed for cross building c++ libraries with clang) and CPP (needed to cross build some libraries when gcc is the target default compiler but gcc is not installed on the building host) Discussed with: imp
2014-04-03 07:28:36 +00:00
TOOLS_PREFIX=${XDTP}
Fix xdev-install when installing to a location other than /
2013-03-31 08:54:04 +00:00
CD2CFLAGS=-isystem ${XDDESTDIR}/usr/include -L${XDDESTDIR}/usr/lib \
Some xdev fixes: - if TARGET_ARCH is not defined and XDEV_ARCH is defined then early define TARGET_ARCH to the valud of XDEV_ARCH: This allow the xdev-build target to be able to correctly chose the compiler it needs to build - Allow overwriting XDTP to allow a user to not chose where the xdev env will live in - Fix build for gcc only xdev (like ia64) by providing the proper -B to the toolchain and not relying on gcc being installed already in base - Fix TOOLS_PREFIX so the generated toolchain has the right default sysroot when installed intead of getting the DESTDIR one - Fix supporting DESTDIR - Also overwrite CXX (needed for cross building c++ libraries with clang) and CPP (needed to cross build some libraries when gcc is the target default compiler but gcc is not installed on the building host) Discussed with: imp
2014-04-03 07:28:36 +00:00
--sysroot=${XDDESTDIR}/ -B${XDDESTDIR}/usr/libexec \
-B${XDDESTDIR}/usr/bin -B${XDDESTDIR}/usr/lib
CD2ENV=${CDENV} CC="${CC} ${CD2CFLAGS}" CXX="${CXX} ${CD2CFLAGS}" \
CPP="${CPP} ${CD2CFLAGS}" \
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
MACHINE=${TARGET} MACHINE_ARCH=${TARGET_ARCH}
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
CDTMP= ${MAKEOBJDIRPREFIX}/${XDDIR}/${.CURDIR}/tmp
CDMAKE=${CDENV} PATH=${CDTMP}/usr/bin:${PATH} ${MAKE} ${NOFUN}
Allow 'make xdev' to work when DESTDIR is set. Submitted by: Patrick Kelsey <kelsey@ieee.org>
2013-10-16 16:46:25 +00:00
CD2MAKE=${CD2ENV} PATH=${CDTMP}/usr/bin:${XDDESTDIR}/usr/bin:${PATH} ${MAKE} ${NOFUN}
XDDESTDIR should not be set by the user, instead the user might want to tweak XDTP and let the standard DESTDIR decide where to install. Discussed with: imp
2014-04-03 22:22:10 +00:00
XDDESTDIR=${DESTDIR}/${XDTP}
Restore missing OSREL definition that accidetnally dropped from an earlier version of this patch.
2009-03-15 23:52:13 +00:00
.if !defined(OSREL)
OSREL!= uname -r | sed -e 's/[-(].*//'
.endif
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
Separate out the links creation from the other targets. This was supposed to have been done for the original commit, but somebody forgot. Pointy-hat-to: imp@
2014-07-10 18:28:12 +00:00
.ORDER: xdev-build xdev-install xdev-links
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
xdev: xdev-build xdev-install
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
.ORDER: _xb-worldtmp _xb-bootstrap-tools _xb-build-tools _xb-cross-tools
xdev-build: _xb-worldtmp _xb-bootstrap-tools _xb-build-tools _xb-cross-tools
_xb-worldtmp:
mkdir -p ${CDTMP}/usr
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${CDTMP}/usr >/dev/null
_xb-bootstrap-tools:
.for _tool in \
Build gperf with xdev as part of _xb-bootstrap-tools This will unbreak the build when "env MK_CXX=no make delete-old" has been run on the build host post-r272849 Tested with the following commands: /bin/sh export __MAKE_CONF=/dev/null SRCCONF=/dev/null export MK_CLANG=no MK_CLANG_BOOTSTRAP=no MK_GCC=yes MK_GCC_BOOTSTRAP=yes export MK_GNUCXX=yes TARGET=armv6 TARGET_ARCH=arm make xdev make toolchain make xdev-build sudo -E make xdev-install /usr/armv6-freebsd/usr/bin/cc -dumpmachine | grep arm X-MFC with: r272849 Reported by: Dan Raymond <draymond@foxvalley.net>, gjb
2014-12-08 09:09:50 +00:00
${_clang_tblgen} \
${_gperf}
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${CDMAKE} DIRPRFX=${_tool}/ obj && \
${CDMAKE} DIRPRFX=${_tool}/ depend && \
${CDMAKE} DIRPRFX=${_tool}/ all && \
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
${CDMAKE} DIRPRFX=${_tool}/ DESTDIR=${CDTMP} install
.endfor
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
_xb-build-tools:
Hmmm, specifying TARGET and TARGET_ARCH in the environment doesn't seem to work when building xdev anymore (most likely my changes lately moving the TARGET guessing stuff to Makefile from Makefile.inc1, but I really don't grok why). Fix make xdev by putting them on the command line. This will work either way while I try to figure it out.
2011-02-11 04:03:39 +00:00
${_+_}@cd ${.CURDIR}; \
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
${CDBENV} ${MAKE} -f Makefile.inc1 ${NOFUN} build-tools
_xb-cross-tools:
.for _tool in \
Ensure make xdev respect which compiler is CC and which compilers should be built according to standard build options
2014-04-01 06:46:59 +00:00
${_binutils} \
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
${_elftctools} \
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
usr.bin/ar \
${_clang_libs} \
Ensure make xdev respect which compiler is CC and which compilers should be built according to standard build options
2014-04-01 06:46:59 +00:00
${_clang} \
${_cc}
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
${_+_}@${ECHODIR} "===> xdev ${_tool} (obj,depend,all)"; \
Use && rather than ; when success of previous job matters.
2013-06-30 15:00:07 +00:00
cd ${.CURDIR}/${_tool} && \
${CDMAKE} DIRPRFX=${_tool}/ obj && \
${CDMAKE} DIRPRFX=${_tool}/ depend && \
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
${CDMAKE} DIRPRFX=${_tool}/ all
.endfor
_xi-mtree:
${_+_}@${ECHODIR} "mtree populating ${XDDESTDIR}"
mkdir -p ${XDDESTDIR}
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.root.dist \
-p ${XDDESTDIR} >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
-p ${XDDESTDIR}/usr >/dev/null
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
-p ${XDDESTDIR}/usr/include >/dev/null
Run mtree for BSD.tests.dist during make xdev-install, if the tests are enabled (which they are in the default configuration). Otherwise, it will fail because ${XDDESTDIR}/usr/include/atf-c does not exist. MFC after: 3 days
2014-07-21 21:26:10 +00:00
.if ${MK_TESTS} != "no"
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
mkdir -p ${XDDESTDIR}${TESTSBASE}
Run mtree for BSD.tests.dist during make xdev-install, if the tests are enabled (which they are in the default configuration). Otherwise, it will fail because ${XDDESTDIR}/usr/include/atf-c does not exist. MFC after: 3 days
2014-07-21 21:26:10 +00:00
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.tests.dist \
Fix building/installing tests when TESTSBASE != /usr/tests The work in r258233 hardcoded the assumption that tests was the last component of the tests tree by pushing tests as an explicit prefix for the paths in BSD.tests.dist and /usr was the prefix for all tests, per BSD.usr.dist and all of the mtree calls used in Makefile.inc1. This assumption breaks if/when one provides a custom TESTSBASE "prefix", e.g. TESTSBASE=/mytests . One thing that r258233 did properly though was remove "/usr/tests" creation from BSD.usr.dist -- that should have not been there in the first place. That was an "oops" on my part for the work that was originally committed in r241823 MFC after: 2 weeks Phabric: D1301 Reviewed by: imp Sponsored by: EMC / Isilon Storage Division
2014-12-18 18:16:00 +00:00
-p ${XDDESTDIR}${TESTSBASE} >/dev/null
Run mtree for BSD.tests.dist during make xdev-install, if the tests are enabled (which they are in the default configuration). Otherwise, it will fail because ${XDDESTDIR}/usr/include/atf-c does not exist. MFC after: 3 days
2014-07-21 21:26:10 +00:00
.endif
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
Separate out the links creation from the other targets. This was supposed to have been done for the original commit, but somebody forgot. Pointy-hat-to: imp@
2014-07-10 18:28:12 +00:00
.ORDER: xdev-build _xi-mtree _xi-cross-tools _xi-includes _xi-libraries
xdev-install: xdev-build _xi-mtree _xi-cross-tools _xi-includes _xi-libraries
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
_xi-cross-tools:
@echo "_xi-cross-tools"
.for _tool in \
Ensure make xdev respect which compiler is CC and which compilers should be built according to standard build options
2014-04-01 06:46:59 +00:00
${_binutils} \
Build infrastructure for elftoolchain tools Set WITH_ELFTOOLCHAIN_TOOLS in src.conf to use the elftoolchain version of the following tools: * addr2line * elfcopy (strip / mcs) * nm * size * strings Reviewed by: bapt (earlier version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D1224
2014-12-01 17:49:42 +00:00
${_elftctools} \
Fix xdev. Clang and libc were not building correctly on older worlds, for example, on 9.1. * To fix clang add an _xb-bootstrap-tools target that mirrors the existing bootstrap-tools target in the full world. * For libc have the compiler use the newly installed includes, and, while here, tell the compiler about the xdev library path as some other libraries will link against the installed libraries.
2013-03-31 08:31:06 +00:00
usr.bin/ar \
Ensure make xdev respect which compiler is CC and which compilers should be built according to standard build options
2014-04-01 06:46:59 +00:00
${_clang_libs} \
${_clang} \
${_cc}
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
${_+_}@${ECHODIR} "===> xdev ${_tool} (install)"; \
cd ${.CURDIR}/${_tool}; \
${CDMAKE} DIRPRFX=${_tool}/ install DESTDIR=${XDDESTDIR}
.endfor
_xi-includes:
${_+_}cd ${.CURDIR}; ${CD2MAKE} -f Makefile.inc1 par-includes \
DESTDIR=${XDDESTDIR}
_xi-libraries:
${_+_}cd ${.CURDIR}; ${CD2MAKE} -f Makefile.inc1 libraries \
DESTDIR=${XDDESTDIR}
Separate out the links creation from the other targets. This was supposed to have been done for the original commit, but somebody forgot. Pointy-hat-to: imp@
2014-07-10 18:28:12 +00:00
xdev-links:
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
${_+_}cd ${XDDESTDIR}/usr/bin; \
Separate out the links creation from the other targets. This was supposed to have been done for the original commit, but somebody forgot. Pointy-hat-to: imp@
2014-07-10 18:28:12 +00:00
mkdir -p ../../../../usr/bin; \
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
for i in *; do \
ln -sf ../../${XDTP}/usr/bin/$$i \
../../../../usr/bin/${XDDIR}-$$i; \
ln -sf ../../${XDTP}/usr/bin/$$i \
../../../../usr/bin/${XDDIR}${OSREL}-$$i; \
done
Provide proper error message when trying to build xdev, xdev-build or xdev-install targets without either XDEV or XDEV_ARCH defined.
2011-11-26 00:30:39 +00:00
.else
Separate out the links creation from the other targets. This was supposed to have been done for the original commit, but somebody forgot. Pointy-hat-to: imp@
2014-07-10 18:28:12 +00:00
xdev xdev-build xdev-install xdev-links:
Deprecate the use of XDEV and XDEV_ARCH and just use TARGET/TARGET_ARCH for the xdev build target, which is awesome and totally works. Reapply svn R268377 with correct name of libsupc++ here as this does resolve one dependancy race when building the xdev target. the xdev target builds for amd64, i386, mips, mips64 and armv6 with this commit, must be built as root, must be built from /usr/src, must not have a /usr/obj and places the xdev tools in /usr/$TARGET_ARCH-freebsd the xdev target still leaves some assorted files strewn about your /usr/src when this is done and needs to be investigated further. Phabric: https://phabric.freebsd.org/D385 Submitted by: bsdimp
2014-07-23 22:18:43 +00:00
@echo "*** Error: Both TARGET and TARGET_ARCH must be defined for \"${.TARGET}\" target"
Implement the xdev target. When you define XDEV=arch XDEV_ARCH=arch, you can build the cross development tools and install them as $XDEV-freebsd-xxx for each tool. This allows one to use autoconf to find the tools for cross building scenarios.
2009-03-13 07:23:58 +00:00
.endif
Reference in New Issue Copy Permalink