UPDATING revision 1.316
11.316Smrg$NetBSD: UPDATING,v 1.316 2020/10/17 07:41:25 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.316Smrg20201016:
231.316Smrg	MIPS kernel modules have been disabled until they work.  This will
241.316Smrg	turn up in extra files in the DESTDIR, which should be cleaned.
251.316Smrg
261.315Smrg20200925:
271.315Smrg	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
281.315Smrg	in both the tools and external dirs.
291.315Smrg
301.314Smrg20200912:
311.314Smrg	GCC 9 has arrived for Arm and x86 platforms, and will be coming
321.314Smrg	for several more, as will binutils 2.34.  Clean as required.
331.314Smrg
341.313Smrg20200907:
351.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
361.313Smrg	probably requires cleaning the tools/binutils.
371.313Smrg
381.311Smrg20200811:
391.312Smrg	GCC updates may require cleaning the objdir.  This may occur
401.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
411.312Smrg	GCC 9 upgrade.
421.311Smrg
431.309Schristos20200614:
441.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
451.310Schristos	should handle the migration
461.309Schristos
471.308Schristos20200601:
481.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
491.308Schristos	created in the build directories and need cleaning.
501.308Schristos
511.307Smrg20200311:
521.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
531.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
541.307Smrg
551.306Schristos20191118:
561.306Schristos	More architectures were switched to gcc8:
571.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
581.306Schristos	The same comments as in 20191022 apply.
591.306Schristos
601.305Smartin20191112:
611.305Smartin	The LLVM update requires a clean rebuild for all architectures using
621.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
631.305Smartin
641.304Smartin20191022:
651.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
661.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
671.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
681.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
691.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
701.304Smartin	daily builds and install that before doing the next in-place build.
711.304Smartin
721.303Smrg20191001:
731.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
741.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
751.303Smrg	directory, and also clean src/external/gpl3/gcc.
761.303Smrg
771.302Sriastrad20190903:
781.306Schristos	Files with names that coincide with existing files' names on
791.302Sriastrad	case-insensitive file systems were inadvertently committed, for
801.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
811.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
821.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
831.302Sriastrad	manually delete the following files in your DESTDIR (which is
841.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
851.302Sriastrad	them:
861.302Sriastrad
871.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
881.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
891.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
901.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
911.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
921.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
931.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
941.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
951.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
961.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
971.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
981.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
991.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
1001.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
1011.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
1021.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
1031.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
1041.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
1051.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
1061.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
1071.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
1081.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
1091.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
1101.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
1111.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
1121.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
1131.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
1141.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
1151.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
1161.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
1171.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
1181.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
1191.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
1201.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
1211.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
1221.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
1231.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
1241.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
1251.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
1261.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
1271.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
1281.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
1291.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
1301.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
1311.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
1321.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
1331.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
1341.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
1351.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
1361.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
1371.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
1381.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
1391.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
1401.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
1411.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
1421.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
1431.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
1441.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
1451.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
1461.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
1471.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
1481.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
1491.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
1501.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
1511.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
1521.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
1531.302Sriastrad
1541.302Sriastrad	We will re-import these radeon firmware images another way
1551.302Sriastrad	later.
1561.302Sriastrad
1571.301Smartin20190727:
1581.301Smartin	The uefi bootloader has gained tftp support and needs a clean
1591.301Smartin	build. If you do update builds, manually clean its object
1601.301Smartin	directory by something like:
1611.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
1621.301Smartin
1631.300Smartin20190723:
1641.300Smartin	The jemalloc allocator in libc is now build without extended
1651.300Smartin	debugging (for performance reasons). In update builds make sure
1661.300Smartin	to rebuild it completly, by removing all affected object files,
1671.300Smartin	including compat builds, something like:
1681.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
1691.300Smartin
1701.299Smrg20190207:
1711.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
1721.299Smrg
1731.298Smartin20180924:
1741.298Smartin	A newer OpenSSL version has been imported. If you are doing
1751.298Smartin	update builds, make sure to remove all old obj dirs, like:
1761.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
1771.298Smartin
1781.297Sjoerg20180717:
1791.297Sjoerg	On aarch64 int64_t and related types have changed from long long
1801.297Sjoerg	to long. This requires recompiling all C++ binaries.
1811.297Sjoerg
1821.296Smartin20180713:
1831.296Smartin	On amd64 and i386 static binaries are now build position
1841.296Smartin	independend. This requires recompilation of all object
1851.296Smartin	files used to create the crunched /rescue binary.
1861.296Smartin	Clean the rescue directory in your obj directory before
1871.296Smartin	doing an update build, otherwise linking will fail.
1881.296Smartin
1891.293Sjakllsch20180414:
1901.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
1911.293Sjakllsch	removal of tools/binutils objects directory may be required
1921.293Sjakllsch	to fix tools build failure.
1931.293Sjakllsch
1941.292Smrg20180311:
1951.292Smrg	bdftopcf was updated and may need cleaning in the
1961.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
1971.292Smrg	link errors.
1981.292Smrg
1991.291Smrg20180212:
2001.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
2011.291Smrg	any failure that looks like GCC or openssl is best handled by
2021.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
2031.291Smrg	is recommended if build failures occur.
2041.291Smrg
2051.288Smartin20171225:
2061.288Smartin	removal of the vadvise syscall requires manual removal of all
2071.288Smartin	associated files from the libc build object directory (including
2081.289Schristos	the .depend files) - a command like:
2091.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
2101.289Schristos	For architectures that support multiple "compat" binary targets,
2111.289Schristos	you'll need to cleanup both the regular libc directory and the
2121.290Smartin	compat ones (the above command will do that).
2131.288Smartin
2141.287Skre20171010:
2151.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
2161.287Skre	means that its objdir (or *.d and .depend at least) might need
2171.287Skre	to be manually removed - or a build done once without -u.
2181.287Skre
2191.286Smrg20170822:
2201.286Smrg	a new version of GMP has been imported and probably
2211.286Smrg	will break parts of builds related to themselves or GCC, both
2221.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2231.286Smrg	and MPC objdirs or build once without -u.
2241.286Smrg
2251.285Smrg20170816:
2261.285Smrg	a new version of MPFR and MPC have been imported and probably
2271.285Smrg	will break parts of builds related to themselves or GCC, both
2281.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2291.285Smrg	and MPC objdirs or build once without -u.
2301.285Smrg
2311.284Smartin20170402:
2321.284Smartin	a new version of dhcpcd has been imported, which does not support
2331.284Smartin	update builds from the previous version. Remove your
2341.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
2351.284Smartin
2361.281Sroy20170211:
2371.281Sroy	a new terminfo database has been imported.
2381.281Sroy	The structure of it has changed slightly from prior versions and
2391.281Sroy	an updated tic tool is required.
2401.281Sroy	If you build.sh, don't use -u
2411.281Sroy
2421.280Skre20170207:
2431.278Skre	various arch dependent libc/exect.S files were removed
2441.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
2451.279Skre	if it exists) or do a clean build.
2461.279Skre	(This is a bug in the make system, it should be corrected without
2471.279Skre	human intervention, but isn't.)
2481.278Skre
2491.277Smartin20170104:
2501.277Smartin	xinput build options have changed.
2511.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
2521.277Smartin	if you build.sh -u
2531.277Smartin
2541.276Smartin20170103:
2551.276Smartin	a new version of flex has been imported.
2561.276Smartin	Remove the file from obj (external/bsd/flex)
2571.276Smartin	if you build.sh -u
2581.276Smartin
2591.275Sspz20161014:
2601.275Sspz	a new version of OpenSSL has been imported.
2611.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
2621.275Sspz	if you build.sh -u
2631.275Sspz
2641.274Smartin20161009:
2651.274Smartin	a new version of dhcpcd has been imported with slightly changed
2661.274Smartin	build infrastructure. When doing a build.sh -u this requires
2671.274Smartin	pruning the external/bsd/dhcpcd objdir.
2681.274Smartin
2691.273Smrg20160914:
2701.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
2711.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
2721.273Smrg	and a clean objdir.
2731.273Smrg
2741.272Sdholland20160527:
2751.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
2761.272Sdholland	been enabled. (see the amd64 entry two down for further info)
2771.272Sdholland
2781.270Schristos20160418:
2791.270Schristos	libedit needs manual removal of all autogenerated files since
2801.271Schristos	some of them are not autogenerated anymore. Remember that there
2811.271Schristos	might be two copies of libedit if your platform builds "compat".
2821.270Schristos
2831.268Sriastrad20160410:
2841.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
2851.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
2861.268Sriastrad	executables, means all code, including executables and not just
2871.268Sriastrad	shared libraries, is position-independent and hence able to be
2881.268Sriastrad	relocated by ASLR, address space layout randomization.
2891.268Sriastrad
2901.268Sriastrad	The change was made in Makefile variables for compiler and
2911.268Sriastrad	linker flags, for which make(1) does not record dependencies,
2921.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
2931.268Sriastrad
2941.268Sriastrad	Partial rebuilds with some modified source files will likely
2951.268Sriastrad	fail when linking executables, since the linker refuses to mix
2961.268Sriastrad	position-independent code with position-dependent code in
2971.268Sriastrad	position-independent executables:
2981.268Sriastrad
2991.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
3001.268Sriastrad
3011.267Smrg20160401:
3021.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
3031.269Sdholland	Some people have found that cleandir is not sufficient, so if
3041.269Sdholland	in doubt delete the entire object directory tree for gcc.
3051.267Smrg
3061.266Saymeric20160306:
3071.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
3081.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
3091.265Saymeric	non-NetBSD hosts if linked with stale object files produced
3101.265Saymeric	while they included a non-NetBSD regex.h.
3111.265Saymeric	In any case, you should "make cleandir" at least these tools
3121.265Saymeric	before updating your toolchain.
3131.265Saymeric
3141.264Smartin20160125:
3151.264Smartin	Dtrace has been enabled by default on some architectures.
3161.264Smartin	When doing an update build, make sure to clean the etc/mtree
3171.264Smartin	object directory before starting the build - otherwise the
3181.264Smartin	needed directories in destdir will not be created.
3191.264Smartin	An easy way to do this is:
3201.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
3211.264Smartin
3221.263Sdholland20150818:
3231.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
3241.263Sdholland	again.
3251.263Sdholland
3261.262Schristos20150413:
3271.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
3281.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
3291.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
3301.262Schristos
3311.261Smartin20150404:
3321.261Smartin	Lint changes require a full rebuild of the tool, so make
3331.261Smartin	sure to build without -u option to build.sh, or manually
3341.261Smartin	do a make cleandir in src/tools/lint1 and
3351.261Smartin	src/usr.bin/xlint.
3361.261Smartin
3371.260Sskrll20150310:
3381.260Sskrll	Improvements to openssl for arm mean that update builds of
3391.260Sskrll	the openssl libraries will fail. A make cleandir in
3401.260Sskrll	external/bsd/openssl/lib is needed
3411.260Sskrll
3421.258Smartin20141026:
3431.259Smsaitoh	A mishap during the import of pppd may cause your corruption
3441.258Smartin	in your cvs directory if you happened to do a cvs update
3451.258Smartin	during a short period of time. To fix, just remove the
3461.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
3471.258Smartin	and let cvs restore it on next update.
3481.258Smartin
3491.256Sapb20140721:
3501.256Sapb	The src/external/mit/lua/src directory was accidentally created
3511.256Sapb	and then deleted in the CVS repository.  If you get errors like
3521.256Sapb
3531.256Sapb	cvs [update aborted]: cannot open directory
3541.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
3551.256Sapb
3561.256Sapb	then delete your local copy of that directory tree and try again.
3571.256Sapb
3581.255Sjoerg20140530:
3591.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
3601.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
3611.255Sjoerg
3621.251Smartin20140131:
3631.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
3641.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
3651.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
3661.251Smartin
3671.250Schristos20131227:
3681.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
3691.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
3701.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
3711.250Schristos	   statements to avoid being exposed.
3721.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
3731.250Schristos	   to make clean in libc
3741.250Schristos
3751.249Smrg20131129:
3761.249Smrg	The GMP sources were updated, and builds will likely fail without
3771.249Smrg	cleaning their build trees for both tools and in-tree, like below.
3781.249Smrg
3791.248Smrg20131128:
3801.248Smrg	The MPC and MPFR sources were updated, and builds may require their
3811.248Smrg	tools and in-tree directories cleaned for successful updates.
3821.248Smrg
3831.246Smartin20130605:
3841.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
3851.247Sspz	to IPSEC (and the older IPSEC version removed).
3861.247Sspz
3871.247Sspz20130605:
3881.246Smartin	Previous freetype installations eroneously installed private
3891.246Smartin	header files. If you are building against a non-empty $DESTDIR,
3901.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
3911.246Smartin
3921.245Smrg20130531:
3931.245Smrg	The xdm update may cause build failure due to xdm.man being
3941.245Smrg	in the obj tree.  Make sure to ensure any like this:
3951.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
3961.245Smrg	is fixed by deleting the xdm.man in the obj tree.
3971.245Smrg
3981.244Smrg20130530:
3991.244Smrg	Updates of many xsrc packages will leave old .pc files around.
4001.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
4011.244Smrg
4021.242Schristos20130301:
4031.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
4041.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
4051.242Schristos
4061.238Sdholland20120726:
4071.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
4081.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
4091.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
4101.241Swiz	some cases may succeed and install broken OpenSSL libraries that
4111.240Sdholland	cause third-party software to link incorrectly and/or crash.
4121.238Sdholland
4131.237Swiz20120507:
4141.241Swiz	The database schema for makemandb was changed.  You will
4151.237Swiz	need to update the database using 'makemandb -f' or wait
4161.237Swiz	for the next weekly run to fix it.
4171.237Swiz
4181.236Sbsh20120319:
4191.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
4201.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
4211.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
4221.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
4231.236Sbsh	mk.conf.
4241.236Sbsh
4251.235Sjoerg20120216:
4261.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
4271.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
4281.239Sdholland	and 20120216, daily and weekly could have created an unreadable
4291.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
4301.235Sjoerg	the next run of weekly will fix it.
4311.233Sjoerg
4321.232Schristos20111227:
4331.232Schristos	If you built between 20111225 and 20111227 you need to remove
4341.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
4351.232Schristos	bump has been reverted.
4361.232Schristos
4371.231Stls20111125:
4381.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
4391.231Stls	means it should no longer be explicitly listed in kernel
4401.231Stls	configuration files.  The line "pseudo-device rnd" should be
4411.231Stls	removed from any custom kernel config files users may have.
4421.231Stls
4431.230Stls20111119:
4441.230Stls	A problem with the datastructures used by the rndctl(8)
4451.230Stls	utility (pointers in datastructures in an array, making 32->64
4461.230Stls	bit compatibility very painful) has been fixed in a
4471.230Stls	non-backwards-compatible way.  If you replace your kernel,
4481.230Stls	replace your rndctl executable too.
4491.241Swiz
4501.229Sjym20111001:
4511.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
4521.229Sjym	changed and their new version is not backward compatible with the old
4531.241Swiz	one.  So ensure that all consumers of these functions (currently:
4541.229Sjym	quota2 code and its tests) are updated together with the new lib.
4551.229Sjym
4561.228Smrg20110817:
4571.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
4581.228Smrg	DESTDIR for them should be deleted before updating.
4591.228Smrg
4601.227Sriastrad20110806:
4611.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
4621.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
4631.227Sriastrad
4641.226Smrg20110805:
4651.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
4661.226Smrg	the tree to be cleaned.  Best to delete both objdir and
4671.226Smrg	DESTDIR before running this update.  So far, only the
4681.226Smrg	sparc64, mips and powerpc platforms have changed.
4691.226Smrg
4701.225Smatt20110803:
4711.241Swiz	The layout of external/public-domain/xz has changed.  To do an
4721.225Smatt	update build you will have to remove the contents of the OBJDIR
4731.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
4741.225Smatt	is now a directory.
4751.225Smatt
4761.223Sjoerg20110410:
4771.241Swiz	The configuration of src/tools/gcc has changed.  To do an
4781.224Sdholland	update build you have to clean both tools/binutils and
4791.224Sdholland	tools/gcc by hand.
4801.223Sjoerg
4811.222Splunky20110328:
4821.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
4831.241Swiz	ordering issues with "make all".  It may be necessary to remove
4841.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
4851.222Splunky	if your update build fails, as the "Xorg" entry there is now a
4861.222Splunky	directory.
4871.222Splunky
4881.220Sjoerg20110121:
4891.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
4901.220Sjoerg	the build of individual parts of the tree.  This is handled
4911.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
4921.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
4931.218Sjoerg
4941.217Sjruoho20101217:
4951.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
4961.241Swiz	by default.  It may be necessary to manually update passwd(5) and
4971.217Sjruoho	group(5) in order to make the program work with existing setups.
4981.217Sjruoho
4991.216Schristos20101125:
5001.216Schristos	The latest changes to setenv(3) dissallow setting environment
5011.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
5021.241Swiz	assumed that this was allowed.  Installing a new libc with an
5031.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
5041.216Schristos	break which affects the autoconf tests for dependency finding,
5051.216Schristos	so building gcc will end up printing:
5061.216Schristos	    checking dependency style of gcc... none
5071.216Schristos	    configure: error: no usable dependency style found
5081.216Schristos	Fix it by rebuilding and re-installing env.
5091.138Slukem
5101.215Smrg20101119:
5111.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
5121.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
5131.215Smrg	have any build problems with xsrc, or problems with mismatched
5141.215Smrg	versions between xorg-server and drivers.
5151.215Smrg
5161.213Sjmmv20100604:
5171.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
5181.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
5191.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
5201.213Sjmmv	trees by hand.
5211.213Sjmmv
5221.211Stnozaki20100522:
5231.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
5241.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
5251.212Smrg	build problems with xsrc.
5261.212Smrg
5271.212Smrg20100522:
5281.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
5291.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
5301.211Stnozaki
5311.210Schristos20100520:
5321.241Swiz	The location of the xkb compiled descriptions has changed.  Please
5331.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
5341.210Schristos
5351.209Snjoly20100222:
5361.209Snjoly	The shared objects file extension has been changed from .so to
5371.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
5381.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
5391.209Snjoly	your object directories.
5401.209Snjoly
5411.208Sroy20100204:
5421.208Sroy	The termcap database has been removed from the sources,
5431.208Sroy	but has not been marked obsolete so it is not removed
5441.208Sroy	from the system when upgrading.
5451.208Sroy	As such, you will need to remove them from your object
5461.208Sroy	and destination directories.
5471.208Sroy
5481.203Sdyoung20091101:
5491.205Sdholland        After updating, it may be necessary to make the 'cleandir'
5501.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
5511.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
5521.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
5531.203Sdyoung
5541.202Smrg20091001:
5551.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
5561.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
5571.206Sdholland
5581.206Sdholland20091001:
5591.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
5601.202Smrg	symlink, failing the build.  Delete the link, and the subdir
5611.202Smrg	it is in, and retry your build.
5621.202Smrg
5631.201Sdsl20090718:
5641.201Sdsl	libc build changed so that strchr() provides the extra entry
5651.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
5661.201Sdsl	may fail because the archive contains the unwanted index.o.
5671.201Sdsl	(Similarly for strrchr() and rindex().)
5681.201Sdsl
5691.198Smrg20090709:
5701.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
5711.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
5721.198Smrg
5731.197Smrg20090616:
5741.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
5751.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
5761.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
5771.197Smrg	subdirectory has been changed into a file, and this needs to
5781.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
5791.197Smrg
5801.195Sperry20090501:
5811.195Sperry	Several new functions were added to string.h/libc, and this
5821.195Sperry	can cause autoconf problems during the tool build for people
5831.241Swiz	who fail to clean out their tools objects properly.  If you
5841.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
5851.195Sperry	failure during the tool build, clean out all your tools
5861.195Sperry	objects and start again.
5871.195Sperry
5881.194Smrg20090325:
5891.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
5901.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
5911.194Smrg
5921.192Sskrll20090126:
5931.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
5941.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
5951.207Smbalmer	to avoid using the old assembly stub.
5961.192Sskrll
5971.191Sjoerg20090202:
5981.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
5991.191Sjoerg	detection.  It is recommented to rebuild the cache with
6001.191Sjoerg	``pkg_admin rebuild''.
6011.191Sjoerg
6021.184Schristos20090110:
6031.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
6041.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
6051.188Schristos	   This is needed even in the MODULAR kernel because there is
6061.188Schristos	   conditionally compiled code in rtsock.c.
6071.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
6081.184Schristos	   before installing.
6091.184Schristos	3. If you don't use build.sh and you build directly to root, and
6101.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
6111.184Schristos	   are installed properly, and start building libraries first libc
6121.184Schristos	   and libutil, install them and then continue building all the
6131.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
6141.184Schristos	   the new libraries are installed, you can restart the build.
6151.184Schristos	4. If you compile packages and you notice link time warnings,
6161.189Shubertf	   rebuild the required packages to update their shared libraries.
6171.189Shubertf	   Any package you rebuild will require rebuilding all the packages
6181.189Shubertf	   that depend on it.
6191.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
6201.186Schristos	   will be upgraded and it will not be backwards compatible.
6211.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
6221.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
6231.241Swiz	   for utmp.  You are better off removing the old files after
6241.190Sapb	   upgrading.  The automated clearing of /var/run during
6251.190Sapb	   boot, and the automated rotating of files in /var/log by
6261.190Sapb	   newsyslog(8), may mean that you do not have to remove the
6271.190Sapb	   files manually.
6281.190Sapb	7. The optional accounting file (/var/account/acct, see
6291.190Sapb	   accton(8)) has not been versioned, and will need to be
6301.190Sapb	   removed.  The automatic rotation of the accounting file by
6311.190Sapb	   /etc/daily limits the bad consequences of failure to remove
6321.190Sapb	   the file.
6331.196Sdholland	8. Application software that writes time_t to binary files on
6341.241Swiz	   disk will break or need attention.  Most notably: if you are
6351.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
6361.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
6371.185Sjmcneill
6381.183Spgoyette20081219:
6391.183Spgoyette	config(1) has been updated, and one of the files it creates -
6401.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
6411.183Spgoyette	(done automatically by build.sh) and then you need to rerun
6421.183Spgoyette	config on all kernel configuration files before rebuilding those
6431.183Spgoyette	kernels.
6441.183Spgoyette
6451.181Scube20081205:
6461.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
6471.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
6481.181Scube	set and will appear as extra files for MKX11=no update builds.
6491.178Slukem
6501.179Stsutsui20081122:
6511.182Stsutsui	On i386, various kernel options(4) in GENERIC including
6521.180Swiz	file systems have been disabled and moved into kernel modules.
6531.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
6541.179Stsutsui	following files as well as a new GENERIC kernel:
6551.179Stsutsui
6561.179Stsutsui	- build and install kernel modules from src/sys/modules
6571.179Stsutsui
6581.179Stsutsui	- install the latest bootloader, which will load a module
6591.180Swiz	  for the file system from which the kernel is loaded automatically
6601.179Stsutsui
6611.180Swiz	If you have to load your kernel from a file system which is not of
6621.180Swiz	the same type as the root file system, you have to load the necessary
6631.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
6641.179Stsutsui
6651.178Slukem20080827:
6661.178Slukem	If you built and installed a libc from sources between
6671.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
6681.178Slukem	which results in false errors reported by lint(1).
6691.178Slukem	Since this breaks the libc build itself, manual help is
6701.180Swiz	needed -- lint must be disabled temporarily, e.g.:
6711.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
6721.178Slukem
6731.177Schristos20080813:
6741.177Schristos	MKDEBUG build was broken because the .depend files did not know
6751.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
6761.177Schristos
6771.200Sdholland20080802:
6781.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
6791.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
6801.200Sdholland	for -current.
6811.200Sdholland
6821.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
6831.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
6841.200Sdholland	be recompiled.
6851.200Sdholland
6861.200Sdholland	One way to find affected pkgsrc packages:
6871.200Sdholland
6881.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
6891.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
6901.200Sdholland
6911.175Ssimonb20080731:
6921.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
6931.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
6941.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
6951.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
6961.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
6971.176Ssimonb	also requires the super block to be in the UFS2 format.  You
6981.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
6991.175Ssimonb
7001.174Slukem20080721:
7011.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
7021.174Slukem	isn't defined.
7031.174Slukem
7041.173Sfreza20080531:
7051.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
7061.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
7071.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
7081.241Swiz	won't work correctly.  The following sequence of commands:
7091.173Sfreza
7101.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
7111.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
7121.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
7131.173Sfreza
7141.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
7151.173Sfreza
7161.172Slukem20080503:
7171.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
7181.172Slukem
7191.171She20080521:
7201.171She	For a while, unprivileged UPDATE builds would fail to
7211.171She	succeed at the checkflist stage, complaining that
7221.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
7231.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
7241.171She	If you already hit this problem, update the .mk file,
7251.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
7261.171She
7271.174Slukem20080303:
7281.174Slukem	Linker warnings are now fatal if $WARNS>0.
7291.174Slukem
7301.170Schristos20080126:
7311.170Schristos	The posix_fadvise system call has been changed from an assembly
7321.241Swiz	stub, to a c file that calls an assembly stub.  You need to
7331.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
7341.170Schristos	avoid using the old assembly stub.
7351.170Schristos
7361.168Sjoerg20071209:
7371.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
7381.168Sjoerg	get ACPI errors before the attachment, please update your kernel
7391.169Swiz	configuration file appropriately or see GENERIC for more details.
7401.168Sjoerg
7411.166Sxtraeme20071115:
7421.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
7431.166Sxtraeme	argument specified in the kernel configuration file is not valid
7441.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
7451.241Swiz	rather than the EC address port.  Please update your kernel
7461.167Swiz	configuration file appropriately or see GENERIC for more details.
7471.166Sxtraeme
7481.165Sjmmv20071028:
7491.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
7501.165Sjmmv	You need to update any custom kernel configuration file you have
7511.165Sjmmv	to remove any references to pccons (which includes removing the
7521.165Sjmmv	now useless XSERVER option) and replace them with the correct
7531.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
7541.165Sjmmv	for more details.
7551.165Sjmmv
7561.164Sgdt20070913:
7571.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
7581.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
7591.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
7601.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
7611.164Sgdt	could not enumerate interfaces.  (These are noted because
7621.164Sgdt	normal kernel/userspace version matching hygiene is not
7631.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
7641.164Sgdt	and userland are from after 20070913.
7651.164Sgdt
7661.163Sjoerg20070703:
7671.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
7681.199Sdholland	calls the target-specific strip program, and the logic to pass
7691.199Sdholland	down STRIP from make has been removed.  This requires a
7701.199Sdholland	re-installation of tools.
7711.163Sjoerg
7721.161Sdsl20070422:
7731.161Sdsl	The way OS emulations lookup filenames inside the emulation root
7741.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
7751.161Sdsl	to userspace) namei() and lookup() directly check the emulation
7761.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
7771.167Swiz	root file system will be relative to that file system - unless they
7781.161Sdsl	start /../ this is useful when the emulated root is a real install
7791.161Sdsl	that has such links.
7801.161Sdsl	This might affect symlinks that have been added to reference outside
7811.161Sdsl	the emulated root.
7821.161Sdsl
7831.160Sjmcneill20070412:
7841.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
7851.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
7861.160Sjmcneill	example.
7871.160Sjmcneill
7881.159Sgdt20070319:
7891.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
7901.159Sgdt        on many platforms due to incorrect flags settings.  If you
7911.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
7921.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
7931.159Sgdt	rebuild of object files that might have been built
7941.159Sgdt	incorrectly, and ensure that you have at least
7951.159Sgdt	src/lib/libc/Makefile 1.130.
7961.159Sgdt
7971.241Swiz20070210:
7981.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
7991.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
8001.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
8011.158Sdbj        will allow dependencies on those files to get get rebuilt
8021.158Sdbj
8031.157Sapb20070209:
8041.157Sapb        The threading model was changed when the newlock2 branch
8051.157Sapb        was merged to NetBSD-current.  If you boot with a new
8061.157Sapb        kernel (version 4.99.10), then you also need a new pthread
8071.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
8081.157Sapb        an old kernel, then you need the old pthread library
8091.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
8101.157Sapb        the pthread library in sync, old threaded applications should
8111.157Sapb        continue to work with an old or new kernel.  Note that named(8)
8121.157Sapb	is the only threaded application in the base system.
8131.157Sapb
8141.154She20061214:
8151.154She	Following the move of string_to_flags() and flags_to_string()
8161.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
8171.154She	will need to do a "make cleandir" in
8181.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
8191.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
8201.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
8211.156She		as the installation images in distrib/
8221.154She	in order to excise stale references to the old stat_flags.h header
8231.154She	file in the ls sources -- stat_flags.h has been removed.
8241.154She
8251.152Schristos20061108:
8261.152Schristos	The configure script used in the src/tools/gcc compiler has been
8271.152Schristos	changed to indicate that our libc has ssp support built-in and
8281.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
8291.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
8301.152Schristos
8311.151Srpaulo20061009:
8321.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
8331.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
8341.151Srpaulo
8351.150Sbjh2120060814:
8361.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
8371.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
8381.150Sbjh21	kernel configuration for an example.  X servers from the last
8391.150Sbjh21	few years should cope.
8401.150Sbjh21
8411.149Schristos20060703:
8421.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
8431.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
8441.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
8451.149Schristos
8461.148Sdogcow20060627:
8471.148Sdogcow	socket(2) has changed, and its system call has been versioned.
8481.148Sdogcow	For userlands with the old version of socket(2), make sure that
8491.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
8501.148Sdogcow	errors will result.
8511.148Sdogcow
8521.1SabsHints for a more successful build:
8531.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8541.123Sjmc    Use build.sh, but do not use its "expert mode":
8551.132Sjmmv	This will automatically build the tools in the
8561.123Sjmc	   correct order, and it will keep the tools and the
8571.123Sjmc	   new build products from interfering with the running
8581.123Sjmc	   system.  This will allow you to ignore most of the
8591.123Sjmc	   other advice in this file.
8601.2Smrg    Build a new kernel first:
8611.2Smrg	This makes sure that any new system calls or features
8621.2Smrg	   expected by the new userland will be present.  This
8631.2Smrg	   helps to avoid critical errors when upgrading.
8641.1Sabs    Use object directories:
8651.1Sabs	This helps to keep stale object
8661.1Sabs	   files from polluting the build if a Makefile "forgets"
8671.1Sabs	   about one.  It also makes it easier to clean up after
8681.1Sabs	   a build.  It's also necessary if you want to use the
8691.1Sabs	   same source tree for multiple machines.
8701.123Sjmc	   To use object directories with build.sh:
8711.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
8721.123Sjmc	   To use object directories without using build.sh:
8731.1Sabs	    a) cd /usr/src ; make cleandir
8741.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
8751.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
8761.1Sabs	    d) cd /usr/src ; make build
8771.2Smrg	   Note that running "make obj" in a directory will create
8781.2Smrg	   in obj.$MACHINE directory.
8791.1Sabs    Build to a DESTDIR:
8801.123Sjmc	This helps to keep old installed files (especially libraries)
8811.123Sjmc	   from interfering with the new build.
8821.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
8831.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
8841.123Sjmc	   environment variable before running make build.  It should be
8851.123Sjmc	   set to the pathname of an initially empty directory.
8861.123Sjmc	   Problems: if you do not use build.sh, you might need to
8871.123Sjmc		update critical utilities without using DESTDIR since
8881.123Sjmc		nothing is executed from what is installed in DESTDIR.
8891.123Sjmc		(See critical utils, below.)
8901.1Sabs    Build often:
8911.1Sabs	This keeps critical utilities current enough to not choke
8921.1Sabs	on any other part of the source tree that depends on up to
8931.123Sjmc	date functionality.  If you use build.sh, you should not have
8941.123Sjmc	this problem.
8951.241Swiz
8961.1SabsWhat to do if things don't work:
8971.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8981.230StlsWhen things don't work there are usually a few things that commonly
8991.1Sabsshould be done.
9001.1Sabs    1)	make includes
9011.1Sabs	This should be done automatically by make build.
9021.1Sabs    2)  cd share/mk && make install
9031.1Sabs	Again, automatically done by make build.
9041.1Sabs
9051.1SabsFailsafe rebuild of a small part of the tree:
9061.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9071.1SabsTo make sure you rebuild something correctly you want to do
9081.1Sabssomething like the following:
9091.1Sabs    1)  Make sure the includes and .mk files are up to date.
9101.1Sabs    2)  Make sure any program used to build the particular
9111.1Sabs	utility is up to date.  (yacc, lex, etc...)
9121.1Sabs    3)  cd ...path/to/util...
9131.1Sabs	make cleandir
9141.1Sabs	rm ...all obj directories...
9151.1Sabs	make cleandir			# yes, again
9161.1Sabs	make obj
9171.1Sabs	make depend && make
9181.1Sabs
9191.1SabsFailsafe rebuild of the entire tree:
9201.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9211.1SabsIf you really want to make sure the source tree is clean and
9221.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
9231.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
9241.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
9251.1Sabs
9261.1Sabs---cut here---
9271.1Sabs#!/bin/sh
9281.1Sabs. /etc/mk.conf
9291.1Sabs
9301.58Slukemif [ -z $NETBSDSRCDIR ] ; then
9311.58Slukem    NETBSDSRCDIR=/usr/src
9321.1Sabsfi
9331.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
9341.1Sabs    echo Unable to find sources
9351.1Sabs    exit 1
9361.1Sabsfi
9371.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
9381.1Sabs
9391.1Sabsif [ -z $BSDOBJDIR ] ; then
9401.1Sabs    BSDOBJDIR=/usr/obj
9411.1Sabsfi
9421.1Sabsif [ -d $BSDOBJDIR ] ; then
9431.1Sabs    rm -rf $BSDOBJDIR
9441.1Sabsfi
9451.1Sabs
9461.58Slukemcd $NETBSDSRCDIR && make cleandir
9471.1Sabs
9481.1Sabs---cut here---
9491.1Sabs
9501.1SabsCritical utilities:
9511.1Sabs^^^^^^^^^^^^^^^^^^^
9521.3Sitojun	usr.bin/compile_et
9531.1Sabs	usr.bin/make
9541.1Sabs	usr.bin/yacc
9551.1Sabs	usr.bin/lex
9561.11Slukem	usr.bin/xlint
9571.142Sdrochner	usr.bin/config
9581.1Sabs
9591.34SsimonbOther problems and possible solutions:
9601.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9611.1SabsSymptom:Complaints involving a Makefile.
9621.17SerhFix:	Rebuild usr.bin/make:
9631.17Serh	cd usr.bin/make && make && make install
9641.111Ssimonb	Or, a failsafe method if that doesn't work:
9651.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
9661.17Serh
9671.1SabsFix:	Make sure .mk files are up to date.
9681.1Sabs	cd share/mk && make install
9691.2Smrg
9701.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
9711.142SdrochnerFix:	Rebuild usr.bin/config
9721.1Sabs
9731.1SabsSymptom:
9741.1SabsFix:	Rebuild usr.bin/yacc
9751.1Sabs
9761.1SabsSymptom:
9771.1SabsFix:	Rebuild usr.bin/lex
9781.1Sabs
9791.1SabsSymptom:
9801.1SabsFix:	rm /usr/lib/libbfd.a
9811.4Sitojun
9821.4SitojunSymptom:Obsolete intermediate files are used during compilation
9831.4SitojunFix:	Try the following sequence of commands in the directory in question.
9841.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
9851.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
9861.4Sitojun	may remain.  The command tries to clean everything up)
9871.5Swiz
9881.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
9891.207Smbalmer	pointer type
9901.5SwizFix:	Rebuild and install usr.bin/menuc
9911.12Sitojun
9921.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9931.12SitojunFix:	Build and install usr.bin/mklocale
9941.13Sdogcow
9951.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9961.13SdogcowFix:    Rebuild and install lib/libc
9971.13Sdogcow
9981.142SdrochnerSymptom:usr.bin/config fails to build.
9991.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
10001.13Sdogcow
10011.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
10021.19ScgdFix:    Rebuild and install lib/libc
10031.24Sabs
10041.24SabsSymptom:lint does not understand the '-X' option
10051.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
10061.223Sjoerg
10071.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
10081.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
10091.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
10101.257Sapb
10111.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
10121.257Sapb	No such file or directory.
10131.257SapbCause:	If a directory is created by mistake, then it is sometimes
10141.257Sapb	deleted from the CVS repository using administrative commands
10151.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
10161.257Sapb	contains references to a directory that has been deleted on the
10171.257Sapb	server in this way, then "cvs update" reports this error.
10181.257SapbFix:	Recursively delete the affected directory from your working tree
10191.257Sapb	and try the update again.
1020