d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
87f515fb7a
freebsd-dev/Makefile.inc1

1099 lines
33 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:
Invert the condition that installs the dynamic linker early, since DYNAMICROOT is now the default. Also document -DNO_DYNAMICROOT since that is going to be a documented feature. Submitted by: matusita, rushani
2003-11-16 21:17:43 +00:00
# -DNO_DYNAMICROOT do not link /bin and /sbin dynamically
Negate the logic of MAKE_KERBEROS5, and replace it with NO_KERBEROS.
2003-05-05 08:44:40 +00:00
# -DNO_KERBEROS Do not build Heimdal (Kerberos 5)
Apparently we prefer underscores in new options. Sorry for the churn folks. Requested by: obrien
2003-07-14 16:21:16 +00:00
# -DNO_RESCUE do not build rescue binaries
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
# -DNOCLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir
# -DNOCLEAN do not clean at all
# -DNOCRYPT will prevent building of crypt versions
Add -DNOMAN to the list.
2003-02-11 19:21:13 +00:00
# -DNOMAN do not build the manual pages
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
# -DNOPROFILE do not build profiled libraries
# -DNOGAMES do not go into games subdir
# -DNOSHARE do not go into share subdir
# -DNOINFO do not make or install info files
# -DNOLIBC_R do not build libc_r.
Document NO_FORTRAN.
1999-05-03 17:54:59 +00:00
# -DNO_FORTRAN do not build g77 and related libraries.
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
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
# -DNO_DOCUPDATE do not update doc in ${MAKE} 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
# LOCAL_DIRS="list of dirs" to add additional dirs to the SUBDIR list
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
# TARGET_ARCH="arch" to crossbuild world to a different 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
#
# The intended user-driven targets are:
# buildworld - rebuild *everything*, including glue to help do upgrades
# installworld- install everything built by "buildworld"
# update - convenient way to update your source tree (eg: sup/cvs)
#
# Standard targets (not defined here) are documented in the makefiles in
# /usr/share/mk. These include:
# obj depend all install clean cleandepend cleanobj
# We must do share/info early so that installation of info `dir'
# entries works correctly. Do it first since it is less likely to
# grow dependencies on include and lib than vice versa.
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
#
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
# We must do lib and libexec before bin, because if installworld
# 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
#
# We must do etc last for install/distribute to work.
#
SUBDIR= share/info include lib libexec bin
.if !defined(NOGAMES)
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
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
SUBDIR+=gnu
.if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL)
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
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NO_RESCUE)
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
.if !defined(NOCRYPT)
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
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NOSHARE)
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
sys/boot seems to compile fine on Alpha; unbreak ``make release''. Prodded by: re-alpha (wilko)
2004-08-16 18:17:14 +00:00
SUBDIR+=sys usr.bin usr.sbin 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
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
# These 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)
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
SUBDIR+= ${_DIR}
.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
.if defined(SUBDIR_OVERRIDE)
SUBDIR= ${SUBDIR_OVERRIDE}
.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
.if defined(NOCLEANDIR)
CLEANDIR= clean cleandepend
.else
CLEANDIR= cleandir
.endif
Add the CVS knob so it may be overridden (or have options added). Submitted by: Andrea Campi <andrea@webcom.it>
2001-11-19 17:43:29 +00:00
CVS?= cvs
Show stray files during "cvs update".
2004-11-12 13:22:22 +00:00
CVSFLAGS?= -A -P -d -I!
Set full-path of cvsup. In src/Makefile rev 1.232, environment variable PATH is set explicitly to /sbin:/bin:/usr/sbin:/usr/bin. As a result, binaries located on non-standard path cannot be executed without full-path (it's the change of this revision). However, cvsup is not in our base system -- you lose if you try to "make update" without setting SUP in make.conf or command line argument. I think it is safe to assume that cvsup is located at /usr/local/bin, and it would help other people who first try to do "make update". PR: 31932 MFC after: 1 day
2001-11-13 15:47:40 +00:00
SUP?= /usr/local/bin/cvsup
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
SUPFLAGS?= -g -L 2 -P -
Define SUPHOST. If this is set a '-h ${SUPHOST}' is added to the SUPFLAGS when a 'make update' is run. This means that the supfile doesn't need to be edited because the -h will override the CHANGE_THIS.FreeBSD.org host.
2000-08-13 12:36:40 +00:00
.if defined(SUPHOST)
SUPFLAGS+= -h ${SUPHOST}
.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
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
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
TARGET_ARCH?= ${MACHINE_ARCH}
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
.if ${TARGET_ARCH} == ${MACHINE_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
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
TARGET?= ${TARGET_ARCH}
- 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
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
Allow buildworld and friends to complete when make(1) is called with some debug flags (-d). Noticed by: Gleb Smirnoff
2004-05-17 16:19:51 +00:00
_CPUTYPE!= MAKEFLAGS= ${MAKE} -f /dev/null -m ${.CURDIR}/share/mk \
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
CPUTYPE=${_TARGET_CPUTYPE} -V CPUTYPE
.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)
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
BUILD_ARCH!= sysctl -n hw.machine_arch
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
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
.if ${MACHINE} == ${TARGET}
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
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
OBJTREE= ${MAKEOBJDIRPREFIX}/${TARGET}
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
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
WORLDTMP= ${OBJTREE}${.CURDIR}/${MACHINE_ARCH}
Don't build caesar as a tool. fortune(6) doesn't depend on it anymore. Update comments and variable names as well to wipe out any traces that may confuse people in the future.
1999-12-23 19:18:28 +00:00
# /usr/games added for fortune which depend on strfile
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
BPATH= ${WORLDTMP}/legacy/usr/sbin:${WORLDTMP}/legacy/usr/bin:${WORLDTMP}/legacy/usr/games
XPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
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
Specify the full path to mktemp
2001-12-23 22:49:06 +00:00
INSTALLTMP!= /usr/bin/mktemp -d -u -t install
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,
# build-tools and cross-tools stages.
# 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
# are needed for cross-builds. A cross-compiler is one
# 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} \
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
CPUTYPE=${TARGET_CPUTYPE} \
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
GROFF_BIN_PATH=${WORLDTMP}/legacy/usr/bin \
GROFF_FONT_PATH=${WORLDTMP}/legacy/usr/share/groff_font \
GROFF_TMAC_PATH=${WORLDTMP}/legacy/usr/share/tmac
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} \
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} \
${BMAKEENV} ${MAKE} -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} \
Restore the ordering of NO's and remove one redundant NOLINT. Reviewed by: markm
2003-04-30 12:38:20 +00:00
-DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE \
-DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS
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} \
${BMAKEENV} ${MAKE} -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= \
Restore the ordering of NO's and remove one redundant NOLINT. Reviewed by: markm
2003-04-30 12:38:20 +00:00
BOOTSTRAPPING=${OSRELDATE} -DNOLINT -DNO_CPU_CFLAGS -DNO_WARNS
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
Restore the ordering of NO's and remove one redundant NOLINT. Reviewed by: markm
2003-04-30 12:38:20 +00:00
XMAKE= TOOLS_PREFIX=${WORLDTMP} ${BMAKE} -DNO_FORTRAN -DNO_GDB
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} \
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}
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
WMAKE= ${WMAKEENV} ${MAKE} -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
Ruslan told me I should have quoted the arch strings when comparing to MACHINE_ARCH. Belatedly get around to doing it.
2004-11-10 23:38:00 +00:00
.if ${MACHINE_ARCH} == "amd64"
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
LIB32TMP= ${OBJTREE}${.CURDIR}/lib32
LIB32PREFLAGS= -m32 -march=athlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT
LIB32POSTFLAGS= -I${LIB32TMP}/usr/include \
-L${LIB32TMP}/usr/lib32 \
-B${LIB32TMP}/usr/lib32
LIB32CC= ${LIB32PREFLAGS} \
${LIB32POSTFLAGS}
LIB32CXX= ${LIB32PREFLAGS} -I${LIB32TMP}/usr/include/c++/3.4 \
${LIB32POSTFLAGS}
LIB32OBJC= ${LIB32PREFLAGS} -I${LIB32TMP}/usr/include/objc \
${LIB32POSTFLAGS}
# Yes, the flags are redundant.
LIB32MAKEENV= MAKEOBJDIRPREFIX=${OBJTREE}/lib32 \
_SHLIBDIRPREFIX=${LIB32TMP} \
MACHINE_ARCH=i386 \
INSTALL="sh ${.CURDIR}/tools/install.sh" \
PATH=${TMPPATH} \
CC="cc ${LIB32CC}" \
CXX="c++ ${LIB32CXX}" \
OBJC="cc ${LIB32OBJC}" \
LD="ld -m elf_i386_fbsd -Y P,${LIB32TMP}/usr/lib32" \
AS="as --32" \
LIBDIR=/usr/lib32 \
SHLIBDIR=/usr/lib32
LIB32MAKE= ${LIB32MAKEENV} ${MAKE} -DNO_CPU_CFLAGS -DCOMPAT_32BIT \
-DNO_BIND -DNOMAN -DNODOC -DNOINFO -DNOHTML \
CC="cc ${LIB32CC}" \
CXX="c++ ${LIB32CXX}" \
OBJC="cc ${LIB32OBJC}" \
LD="ld -m elf_i386_fbsd -Y P,${LIB32TMP}/usr/lib32" \
AS="as --32" \
LIBDIR=/usr/lib32 \
SHLIBDIR=/usr/lib32
.endif
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
# install stage
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)
Move mtree to bootstrap-tools and add PATH=${TMPPATH} to IMAKEENV to pick it
2000-07-18 01:49:05 +00:00
IMAKEENV= ${CROSSENV} \
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
PATH=${STRICTTMPPATH}:${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
.else
IMAKEENV= ${CROSSENV} \
PATH=${TMPPATH}:${INSTALLTMP}
.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
IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1
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}
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 "--------------------------------------------------------------"
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
.if !defined(NOCLEAN)
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}
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
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
# XXX - These two can depend on any header file.
rm -f ${OBJTREE}${.CURDIR}/usr.bin/kdump/ioctl.c
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 \
Catch another gcc-3.3 c++ include path reference and update it to 3.4.
2004-10-11 23:51:13 +00:00
usr/bin usr/games usr/include/c++/3.4 usr/include/sys usr/lib \
Only create directories that are really needed.
2003-04-13 14:34:17 +00:00
usr/libexec usr/sbin usr/share/dict \
usr/share/groff_font/devX100 \
usr/share/groff_font/devX100-12 \
usr/share/groff_font/devX75 \
usr/share/groff_font/devX75-12 \
usr/share/groff_font/devascii \
usr/share/groff_font/devcp1047 \
usr/share/groff_font/devdvi \
usr/share/groff_font/devhtml \
usr/share/groff_font/devkoi8-r \
usr/share/groff_font/devlatin1 \
usr/share/groff_font/devlbp \
usr/share/groff_font/devlj4 \
usr/share/groff_font/devps \
usr/share/groff_font/devutf8 \
usr/share/tmac/mdoc usr/share/tmac/mm
mkdir -p ${WORLDTMP}/legacy/${_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
Only create directories that are really needed.
2003-04-13 14:34:17 +00:00
.for _dir in \
In preparation for libraries being installed in /lib, add lib to the list of build directories during the tool creation phase of the build.
2003-08-17 07:50:15 +00:00
lib usr/bin usr/include usr/lib/compat/aout usr/libdata/ldscripts \
Create /usr/sbin in ${WORLDTMP}. I've accidentally removed it in revision 1.343, but it's needed for btxld(8), and this fix (along with the --enable-64-bit-bfd configured BFD on i386) allows other architectures to successfully cross-build the i386 world. Tested on: alpha
2004-03-19 15:08:58 +00:00
usr/libexec usr/sbin usr/share/misc \
Move the SNMP MIBs and tree definitions from /usr/share/bsnmp to /usr/share/snmp. This mirrors the use of /usr/local/share/snmp and makes also more sense when non-bsnmp-specific MIBs go in.
2004-04-14 16:06:19 +00:00
usr/share/snmp/defs usr/share/snmp/mibs
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
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}
1. Add much finer granularity to the NO_BIND knobs with the addition of: NO_BIND_DNSSEC, NO_BIND_ETC, NO_BIND_NAMED, and NO_BIND_UTILS. 2. Make creation of directories in /usr/include that are only needed in the WITH_BIND_LIBS case conditional. Reviewed by: ru, des
2004-09-27 08:23:43 +00:00
.if defined(WITH_BIND_LIBS) && !defined(NO_BIND)
mtree -deU -f ${.CURDIR}/etc/mtree/BIND.include.dist \
-p ${WORLDTMP}/usr/include >/dev/null
.endif
-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:
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
.if !defined(NOCLEAN)
@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-/}
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
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 "--------------------------------------------------------------"
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} 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}; \
Alongside revision 1.382, don't build profiled libraries so early in the build -- it's OK to keep this for the "make all" phase.
2004-01-15 09:50:54 +00:00
${WMAKE} -DNOFSCHG -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPROFILE \
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
Ruslan told me I should have quoted the arch strings when comparing to MACHINE_ARCH. Belatedly get around to doing it.
2004-11-10 23:38:00 +00:00
.if ${MACHINE_ARCH} == "amd64"
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 "--------------------------------------------------------------"
.for _dir in \
lib lib32 usr/bin usr/include usr/lib32 usr/libdata/ldscripts \
usr/libexec usr/sbin usr/share/misc \
usr/share/snmp/defs usr/share/snmp/mibs
mkdir -p ${LIB32TMP}/${_dir}
.endfor
mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \
-p ${LIB32TMP}/usr/include >/dev/null
ln -sf ${.CURDIR}/sys ${WORLDTMP}
In the amd64 hybrid libraries case, move the kerberos5 tools to before building the kerberos5 includes. This is not the same patch that Bjoern A. Zeeb came up with, but the credit still goes to him for finding the problem. Thanks!
2004-11-20 23:41:25 +00:00
.if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL)
.for _t in obj depend all
cd ${.CURDIR}/kerberos5/tools; \
MAKEOBJDIRPREFIX=${OBJTREE}/lib32 ${MAKE} ${_t}
.endfor
.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
.for _t in obj includes
cd ${.CURDIR}/include; \
${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
cd ${.CURDIR}/lib; \
${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
cd ${.CURDIR}/gnu/lib; \
${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
.if !defined(NOCRYPT)
cd ${.CURDIR}/secure/lib; \
${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
.endif
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
.if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL)
cd ${.CURDIR}/kerberos5/lib; \
${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
.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
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
.for _dir in usr.sbin/pcvt/keycap usr.bin/lex/lib
cd ${.CURDIR}/${_dir}; \
${LIB32MAKE} DESTDIR=${LIB32TMP} obj
.endfor
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 _dir in lib/libncurses lib/libmagic
cd ${.CURDIR}/${_dir}; \
MAKEOBJDIRPREFIX=${OBJTREE}/lib32 ${MAKE} build-tools
.endfor
cd ${.CURDIR}; \
${LIB32MAKE} -f Makefile.inc1 DESTDIR=${LIB32TMP} libraries
.for _t in obj depend all
cd ${.CURDIR}/libexec/rtld-elf; \
PROG=ld-elf32.so.1 ${LIB32MAKE} DESTDIR=${LIB32TMP} ${_t}
.endfor
install32:
mkdir -p ${DESTDIR}/usr/lib32 # XXX add to mtree
cd ${.CURDIR}/lib; ${LIB32MAKE} install
cd ${.CURDIR}/gnu/lib; ${LIB32MAKE} install
.if !defined(NOCRYPT)
cd ${.CURDIR}/secure/lib; ${LIB32MAKE} install
.endif
cd ${.CURDIR}/libexec/rtld-elf; PROG=ld-elf32.so.1 ${LIB32MAKE} install
.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
Ruslan told me I should have quoted the arch strings when comparing to MACHINE_ARCH. Belatedly get around to doing it.
2004-11-10 23:38:00 +00:00
.if ${MACHINE_ARCH} == "amd64" && defined(WITH_LIB32)
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
buildworld: ${WMAKE_TGTS}
.ORDER: ${WMAKE_TGTS}
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
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_TGTS= ${WMAKE_TGTS:N_depend:Neverything}
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
#
# Use this to add checks to installworld/installkernel targets.
#
SPECIAL_INSTALLCHECKS=
#
# The following install-time check will see if the installation will
# change the type used for time_t, and if it will, the target makes
# sure that the user is expecting to make that change.
#
.if ${TARGET_ARCH} == "sparc64"
SPECIAL_INSTALLCHECKS+=sparc64_installcheck
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
CUR_TIMET!= grep __time_t /usr/include/machine/_types.h | awk '{print $$2}'
SRC_TIMET!= grep __time_t ${.CURDIR}/sys/sparc64/include/_types.h | \
awk '{print $$2}'
NEWSPARC_TIMETYPE?=${CUR_TIMET}
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
sparc64_installcheck:
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
.if ${CUR_TIMET} != ${SRC_TIMET}
@echo
.if ${NEWSPARC_TIMETYPE} != ${SRC_TIMET}
@echo "*** ERROR: This target would change the type used for time_t!"
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
.else
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@echo "* Note: This installation changes the type used for time_t."
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
.endif
@echo "* "
Get rid of the THISHOST variable when building on sparc64. The problem with it is that it is set by calling hostname and hostname isn't normally in the path at that point.
2004-07-08 09:08:09 +00:00
@echo "* This host has time_t defined as ${CUR_TIMET},"
Reword two more lines to avoid wrapping.
2004-03-05 18:16:28 +00:00
@echo "* and this installation would change that to type ${SRC_TIMET}."
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
.if ${NEWSPARC_TIMETYPE} != ${SRC_TIMET}
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
@echo "* "
@echo "* If that is *NOT* what you wanted, then you need to change the"
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@echo "* typedef of __time_t in ${.CURDIR}/sys/sparc64/include/_types.h"
@echo "* from '${SRC_TIMET}' to '${CUR_TIMET}'. After that you *MUST*"
@echo "* do a complete cleanworld, buildworld, buildkernel before you"
@echo "* retry the 'make' command. Also read /usr/src/UPDATING.64BTT."
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
@echo "* "
@echo "* If that *is* what you want, then enter the commands:"
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@echo " NEWSPARC_TIMETYPE=${SRC_TIMET}"
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
@echo " export NEWSPARC_TIMETYPE"
@echo "* and repeat your 'make' command."
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@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
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
.endif
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@echo
.elif ${NEWSPARC_TIMETYPE} != ${SRC_TIMET}
@echo
@echo "*** ERROR: NEWSPARC_TIMETYPE is set to '${NEWSPARC_TIMETYPE}'"
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
@echo "*** but ${.CURDIR}/sys/sparc64/include/_types.h"
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@echo "*** has __time_t defined as '${SRC_TIMET}'."
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
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
.else
Minor stylistic improvements in the SPECIAL_INSTALLCHECKS section, mainly to reduce the number of wrapped lines. Suggested by: bde
2004-03-04 18:41:35 +00:00
@# in sparc64_installcheck, all TIMETYPEs == '${CUR_TIMET}'
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
.endif
.endif
Despite the fact that it is documented in the handbook, the release notes, and UPDATING and has been posted to both freebsd-current and freebsd-stable, users are still not adding the required smmsp user and group before doing an installworld. Therefore, don't let users do an installworld unless they have followed directions. Add a new installcheck Makefile target which installworld runs before actually starting the installation. This target can be used by other parts of userland as well. The first addition to the target is to check for the smmsp user and group if NO_SENDMAIL isn't defined. Others may add checks to this target as they see fit. MFC after: 1 week
2002-04-20 19:04:59 +00:00
#
# installcheck
#
# Checks to be sure system is ready for installworld
#
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
CHECK_UIDS=
CHECK_GIDS=
Despite the fact that it is documented in the handbook, the release notes, and UPDATING and has been posted to both freebsd-current and freebsd-stable, users are still not adding the required smmsp user and group before doing an installworld. Therefore, don't let users do an installworld unless they have followed directions. Add a new installcheck Makefile target which installworld runs before actually starting the installation. This target can be used by other parts of userland as well. The first addition to the target is to check for the smmsp user and group if NO_SENDMAIL isn't defined. Others may add checks to this target as they see fit. MFC after: 1 week
2002-04-20 19:04:59 +00:00
.if !defined(NO_SENDMAIL)
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
CHECK_UIDS+= smmsp
CHECK_GIDS+= smmsp
Despite the fact that it is documented in the handbook, the release notes, and UPDATING and has been posted to both freebsd-current and freebsd-stable, users are still not adding the required smmsp user and group before doing an installworld. Therefore, don't let users do an installworld unless they have followed directions. Add a new installcheck Makefile target which installworld runs before actually starting the installation. This target can be used by other parts of userland as well. The first addition to the target is to check for the smmsp user and group if NO_SENDMAIL isn't defined. Others may add checks to this target as they see fit. MFC after: 1 week
2002-04-20 19:04:59 +00:00
.endif
Add installcheck for proxy:proxy and authpf. Suggested by: ru Approved by: bms(mentor)
2004-03-10 16:34:11 +00:00
.if !defined(NO_PF)
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
CHECK_UIDS+= proxy
CHECK_GIDS+= proxy authpf
.endif
installcheck: ${SPECIAL_INSTALLCHECKS}
.for uid in ${CHECK_UIDS}
Hide internal implementation details of UID/GID checks from the user.
2004-03-12 13:24:17 +00:00
@if ! `id -u ${uid} >/dev/null 2>&1`; then \
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
echo "ERROR: Required ${uid} user is missing, see /usr/src/UPDATING."; \
Add installcheck for proxy:proxy and authpf. Suggested by: ru Approved by: bms(mentor)
2004-03-10 16:34:11 +00:00
false; \
fi
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
.endfor
.for gid in ${CHECK_GIDS}
Hide internal implementation details of UID/GID checks from the user.
2004-03-12 13:24:17 +00:00
@if ! `find / -prune -group ${gid} >/dev/null 2>&1`; then \
Use find(1) instead of ``pw groupshow'' to detect missing groups. Restore checks for recently added PF groups. Reviewed by: mlaier
2004-03-12 13:20:24 +00:00
echo "ERROR: Required ${gid} group is missing, see /usr/src/UPDATING."; \
false; \
fi
.endfor
Despite the fact that it is documented in the handbook, the release notes, and UPDATING and has been posted to both freebsd-current and freebsd-stable, users are still not adding the required smmsp user and group before doing an installworld. Therefore, don't let users do an installworld unless they have followed directions. Add a new installcheck Makefile target which installworld runs before actually starting the installation. This target can be used by other parts of userland as well. The first addition to the target is to check for the smmsp user and group if NO_SENDMAIL isn't defined. Others may add checks to this target as they see fit. MFC after: 1 week
2002-04-20 19:04:59 +00:00
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'.
#
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
distributeworld installworld: installcheck
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}
Doh, committed to the wrong branch. Spotted by: johan
2003-03-04 17:24:18 +00:00
for prog in [ awk cap_mkdb cat chflags chmod chown \
date echo egrep find grep \
Bootstrap makewhatis(1).
2002-05-27 15:51:38 +00:00
ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
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
test true uname wc zic; do \
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
cp `which $$prog` ${INSTALLTMP}; \
done
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}; ${IMAKE} re${.TARGET:S/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
rm -rf ${INSTALLTMP}
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.
#
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
reinstall: ${SPECIAL_INSTALLCHECKS}
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 "--------------------------------------------------------------"
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 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
Ruslan told me I should have quoted the arch strings when comparing to MACHINE_ARCH. Belatedly get around to doing it.
2004-11-10 23:38:00 +00:00
.if ${MACHINE_ARCH} == "amd64" && defined(WITH_LIB32)
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
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
redistribute:
@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
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
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.
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
.if !defined(KERNCONF) && defined(KERNEL)
KERNCONF= ${KERNEL}
For variables that are only checked with defined(), don't provide any fake value.
2004-10-24 15:33:08 +00:00
KERNWARN=
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
.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
#
# 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)
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
@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
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
.if defined(KERNWARN)
@echo "--------------------------------------------------------------"
@echo ">>> WARNING: KERNEL= setting should be changed to KERNCONF="
@echo "--------------------------------------------------------------"
@sleep 3
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} \
${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
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
.if !defined(NOCLEAN) && !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 "--------------------------------------------------------------"
Run "make cleandir" if NO_MODULES are set, or there is no sys/modules directory. Previous commit breaks buildkernel if NO_MODULES was set. Sorry... Noticed by: mike
2001-11-15 07:04:23 +00:00
cd ${KRNLOBJDIR}/${_kernel}; \
Catch up with sys/conf/kern.post.mk,v 1.39 -- we can now use plain ${CLEANDIR} to clean kernel and modules. This has an additional nicety of respecting NOCLEANDIR.
2003-03-03 08:50:32 +00:00
${KMAKEENV} ${MAKE} KERNEL=${INSTKERNNAME} ${CLEANDIR}
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 "--------------------------------------------------------------"
@echo ">>> stage 2.2: rebuilding the object tree"
@echo "--------------------------------------------------------------"
cd ${KRNLOBJDIR}/${_kernel}; \
${KMAKEENV} ${MAKE} KERNEL=${INSTKERNNAME} obj
@echo
@echo "--------------------------------------------------------------"
@echo ">>> stage 2.3: build tools"
@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 ${KRNLOBJDIR}/${_kernel}; \
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
MAKESRCPATH=${KERNSRCDIR}/dev/aic7xxx/aicasm \
${MAKE} -DNO_CPU_CFLAGS -f ${KERNSRCDIR}/dev/aic7xxx/aicasm/Makefile
Respect ``makeoptions NO_MODULES'' specified in the kernel config file.
2003-02-21 11:19:25 +00:00
# XXX - Gratuitously builds aicasm in the ``makeoptions NO_MODULES'' case.
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
.if !defined(MODULES_WITH_WORLD) && !defined(NO_MODULES) && exists(${KERNSRCDIR}/modules)
Respect ``makeoptions NO_MODULES'' specified in the kernel config file.
2003-02-21 11:19:25 +00:00
.for target in obj depend all
Hopefully fix the "aicasm" build-tool issue when using ${KERNSRCDIR} different from ${.CURDIR}. Reported by: jhb
2004-11-23 09:09:47 +00:00
cd ${KERNSRCDIR}/modules/aic7xxx/aicasm; \
Hook the aic7xxx modules up. This requires some extra care since aicasm is a compiler tool and needs to be compiled by the host compiler. I've tested this in i386->sparc cross-build, 4.7->current upgrade, normal buildkernel target, and normal /sys/i386/compile/GENERIC configurations. Submitted by: ru
2002-11-03 23:48:14 +00:00
MAKEOBJDIRPREFIX=${KRNLOBJDIR}/${_kernel}/modules \
Respect ``makeoptions NO_MODULES'' specified in the kernel config file.
2003-02-21 11:19:25 +00:00
${MAKE} -DNO_CPU_CFLAGS ${target}
.endfor
Hook the aic7xxx modules up. This requires some extra care since aicasm is a compiler tool and needs to be compiled by the host compiler. I've tested this in i386->sparc cross-build, 4.7->current upgrade, normal buildkernel target, and normal /sys/i386/compile/GENERIC configurations. Submitted by: ru
2002-11-03 23:48:14 +00:00
.endif
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 "--------------------------------------------------------------"
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
cd ${KRNLOBJDIR}/${_kernel}; \
Hook the aic7xxx modules up. This requires some extra care since aicasm is a compiler tool and needs to be compiled by the host compiler. I've tested this in i386->sparc cross-build, 4.7->current upgrade, normal buildkernel target, and normal /sys/i386/compile/GENERIC configurations. Submitted by: ru
2002-11-03 23:48:14 +00:00
${KMAKEENV} ${MAKE} KERNEL=${INSTKERNNAME} 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 "--------------------------------------------------------------"
@echo ">>> stage 3.2: building everything"
@echo "--------------------------------------------------------------"
Add -DNO_KERNELDEPEND and -DNO_KERNELCONFIG Not reviewed by: sheldonh
2000-06-15 10:00:20 +00:00
cd ${KRNLOBJDIR}/${_kernel}; \
Hook the aic7xxx modules up. This requires some extra care since aicasm is a compiler tool and needs to be compiled by the host compiler. I've tested this in i386->sparc cross-build, 4.7->current upgrade, normal buildkernel target, and normal /sys/i386/compile/GENERIC configurations. Submitted by: ru
2002-11-03 23:48:14 +00:00
${KMAKEENV} ${MAKE} KERNEL=${INSTKERNNAME} 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 \
reinstallkernel reinstallkernel.debug: ${SPECIAL_INSTALLCHECKS}
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)
@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 "--------------------------------------------------------------"
@echo ">>> Making hierarchy"
@echo "--------------------------------------------------------------"
cd ${.CURDIR}; \
${CROSSENV} PATH=${TMPPATH} ${MAKE} -f Makefile.inc1 hierarchy
@echo
@echo "--------------------------------------------------------------"
@echo ">>> Installing kernel"
@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} \
Allow installkernel.debug and reinstallkernel.debug.
2003-06-22 10:01:03 +00:00
${MAKE} 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
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 the source tree, by running sup and/or running cvs to update to the
# latest copy.
#
update:
.if defined(SUP_UPDATE)
@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 ">>> Running ${SUP}"
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 "--------------------------------------------------------------"
It is possible for someone to want to 'make update' wht SUPFILE not defined while SUPFILE1 or PORTSSUPFILE are defined.
1999-12-16 01:21:48 +00:00
.if defined(SUPFILE)
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
@${SUP} ${SUPFLAGS} ${SUPFILE}
It is possible for someone to want to 'make update' wht SUPFILE not defined while SUPFILE1 or PORTSSUPFILE are defined.
1999-12-16 01:21:48 +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
.if defined(SUPFILE1)
@${SUP} ${SUPFLAGS} ${SUPFILE1}
.endif
.if defined(SUPFILE2)
@${SUP} ${SUPFLAGS} ${SUPFILE2}
.endif
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
.if defined(PORTSSUPFILE) && !defined(NO_PORTSUPDATE)
'make update' in the ports directory.
1999-06-01 02:55:44 +00:00
@${SUP} ${SUPFLAGS} ${PORTSSUPFILE}
.endif
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
.if defined(DOCSUPFILE) && !defined(NO_DOCUPDATE)
@${SUP} ${SUPFLAGS} ${DOCSUPFILE}
.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
.endif
.if defined(CVS_UPDATE)
@echo "--------------------------------------------------------------"
${.CURDIR} doesn't have to be /usr/src, especially in a cvs checkout. Make sure what is reported to the user is accurate. Stolen From: mharo
1999-06-04 17:34:28 +00:00
@echo ">>> Updating ${.CURDIR} from cvs repository" ${CVSROOT}
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 "--------------------------------------------------------------"
Add a CVSTAG makefile variable that can be set in /etc/make.conf that determines which CVS tag to track when running make update. This makes it easier to configure a box to track a particular release if it does automated updates from a cvs repository.
2004-08-24 23:12:16 +00:00
cd ${.CURDIR}; ${CVS} -R -q update ${CVSFLAGS}
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.
#
#
-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: Build compatibility shims for the next three targets
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:
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)"; \
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
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
libc_gen/basename.c depends on include/libgen.h.
2003-04-11 17:58:17 +00:00
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX}/legacy includes; \
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
${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
#
# bootstrap-tools: Build tools needed for compatibility
#
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NOGAMES)
Moved libbuild target to where it belongs. Added a comment.
2003-04-06 21:33:49 +00:00
_strfile= games/fortune/strfile
.endif
Wrap gperf & groff wth NO_CXX.
2003-05-31 21:29:38 +00:00
.if !defined(NO_CXX)
_gperf= gnu/usr.bin/gperf
For the time being, upgrade the whole Groff (to version 1.19), but stop doing so again on the next __FreeBSD_version bump.
2003-05-01 20:41:03 +00:00
.if ${BOOTSTRAPPING} < 500113
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
_groff= gnu/usr.bin/groff
.else
_groff= gnu/usr.bin/groff/tmac
.endif
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
lex(1) prior to flex.skl,v 1.8 and gen.c,v 1.7 requires bootstrapping. Prodded by: nectar
2004-01-16 16:06:54 +00:00
.if ${BOOTSTRAPPING} < 502102
_lex= usr.bin/lex
.endif
Fixed style bugs related to parentheses in Makefile.inc1. Submitted by: bde Fixed nearby bug: propagate the root Makefile's idea of the appropriate "make" binary down to release/Makefile.
2003-07-04 14:27:06 +00:00
.if ${BOOTSTRAPPING} < 450005 || \
${BOOTSTRAPPING} >= 500000 && ${BOOTSTRAPPING} < 500034
uudecode.c rev. 1.23 in HEAD and rev. 1.13.2.3 in RELENG_4, and onwards, have no known backwards compatibility issues.
2003-04-13 15:09:26 +00:00
_uudecode= usr.bin/uudecode
.endif
Fixed style bugs related to parentheses in Makefile.inc1. Submitted by: bde Fixed nearby bug: propagate the root Makefile's idea of the appropriate "make" binary down to release/Makefile.
2003-07-04 14:27:06 +00:00
.if ${BOOTSTRAPPING} < 430002 || \
${BOOTSTRAPPING} >= 500000 && ${BOOTSTRAPPING} < 500019
xargs.c rev. 1.10 in HEAD and rev. 1.9.2.1 in RELENG_4, and onwards, have support for the -J option we need.
2003-04-13 16:05:28 +00:00
_xargs= usr.bin/xargs
.endif
Fixed style bugs related to parentheses in Makefile.inc1. Submitted by: bde Fixed nearby bug: propagate the root Makefile's idea of the appropriate "make" binary down to release/Makefile.
2003-07-04 14:27:06 +00:00
.if ${BOOTSTRAPPING} < 430002 || \
${BOOTSTRAPPING} >= 500000 && ${BOOTSTRAPPING} < 500018
yacc(1) with skeleton.c rev. 1.29 in HEAD and rev. 1.28.2.1 in RELENG_4, and onwards, are believed to not require bootstrapping.
2003-04-13 16:26:31 +00:00
_yacc= usr.bin/yacc
.endif
Apparently we prefer underscores in new options. Sorry for the churn folks. Requested by: obrien
2003-07-14 16:21:16 +00:00
.if !defined(NO_RESCUE) && \
Fix recent breakage in rescue. We need to build a new crunchgen that will not emit the bad MAKE=make line that caused the breakage. Submitted by: ru
2004-08-10 13:18:05 +00:00
${BOOTSTRAPPING} < 502128
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
_crunchgen= usr.sbin/crunch/crunchgen
.endif
Ensure that a new gensnmptree is built. This should fix the problems with the snmp_atm module.
2004-08-11 16:45:20 +00:00
.if ${BOOTSTRAPPING} < 502128
Create the OID and tree files while building the modules and the daemon instead of creating them by hand and storing them in the CVS tree. Add gensnmptree to the bootstrap tools (it is used to generated these files). This simplifies the update procedure. Submitted by: ru
2004-01-23 16:22:49 +00:00
_gensnmptree= usr.sbin/bsnmpd/gensnmptree
.endif
kbdcontrol.c rev. 1.35 and onwards support the KEYMAP_PATH environment variable, and don't need to be bootstrapped.
2003-04-14 14:46:13 +00:00
.if ${BOOTSTRAPPING} < 500019
_kbdcontrol= usr.sbin/kbdcontrol
.endif
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
bootstrap-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
.for _tool in \
${_strfile} \
${_gperf} \
${_groff} \
gnu/usr.bin/texinfo \
usr.bin/colldef \
lex(1) prior to flex.skl,v 1.8 and gen.c,v 1.7 requires bootstrapping. Prodded by: nectar
2004-01-16 16:06:54 +00:00
${_lex} \
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/makewhatis \
usr.bin/rpcgen \
${_uudecode} \
${_xargs} \
usr.bin/xinstall \
${_yacc} \
usr.sbin/config \
${_crunchgen} \
Create the OID and tree files while building the modules and the daemon instead of creating them by hand and storing them in the CVS tree. Add gensnmptree to the bootstrap tools (it is used to generated these files). This simplifies the update procedure. Submitted by: ru
2004-01-23 16:22:49 +00:00
${_gensnmptree} \
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
${_kbdcontrol}
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)"; \
Similar to bsd.subdir.mk, echo the name of the dir before doing the cd. This is done for bootstrap-tools, build-tools, cross-tools, and the libraries loop. Reviewed by: ru Approved by: sheldonh (mentor) MFC after: 1 week
2002-08-23 12:49:16 +00:00
cd ${.CURDIR}/${_tool}; \
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}/ 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
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
#
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
.if defined(MODULES_WITH_WORLD) && exists(${KERNSRCDIR}/modules)
Hook the aic7xxx modules up. This requires some extra care since aicasm is a compiler tool and needs to be compiled by the host compiler. I've tested this in i386->sparc cross-build, 4.7->current upgrade, normal buildkernel target, and normal /sys/i386/compile/GENERIC configurations. Submitted by: ru
2002-11-03 23:48:14 +00:00
_aicasm= sys/modules/aic7xxx/aicasm
.endif
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NOSHARE)
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
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL)
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
_kerberos5_tools= kerberos5/tools
Grrrr... This was supoosed to go with the commit to kerberosIV/.../libroken's Makefile. Fix make world by building appropriate build-tools. Submitted by: marcel
1999-12-30 10:31:21 +00:00
.endif
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NO_RESCUE)
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
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
build-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
.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} \
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
lib/libncurses \
${_share} \
${_aicasm} \
usr.bin/awk \
The file(1) related build-tool moved to libmagic.
2004-08-09 10:51:01 +00:00
lib/libmagic \
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.sbin/sysinstall
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)"; \
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
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
${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 \
A fix from rev. 1.52 of gnu/usr.bin/cc/cc_tools/Makefile was lost in rev. 1.57. Fix this regression by making cc_tools a new-style build-tool in Makefile.inc1. For details of what has been fixed, please see the gnu/usr.bin/cc/cc_tools/Makefile,v 1.52 commit log. Caught this by accidentally touching param.h while in the process of cross-buildworld for amd64.
2004-08-18 13:21:40 +00:00
gnu/usr.bin/cc/cc_tools \
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
${_kerberos5_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)"; \
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
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
${MAKE} DIRPRFX=${_tool}/ depend; \
${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
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
#
# cross-tools: Build cross-building tools
#
elf2aout.c,v 1.6 and onwards have no known backward compatibility issues.
2003-04-13 15:43:29 +00:00
.if ${TARGET_ARCH} == "sparc64" && ${TARGET_ARCH} != ${MACHINE_ARCH} && \
${BOOTSTRAPPING} < 500037
Move elf2aout back to /usr/bin -- it is a general development tool, not a sysadmin tool.
2002-12-30 10:01:26 +00:00
_elf2aout= usr.bin/elf2aout
Bootstrap elf2aout(1) for sparc64; used to build sys/boot/sparc64/boot1.
2002-05-20 14:42:48 +00:00
.endif
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
.if ${TARGET_ARCH} == "i386" && ${TARGET_ARCH} != ${MACHINE_ARCH}
_btxld= usr.sbin/btxld
.endif
Apparently we prefer underscores in new options. Sorry for the churn folks. Requested by: obrien
2003-07-14 16:21:16 +00:00
.if (!defined(NO_RESCUE) || \
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
defined(RELEASEDIR)) && \
Revert rev. 1.378, and restore the correct arithmetic expression syntax. The make buildworld mv /usr/include /usr/include.old make installworld issue has been fixed a month ago in Makefile,v 1.285, and there is no valid reason to continue to keep the wrong syntax here -- buildworld takes care of upgrading a make for you if necessary. But if you find yourself in an environment with an old make(1) binary that breaks on this, and this is because you attempted to run a target other than buildworld, don't whine but try again with -DALWAYS_CHECK_MAKE defined -- it should do the trick. Otherwise, if you still have a problem, please report it as a bug and attach the ``make -dl ...'' output. Reviewed by: marcel
2003-08-30 13:48:16 +00:00
(${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} < 501101)
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
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
.if ${TARGET_ARCH} == "alpha" && ${TARGET_ARCH} != ${MACHINE_ARCH}
_elf2exe= usr.sbin/elf2exe
.endif
.if ${TARGET_ARCH} == "i386" && ${TARGET_ARCH} != ${MACHINE_ARCH} && \
defined(RELEASEDIR)
_kgzip= usr.sbin/kgzip
.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
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
cross-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
.for _tool in \
gnu/usr.bin/binutils \
gnu/usr.bin/cc \
${_elf2aout} \
usr.bin/xlint/lint1 usr.bin/xlint/lint2 usr.bin/xlint/xlint \
${_btxld} \
${_crunchide} \
${_elf2exe} \
${_kgzip}
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)"; \
Similar to bsd.subdir.mk, echo the name of the dir before doing the cd. This is done for bootstrap-tools, build-tools, cross-tools, and the libraries loop. Reviewed by: ru Approved by: sheldonh (mentor) MFC after: 1 week
2002-08-23 12:49:16 +00:00
cd ${.CURDIR}/${_tool}; \
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}/ obj; \
${MAKE} DIRPRFX=${_tool}/ depend; \
${MAKE} DIRPRFX=${_tool}/ all; \
${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
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
#
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:
cd ${.CURDIR}/etc; ${MAKE} 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
#
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
libraries:
cd ${.CURDIR}; \
${MAKE} -f Makefile.inc1 _startup_libs; \
${MAKE} -f Makefile.inc1 _prebuild_libs; \
${MAKE} -f Makefile.inc1 _generic_libs;
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:
#
Quiet the peanut gallary and back out magical "breakage".
2002-05-12 13:37:59 +00:00
# gnu/lib/csu, gnu/lib/libgcc and lib/csu must be built before all
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
# shared libraries for ELF.
#
Quiet the peanut gallary and back out magical "breakage".
2002-05-12 13:37:59 +00:00
_startup_libs= gnu/lib/csu gnu/lib/libgcc
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
.if exists(${.CURDIR}/lib/csu/${MACHINE_ARCH}-elf)
_startup_libs+= lib/csu/${MACHINE_ARCH}-elf
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
.else
Quiet the peanut gallary and back out magical "breakage".
2002-05-12 13:37:59 +00:00
_startup_libs+= lib/csu/${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
.endif
Minor tweaks to the build process so that we can build 5.1-current on 4.8-stable: Must build lib/libc before libpthread. Fix how we do this to be more consistant with how lists are handled in the file. Also, don't bother to prebuild libc if we're not building libpthread. Submitted by: ru@ Reviewed by: bde@ (before ru@ submitted it)
2003-06-14 17:50:13 +00:00
_prebuild_libs=
Catch up with libpthread/support/Makefile.inc,v 1.6 and revert Makefile.inc1 revisions 1.365 and 1.367: libc_pic.a is no longer necessary to build libpthread.so (ie: libkse.so).
2003-09-15 21:18:30 +00:00
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
_generic_libs= gnu/lib
Make sure libskey is built before libpam. It is required for one of the PAM modules. Fix the comments describing the PAM dependencies to be consistent with other related comments.
1998-11-20 02:03:52 +00:00
Drop directory existence checks. OK'ed by: bde
2004-02-13 21:52:08 +00:00
.if !defined(NO_KERBEROS) && !defined(NOCRYPT) && !defined(NO_OPENSSL)
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
_prebuild_libs+= kerberos5/lib/libasn1
_prebuild_libs+= kerberos5/lib/libgssapi
_prebuild_libs+= kerberos5/lib/libkrb5
_prebuild_libs+= kerberos5/lib/libroken
_generic_libs+= kerberos5/lib
.endif
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +00:00
-lbsdxml lives in lib/libexpat. *Blush* Submitted by: tmm (Makefile.inc1)
2003-05-18 00:40:22 +00:00
_prebuild_libs+= lib/libcom_err lib/libcrypt lib/libexpat \
Unbreak world: record libgeom dependency on libbsdxml here too. Forgotten by: ru Submitted by: des Verified by: tools/make_libdeps.sh Approved by: re (scottl) (related change)
2003-05-17 23:07:09 +00:00
lib/libkvm lib/libmd \
The snmp_netgraph module depends on libnetgraph. So add a dependency and add libnetgraph to the list of prebuilt libraries in the main Makefile. Reviewed by: ru
2003-11-12 17:09:13 +00:00
lib/libncurses lib/libnetgraph lib/libopie lib/libpam \
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
lib/libradius \
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
lib/libsbuf lib/libtacplus lib/libutil \
libufs does not need built before most things, after all. Submitted by: bde, ru
2002-07-01 17:51:43 +00:00
lib/libz lib/msun
- 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
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
Switch from BIND 8 to BIND 9. Submitted by: (in part) dougb@, trhodes@ Reviewed by: dougb@, trhodes@, re@ MFC after: 5 days
2004-09-21 19:01:48 +00:00
.if !defined(NO_BIND)
Hopefully fix alpha and sparc64 builds: on these architectures, libpthread is provided by src/lib/libc_r. Also, removed lib/bind from _generic_libs, "lib" will suffice. Also, removed redundant lib/bind dependency on lib/libpthread (as lib/bind is not in the _prebuild_libs, it's not needed). Prodded by: trhodes@ reporting that des@ is on the flight
2004-09-21 21:47:05 +00:00
.if ${MACHINE_ARCH} == "alpha" || ${MACHINE_ARCH} == "sparc64"
_prebuild_libs+= lib/libc_r
.else
Switch from BIND 8 to BIND 9. Submitted by: (in part) dougb@, trhodes@ Reviewed by: dougb@, trhodes@, re@ MFC after: 5 days
2004-09-21 19:01:48 +00:00
_prebuild_libs+= lib/libpthread
Hopefully fix alpha and sparc64 builds: on these architectures, libpthread is provided by src/lib/libc_r. Also, removed lib/bind from _generic_libs, "lib" will suffice. Also, removed redundant lib/bind dependency on lib/libpthread (as lib/bind is not in the _prebuild_libs, it's not needed). Prodded by: trhodes@ reporting that des@ is on the flight
2004-09-21 21:47:05 +00:00
.endif
Switch from BIND 8 to BIND 9. Submitted by: (in part) dougb@, trhodes@ Reviewed by: dougb@, trhodes@, re@ MFC after: 5 days
2004-09-21 19:01:48 +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
_generic_libs+= lib
Retire the useless NOSECURE knob. Approved by: re (scottl)
2003-05-19 15:52:01 +00:00
.if !defined(NOCRYPT)
libfetch now depends on libcrypto and libssl.
2002-06-06 13:45:46 +00:00
.if !defined(NO_OPENSSL)
_prebuild_libs+= secure/lib/libcrypto secure/lib/libssl
- 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
lib/libradius__L: secure/lib/libssl__L
Record the libssl.so dependency on libcrypto.so. This should help some ports that depend on libradius that recently gained the dependency on libssl. This is also how the stock OpenSSL build would link libssl.so on FreeBSD. Prompted by: kris OK'ed by: markm, nectar
2004-05-13 07:51:47 +00:00
secure/lib/libssl__L: secure/lib/libcrypto__L
Make NO_OPENSSL actually imply NO_OPENSSH, as documented in make.conf(5).
2002-06-21 08:54:03 +00:00
.if !defined(NO_OPENSSH)
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
_prebuild_libs+= secure/lib/libssh
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
secure/lib/libssh__L: lib/libz__L secure/lib/libcrypto__L lib/libcrypt__L
.if !defined(NO_KERBEROS)
secure/lib/libssh__L: kerberos5/lib/libgssapi__L kerberos5/lib/libkrb5__L \
kerberos5/lib/libasn1__L lib/libcom_err__L lib/libmd__L \
kerberos5/lib/libroken__L
.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
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
_generic_libs+= 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
- 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
.if defined(NOCRYPT) || defined(NO_OPENSSL)
lib/libradius__L: lib/libmd__L
.endif
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
.if !defined(NO_NIS)
_prebuild_libs+= lib/libypclnt
.endif
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
_generic_libs+= usr.bin/lex/lib
Sort _startup_libs, _prebuild_libs, and _generic_libs lists alphabetically. Submitted by: bde, ru
2002-04-16 14:38:15 +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
.if ${MACHINE_ARCH} == "i386"
_generic_libs+= usr.sbin/pcvt/keycap
Fix cross-building. o Move building libperl and miniperl from build-tools to cross-tools. libperl uses MACHINE_ARCH to determine the right configuration, which doesn't match the build machine when cross-building if they are built as build- tools. o Since miniperl needs to be built as a cross-tool, it needs to be installed under /usr/obj so that it can be used (cross-tools have a special object directory to avoid build conflicts. As a downside, you can't easily run cross-tools from their object directory). Remove the install and distribute override targets. To avoid having miniperl installed by installworld, remove it from SUBDIR. o We can't pickup miniperl from the object directory but since it's installed, depend on PATH. This is save, because the makefiles are run with a known path. o Build libperl again as part of the library target. A _libperl variable existed, but it was never defined. o Add chmod to the list of saved tools, because perl conditionally uses it during install. The bootstrap-tools and cross-tools targets are modified to avoid building profiled and shared libraries. While here, have these targets build static binaries instead of shared binaries. Approved by: markm
2000-11-20 02:17:34 +00:00
.endif
Make dynamic PAM modules depend on dynamic PAM library. Requested by: des, markm
2002-11-14 19:24:51 +00:00
.for _lib in ${_startup_libs} ${_prebuild_libs:Nlib/libpam} ${_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
${_lib}__L: .PHONY
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})
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} "===> ${_lib} (depend,all,install)"; \
Similar to bsd.subdir.mk, echo the name of the dir before doing the cd. This is done for bootstrap-tools, build-tools, cross-tools, and the libraries loop. Reviewed by: ru Approved by: sheldonh (mentor) MFC after: 1 week
2002-08-23 12:49:16 +00:00
cd ${.CURDIR}/${_lib}; \
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=${_lib}/ depend; \
${MAKE} DIRPRFX=${_lib}/ all; \
${MAKE} 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
Make dynamic PAM modules depend on dynamic PAM library. Requested by: des, markm
2002-11-14 19:24:51 +00:00
# libpam is special: we need to build static PAM modules before
# static PAM library, and dynamic PAM library before dynamic PAM
# modules.
lib/libpam__L: .PHONY
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} "===> lib/libpam (depend,all,install)"; \
Make dynamic PAM modules depend on dynamic PAM library. Requested by: des, markm
2002-11-14 19:24:51 +00:00
cd ${.CURDIR}/lib/libpam; \
${MAKE} DIRPRFX=lib/libpam/ depend; \
${MAKE} DIRPRFX=lib/libpam/ -D_NO_LIBPAM_SO_YET all; \
${MAKE} DIRPRFX=lib/libpam/ -D_NO_LIBPAM_SO_YET install
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}
${entry}.${__target}__D: .PHONY
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 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>
Reference in New Issue Copy Permalink