UPDATING revision 1.303
11.303Smrg$NetBSD: UPDATING,v 1.303 2019/10/01 09:36:56 mrg Exp $
21.1Sabs
31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent
41.123Sjmcchanges that might cause problems in the build process, and a guide for
51.123Sjmcwhat to do if something doesn't work.
61.1Sabs
71.123SjmcFor a more detailed description of the recommended way to build NetBSD
81.123Sjmcusing build.sh, see the BUILDING file.
91.123Sjmc
101.123SjmcNote that much of the advice in this UPDATING file was written before
111.123Sjmcbuild.sh existed.  Nevertheless, the advice here may be useful for
121.123Sjmcworking around specific problems with build.sh.
131.123Sjmc
141.257SapbSections are marked with "^^^^^".  After the section on "Recent changes"
151.257Sapbare several sections containing more general information.
161.257Sapb
171.123SjmcSee also: BUILDING, build.sh, Makefile.
181.1Sabs
191.1SabsRecent changes:
201.1Sabs^^^^^^^^^^^^^^^
211.230Stls
221.303Smrg20191001:
231.303Smrg
241.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
251.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
261.303Smrg	directory, and also clean src/external/gpl3/gcc.
271.303Smrg
281.302Sriastrad20190903:
291.302Sriastrad
301.302Sriastrad	File with names that coincide with existing files' names on
311.302Sriastrad	case-insensitive file systems were inadvertently committed, for
321.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
331.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
341.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
351.302Sriastrad	manually delete the following files in your DESTDIR (which is
361.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
371.302Sriastrad	them:
381.302Sriastrad
391.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
401.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
411.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
421.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
431.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
441.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
451.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
461.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
471.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
481.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
491.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
501.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
511.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
521.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
531.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
541.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
551.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
561.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
571.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
581.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
591.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
601.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
611.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
621.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
631.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
641.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
651.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
661.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
671.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
681.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
691.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
701.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
711.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
721.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
731.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
741.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
751.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
761.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
771.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
781.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
791.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
801.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
811.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
821.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
831.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
841.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
851.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
861.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
871.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
881.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
891.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
901.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
911.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
921.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
931.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
941.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
951.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
961.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
971.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
981.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
991.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
1001.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
1011.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
1021.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
1031.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
1041.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
1051.302Sriastrad
1061.302Sriastrad	We will re-import these radeon firmware images another way
1071.302Sriastrad	later.
1081.302Sriastrad
1091.301Smartin20190727:
1101.301Smartin	The uefi bootloader has gained tftp support and needs a clean
1111.301Smartin	build. If you do update builds, manually clean its object
1121.301Smartin	directory by something like:
1131.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
1141.301Smartin
1151.300Smartin20190723:
1161.300Smartin	The jemalloc allocator in libc is now build without extended
1171.300Smartin	debugging (for performance reasons). In update builds make sure
1181.300Smartin	to rebuild it completly, by removing all affected object files,
1191.300Smartin	including compat builds, something like:
1201.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
1211.300Smartin
1221.299Smrg20190207:
1231.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
1241.299Smrg
1251.298Smartin20180924:
1261.298Smartin	A newer OpenSSL version has been imported. If you are doing
1271.298Smartin	update builds, make sure to remove all old obj dirs, like:
1281.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
1291.298Smartin
1301.297Sjoerg20180717:
1311.297Sjoerg	On aarch64 int64_t and related types have changed from long long
1321.297Sjoerg	to long. This requires recompiling all C++ binaries.
1331.297Sjoerg
1341.296Smartin20180713:
1351.296Smartin	On amd64 and i386 static binaries are now build position
1361.296Smartin	independend. This requires recompilation of all object
1371.296Smartin	files used to create the crunched /rescue binary.
1381.296Smartin	Clean the rescue directory in your obj directory before
1391.296Smartin	doing an update build, otherwise linking will fail.
1401.296Smartin
1411.293Sjakllsch20180414:
1421.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
1431.293Sjakllsch	removal of tools/binutils objects directory may be required
1441.293Sjakllsch	to fix tools build failure.
1451.293Sjakllsch
1461.292Smrg20180311:
1471.292Smrg	bdftopcf was updated and may need cleaning in the
1481.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
1491.292Smrg	link errors.
1501.292Smrg
1511.291Smrg20180212:
1521.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
1531.291Smrg	any failure that looks like GCC or openssl is best handled by
1541.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
1551.291Smrg	is recommended if build failures occur.
1561.291Smrg
1571.288Smartin20171225:
1581.288Smartin	removal of the vadvise syscall requires manual removal of all
1591.288Smartin	associated files from the libc build object directory (including
1601.289Schristos	the .depend files) - a command like:
1611.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
1621.289Schristos	For architectures that support multiple "compat" binary targets,
1631.289Schristos	you'll need to cleanup both the regular libc directory and the
1641.290Smartin	compat ones (the above command will do that).
1651.288Smartin
1661.287Skre20171010:
1671.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
1681.287Skre	means that its objdir (or *.d and .depend at least) might need
1691.287Skre	to be manually removed - or a build done once without -u.
1701.287Skre
1711.286Smrg20170822:
1721.286Smrg	a new version of GMP has been imported and probably
1731.286Smrg	will break parts of builds related to themselves or GCC, both
1741.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
1751.286Smrg	and MPC objdirs or build once without -u.
1761.286Smrg
1771.285Smrg20170816:
1781.285Smrg	a new version of MPFR and MPC have been imported and probably
1791.285Smrg	will break parts of builds related to themselves or GCC, both
1801.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
1811.285Smrg	and MPC objdirs or build once without -u.
1821.285Smrg
1831.284Smartin20170402:
1841.284Smartin	a new version of dhcpcd has been imported, which does not support
1851.284Smartin	update builds from the previous version. Remove your
1861.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
1871.284Smartin
1881.281Sroy20170211:
1891.281Sroy	a new terminfo database has been imported.
1901.281Sroy	The structure of it has changed slightly from prior versions and
1911.281Sroy	an updated tic tool is required.
1921.281Sroy	If you build.sh, don't use -u
1931.281Sroy
1941.280Skre20170207:
1951.278Skre	various arch dependent libc/exect.S files were removed
1961.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
1971.279Skre	if it exists) or do a clean build.
1981.279Skre	(This is a bug in the make system, it should be corrected without
1991.279Skre	human intervention, but isn't.)
2001.278Skre
2011.277Smartin20170104:
2021.277Smartin	xinput build options have changed.
2031.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
2041.277Smartin	if you build.sh -u
2051.277Smartin
2061.276Smartin20170103:
2071.276Smartin	a new version of flex has been imported.
2081.276Smartin	Remove the file from obj (external/bsd/flex)
2091.276Smartin	if you build.sh -u
2101.276Smartin
2111.275Sspz20161014:
2121.275Sspz	a new version of OpenSSL has been imported.
2131.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
2141.275Sspz	if you build.sh -u
2151.275Sspz
2161.274Smartin20161009:
2171.274Smartin	a new version of dhcpcd has been imported with slightly changed
2181.274Smartin	build infrastructure. When doing a build.sh -u this requires
2191.274Smartin	pruning the external/bsd/dhcpcd objdir.
2201.274Smartin
2211.273Smrg20160914:
2221.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
2231.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
2241.273Smrg	and a clean objdir.
2251.273Smrg
2261.272Sdholland20160527:
2271.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
2281.272Sdholland	been enabled. (see the amd64 entry two down for further info)
2291.272Sdholland
2301.270Schristos20160418:
2311.270Schristos	libedit needs manual removal of all autogenerated files since
2321.271Schristos	some of them are not autogenerated anymore. Remember that there
2331.271Schristos	might be two copies of libedit if your platform builds "compat".
2341.270Schristos
2351.268Sriastrad20160410:
2361.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
2371.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
2381.268Sriastrad	executables, means all code, including executables and not just
2391.268Sriastrad	shared libraries, is position-independent and hence able to be
2401.268Sriastrad	relocated by ASLR, address space layout randomization.
2411.268Sriastrad
2421.268Sriastrad	The change was made in Makefile variables for compiler and
2431.268Sriastrad	linker flags, for which make(1) does not record dependencies,
2441.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
2451.268Sriastrad
2461.268Sriastrad	Partial rebuilds with some modified source files will likely
2471.268Sriastrad	fail when linking executables, since the linker refuses to mix
2481.268Sriastrad	position-independent code with position-dependent code in
2491.268Sriastrad	position-independent executables:
2501.268Sriastrad
2511.268Sriastrad		.../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC
2521.268Sriastrad
2531.267Smrg20160401:
2541.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
2551.269Sdholland	Some people have found that cleandir is not sufficient, so if
2561.269Sdholland	in doubt delete the entire object directory tree for gcc.
2571.267Smrg
2581.266Saymeric20160306:
2591.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
2601.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
2611.265Saymeric	non-NetBSD hosts if linked with stale object files produced
2621.265Saymeric	while they included a non-NetBSD regex.h.
2631.265Saymeric	In any case, you should "make cleandir" at least these tools
2641.265Saymeric	before updating your toolchain.
2651.265Saymeric
2661.264Smartin20160125:
2671.264Smartin	Dtrace has been enabled by default on some architectures.
2681.264Smartin	When doing an update build, make sure to clean the etc/mtree
2691.264Smartin	object directory before starting the build - otherwise the
2701.264Smartin	needed directories in destdir will not be created.
2711.264Smartin	An easy way to do this is:
2721.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
2731.264Smartin
2741.263Sdholland20150818:
2751.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
2761.263Sdholland	again.
2771.263Sdholland
2781.262Schristos20150413:
2791.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
2801.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
2811.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
2821.262Schristos
2831.261Smartin20150404:
2841.261Smartin	Lint changes require a full rebuild of the tool, so make
2851.261Smartin	sure to build without -u option to build.sh, or manually
2861.261Smartin	do a make cleandir in src/tools/lint1 and
2871.261Smartin	src/usr.bin/xlint.
2881.261Smartin
2891.260Sskrll20150310:
2901.260Sskrll	Improvements to openssl for arm mean that update builds of
2911.260Sskrll	the openssl libraries will fail. A make cleandir in
2921.260Sskrll	external/bsd/openssl/lib is needed
2931.260Sskrll
2941.258Smartin20141026:
2951.259Smsaitoh	A mishap during the import of pppd may cause your corruption
2961.258Smartin	in your cvs directory if you happened to do a cvs update
2971.258Smartin	during a short period of time. To fix, just remove the
2981.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
2991.258Smartin	and let cvs restore it on next update.
3001.258Smartin
3011.256Sapb20140721:
3021.256Sapb	The src/external/mit/lua/src directory was accidentally created
3031.256Sapb	and then deleted in the CVS repository.  If you get errors like
3041.256Sapb
3051.256Sapb	cvs [update aborted]: cannot open directory
3061.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
3071.256Sapb
3081.256Sapb	then delete your local copy of that directory tree and try again.
3091.256Sapb
3101.255Sjoerg20140530:
3111.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
3121.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
3131.255Sjoerg
3141.251Smartin20140131:
3151.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
3161.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
3171.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
3181.251Smartin
3191.250Schristos20131227:
3201.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
3211.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
3221.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
3231.250Schristos	   statements to avoid being exposed.
3241.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
3251.250Schristos	   to make clean in libc
3261.250Schristos
3271.249Smrg20131129:
3281.249Smrg	The GMP sources were updated, and builds will likely fail without
3291.249Smrg	cleaning their build trees for both tools and in-tree, like below.
3301.249Smrg
3311.248Smrg20131128:
3321.248Smrg	The MPC and MPFR sources were updated, and builds may require their
3331.248Smrg	tools and in-tree directories cleaned for successful updates.
3341.248Smrg
3351.246Smartin20130605:
3361.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
3371.247Sspz	to IPSEC (and the older IPSEC version removed).
3381.247Sspz
3391.247Sspz20130605:
3401.246Smartin	Previous freetype installations eroneously installed private
3411.246Smartin	header files. If you are building against a non-empty $DESTDIR,
3421.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
3431.246Smartin
3441.245Smrg20130531:
3451.245Smrg	The xdm update may cause build failure due to xdm.man being
3461.245Smrg	in the obj tree.  Make sure to ensure any like this:
3471.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
3481.245Smrg	is fixed by deleting the xdm.man in the obj tree.
3491.245Smrg
3501.244Smrg20130530:
3511.244Smrg	Updates of many xsrc packages will leave old .pc files around.
3521.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
3531.244Smrg
3541.242Schristos20130301:
3551.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
3561.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
3571.242Schristos
3581.238Sdholland20120726:
3591.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
3601.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
3611.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
3621.241Swiz	some cases may succeed and install broken OpenSSL libraries that
3631.240Sdholland	cause third-party software to link incorrectly and/or crash.
3641.238Sdholland
3651.237Swiz20120507:
3661.241Swiz	The database schema for makemandb was changed.  You will
3671.237Swiz	need to update the database using 'makemandb -f' or wait
3681.237Swiz	for the next weekly run to fix it.
3691.237Swiz
3701.236Sbsh20120319:
3711.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
3721.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
3731.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
3741.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
3751.236Sbsh	mk.conf.
3761.236Sbsh
3771.235Sjoerg20120216:
3781.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
3791.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
3801.239Sdholland	and 20120216, daily and weekly could have created an unreadable
3811.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
3821.235Sjoerg	the next run of weekly will fix it.
3831.233Sjoerg
3841.232Schristos20111227:
3851.232Schristos	If you built between 20111225 and 20111227 you need to remove
3861.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
3871.232Schristos	bump has been reverted.
3881.232Schristos
3891.231Stls20111125:
3901.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
3911.231Stls	means it should no longer be explicitly listed in kernel
3921.231Stls	configuration files.  The line "pseudo-device rnd" should be
3931.231Stls	removed from any custom kernel config files users may have.
3941.231Stls
3951.230Stls20111119:
3961.230Stls	A problem with the datastructures used by the rndctl(8)
3971.230Stls	utility (pointers in datastructures in an array, making 32->64
3981.230Stls	bit compatibility very painful) has been fixed in a
3991.230Stls	non-backwards-compatible way.  If you replace your kernel,
4001.230Stls	replace your rndctl executable too.
4011.241Swiz
4021.229Sjym20111001:
4031.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
4041.229Sjym	changed and their new version is not backward compatible with the old
4051.241Swiz	one.  So ensure that all consumers of these functions (currently:
4061.229Sjym	quota2 code and its tests) are updated together with the new lib.
4071.229Sjym
4081.228Smrg20110817:
4091.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
4101.228Smrg	DESTDIR for them should be deleted before updating.
4111.228Smrg
4121.227Sriastrad20110806:
4131.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
4141.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
4151.227Sriastrad
4161.226Smrg20110805:
4171.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
4181.226Smrg	the tree to be cleaned.  Best to delete both objdir and
4191.226Smrg	DESTDIR before running this update.  So far, only the
4201.226Smrg	sparc64, mips and powerpc platforms have changed.
4211.226Smrg
4221.225Smatt20110803:
4231.241Swiz	The layout of external/public-domain/xz has changed.  To do an
4241.225Smatt	update build you will have to remove the contents of the OBJDIR
4251.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
4261.225Smatt	is now a directory.
4271.225Smatt
4281.223Sjoerg20110410:
4291.241Swiz	The configuration of src/tools/gcc has changed.  To do an
4301.224Sdholland	update build you have to clean both tools/binutils and
4311.224Sdholland	tools/gcc by hand.
4321.223Sjoerg
4331.222Splunky20110328:
4341.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
4351.241Swiz	ordering issues with "make all".  It may be necessary to remove
4361.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
4371.222Splunky	if your update build fails, as the "Xorg" entry there is now a
4381.222Splunky	directory.
4391.222Splunky
4401.220Sjoerg20110121:
4411.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
4421.220Sjoerg	the build of individual parts of the tree.  This is handled
4431.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
4441.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
4451.218Sjoerg
4461.217Sjruoho20101217:
4471.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
4481.241Swiz	by default.  It may be necessary to manually update passwd(5) and
4491.217Sjruoho	group(5) in order to make the program work with existing setups.
4501.217Sjruoho
4511.216Schristos20101125:
4521.216Schristos	The latest changes to setenv(3) dissallow setting environment
4531.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
4541.241Swiz	assumed that this was allowed.  Installing a new libc with an
4551.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
4561.216Schristos	break which affects the autoconf tests for dependency finding,
4571.216Schristos	so building gcc will end up printing:
4581.216Schristos	    checking dependency style of gcc... none
4591.216Schristos	    configure: error: no usable dependency style found
4601.216Schristos	Fix it by rebuilding and re-installing env.
4611.138Slukem
4621.215Smrg20101119:
4631.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
4641.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
4651.215Smrg	have any build problems with xsrc, or problems with mismatched
4661.215Smrg	versions between xorg-server and drivers.
4671.215Smrg
4681.213Sjmmv20100604:
4691.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
4701.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
4711.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
4721.213Sjmmv	trees by hand.
4731.213Sjmmv
4741.211Stnozaki20100522:
4751.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
4761.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
4771.212Smrg	build problems with xsrc.
4781.212Smrg
4791.212Smrg20100522:
4801.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
4811.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
4821.211Stnozaki
4831.210Schristos20100520:
4841.241Swiz	The location of the xkb compiled descriptions has changed.  Please
4851.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
4861.210Schristos
4871.209Snjoly20100222:
4881.209Snjoly	The shared objects file extension has been changed from .so to
4891.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
4901.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
4911.209Snjoly	your object directories.
4921.209Snjoly
4931.208Sroy20100204:
4941.208Sroy	The termcap database has been removed from the sources,
4951.208Sroy	but has not been marked obsolete so it is not removed
4961.208Sroy	from the system when upgrading.
4971.208Sroy	As such, you will need to remove them from your object
4981.208Sroy	and destination directories.
4991.208Sroy
5001.203Sdyoung20091101:
5011.205Sdholland        After updating, it may be necessary to make the 'cleandir'
5021.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
5031.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
5041.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
5051.203Sdyoung
5061.202Smrg20091001:
5071.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
5081.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
5091.206Sdholland
5101.206Sdholland20091001:
5111.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
5121.202Smrg	symlink, failing the build.  Delete the link, and the subdir
5131.202Smrg	it is in, and retry your build.
5141.202Smrg
5151.201Sdsl20090718:
5161.201Sdsl	libc build changed so that strchr() provides the extra entry
5171.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
5181.201Sdsl	may fail because the archive contains the unwanted index.o.
5191.201Sdsl	(Similarly for strrchr() and rindex().)
5201.201Sdsl
5211.198Smrg20090709:
5221.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
5231.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
5241.198Smrg
5251.197Smrg20090616:
5261.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
5271.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
5281.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
5291.197Smrg	subdirectory has been changed into a file, and this needs to
5301.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
5311.197Smrg
5321.195Sperry20090501:
5331.195Sperry	Several new functions were added to string.h/libc, and this
5341.195Sperry	can cause autoconf problems during the tool build for people
5351.241Swiz	who fail to clean out their tools objects properly.  If you
5361.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
5371.195Sperry	failure during the tool build, clean out all your tools
5381.195Sperry	objects and start again.
5391.195Sperry
5401.194Smrg20090325:
5411.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
5421.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
5431.194Smrg
5441.192Sskrll20090126:
5451.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
5461.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
5471.207Smbalmer	to avoid using the old assembly stub.
5481.192Sskrll
5491.191Sjoerg20090202:
5501.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
5511.191Sjoerg	detection.  It is recommented to rebuild the cache with
5521.191Sjoerg	``pkg_admin rebuild''.
5531.191Sjoerg
5541.184Schristos20090110:
5551.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
5561.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
5571.188Schristos	   This is needed even in the MODULAR kernel because there is
5581.188Schristos	   conditionally compiled code in rtsock.c.
5591.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
5601.184Schristos	   before installing.
5611.184Schristos	3. If you don't use build.sh and you build directly to root, and
5621.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
5631.184Schristos	   are installed properly, and start building libraries first libc
5641.184Schristos	   and libutil, install them and then continue building all the
5651.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
5661.184Schristos	   the new libraries are installed, you can restart the build.
5671.184Schristos	4. If you compile packages and you notice link time warnings,
5681.189Shubertf	   rebuild the required packages to update their shared libraries.
5691.189Shubertf	   Any package you rebuild will require rebuilding all the packages
5701.189Shubertf	   that depend on it.
5711.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
5721.186Schristos	   will be upgraded and it will not be backwards compatible.
5731.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
5741.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
5751.241Swiz	   for utmp.  You are better off removing the old files after
5761.190Sapb	   upgrading.  The automated clearing of /var/run during
5771.190Sapb	   boot, and the automated rotating of files in /var/log by
5781.190Sapb	   newsyslog(8), may mean that you do not have to remove the
5791.190Sapb	   files manually.
5801.190Sapb	7. The optional accounting file (/var/account/acct, see
5811.190Sapb	   accton(8)) has not been versioned, and will need to be
5821.190Sapb	   removed.  The automatic rotation of the accounting file by
5831.190Sapb	   /etc/daily limits the bad consequences of failure to remove
5841.190Sapb	   the file.
5851.196Sdholland	8. Application software that writes time_t to binary files on
5861.241Swiz	   disk will break or need attention.  Most notably: if you are
5871.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
5881.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
5891.185Sjmcneill
5901.183Spgoyette20081219:
5911.183Spgoyette	config(1) has been updated, and one of the files it creates -
5921.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
5931.183Spgoyette	(done automatically by build.sh) and then you need to rerun
5941.183Spgoyette	config on all kernel configuration files before rebuilding those
5951.183Spgoyette	kernels.
5961.183Spgoyette
5971.181Scube20081205:
5981.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
5991.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
6001.181Scube	set and will appear as extra files for MKX11=no update builds.
6011.178Slukem
6021.179Stsutsui20081122:
6031.182Stsutsui	On i386, various kernel options(4) in GENERIC including
6041.180Swiz	file systems have been disabled and moved into kernel modules.
6051.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
6061.179Stsutsui	following files as well as a new GENERIC kernel:
6071.179Stsutsui
6081.179Stsutsui	- build and install kernel modules from src/sys/modules
6091.179Stsutsui
6101.179Stsutsui	- install the latest bootloader, which will load a module
6111.180Swiz	  for the file system from which the kernel is loaded automatically
6121.179Stsutsui
6131.180Swiz	If you have to load your kernel from a file system which is not of
6141.180Swiz	the same type as the root file system, you have to load the necessary
6151.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
6161.179Stsutsui
6171.178Slukem20080827:
6181.178Slukem	If you built and installed a libc from sources between
6191.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
6201.178Slukem	which results in false errors reported by lint(1).
6211.178Slukem	Since this breaks the libc build itself, manual help is
6221.180Swiz	needed -- lint must be disabled temporarily, e.g.:
6231.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
6241.178Slukem
6251.177Schristos20080813:
6261.177Schristos	MKDEBUG build was broken because the .depend files did not know
6271.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
6281.177Schristos
6291.200Sdholland20080802:
6301.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
6311.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
6321.200Sdholland	for -current.
6331.200Sdholland
6341.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
6351.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
6361.200Sdholland	be recompiled.
6371.200Sdholland
6381.200Sdholland	One way to find affected pkgsrc packages:
6391.200Sdholland
6401.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
6411.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
6421.200Sdholland
6431.175Ssimonb20080731:
6441.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
6451.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
6461.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
6471.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
6481.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
6491.176Ssimonb	also requires the super block to be in the UFS2 format.  You
6501.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
6511.175Ssimonb
6521.174Slukem20080721:
6531.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
6541.174Slukem	isn't defined.
6551.174Slukem
6561.173Sfreza20080531:
6571.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
6581.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
6591.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
6601.241Swiz	won't work correctly.  The following sequence of commands:
6611.173Sfreza
6621.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
6631.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
6641.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
6651.173Sfreza
6661.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
6671.173Sfreza
6681.172Slukem20080503:
6691.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
6701.172Slukem
6711.171She20080521:
6721.171She	For a while, unprivileged UPDATE builds would fail to
6731.171She	succeed at the checkflist stage, complaining that
6741.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
6751.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
6761.171She	If you already hit this problem, update the .mk file,
6771.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
6781.171She
6791.174Slukem20080303:
6801.174Slukem	Linker warnings are now fatal if $WARNS>0.
6811.174Slukem
6821.170Schristos20080126:
6831.170Schristos	The posix_fadvise system call has been changed from an assembly
6841.241Swiz	stub, to a c file that calls an assembly stub.  You need to
6851.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
6861.170Schristos	avoid using the old assembly stub.
6871.170Schristos
6881.168Sjoerg20071209:
6891.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
6901.168Sjoerg	get ACPI errors before the attachment, please update your kernel
6911.169Swiz	configuration file appropriately or see GENERIC for more details.
6921.168Sjoerg
6931.166Sxtraeme20071115:
6941.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
6951.166Sxtraeme	argument specified in the kernel configuration file is not valid
6961.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
6971.241Swiz	rather than the EC address port.  Please update your kernel
6981.167Swiz	configuration file appropriately or see GENERIC for more details.
6991.166Sxtraeme
7001.165Sjmmv20071028:
7011.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
7021.165Sjmmv	You need to update any custom kernel configuration file you have
7031.165Sjmmv	to remove any references to pccons (which includes removing the
7041.165Sjmmv	now useless XSERVER option) and replace them with the correct
7051.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
7061.165Sjmmv	for more details.
7071.165Sjmmv
7081.164Sgdt20070913:
7091.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
7101.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
7111.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
7121.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
7131.164Sgdt	could not enumerate interfaces.  (These are noted because
7141.164Sgdt	normal kernel/userspace version matching hygiene is not
7151.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
7161.164Sgdt	and userland are from after 20070913.
7171.164Sgdt
7181.163Sjoerg20070703:
7191.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
7201.199Sdholland	calls the target-specific strip program, and the logic to pass
7211.199Sdholland	down STRIP from make has been removed.  This requires a
7221.199Sdholland	re-installation of tools.
7231.163Sjoerg
7241.161Sdsl20070422:
7251.161Sdsl	The way OS emulations lookup filenames inside the emulation root
7261.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
7271.161Sdsl	to userspace) namei() and lookup() directly check the emulation
7281.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
7291.167Swiz	root file system will be relative to that file system - unless they
7301.161Sdsl	start /../ this is useful when the emulated root is a real install
7311.161Sdsl	that has such links.
7321.161Sdsl	This might affect symlinks that have been added to reference outside
7331.161Sdsl	the emulated root.
7341.161Sdsl
7351.160Sjmcneill20070412:
7361.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
7371.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
7381.160Sjmcneill	example.
7391.160Sjmcneill
7401.159Sgdt20070319:
7411.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
7421.159Sgdt        on many platforms due to incorrect flags settings.  If you
7431.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
7441.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
7451.159Sgdt	rebuild of object files that might have been built
7461.159Sgdt	incorrectly, and ensure that you have at least
7471.159Sgdt	src/lib/libc/Makefile 1.130.
7481.159Sgdt
7491.241Swiz20070210:
7501.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
7511.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
7521.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
7531.158Sdbj        will allow dependencies on those files to get get rebuilt
7541.158Sdbj
7551.157Sapb20070209:
7561.157Sapb        The threading model was changed when the newlock2 branch
7571.157Sapb        was merged to NetBSD-current.  If you boot with a new
7581.157Sapb        kernel (version 4.99.10), then you also need a new pthread
7591.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
7601.157Sapb        an old kernel, then you need the old pthread library
7611.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
7621.157Sapb        the pthread library in sync, old threaded applications should
7631.157Sapb        continue to work with an old or new kernel.  Note that named(8)
7641.157Sapb	is the only threaded application in the base system.
7651.157Sapb
7661.154She20061214:
7671.154She	Following the move of string_to_flags() and flags_to_string()
7681.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
7691.154She	will need to do a "make cleandir" in
7701.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
7711.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
7721.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
7731.156She		as the installation images in distrib/
7741.154She	in order to excise stale references to the old stat_flags.h header
7751.154She	file in the ls sources -- stat_flags.h has been removed.
7761.154She
7771.152Schristos20061108:
7781.152Schristos	The configure script used in the src/tools/gcc compiler has been
7791.152Schristos	changed to indicate that our libc has ssp support built-in and
7801.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
7811.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
7821.152Schristos
7831.151Srpaulo20061009:
7841.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
7851.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
7861.151Srpaulo
7871.150Sbjh2120060814:
7881.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
7891.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
7901.150Sbjh21	kernel configuration for an example.  X servers from the last
7911.150Sbjh21	few years should cope.
7921.150Sbjh21
7931.149Schristos20060703:
7941.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
7951.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
7961.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
7971.149Schristos
7981.148Sdogcow20060627:
7991.148Sdogcow	socket(2) has changed, and its system call has been versioned.
8001.148Sdogcow	For userlands with the old version of socket(2), make sure that
8011.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
8021.148Sdogcow	errors will result.
8031.148Sdogcow
8041.1SabsHints for a more successful build:
8051.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8061.123Sjmc    Use build.sh, but do not use its "expert mode":
8071.132Sjmmv	This will automatically build the tools in the
8081.123Sjmc	   correct order, and it will keep the tools and the
8091.123Sjmc	   new build products from interfering with the running
8101.123Sjmc	   system.  This will allow you to ignore most of the
8111.123Sjmc	   other advice in this file.
8121.2Smrg    Build a new kernel first:
8131.2Smrg	This makes sure that any new system calls or features
8141.2Smrg	   expected by the new userland will be present.  This
8151.2Smrg	   helps to avoid critical errors when upgrading.
8161.1Sabs    Use object directories:
8171.1Sabs	This helps to keep stale object
8181.1Sabs	   files from polluting the build if a Makefile "forgets"
8191.1Sabs	   about one.  It also makes it easier to clean up after
8201.1Sabs	   a build.  It's also necessary if you want to use the
8211.1Sabs	   same source tree for multiple machines.
8221.123Sjmc	   To use object directories with build.sh:
8231.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
8241.123Sjmc	   To use object directories without using build.sh:
8251.1Sabs	    a) cd /usr/src ; make cleandir
8261.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
8271.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
8281.1Sabs	    d) cd /usr/src ; make build
8291.2Smrg	   Note that running "make obj" in a directory will create
8301.2Smrg	   in obj.$MACHINE directory.
8311.1Sabs    Build to a DESTDIR:
8321.123Sjmc	This helps to keep old installed files (especially libraries)
8331.123Sjmc	   from interfering with the new build.
8341.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
8351.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
8361.123Sjmc	   environment variable before running make build.  It should be
8371.123Sjmc	   set to the pathname of an initially empty directory.
8381.123Sjmc	   Problems: if you do not use build.sh, you might need to
8391.123Sjmc		update critical utilities without using DESTDIR since
8401.123Sjmc		nothing is executed from what is installed in DESTDIR.
8411.123Sjmc		(See critical utils, below.)
8421.1Sabs    Build often:
8431.1Sabs	This keeps critical utilities current enough to not choke
8441.1Sabs	on any other part of the source tree that depends on up to
8451.123Sjmc	date functionality.  If you use build.sh, you should not have
8461.123Sjmc	this problem.
8471.241Swiz
8481.1SabsWhat to do if things don't work:
8491.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8501.230StlsWhen things don't work there are usually a few things that commonly
8511.1Sabsshould be done.
8521.1Sabs    1)	make includes
8531.1Sabs	This should be done automatically by make build.
8541.1Sabs    2)  cd share/mk && make install
8551.1Sabs	Again, automatically done by make build.
8561.1Sabs
8571.1SabsFailsafe rebuild of a small part of the tree:
8581.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8591.1SabsTo make sure you rebuild something correctly you want to do
8601.1Sabssomething like the following:
8611.1Sabs    1)  Make sure the includes and .mk files are up to date.
8621.1Sabs    2)  Make sure any program used to build the particular
8631.1Sabs	utility is up to date.  (yacc, lex, etc...)
8641.1Sabs    3)  cd ...path/to/util...
8651.1Sabs	make cleandir
8661.1Sabs	rm ...all obj directories...
8671.1Sabs	make cleandir			# yes, again
8681.1Sabs	make obj
8691.1Sabs	make depend && make
8701.1Sabs
8711.1SabsFailsafe rebuild of the entire tree:
8721.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8731.1SabsIf you really want to make sure the source tree is clean and
8741.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
8751.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
8761.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
8771.1Sabs
8781.1Sabs---cut here---
8791.1Sabs#!/bin/sh
8801.1Sabs. /etc/mk.conf
8811.1Sabs
8821.58Slukemif [ -z $NETBSDSRCDIR ] ; then
8831.58Slukem    NETBSDSRCDIR=/usr/src
8841.1Sabsfi
8851.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
8861.1Sabs    echo Unable to find sources
8871.1Sabs    exit 1
8881.1Sabsfi
8891.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
8901.1Sabs
8911.1Sabsif [ -z $BSDOBJDIR ] ; then
8921.1Sabs    BSDOBJDIR=/usr/obj
8931.1Sabsfi
8941.1Sabsif [ -d $BSDOBJDIR ] ; then
8951.1Sabs    rm -rf $BSDOBJDIR
8961.1Sabsfi
8971.1Sabs
8981.58Slukemcd $NETBSDSRCDIR && make cleandir
8991.1Sabs
9001.1Sabs---cut here---
9011.1Sabs
9021.1SabsCritical utilities:
9031.1Sabs^^^^^^^^^^^^^^^^^^^
9041.3Sitojun	usr.bin/compile_et
9051.1Sabs	usr.bin/make
9061.1Sabs	usr.bin/yacc
9071.1Sabs	usr.bin/lex
9081.11Slukem	usr.bin/xlint
9091.142Sdrochner	usr.bin/config
9101.1Sabs
9111.34SsimonbOther problems and possible solutions:
9121.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9131.1SabsSymptom:Complaints involving a Makefile.
9141.17SerhFix:	Rebuild usr.bin/make:
9151.17Serh	cd usr.bin/make && make && make install
9161.111Ssimonb	Or, a failsafe method if that doesn't work:
9171.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
9181.17Serh
9191.1SabsFix:	Make sure .mk files are up to date.
9201.1Sabs	cd share/mk && make install
9211.2Smrg
9221.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
9231.142SdrochnerFix:	Rebuild usr.bin/config
9241.1Sabs
9251.1SabsSymptom:
9261.1SabsFix:	Rebuild usr.bin/yacc
9271.1Sabs
9281.1SabsSymptom:
9291.1SabsFix:	Rebuild usr.bin/lex
9301.1Sabs
9311.1SabsSymptom:
9321.1SabsFix:	rm /usr/lib/libbfd.a
9331.4Sitojun
9341.4SitojunSymptom:Obsolete intermediate files are used during compilation
9351.4SitojunFix:	Try the following sequence of commands in the directory in question.
9361.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
9371.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
9381.4Sitojun	may remain.  The command tries to clean everything up)
9391.5Swiz
9401.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
9411.207Smbalmer	pointer type
9421.5SwizFix:	Rebuild and install usr.bin/menuc
9431.12Sitojun
9441.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9451.12SitojunFix:	Build and install usr.bin/mklocale
9461.13Sdogcow
9471.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9481.13SdogcowFix:    Rebuild and install lib/libc
9491.13Sdogcow
9501.142SdrochnerSymptom:usr.bin/config fails to build.
9511.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9521.13Sdogcow
9531.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9541.19ScgdFix:    Rebuild and install lib/libc
9551.24Sabs
9561.24SabsSymptom:lint does not understand the '-X' option
9571.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
9581.223Sjoerg
9591.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
9601.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
9611.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
9621.257Sapb
9631.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
9641.257Sapb	No such file or directory.
9651.257SapbCause:	If a directory is created by mistake, then it is sometimes
9661.257Sapb	deleted from the CVS repository using administrative commands
9671.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
9681.257Sapb	contains references to a directory that has been deleted on the
9691.257Sapb	server in this way, then "cvs update" reports this error.
9701.257SapbFix:	Recursively delete the affected directory from your working tree
9711.257Sapb	and try the update again.
972