UPDATING revision 1.313
11.313Smrg$NetBSD: UPDATING,v 1.313 2020/09/07 10:19:02 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.313Smrg20200907:
231.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
241.313Smrg	probably requires cleaning the tools/binutils.
251.313Smrg
261.311Smrg20200811:
271.312Smrg	GCC updates may require cleaning the objdir.  This may occur
281.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
291.312Smrg	GCC 9 upgrade.
301.311Smrg
311.309Schristos20200614:
321.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
331.310Schristos	should handle the migration
341.309Schristos
351.308Schristos20200601:
361.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
371.308Schristos	created in the build directories and need cleaning.
381.308Schristos
391.307Smrg20200311:
401.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
411.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
421.307Smrg
431.306Schristos20191118:
441.306Schristos	More architectures were switched to gcc8:
451.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
461.306Schristos	The same comments as in 20191022 apply.
471.306Schristos
481.305Smartin20191112:
491.305Smartin	The LLVM update requires a clean rebuild for all architectures using
501.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
511.305Smartin
521.304Smartin20191022:
531.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
541.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
551.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
561.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
571.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
581.304Smartin	daily builds and install that before doing the next in-place build.
591.304Smartin
601.303Smrg20191001:
611.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
621.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
631.303Smrg	directory, and also clean src/external/gpl3/gcc.
641.303Smrg
651.302Sriastrad20190903:
661.306Schristos	Files with names that coincide with existing files' names on
671.302Sriastrad	case-insensitive file systems were inadvertently committed, for
681.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
691.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
701.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
711.302Sriastrad	manually delete the following files in your DESTDIR (which is
721.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
731.302Sriastrad	them:
741.302Sriastrad
751.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
761.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
771.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
781.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
791.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
801.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
811.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
821.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
831.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
841.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
851.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
861.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
871.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
881.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
891.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
901.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
911.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
921.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
931.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
941.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
951.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
961.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
971.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
981.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
991.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
1001.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
1011.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
1021.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
1031.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
1041.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
1051.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
1061.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
1071.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
1081.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
1091.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
1101.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
1111.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
1121.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
1131.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
1141.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
1151.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
1161.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
1171.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
1181.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
1191.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
1201.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
1211.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
1221.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
1231.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
1241.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
1251.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
1261.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
1271.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
1281.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
1291.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
1301.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
1311.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
1321.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
1331.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
1341.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
1351.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
1361.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
1371.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
1381.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
1391.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
1401.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
1411.302Sriastrad
1421.302Sriastrad	We will re-import these radeon firmware images another way
1431.302Sriastrad	later.
1441.302Sriastrad
1451.301Smartin20190727:
1461.301Smartin	The uefi bootloader has gained tftp support and needs a clean
1471.301Smartin	build. If you do update builds, manually clean its object
1481.301Smartin	directory by something like:
1491.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
1501.301Smartin
1511.300Smartin20190723:
1521.300Smartin	The jemalloc allocator in libc is now build without extended
1531.300Smartin	debugging (for performance reasons). In update builds make sure
1541.300Smartin	to rebuild it completly, by removing all affected object files,
1551.300Smartin	including compat builds, something like:
1561.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
1571.300Smartin
1581.299Smrg20190207:
1591.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
1601.299Smrg
1611.298Smartin20180924:
1621.298Smartin	A newer OpenSSL version has been imported. If you are doing
1631.298Smartin	update builds, make sure to remove all old obj dirs, like:
1641.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
1651.298Smartin
1661.297Sjoerg20180717:
1671.297Sjoerg	On aarch64 int64_t and related types have changed from long long
1681.297Sjoerg	to long. This requires recompiling all C++ binaries.
1691.297Sjoerg
1701.296Smartin20180713:
1711.296Smartin	On amd64 and i386 static binaries are now build position
1721.296Smartin	independend. This requires recompilation of all object
1731.296Smartin	files used to create the crunched /rescue binary.
1741.296Smartin	Clean the rescue directory in your obj directory before
1751.296Smartin	doing an update build, otherwise linking will fail.
1761.296Smartin
1771.293Sjakllsch20180414:
1781.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
1791.293Sjakllsch	removal of tools/binutils objects directory may be required
1801.293Sjakllsch	to fix tools build failure.
1811.293Sjakllsch
1821.292Smrg20180311:
1831.292Smrg	bdftopcf was updated and may need cleaning in the
1841.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
1851.292Smrg	link errors.
1861.292Smrg
1871.291Smrg20180212:
1881.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
1891.291Smrg	any failure that looks like GCC or openssl is best handled by
1901.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
1911.291Smrg	is recommended if build failures occur.
1921.291Smrg
1931.288Smartin20171225:
1941.288Smartin	removal of the vadvise syscall requires manual removal of all
1951.288Smartin	associated files from the libc build object directory (including
1961.289Schristos	the .depend files) - a command like:
1971.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
1981.289Schristos	For architectures that support multiple "compat" binary targets,
1991.289Schristos	you'll need to cleanup both the regular libc directory and the
2001.290Smartin	compat ones (the above command will do that).
2011.288Smartin
2021.287Skre20171010:
2031.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
2041.287Skre	means that its objdir (or *.d and .depend at least) might need
2051.287Skre	to be manually removed - or a build done once without -u.
2061.287Skre
2071.286Smrg20170822:
2081.286Smrg	a new version of GMP has been imported and probably
2091.286Smrg	will break parts of builds related to themselves or GCC, both
2101.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2111.286Smrg	and MPC objdirs or build once without -u.
2121.286Smrg
2131.285Smrg20170816:
2141.285Smrg	a new version of MPFR and MPC have been imported and probably
2151.285Smrg	will break parts of builds related to themselves or GCC, both
2161.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2171.285Smrg	and MPC objdirs or build once without -u.
2181.285Smrg
2191.284Smartin20170402:
2201.284Smartin	a new version of dhcpcd has been imported, which does not support
2211.284Smartin	update builds from the previous version. Remove your
2221.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
2231.284Smartin
2241.281Sroy20170211:
2251.281Sroy	a new terminfo database has been imported.
2261.281Sroy	The structure of it has changed slightly from prior versions and
2271.281Sroy	an updated tic tool is required.
2281.281Sroy	If you build.sh, don't use -u
2291.281Sroy
2301.280Skre20170207:
2311.278Skre	various arch dependent libc/exect.S files were removed
2321.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
2331.279Skre	if it exists) or do a clean build.
2341.279Skre	(This is a bug in the make system, it should be corrected without
2351.279Skre	human intervention, but isn't.)
2361.278Skre
2371.277Smartin20170104:
2381.277Smartin	xinput build options have changed.
2391.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
2401.277Smartin	if you build.sh -u
2411.277Smartin
2421.276Smartin20170103:
2431.276Smartin	a new version of flex has been imported.
2441.276Smartin	Remove the file from obj (external/bsd/flex)
2451.276Smartin	if you build.sh -u
2461.276Smartin
2471.275Sspz20161014:
2481.275Sspz	a new version of OpenSSL has been imported.
2491.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
2501.275Sspz	if you build.sh -u
2511.275Sspz
2521.274Smartin20161009:
2531.274Smartin	a new version of dhcpcd has been imported with slightly changed
2541.274Smartin	build infrastructure. When doing a build.sh -u this requires
2551.274Smartin	pruning the external/bsd/dhcpcd objdir.
2561.274Smartin
2571.273Smrg20160914:
2581.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
2591.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
2601.273Smrg	and a clean objdir.
2611.273Smrg
2621.272Sdholland20160527:
2631.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
2641.272Sdholland	been enabled. (see the amd64 entry two down for further info)
2651.272Sdholland
2661.270Schristos20160418:
2671.270Schristos	libedit needs manual removal of all autogenerated files since
2681.271Schristos	some of them are not autogenerated anymore. Remember that there
2691.271Schristos	might be two copies of libedit if your platform builds "compat".
2701.270Schristos
2711.268Sriastrad20160410:
2721.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
2731.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
2741.268Sriastrad	executables, means all code, including executables and not just
2751.268Sriastrad	shared libraries, is position-independent and hence able to be
2761.268Sriastrad	relocated by ASLR, address space layout randomization.
2771.268Sriastrad
2781.268Sriastrad	The change was made in Makefile variables for compiler and
2791.268Sriastrad	linker flags, for which make(1) does not record dependencies,
2801.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
2811.268Sriastrad
2821.268Sriastrad	Partial rebuilds with some modified source files will likely
2831.268Sriastrad	fail when linking executables, since the linker refuses to mix
2841.268Sriastrad	position-independent code with position-dependent code in
2851.268Sriastrad	position-independent executables:
2861.268Sriastrad
2871.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
2881.268Sriastrad
2891.267Smrg20160401:
2901.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
2911.269Sdholland	Some people have found that cleandir is not sufficient, so if
2921.269Sdholland	in doubt delete the entire object directory tree for gcc.
2931.267Smrg
2941.266Saymeric20160306:
2951.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
2961.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
2971.265Saymeric	non-NetBSD hosts if linked with stale object files produced
2981.265Saymeric	while they included a non-NetBSD regex.h.
2991.265Saymeric	In any case, you should "make cleandir" at least these tools
3001.265Saymeric	before updating your toolchain.
3011.265Saymeric
3021.264Smartin20160125:
3031.264Smartin	Dtrace has been enabled by default on some architectures.
3041.264Smartin	When doing an update build, make sure to clean the etc/mtree
3051.264Smartin	object directory before starting the build - otherwise the
3061.264Smartin	needed directories in destdir will not be created.
3071.264Smartin	An easy way to do this is:
3081.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
3091.264Smartin
3101.263Sdholland20150818:
3111.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
3121.263Sdholland	again.
3131.263Sdholland
3141.262Schristos20150413:
3151.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
3161.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
3171.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
3181.262Schristos
3191.261Smartin20150404:
3201.261Smartin	Lint changes require a full rebuild of the tool, so make
3211.261Smartin	sure to build without -u option to build.sh, or manually
3221.261Smartin	do a make cleandir in src/tools/lint1 and
3231.261Smartin	src/usr.bin/xlint.
3241.261Smartin
3251.260Sskrll20150310:
3261.260Sskrll	Improvements to openssl for arm mean that update builds of
3271.260Sskrll	the openssl libraries will fail. A make cleandir in
3281.260Sskrll	external/bsd/openssl/lib is needed
3291.260Sskrll
3301.258Smartin20141026:
3311.259Smsaitoh	A mishap during the import of pppd may cause your corruption
3321.258Smartin	in your cvs directory if you happened to do a cvs update
3331.258Smartin	during a short period of time. To fix, just remove the
3341.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
3351.258Smartin	and let cvs restore it on next update.
3361.258Smartin
3371.256Sapb20140721:
3381.256Sapb	The src/external/mit/lua/src directory was accidentally created
3391.256Sapb	and then deleted in the CVS repository.  If you get errors like
3401.256Sapb
3411.256Sapb	cvs [update aborted]: cannot open directory
3421.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
3431.256Sapb
3441.256Sapb	then delete your local copy of that directory tree and try again.
3451.256Sapb
3461.255Sjoerg20140530:
3471.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
3481.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
3491.255Sjoerg
3501.251Smartin20140131:
3511.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
3521.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
3531.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
3541.251Smartin
3551.250Schristos20131227:
3561.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
3571.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
3581.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
3591.250Schristos	   statements to avoid being exposed.
3601.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
3611.250Schristos	   to make clean in libc
3621.250Schristos
3631.249Smrg20131129:
3641.249Smrg	The GMP sources were updated, and builds will likely fail without
3651.249Smrg	cleaning their build trees for both tools and in-tree, like below.
3661.249Smrg
3671.248Smrg20131128:
3681.248Smrg	The MPC and MPFR sources were updated, and builds may require their
3691.248Smrg	tools and in-tree directories cleaned for successful updates.
3701.248Smrg
3711.246Smartin20130605:
3721.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
3731.247Sspz	to IPSEC (and the older IPSEC version removed).
3741.247Sspz
3751.247Sspz20130605:
3761.246Smartin	Previous freetype installations eroneously installed private
3771.246Smartin	header files. If you are building against a non-empty $DESTDIR,
3781.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
3791.246Smartin
3801.245Smrg20130531:
3811.245Smrg	The xdm update may cause build failure due to xdm.man being
3821.245Smrg	in the obj tree.  Make sure to ensure any like this:
3831.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
3841.245Smrg	is fixed by deleting the xdm.man in the obj tree.
3851.245Smrg
3861.244Smrg20130530:
3871.244Smrg	Updates of many xsrc packages will leave old .pc files around.
3881.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
3891.244Smrg
3901.242Schristos20130301:
3911.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
3921.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
3931.242Schristos
3941.238Sdholland20120726:
3951.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
3961.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
3971.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
3981.241Swiz	some cases may succeed and install broken OpenSSL libraries that
3991.240Sdholland	cause third-party software to link incorrectly and/or crash.
4001.238Sdholland
4011.237Swiz20120507:
4021.241Swiz	The database schema for makemandb was changed.  You will
4031.237Swiz	need to update the database using 'makemandb -f' or wait
4041.237Swiz	for the next weekly run to fix it.
4051.237Swiz
4061.236Sbsh20120319:
4071.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
4081.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
4091.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
4101.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
4111.236Sbsh	mk.conf.
4121.236Sbsh
4131.235Sjoerg20120216:
4141.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
4151.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
4161.239Sdholland	and 20120216, daily and weekly could have created an unreadable
4171.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
4181.235Sjoerg	the next run of weekly will fix it.
4191.233Sjoerg
4201.232Schristos20111227:
4211.232Schristos	If you built between 20111225 and 20111227 you need to remove
4221.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
4231.232Schristos	bump has been reverted.
4241.232Schristos
4251.231Stls20111125:
4261.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
4271.231Stls	means it should no longer be explicitly listed in kernel
4281.231Stls	configuration files.  The line "pseudo-device rnd" should be
4291.231Stls	removed from any custom kernel config files users may have.
4301.231Stls
4311.230Stls20111119:
4321.230Stls	A problem with the datastructures used by the rndctl(8)
4331.230Stls	utility (pointers in datastructures in an array, making 32->64
4341.230Stls	bit compatibility very painful) has been fixed in a
4351.230Stls	non-backwards-compatible way.  If you replace your kernel,
4361.230Stls	replace your rndctl executable too.
4371.241Swiz
4381.229Sjym20111001:
4391.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
4401.229Sjym	changed and their new version is not backward compatible with the old
4411.241Swiz	one.  So ensure that all consumers of these functions (currently:
4421.229Sjym	quota2 code and its tests) are updated together with the new lib.
4431.229Sjym
4441.228Smrg20110817:
4451.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
4461.228Smrg	DESTDIR for them should be deleted before updating.
4471.228Smrg
4481.227Sriastrad20110806:
4491.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
4501.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
4511.227Sriastrad
4521.226Smrg20110805:
4531.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
4541.226Smrg	the tree to be cleaned.  Best to delete both objdir and
4551.226Smrg	DESTDIR before running this update.  So far, only the
4561.226Smrg	sparc64, mips and powerpc platforms have changed.
4571.226Smrg
4581.225Smatt20110803:
4591.241Swiz	The layout of external/public-domain/xz has changed.  To do an
4601.225Smatt	update build you will have to remove the contents of the OBJDIR
4611.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
4621.225Smatt	is now a directory.
4631.225Smatt
4641.223Sjoerg20110410:
4651.241Swiz	The configuration of src/tools/gcc has changed.  To do an
4661.224Sdholland	update build you have to clean both tools/binutils and
4671.224Sdholland	tools/gcc by hand.
4681.223Sjoerg
4691.222Splunky20110328:
4701.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
4711.241Swiz	ordering issues with "make all".  It may be necessary to remove
4721.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
4731.222Splunky	if your update build fails, as the "Xorg" entry there is now a
4741.222Splunky	directory.
4751.222Splunky
4761.220Sjoerg20110121:
4771.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
4781.220Sjoerg	the build of individual parts of the tree.  This is handled
4791.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
4801.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
4811.218Sjoerg
4821.217Sjruoho20101217:
4831.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
4841.241Swiz	by default.  It may be necessary to manually update passwd(5) and
4851.217Sjruoho	group(5) in order to make the program work with existing setups.
4861.217Sjruoho
4871.216Schristos20101125:
4881.216Schristos	The latest changes to setenv(3) dissallow setting environment
4891.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
4901.241Swiz	assumed that this was allowed.  Installing a new libc with an
4911.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
4921.216Schristos	break which affects the autoconf tests for dependency finding,
4931.216Schristos	so building gcc will end up printing:
4941.216Schristos	    checking dependency style of gcc... none
4951.216Schristos	    configure: error: no usable dependency style found
4961.216Schristos	Fix it by rebuilding and re-installing env.
4971.138Slukem
4981.215Smrg20101119:
4991.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
5001.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
5011.215Smrg	have any build problems with xsrc, or problems with mismatched
5021.215Smrg	versions between xorg-server and drivers.
5031.215Smrg
5041.213Sjmmv20100604:
5051.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
5061.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
5071.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
5081.213Sjmmv	trees by hand.
5091.213Sjmmv
5101.211Stnozaki20100522:
5111.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
5121.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
5131.212Smrg	build problems with xsrc.
5141.212Smrg
5151.212Smrg20100522:
5161.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
5171.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
5181.211Stnozaki
5191.210Schristos20100520:
5201.241Swiz	The location of the xkb compiled descriptions has changed.  Please
5211.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
5221.210Schristos
5231.209Snjoly20100222:
5241.209Snjoly	The shared objects file extension has been changed from .so to
5251.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
5261.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
5271.209Snjoly	your object directories.
5281.209Snjoly
5291.208Sroy20100204:
5301.208Sroy	The termcap database has been removed from the sources,
5311.208Sroy	but has not been marked obsolete so it is not removed
5321.208Sroy	from the system when upgrading.
5331.208Sroy	As such, you will need to remove them from your object
5341.208Sroy	and destination directories.
5351.208Sroy
5361.203Sdyoung20091101:
5371.205Sdholland        After updating, it may be necessary to make the 'cleandir'
5381.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
5391.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
5401.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
5411.203Sdyoung
5421.202Smrg20091001:
5431.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
5441.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
5451.206Sdholland
5461.206Sdholland20091001:
5471.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
5481.202Smrg	symlink, failing the build.  Delete the link, and the subdir
5491.202Smrg	it is in, and retry your build.
5501.202Smrg
5511.201Sdsl20090718:
5521.201Sdsl	libc build changed so that strchr() provides the extra entry
5531.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
5541.201Sdsl	may fail because the archive contains the unwanted index.o.
5551.201Sdsl	(Similarly for strrchr() and rindex().)
5561.201Sdsl
5571.198Smrg20090709:
5581.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
5591.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
5601.198Smrg
5611.197Smrg20090616:
5621.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
5631.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
5641.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
5651.197Smrg	subdirectory has been changed into a file, and this needs to
5661.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
5671.197Smrg
5681.195Sperry20090501:
5691.195Sperry	Several new functions were added to string.h/libc, and this
5701.195Sperry	can cause autoconf problems during the tool build for people
5711.241Swiz	who fail to clean out their tools objects properly.  If you
5721.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
5731.195Sperry	failure during the tool build, clean out all your tools
5741.195Sperry	objects and start again.
5751.195Sperry
5761.194Smrg20090325:
5771.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
5781.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
5791.194Smrg
5801.192Sskrll20090126:
5811.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
5821.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
5831.207Smbalmer	to avoid using the old assembly stub.
5841.192Sskrll
5851.191Sjoerg20090202:
5861.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
5871.191Sjoerg	detection.  It is recommented to rebuild the cache with
5881.191Sjoerg	``pkg_admin rebuild''.
5891.191Sjoerg
5901.184Schristos20090110:
5911.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
5921.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
5931.188Schristos	   This is needed even in the MODULAR kernel because there is
5941.188Schristos	   conditionally compiled code in rtsock.c.
5951.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
5961.184Schristos	   before installing.
5971.184Schristos	3. If you don't use build.sh and you build directly to root, and
5981.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
5991.184Schristos	   are installed properly, and start building libraries first libc
6001.184Schristos	   and libutil, install them and then continue building all the
6011.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
6021.184Schristos	   the new libraries are installed, you can restart the build.
6031.184Schristos	4. If you compile packages and you notice link time warnings,
6041.189Shubertf	   rebuild the required packages to update their shared libraries.
6051.189Shubertf	   Any package you rebuild will require rebuilding all the packages
6061.189Shubertf	   that depend on it.
6071.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
6081.186Schristos	   will be upgraded and it will not be backwards compatible.
6091.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
6101.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
6111.241Swiz	   for utmp.  You are better off removing the old files after
6121.190Sapb	   upgrading.  The automated clearing of /var/run during
6131.190Sapb	   boot, and the automated rotating of files in /var/log by
6141.190Sapb	   newsyslog(8), may mean that you do not have to remove the
6151.190Sapb	   files manually.
6161.190Sapb	7. The optional accounting file (/var/account/acct, see
6171.190Sapb	   accton(8)) has not been versioned, and will need to be
6181.190Sapb	   removed.  The automatic rotation of the accounting file by
6191.190Sapb	   /etc/daily limits the bad consequences of failure to remove
6201.190Sapb	   the file.
6211.196Sdholland	8. Application software that writes time_t to binary files on
6221.241Swiz	   disk will break or need attention.  Most notably: if you are
6231.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
6241.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
6251.185Sjmcneill
6261.183Spgoyette20081219:
6271.183Spgoyette	config(1) has been updated, and one of the files it creates -
6281.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
6291.183Spgoyette	(done automatically by build.sh) and then you need to rerun
6301.183Spgoyette	config on all kernel configuration files before rebuilding those
6311.183Spgoyette	kernels.
6321.183Spgoyette
6331.181Scube20081205:
6341.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
6351.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
6361.181Scube	set and will appear as extra files for MKX11=no update builds.
6371.178Slukem
6381.179Stsutsui20081122:
6391.182Stsutsui	On i386, various kernel options(4) in GENERIC including
6401.180Swiz	file systems have been disabled and moved into kernel modules.
6411.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
6421.179Stsutsui	following files as well as a new GENERIC kernel:
6431.179Stsutsui
6441.179Stsutsui	- build and install kernel modules from src/sys/modules
6451.179Stsutsui
6461.179Stsutsui	- install the latest bootloader, which will load a module
6471.180Swiz	  for the file system from which the kernel is loaded automatically
6481.179Stsutsui
6491.180Swiz	If you have to load your kernel from a file system which is not of
6501.180Swiz	the same type as the root file system, you have to load the necessary
6511.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
6521.179Stsutsui
6531.178Slukem20080827:
6541.178Slukem	If you built and installed a libc from sources between
6551.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
6561.178Slukem	which results in false errors reported by lint(1).
6571.178Slukem	Since this breaks the libc build itself, manual help is
6581.180Swiz	needed -- lint must be disabled temporarily, e.g.:
6591.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
6601.178Slukem
6611.177Schristos20080813:
6621.177Schristos	MKDEBUG build was broken because the .depend files did not know
6631.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
6641.177Schristos
6651.200Sdholland20080802:
6661.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
6671.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
6681.200Sdholland	for -current.
6691.200Sdholland
6701.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
6711.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
6721.200Sdholland	be recompiled.
6731.200Sdholland
6741.200Sdholland	One way to find affected pkgsrc packages:
6751.200Sdholland
6761.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
6771.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
6781.200Sdholland
6791.175Ssimonb20080731:
6801.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
6811.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
6821.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
6831.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
6841.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
6851.176Ssimonb	also requires the super block to be in the UFS2 format.  You
6861.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
6871.175Ssimonb
6881.174Slukem20080721:
6891.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
6901.174Slukem	isn't defined.
6911.174Slukem
6921.173Sfreza20080531:
6931.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
6941.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
6951.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
6961.241Swiz	won't work correctly.  The following sequence of commands:
6971.173Sfreza
6981.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
6991.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
7001.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
7011.173Sfreza
7021.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
7031.173Sfreza
7041.172Slukem20080503:
7051.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
7061.172Slukem
7071.171She20080521:
7081.171She	For a while, unprivileged UPDATE builds would fail to
7091.171She	succeed at the checkflist stage, complaining that
7101.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
7111.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
7121.171She	If you already hit this problem, update the .mk file,
7131.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
7141.171She
7151.174Slukem20080303:
7161.174Slukem	Linker warnings are now fatal if $WARNS>0.
7171.174Slukem
7181.170Schristos20080126:
7191.170Schristos	The posix_fadvise system call has been changed from an assembly
7201.241Swiz	stub, to a c file that calls an assembly stub.  You need to
7211.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
7221.170Schristos	avoid using the old assembly stub.
7231.170Schristos
7241.168Sjoerg20071209:
7251.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
7261.168Sjoerg	get ACPI errors before the attachment, please update your kernel
7271.169Swiz	configuration file appropriately or see GENERIC for more details.
7281.168Sjoerg
7291.166Sxtraeme20071115:
7301.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
7311.166Sxtraeme	argument specified in the kernel configuration file is not valid
7321.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
7331.241Swiz	rather than the EC address port.  Please update your kernel
7341.167Swiz	configuration file appropriately or see GENERIC for more details.
7351.166Sxtraeme
7361.165Sjmmv20071028:
7371.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
7381.165Sjmmv	You need to update any custom kernel configuration file you have
7391.165Sjmmv	to remove any references to pccons (which includes removing the
7401.165Sjmmv	now useless XSERVER option) and replace them with the correct
7411.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
7421.165Sjmmv	for more details.
7431.165Sjmmv
7441.164Sgdt20070913:
7451.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
7461.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
7471.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
7481.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
7491.164Sgdt	could not enumerate interfaces.  (These are noted because
7501.164Sgdt	normal kernel/userspace version matching hygiene is not
7511.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
7521.164Sgdt	and userland are from after 20070913.
7531.164Sgdt
7541.163Sjoerg20070703:
7551.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
7561.199Sdholland	calls the target-specific strip program, and the logic to pass
7571.199Sdholland	down STRIP from make has been removed.  This requires a
7581.199Sdholland	re-installation of tools.
7591.163Sjoerg
7601.161Sdsl20070422:
7611.161Sdsl	The way OS emulations lookup filenames inside the emulation root
7621.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
7631.161Sdsl	to userspace) namei() and lookup() directly check the emulation
7641.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
7651.167Swiz	root file system will be relative to that file system - unless they
7661.161Sdsl	start /../ this is useful when the emulated root is a real install
7671.161Sdsl	that has such links.
7681.161Sdsl	This might affect symlinks that have been added to reference outside
7691.161Sdsl	the emulated root.
7701.161Sdsl
7711.160Sjmcneill20070412:
7721.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
7731.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
7741.160Sjmcneill	example.
7751.160Sjmcneill
7761.159Sgdt20070319:
7771.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
7781.159Sgdt        on many platforms due to incorrect flags settings.  If you
7791.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
7801.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
7811.159Sgdt	rebuild of object files that might have been built
7821.159Sgdt	incorrectly, and ensure that you have at least
7831.159Sgdt	src/lib/libc/Makefile 1.130.
7841.159Sgdt
7851.241Swiz20070210:
7861.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
7871.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
7881.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
7891.158Sdbj        will allow dependencies on those files to get get rebuilt
7901.158Sdbj
7911.157Sapb20070209:
7921.157Sapb        The threading model was changed when the newlock2 branch
7931.157Sapb        was merged to NetBSD-current.  If you boot with a new
7941.157Sapb        kernel (version 4.99.10), then you also need a new pthread
7951.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
7961.157Sapb        an old kernel, then you need the old pthread library
7971.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
7981.157Sapb        the pthread library in sync, old threaded applications should
7991.157Sapb        continue to work with an old or new kernel.  Note that named(8)
8001.157Sapb	is the only threaded application in the base system.
8011.157Sapb
8021.154She20061214:
8031.154She	Following the move of string_to_flags() and flags_to_string()
8041.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
8051.154She	will need to do a "make cleandir" in
8061.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
8071.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
8081.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
8091.156She		as the installation images in distrib/
8101.154She	in order to excise stale references to the old stat_flags.h header
8111.154She	file in the ls sources -- stat_flags.h has been removed.
8121.154She
8131.152Schristos20061108:
8141.152Schristos	The configure script used in the src/tools/gcc compiler has been
8151.152Schristos	changed to indicate that our libc has ssp support built-in and
8161.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
8171.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
8181.152Schristos
8191.151Srpaulo20061009:
8201.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
8211.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
8221.151Srpaulo
8231.150Sbjh2120060814:
8241.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
8251.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
8261.150Sbjh21	kernel configuration for an example.  X servers from the last
8271.150Sbjh21	few years should cope.
8281.150Sbjh21
8291.149Schristos20060703:
8301.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
8311.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
8321.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
8331.149Schristos
8341.148Sdogcow20060627:
8351.148Sdogcow	socket(2) has changed, and its system call has been versioned.
8361.148Sdogcow	For userlands with the old version of socket(2), make sure that
8371.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
8381.148Sdogcow	errors will result.
8391.148Sdogcow
8401.1SabsHints for a more successful build:
8411.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8421.123Sjmc    Use build.sh, but do not use its "expert mode":
8431.132Sjmmv	This will automatically build the tools in the
8441.123Sjmc	   correct order, and it will keep the tools and the
8451.123Sjmc	   new build products from interfering with the running
8461.123Sjmc	   system.  This will allow you to ignore most of the
8471.123Sjmc	   other advice in this file.
8481.2Smrg    Build a new kernel first:
8491.2Smrg	This makes sure that any new system calls or features
8501.2Smrg	   expected by the new userland will be present.  This
8511.2Smrg	   helps to avoid critical errors when upgrading.
8521.1Sabs    Use object directories:
8531.1Sabs	This helps to keep stale object
8541.1Sabs	   files from polluting the build if a Makefile "forgets"
8551.1Sabs	   about one.  It also makes it easier to clean up after
8561.1Sabs	   a build.  It's also necessary if you want to use the
8571.1Sabs	   same source tree for multiple machines.
8581.123Sjmc	   To use object directories with build.sh:
8591.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
8601.123Sjmc	   To use object directories without using build.sh:
8611.1Sabs	    a) cd /usr/src ; make cleandir
8621.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
8631.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
8641.1Sabs	    d) cd /usr/src ; make build
8651.2Smrg	   Note that running "make obj" in a directory will create
8661.2Smrg	   in obj.$MACHINE directory.
8671.1Sabs    Build to a DESTDIR:
8681.123Sjmc	This helps to keep old installed files (especially libraries)
8691.123Sjmc	   from interfering with the new build.
8701.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
8711.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
8721.123Sjmc	   environment variable before running make build.  It should be
8731.123Sjmc	   set to the pathname of an initially empty directory.
8741.123Sjmc	   Problems: if you do not use build.sh, you might need to
8751.123Sjmc		update critical utilities without using DESTDIR since
8761.123Sjmc		nothing is executed from what is installed in DESTDIR.
8771.123Sjmc		(See critical utils, below.)
8781.1Sabs    Build often:
8791.1Sabs	This keeps critical utilities current enough to not choke
8801.1Sabs	on any other part of the source tree that depends on up to
8811.123Sjmc	date functionality.  If you use build.sh, you should not have
8821.123Sjmc	this problem.
8831.241Swiz
8841.1SabsWhat to do if things don't work:
8851.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8861.230StlsWhen things don't work there are usually a few things that commonly
8871.1Sabsshould be done.
8881.1Sabs    1)	make includes
8891.1Sabs	This should be done automatically by make build.
8901.1Sabs    2)  cd share/mk && make install
8911.1Sabs	Again, automatically done by make build.
8921.1Sabs
8931.1SabsFailsafe rebuild of a small part of the tree:
8941.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8951.1SabsTo make sure you rebuild something correctly you want to do
8961.1Sabssomething like the following:
8971.1Sabs    1)  Make sure the includes and .mk files are up to date.
8981.1Sabs    2)  Make sure any program used to build the particular
8991.1Sabs	utility is up to date.  (yacc, lex, etc...)
9001.1Sabs    3)  cd ...path/to/util...
9011.1Sabs	make cleandir
9021.1Sabs	rm ...all obj directories...
9031.1Sabs	make cleandir			# yes, again
9041.1Sabs	make obj
9051.1Sabs	make depend && make
9061.1Sabs
9071.1SabsFailsafe rebuild of the entire tree:
9081.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9091.1SabsIf you really want to make sure the source tree is clean and
9101.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
9111.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
9121.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
9131.1Sabs
9141.1Sabs---cut here---
9151.1Sabs#!/bin/sh
9161.1Sabs. /etc/mk.conf
9171.1Sabs
9181.58Slukemif [ -z $NETBSDSRCDIR ] ; then
9191.58Slukem    NETBSDSRCDIR=/usr/src
9201.1Sabsfi
9211.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
9221.1Sabs    echo Unable to find sources
9231.1Sabs    exit 1
9241.1Sabsfi
9251.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
9261.1Sabs
9271.1Sabsif [ -z $BSDOBJDIR ] ; then
9281.1Sabs    BSDOBJDIR=/usr/obj
9291.1Sabsfi
9301.1Sabsif [ -d $BSDOBJDIR ] ; then
9311.1Sabs    rm -rf $BSDOBJDIR
9321.1Sabsfi
9331.1Sabs
9341.58Slukemcd $NETBSDSRCDIR && make cleandir
9351.1Sabs
9361.1Sabs---cut here---
9371.1Sabs
9381.1SabsCritical utilities:
9391.1Sabs^^^^^^^^^^^^^^^^^^^
9401.3Sitojun	usr.bin/compile_et
9411.1Sabs	usr.bin/make
9421.1Sabs	usr.bin/yacc
9431.1Sabs	usr.bin/lex
9441.11Slukem	usr.bin/xlint
9451.142Sdrochner	usr.bin/config
9461.1Sabs
9471.34SsimonbOther problems and possible solutions:
9481.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9491.1SabsSymptom:Complaints involving a Makefile.
9501.17SerhFix:	Rebuild usr.bin/make:
9511.17Serh	cd usr.bin/make && make && make install
9521.111Ssimonb	Or, a failsafe method if that doesn't work:
9531.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
9541.17Serh
9551.1SabsFix:	Make sure .mk files are up to date.
9561.1Sabs	cd share/mk && make install
9571.2Smrg
9581.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
9591.142SdrochnerFix:	Rebuild usr.bin/config
9601.1Sabs
9611.1SabsSymptom:
9621.1SabsFix:	Rebuild usr.bin/yacc
9631.1Sabs
9641.1SabsSymptom:
9651.1SabsFix:	Rebuild usr.bin/lex
9661.1Sabs
9671.1SabsSymptom:
9681.1SabsFix:	rm /usr/lib/libbfd.a
9691.4Sitojun
9701.4SitojunSymptom:Obsolete intermediate files are used during compilation
9711.4SitojunFix:	Try the following sequence of commands in the directory in question.
9721.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
9731.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
9741.4Sitojun	may remain.  The command tries to clean everything up)
9751.5Swiz
9761.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
9771.207Smbalmer	pointer type
9781.5SwizFix:	Rebuild and install usr.bin/menuc
9791.12Sitojun
9801.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9811.12SitojunFix:	Build and install usr.bin/mklocale
9821.13Sdogcow
9831.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9841.13SdogcowFix:    Rebuild and install lib/libc
9851.13Sdogcow
9861.142SdrochnerSymptom:usr.bin/config fails to build.
9871.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9881.13Sdogcow
9891.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9901.19ScgdFix:    Rebuild and install lib/libc
9911.24Sabs
9921.24SabsSymptom:lint does not understand the '-X' option
9931.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
9941.223Sjoerg
9951.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
9961.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
9971.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
9981.257Sapb
9991.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
10001.257Sapb	No such file or directory.
10011.257SapbCause:	If a directory is created by mistake, then it is sometimes
10021.257Sapb	deleted from the CVS repository using administrative commands
10031.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
10041.257Sapb	contains references to a directory that has been deleted on the
10051.257Sapb	server in this way, then "cvs update" reports this error.
10061.257SapbFix:	Recursively delete the affected directory from your working tree
10071.257Sapb	and try the update again.
1008