UPDATING revision 1.315
11.315Smrg$NetBSD: UPDATING,v 1.315 2020/09/26 08:02:35 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.315Smrg20200925:
231.315Smrg	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
241.315Smrg	in both the tools and external dirs.
251.315Smrg
261.314Smrg20200912:
271.314Smrg	GCC 9 has arrived for Arm and x86 platforms, and will be coming
281.314Smrg	for several more, as will binutils 2.34.  Clean as required.
291.314Smrg
301.313Smrg20200907:
311.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
321.313Smrg	probably requires cleaning the tools/binutils.
331.313Smrg
341.311Smrg20200811:
351.312Smrg	GCC updates may require cleaning the objdir.  This may occur
361.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
371.312Smrg	GCC 9 upgrade.
381.311Smrg
391.309Schristos20200614:
401.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
411.310Schristos	should handle the migration
421.309Schristos
431.308Schristos20200601:
441.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
451.308Schristos	created in the build directories and need cleaning.
461.308Schristos
471.307Smrg20200311:
481.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
491.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
501.307Smrg
511.306Schristos20191118:
521.306Schristos	More architectures were switched to gcc8:
531.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
541.306Schristos	The same comments as in 20191022 apply.
551.306Schristos
561.305Smartin20191112:
571.305Smartin	The LLVM update requires a clean rebuild for all architectures using
581.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
591.305Smartin
601.304Smartin20191022:
611.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
621.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
631.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
641.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
651.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
661.304Smartin	daily builds and install that before doing the next in-place build.
671.304Smartin
681.303Smrg20191001:
691.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
701.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
711.303Smrg	directory, and also clean src/external/gpl3/gcc.
721.303Smrg
731.302Sriastrad20190903:
741.306Schristos	Files with names that coincide with existing files' names on
751.302Sriastrad	case-insensitive file systems were inadvertently committed, for
761.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
771.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
781.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
791.302Sriastrad	manually delete the following files in your DESTDIR (which is
801.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
811.302Sriastrad	them:
821.302Sriastrad
831.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
841.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
851.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
861.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
871.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
881.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
891.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
901.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
911.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
921.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
931.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
941.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
951.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
961.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
971.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
981.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
991.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
1001.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
1011.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
1021.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
1031.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
1041.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
1051.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
1061.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
1071.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
1081.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
1091.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
1101.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
1111.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
1121.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
1131.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
1141.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
1151.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
1161.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
1171.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
1181.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
1191.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
1201.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
1211.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
1221.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
1231.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
1241.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
1251.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
1261.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
1271.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
1281.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
1291.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
1301.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
1311.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
1321.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
1331.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
1341.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
1351.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
1361.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
1371.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
1381.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
1391.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
1401.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
1411.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
1421.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
1431.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
1441.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
1451.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
1461.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
1471.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
1481.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
1491.302Sriastrad
1501.302Sriastrad	We will re-import these radeon firmware images another way
1511.302Sriastrad	later.
1521.302Sriastrad
1531.301Smartin20190727:
1541.301Smartin	The uefi bootloader has gained tftp support and needs a clean
1551.301Smartin	build. If you do update builds, manually clean its object
1561.301Smartin	directory by something like:
1571.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
1581.301Smartin
1591.300Smartin20190723:
1601.300Smartin	The jemalloc allocator in libc is now build without extended
1611.300Smartin	debugging (for performance reasons). In update builds make sure
1621.300Smartin	to rebuild it completly, by removing all affected object files,
1631.300Smartin	including compat builds, something like:
1641.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
1651.300Smartin
1661.299Smrg20190207:
1671.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
1681.299Smrg
1691.298Smartin20180924:
1701.298Smartin	A newer OpenSSL version has been imported. If you are doing
1711.298Smartin	update builds, make sure to remove all old obj dirs, like:
1721.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
1731.298Smartin
1741.297Sjoerg20180717:
1751.297Sjoerg	On aarch64 int64_t and related types have changed from long long
1761.297Sjoerg	to long. This requires recompiling all C++ binaries.
1771.297Sjoerg
1781.296Smartin20180713:
1791.296Smartin	On amd64 and i386 static binaries are now build position
1801.296Smartin	independend. This requires recompilation of all object
1811.296Smartin	files used to create the crunched /rescue binary.
1821.296Smartin	Clean the rescue directory in your obj directory before
1831.296Smartin	doing an update build, otherwise linking will fail.
1841.296Smartin
1851.293Sjakllsch20180414:
1861.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
1871.293Sjakllsch	removal of tools/binutils objects directory may be required
1881.293Sjakllsch	to fix tools build failure.
1891.293Sjakllsch
1901.292Smrg20180311:
1911.292Smrg	bdftopcf was updated and may need cleaning in the
1921.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
1931.292Smrg	link errors.
1941.292Smrg
1951.291Smrg20180212:
1961.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
1971.291Smrg	any failure that looks like GCC or openssl is best handled by
1981.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
1991.291Smrg	is recommended if build failures occur.
2001.291Smrg
2011.288Smartin20171225:
2021.288Smartin	removal of the vadvise syscall requires manual removal of all
2031.288Smartin	associated files from the libc build object directory (including
2041.289Schristos	the .depend files) - a command like:
2051.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
2061.289Schristos	For architectures that support multiple "compat" binary targets,
2071.289Schristos	you'll need to cleanup both the regular libc directory and the
2081.290Smartin	compat ones (the above command will do that).
2091.288Smartin
2101.287Skre20171010:
2111.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
2121.287Skre	means that its objdir (or *.d and .depend at least) might need
2131.287Skre	to be manually removed - or a build done once without -u.
2141.287Skre
2151.286Smrg20170822:
2161.286Smrg	a new version of GMP has been imported and probably
2171.286Smrg	will break parts of builds related to themselves or GCC, both
2181.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2191.286Smrg	and MPC objdirs or build once without -u.
2201.286Smrg
2211.285Smrg20170816:
2221.285Smrg	a new version of MPFR and MPC have been imported and probably
2231.285Smrg	will break parts of builds related to themselves or GCC, both
2241.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2251.285Smrg	and MPC objdirs or build once without -u.
2261.285Smrg
2271.284Smartin20170402:
2281.284Smartin	a new version of dhcpcd has been imported, which does not support
2291.284Smartin	update builds from the previous version. Remove your
2301.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
2311.284Smartin
2321.281Sroy20170211:
2331.281Sroy	a new terminfo database has been imported.
2341.281Sroy	The structure of it has changed slightly from prior versions and
2351.281Sroy	an updated tic tool is required.
2361.281Sroy	If you build.sh, don't use -u
2371.281Sroy
2381.280Skre20170207:
2391.278Skre	various arch dependent libc/exect.S files were removed
2401.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
2411.279Skre	if it exists) or do a clean build.
2421.279Skre	(This is a bug in the make system, it should be corrected without
2431.279Skre	human intervention, but isn't.)
2441.278Skre
2451.277Smartin20170104:
2461.277Smartin	xinput build options have changed.
2471.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
2481.277Smartin	if you build.sh -u
2491.277Smartin
2501.276Smartin20170103:
2511.276Smartin	a new version of flex has been imported.
2521.276Smartin	Remove the file from obj (external/bsd/flex)
2531.276Smartin	if you build.sh -u
2541.276Smartin
2551.275Sspz20161014:
2561.275Sspz	a new version of OpenSSL has been imported.
2571.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
2581.275Sspz	if you build.sh -u
2591.275Sspz
2601.274Smartin20161009:
2611.274Smartin	a new version of dhcpcd has been imported with slightly changed
2621.274Smartin	build infrastructure. When doing a build.sh -u this requires
2631.274Smartin	pruning the external/bsd/dhcpcd objdir.
2641.274Smartin
2651.273Smrg20160914:
2661.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
2671.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
2681.273Smrg	and a clean objdir.
2691.273Smrg
2701.272Sdholland20160527:
2711.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
2721.272Sdholland	been enabled. (see the amd64 entry two down for further info)
2731.272Sdholland
2741.270Schristos20160418:
2751.270Schristos	libedit needs manual removal of all autogenerated files since
2761.271Schristos	some of them are not autogenerated anymore. Remember that there
2771.271Schristos	might be two copies of libedit if your platform builds "compat".
2781.270Schristos
2791.268Sriastrad20160410:
2801.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
2811.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
2821.268Sriastrad	executables, means all code, including executables and not just
2831.268Sriastrad	shared libraries, is position-independent and hence able to be
2841.268Sriastrad	relocated by ASLR, address space layout randomization.
2851.268Sriastrad
2861.268Sriastrad	The change was made in Makefile variables for compiler and
2871.268Sriastrad	linker flags, for which make(1) does not record dependencies,
2881.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
2891.268Sriastrad
2901.268Sriastrad	Partial rebuilds with some modified source files will likely
2911.268Sriastrad	fail when linking executables, since the linker refuses to mix
2921.268Sriastrad	position-independent code with position-dependent code in
2931.268Sriastrad	position-independent executables:
2941.268Sriastrad
2951.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
2961.268Sriastrad
2971.267Smrg20160401:
2981.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
2991.269Sdholland	Some people have found that cleandir is not sufficient, so if
3001.269Sdholland	in doubt delete the entire object directory tree for gcc.
3011.267Smrg
3021.266Saymeric20160306:
3031.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
3041.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
3051.265Saymeric	non-NetBSD hosts if linked with stale object files produced
3061.265Saymeric	while they included a non-NetBSD regex.h.
3071.265Saymeric	In any case, you should "make cleandir" at least these tools
3081.265Saymeric	before updating your toolchain.
3091.265Saymeric
3101.264Smartin20160125:
3111.264Smartin	Dtrace has been enabled by default on some architectures.
3121.264Smartin	When doing an update build, make sure to clean the etc/mtree
3131.264Smartin	object directory before starting the build - otherwise the
3141.264Smartin	needed directories in destdir will not be created.
3151.264Smartin	An easy way to do this is:
3161.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
3171.264Smartin
3181.263Sdholland20150818:
3191.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
3201.263Sdholland	again.
3211.263Sdholland
3221.262Schristos20150413:
3231.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
3241.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
3251.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
3261.262Schristos
3271.261Smartin20150404:
3281.261Smartin	Lint changes require a full rebuild of the tool, so make
3291.261Smartin	sure to build without -u option to build.sh, or manually
3301.261Smartin	do a make cleandir in src/tools/lint1 and
3311.261Smartin	src/usr.bin/xlint.
3321.261Smartin
3331.260Sskrll20150310:
3341.260Sskrll	Improvements to openssl for arm mean that update builds of
3351.260Sskrll	the openssl libraries will fail. A make cleandir in
3361.260Sskrll	external/bsd/openssl/lib is needed
3371.260Sskrll
3381.258Smartin20141026:
3391.259Smsaitoh	A mishap during the import of pppd may cause your corruption
3401.258Smartin	in your cvs directory if you happened to do a cvs update
3411.258Smartin	during a short period of time. To fix, just remove the
3421.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
3431.258Smartin	and let cvs restore it on next update.
3441.258Smartin
3451.256Sapb20140721:
3461.256Sapb	The src/external/mit/lua/src directory was accidentally created
3471.256Sapb	and then deleted in the CVS repository.  If you get errors like
3481.256Sapb
3491.256Sapb	cvs [update aborted]: cannot open directory
3501.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
3511.256Sapb
3521.256Sapb	then delete your local copy of that directory tree and try again.
3531.256Sapb
3541.255Sjoerg20140530:
3551.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
3561.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
3571.255Sjoerg
3581.251Smartin20140131:
3591.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
3601.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
3611.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
3621.251Smartin
3631.250Schristos20131227:
3641.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
3651.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
3661.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
3671.250Schristos	   statements to avoid being exposed.
3681.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
3691.250Schristos	   to make clean in libc
3701.250Schristos
3711.249Smrg20131129:
3721.249Smrg	The GMP sources were updated, and builds will likely fail without
3731.249Smrg	cleaning their build trees for both tools and in-tree, like below.
3741.249Smrg
3751.248Smrg20131128:
3761.248Smrg	The MPC and MPFR sources were updated, and builds may require their
3771.248Smrg	tools and in-tree directories cleaned for successful updates.
3781.248Smrg
3791.246Smartin20130605:
3801.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
3811.247Sspz	to IPSEC (and the older IPSEC version removed).
3821.247Sspz
3831.247Sspz20130605:
3841.246Smartin	Previous freetype installations eroneously installed private
3851.246Smartin	header files. If you are building against a non-empty $DESTDIR,
3861.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
3871.246Smartin
3881.245Smrg20130531:
3891.245Smrg	The xdm update may cause build failure due to xdm.man being
3901.245Smrg	in the obj tree.  Make sure to ensure any like this:
3911.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
3921.245Smrg	is fixed by deleting the xdm.man in the obj tree.
3931.245Smrg
3941.244Smrg20130530:
3951.244Smrg	Updates of many xsrc packages will leave old .pc files around.
3961.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
3971.244Smrg
3981.242Schristos20130301:
3991.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
4001.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
4011.242Schristos
4021.238Sdholland20120726:
4031.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
4041.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
4051.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
4061.241Swiz	some cases may succeed and install broken OpenSSL libraries that
4071.240Sdholland	cause third-party software to link incorrectly and/or crash.
4081.238Sdholland
4091.237Swiz20120507:
4101.241Swiz	The database schema for makemandb was changed.  You will
4111.237Swiz	need to update the database using 'makemandb -f' or wait
4121.237Swiz	for the next weekly run to fix it.
4131.237Swiz
4141.236Sbsh20120319:
4151.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
4161.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
4171.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
4181.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
4191.236Sbsh	mk.conf.
4201.236Sbsh
4211.235Sjoerg20120216:
4221.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
4231.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
4241.239Sdholland	and 20120216, daily and weekly could have created an unreadable
4251.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
4261.235Sjoerg	the next run of weekly will fix it.
4271.233Sjoerg
4281.232Schristos20111227:
4291.232Schristos	If you built between 20111225 and 20111227 you need to remove
4301.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
4311.232Schristos	bump has been reverted.
4321.232Schristos
4331.231Stls20111125:
4341.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
4351.231Stls	means it should no longer be explicitly listed in kernel
4361.231Stls	configuration files.  The line "pseudo-device rnd" should be
4371.231Stls	removed from any custom kernel config files users may have.
4381.231Stls
4391.230Stls20111119:
4401.230Stls	A problem with the datastructures used by the rndctl(8)
4411.230Stls	utility (pointers in datastructures in an array, making 32->64
4421.230Stls	bit compatibility very painful) has been fixed in a
4431.230Stls	non-backwards-compatible way.  If you replace your kernel,
4441.230Stls	replace your rndctl executable too.
4451.241Swiz
4461.229Sjym20111001:
4471.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
4481.229Sjym	changed and their new version is not backward compatible with the old
4491.241Swiz	one.  So ensure that all consumers of these functions (currently:
4501.229Sjym	quota2 code and its tests) are updated together with the new lib.
4511.229Sjym
4521.228Smrg20110817:
4531.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
4541.228Smrg	DESTDIR for them should be deleted before updating.
4551.228Smrg
4561.227Sriastrad20110806:
4571.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
4581.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
4591.227Sriastrad
4601.226Smrg20110805:
4611.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
4621.226Smrg	the tree to be cleaned.  Best to delete both objdir and
4631.226Smrg	DESTDIR before running this update.  So far, only the
4641.226Smrg	sparc64, mips and powerpc platforms have changed.
4651.226Smrg
4661.225Smatt20110803:
4671.241Swiz	The layout of external/public-domain/xz has changed.  To do an
4681.225Smatt	update build you will have to remove the contents of the OBJDIR
4691.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
4701.225Smatt	is now a directory.
4711.225Smatt
4721.223Sjoerg20110410:
4731.241Swiz	The configuration of src/tools/gcc has changed.  To do an
4741.224Sdholland	update build you have to clean both tools/binutils and
4751.224Sdholland	tools/gcc by hand.
4761.223Sjoerg
4771.222Splunky20110328:
4781.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
4791.241Swiz	ordering issues with "make all".  It may be necessary to remove
4801.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
4811.222Splunky	if your update build fails, as the "Xorg" entry there is now a
4821.222Splunky	directory.
4831.222Splunky
4841.220Sjoerg20110121:
4851.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
4861.220Sjoerg	the build of individual parts of the tree.  This is handled
4871.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
4881.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
4891.218Sjoerg
4901.217Sjruoho20101217:
4911.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
4921.241Swiz	by default.  It may be necessary to manually update passwd(5) and
4931.217Sjruoho	group(5) in order to make the program work with existing setups.
4941.217Sjruoho
4951.216Schristos20101125:
4961.216Schristos	The latest changes to setenv(3) dissallow setting environment
4971.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
4981.241Swiz	assumed that this was allowed.  Installing a new libc with an
4991.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
5001.216Schristos	break which affects the autoconf tests for dependency finding,
5011.216Schristos	so building gcc will end up printing:
5021.216Schristos	    checking dependency style of gcc... none
5031.216Schristos	    configure: error: no usable dependency style found
5041.216Schristos	Fix it by rebuilding and re-installing env.
5051.138Slukem
5061.215Smrg20101119:
5071.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
5081.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
5091.215Smrg	have any build problems with xsrc, or problems with mismatched
5101.215Smrg	versions between xorg-server and drivers.
5111.215Smrg
5121.213Sjmmv20100604:
5131.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
5141.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
5151.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
5161.213Sjmmv	trees by hand.
5171.213Sjmmv
5181.211Stnozaki20100522:
5191.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
5201.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
5211.212Smrg	build problems with xsrc.
5221.212Smrg
5231.212Smrg20100522:
5241.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
5251.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
5261.211Stnozaki
5271.210Schristos20100520:
5281.241Swiz	The location of the xkb compiled descriptions has changed.  Please
5291.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
5301.210Schristos
5311.209Snjoly20100222:
5321.209Snjoly	The shared objects file extension has been changed from .so to
5331.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
5341.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
5351.209Snjoly	your object directories.
5361.209Snjoly
5371.208Sroy20100204:
5381.208Sroy	The termcap database has been removed from the sources,
5391.208Sroy	but has not been marked obsolete so it is not removed
5401.208Sroy	from the system when upgrading.
5411.208Sroy	As such, you will need to remove them from your object
5421.208Sroy	and destination directories.
5431.208Sroy
5441.203Sdyoung20091101:
5451.205Sdholland        After updating, it may be necessary to make the 'cleandir'
5461.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
5471.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
5481.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
5491.203Sdyoung
5501.202Smrg20091001:
5511.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
5521.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
5531.206Sdholland
5541.206Sdholland20091001:
5551.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
5561.202Smrg	symlink, failing the build.  Delete the link, and the subdir
5571.202Smrg	it is in, and retry your build.
5581.202Smrg
5591.201Sdsl20090718:
5601.201Sdsl	libc build changed so that strchr() provides the extra entry
5611.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
5621.201Sdsl	may fail because the archive contains the unwanted index.o.
5631.201Sdsl	(Similarly for strrchr() and rindex().)
5641.201Sdsl
5651.198Smrg20090709:
5661.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
5671.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
5681.198Smrg
5691.197Smrg20090616:
5701.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
5711.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
5721.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
5731.197Smrg	subdirectory has been changed into a file, and this needs to
5741.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
5751.197Smrg
5761.195Sperry20090501:
5771.195Sperry	Several new functions were added to string.h/libc, and this
5781.195Sperry	can cause autoconf problems during the tool build for people
5791.241Swiz	who fail to clean out their tools objects properly.  If you
5801.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
5811.195Sperry	failure during the tool build, clean out all your tools
5821.195Sperry	objects and start again.
5831.195Sperry
5841.194Smrg20090325:
5851.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
5861.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
5871.194Smrg
5881.192Sskrll20090126:
5891.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
5901.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
5911.207Smbalmer	to avoid using the old assembly stub.
5921.192Sskrll
5931.191Sjoerg20090202:
5941.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
5951.191Sjoerg	detection.  It is recommented to rebuild the cache with
5961.191Sjoerg	``pkg_admin rebuild''.
5971.191Sjoerg
5981.184Schristos20090110:
5991.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
6001.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
6011.188Schristos	   This is needed even in the MODULAR kernel because there is
6021.188Schristos	   conditionally compiled code in rtsock.c.
6031.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
6041.184Schristos	   before installing.
6051.184Schristos	3. If you don't use build.sh and you build directly to root, and
6061.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
6071.184Schristos	   are installed properly, and start building libraries first libc
6081.184Schristos	   and libutil, install them and then continue building all the
6091.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
6101.184Schristos	   the new libraries are installed, you can restart the build.
6111.184Schristos	4. If you compile packages and you notice link time warnings,
6121.189Shubertf	   rebuild the required packages to update their shared libraries.
6131.189Shubertf	   Any package you rebuild will require rebuilding all the packages
6141.189Shubertf	   that depend on it.
6151.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
6161.186Schristos	   will be upgraded and it will not be backwards compatible.
6171.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
6181.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
6191.241Swiz	   for utmp.  You are better off removing the old files after
6201.190Sapb	   upgrading.  The automated clearing of /var/run during
6211.190Sapb	   boot, and the automated rotating of files in /var/log by
6221.190Sapb	   newsyslog(8), may mean that you do not have to remove the
6231.190Sapb	   files manually.
6241.190Sapb	7. The optional accounting file (/var/account/acct, see
6251.190Sapb	   accton(8)) has not been versioned, and will need to be
6261.190Sapb	   removed.  The automatic rotation of the accounting file by
6271.190Sapb	   /etc/daily limits the bad consequences of failure to remove
6281.190Sapb	   the file.
6291.196Sdholland	8. Application software that writes time_t to binary files on
6301.241Swiz	   disk will break or need attention.  Most notably: if you are
6311.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
6321.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
6331.185Sjmcneill
6341.183Spgoyette20081219:
6351.183Spgoyette	config(1) has been updated, and one of the files it creates -
6361.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
6371.183Spgoyette	(done automatically by build.sh) and then you need to rerun
6381.183Spgoyette	config on all kernel configuration files before rebuilding those
6391.183Spgoyette	kernels.
6401.183Spgoyette
6411.181Scube20081205:
6421.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
6431.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
6441.181Scube	set and will appear as extra files for MKX11=no update builds.
6451.178Slukem
6461.179Stsutsui20081122:
6471.182Stsutsui	On i386, various kernel options(4) in GENERIC including
6481.180Swiz	file systems have been disabled and moved into kernel modules.
6491.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
6501.179Stsutsui	following files as well as a new GENERIC kernel:
6511.179Stsutsui
6521.179Stsutsui	- build and install kernel modules from src/sys/modules
6531.179Stsutsui
6541.179Stsutsui	- install the latest bootloader, which will load a module
6551.180Swiz	  for the file system from which the kernel is loaded automatically
6561.179Stsutsui
6571.180Swiz	If you have to load your kernel from a file system which is not of
6581.180Swiz	the same type as the root file system, you have to load the necessary
6591.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
6601.179Stsutsui
6611.178Slukem20080827:
6621.178Slukem	If you built and installed a libc from sources between
6631.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
6641.178Slukem	which results in false errors reported by lint(1).
6651.178Slukem	Since this breaks the libc build itself, manual help is
6661.180Swiz	needed -- lint must be disabled temporarily, e.g.:
6671.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
6681.178Slukem
6691.177Schristos20080813:
6701.177Schristos	MKDEBUG build was broken because the .depend files did not know
6711.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
6721.177Schristos
6731.200Sdholland20080802:
6741.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
6751.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
6761.200Sdholland	for -current.
6771.200Sdholland
6781.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
6791.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
6801.200Sdholland	be recompiled.
6811.200Sdholland
6821.200Sdholland	One way to find affected pkgsrc packages:
6831.200Sdholland
6841.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
6851.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
6861.200Sdholland
6871.175Ssimonb20080731:
6881.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
6891.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
6901.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
6911.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
6921.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
6931.176Ssimonb	also requires the super block to be in the UFS2 format.  You
6941.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
6951.175Ssimonb
6961.174Slukem20080721:
6971.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
6981.174Slukem	isn't defined.
6991.174Slukem
7001.173Sfreza20080531:
7011.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
7021.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
7031.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
7041.241Swiz	won't work correctly.  The following sequence of commands:
7051.173Sfreza
7061.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
7071.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
7081.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
7091.173Sfreza
7101.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
7111.173Sfreza
7121.172Slukem20080503:
7131.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
7141.172Slukem
7151.171She20080521:
7161.171She	For a while, unprivileged UPDATE builds would fail to
7171.171She	succeed at the checkflist stage, complaining that
7181.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
7191.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
7201.171She	If you already hit this problem, update the .mk file,
7211.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
7221.171She
7231.174Slukem20080303:
7241.174Slukem	Linker warnings are now fatal if $WARNS>0.
7251.174Slukem
7261.170Schristos20080126:
7271.170Schristos	The posix_fadvise system call has been changed from an assembly
7281.241Swiz	stub, to a c file that calls an assembly stub.  You need to
7291.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
7301.170Schristos	avoid using the old assembly stub.
7311.170Schristos
7321.168Sjoerg20071209:
7331.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
7341.168Sjoerg	get ACPI errors before the attachment, please update your kernel
7351.169Swiz	configuration file appropriately or see GENERIC for more details.
7361.168Sjoerg
7371.166Sxtraeme20071115:
7381.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
7391.166Sxtraeme	argument specified in the kernel configuration file is not valid
7401.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
7411.241Swiz	rather than the EC address port.  Please update your kernel
7421.167Swiz	configuration file appropriately or see GENERIC for more details.
7431.166Sxtraeme
7441.165Sjmmv20071028:
7451.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
7461.165Sjmmv	You need to update any custom kernel configuration file you have
7471.165Sjmmv	to remove any references to pccons (which includes removing the
7481.165Sjmmv	now useless XSERVER option) and replace them with the correct
7491.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
7501.165Sjmmv	for more details.
7511.165Sjmmv
7521.164Sgdt20070913:
7531.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
7541.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
7551.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
7561.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
7571.164Sgdt	could not enumerate interfaces.  (These are noted because
7581.164Sgdt	normal kernel/userspace version matching hygiene is not
7591.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
7601.164Sgdt	and userland are from after 20070913.
7611.164Sgdt
7621.163Sjoerg20070703:
7631.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
7641.199Sdholland	calls the target-specific strip program, and the logic to pass
7651.199Sdholland	down STRIP from make has been removed.  This requires a
7661.199Sdholland	re-installation of tools.
7671.163Sjoerg
7681.161Sdsl20070422:
7691.161Sdsl	The way OS emulations lookup filenames inside the emulation root
7701.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
7711.161Sdsl	to userspace) namei() and lookup() directly check the emulation
7721.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
7731.167Swiz	root file system will be relative to that file system - unless they
7741.161Sdsl	start /../ this is useful when the emulated root is a real install
7751.161Sdsl	that has such links.
7761.161Sdsl	This might affect symlinks that have been added to reference outside
7771.161Sdsl	the emulated root.
7781.161Sdsl
7791.160Sjmcneill20070412:
7801.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
7811.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
7821.160Sjmcneill	example.
7831.160Sjmcneill
7841.159Sgdt20070319:
7851.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
7861.159Sgdt        on many platforms due to incorrect flags settings.  If you
7871.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
7881.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
7891.159Sgdt	rebuild of object files that might have been built
7901.159Sgdt	incorrectly, and ensure that you have at least
7911.159Sgdt	src/lib/libc/Makefile 1.130.
7921.159Sgdt
7931.241Swiz20070210:
7941.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
7951.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
7961.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
7971.158Sdbj        will allow dependencies on those files to get get rebuilt
7981.158Sdbj
7991.157Sapb20070209:
8001.157Sapb        The threading model was changed when the newlock2 branch
8011.157Sapb        was merged to NetBSD-current.  If you boot with a new
8021.157Sapb        kernel (version 4.99.10), then you also need a new pthread
8031.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
8041.157Sapb        an old kernel, then you need the old pthread library
8051.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
8061.157Sapb        the pthread library in sync, old threaded applications should
8071.157Sapb        continue to work with an old or new kernel.  Note that named(8)
8081.157Sapb	is the only threaded application in the base system.
8091.157Sapb
8101.154She20061214:
8111.154She	Following the move of string_to_flags() and flags_to_string()
8121.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
8131.154She	will need to do a "make cleandir" in
8141.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
8151.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
8161.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
8171.156She		as the installation images in distrib/
8181.154She	in order to excise stale references to the old stat_flags.h header
8191.154She	file in the ls sources -- stat_flags.h has been removed.
8201.154She
8211.152Schristos20061108:
8221.152Schristos	The configure script used in the src/tools/gcc compiler has been
8231.152Schristos	changed to indicate that our libc has ssp support built-in and
8241.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
8251.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
8261.152Schristos
8271.151Srpaulo20061009:
8281.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
8291.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
8301.151Srpaulo
8311.150Sbjh2120060814:
8321.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
8331.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
8341.150Sbjh21	kernel configuration for an example.  X servers from the last
8351.150Sbjh21	few years should cope.
8361.150Sbjh21
8371.149Schristos20060703:
8381.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
8391.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
8401.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
8411.149Schristos
8421.148Sdogcow20060627:
8431.148Sdogcow	socket(2) has changed, and its system call has been versioned.
8441.148Sdogcow	For userlands with the old version of socket(2), make sure that
8451.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
8461.148Sdogcow	errors will result.
8471.148Sdogcow
8481.1SabsHints for a more successful build:
8491.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8501.123Sjmc    Use build.sh, but do not use its "expert mode":
8511.132Sjmmv	This will automatically build the tools in the
8521.123Sjmc	   correct order, and it will keep the tools and the
8531.123Sjmc	   new build products from interfering with the running
8541.123Sjmc	   system.  This will allow you to ignore most of the
8551.123Sjmc	   other advice in this file.
8561.2Smrg    Build a new kernel first:
8571.2Smrg	This makes sure that any new system calls or features
8581.2Smrg	   expected by the new userland will be present.  This
8591.2Smrg	   helps to avoid critical errors when upgrading.
8601.1Sabs    Use object directories:
8611.1Sabs	This helps to keep stale object
8621.1Sabs	   files from polluting the build if a Makefile "forgets"
8631.1Sabs	   about one.  It also makes it easier to clean up after
8641.1Sabs	   a build.  It's also necessary if you want to use the
8651.1Sabs	   same source tree for multiple machines.
8661.123Sjmc	   To use object directories with build.sh:
8671.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
8681.123Sjmc	   To use object directories without using build.sh:
8691.1Sabs	    a) cd /usr/src ; make cleandir
8701.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
8711.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
8721.1Sabs	    d) cd /usr/src ; make build
8731.2Smrg	   Note that running "make obj" in a directory will create
8741.2Smrg	   in obj.$MACHINE directory.
8751.1Sabs    Build to a DESTDIR:
8761.123Sjmc	This helps to keep old installed files (especially libraries)
8771.123Sjmc	   from interfering with the new build.
8781.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
8791.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
8801.123Sjmc	   environment variable before running make build.  It should be
8811.123Sjmc	   set to the pathname of an initially empty directory.
8821.123Sjmc	   Problems: if you do not use build.sh, you might need to
8831.123Sjmc		update critical utilities without using DESTDIR since
8841.123Sjmc		nothing is executed from what is installed in DESTDIR.
8851.123Sjmc		(See critical utils, below.)
8861.1Sabs    Build often:
8871.1Sabs	This keeps critical utilities current enough to not choke
8881.1Sabs	on any other part of the source tree that depends on up to
8891.123Sjmc	date functionality.  If you use build.sh, you should not have
8901.123Sjmc	this problem.
8911.241Swiz
8921.1SabsWhat to do if things don't work:
8931.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8941.230StlsWhen things don't work there are usually a few things that commonly
8951.1Sabsshould be done.
8961.1Sabs    1)	make includes
8971.1Sabs	This should be done automatically by make build.
8981.1Sabs    2)  cd share/mk && make install
8991.1Sabs	Again, automatically done by make build.
9001.1Sabs
9011.1SabsFailsafe rebuild of a small part of the tree:
9021.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9031.1SabsTo make sure you rebuild something correctly you want to do
9041.1Sabssomething like the following:
9051.1Sabs    1)  Make sure the includes and .mk files are up to date.
9061.1Sabs    2)  Make sure any program used to build the particular
9071.1Sabs	utility is up to date.  (yacc, lex, etc...)
9081.1Sabs    3)  cd ...path/to/util...
9091.1Sabs	make cleandir
9101.1Sabs	rm ...all obj directories...
9111.1Sabs	make cleandir			# yes, again
9121.1Sabs	make obj
9131.1Sabs	make depend && make
9141.1Sabs
9151.1SabsFailsafe rebuild of the entire tree:
9161.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9171.1SabsIf you really want to make sure the source tree is clean and
9181.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
9191.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
9201.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
9211.1Sabs
9221.1Sabs---cut here---
9231.1Sabs#!/bin/sh
9241.1Sabs. /etc/mk.conf
9251.1Sabs
9261.58Slukemif [ -z $NETBSDSRCDIR ] ; then
9271.58Slukem    NETBSDSRCDIR=/usr/src
9281.1Sabsfi
9291.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
9301.1Sabs    echo Unable to find sources
9311.1Sabs    exit 1
9321.1Sabsfi
9331.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
9341.1Sabs
9351.1Sabsif [ -z $BSDOBJDIR ] ; then
9361.1Sabs    BSDOBJDIR=/usr/obj
9371.1Sabsfi
9381.1Sabsif [ -d $BSDOBJDIR ] ; then
9391.1Sabs    rm -rf $BSDOBJDIR
9401.1Sabsfi
9411.1Sabs
9421.58Slukemcd $NETBSDSRCDIR && make cleandir
9431.1Sabs
9441.1Sabs---cut here---
9451.1Sabs
9461.1SabsCritical utilities:
9471.1Sabs^^^^^^^^^^^^^^^^^^^
9481.3Sitojun	usr.bin/compile_et
9491.1Sabs	usr.bin/make
9501.1Sabs	usr.bin/yacc
9511.1Sabs	usr.bin/lex
9521.11Slukem	usr.bin/xlint
9531.142Sdrochner	usr.bin/config
9541.1Sabs
9551.34SsimonbOther problems and possible solutions:
9561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9571.1SabsSymptom:Complaints involving a Makefile.
9581.17SerhFix:	Rebuild usr.bin/make:
9591.17Serh	cd usr.bin/make && make && make install
9601.111Ssimonb	Or, a failsafe method if that doesn't work:
9611.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
9621.17Serh
9631.1SabsFix:	Make sure .mk files are up to date.
9641.1Sabs	cd share/mk && make install
9651.2Smrg
9661.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
9671.142SdrochnerFix:	Rebuild usr.bin/config
9681.1Sabs
9691.1SabsSymptom:
9701.1SabsFix:	Rebuild usr.bin/yacc
9711.1Sabs
9721.1SabsSymptom:
9731.1SabsFix:	Rebuild usr.bin/lex
9741.1Sabs
9751.1SabsSymptom:
9761.1SabsFix:	rm /usr/lib/libbfd.a
9771.4Sitojun
9781.4SitojunSymptom:Obsolete intermediate files are used during compilation
9791.4SitojunFix:	Try the following sequence of commands in the directory in question.
9801.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
9811.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
9821.4Sitojun	may remain.  The command tries to clean everything up)
9831.5Swiz
9841.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
9851.207Smbalmer	pointer type
9861.5SwizFix:	Rebuild and install usr.bin/menuc
9871.12Sitojun
9881.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9891.12SitojunFix:	Build and install usr.bin/mklocale
9901.13Sdogcow
9911.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9921.13SdogcowFix:    Rebuild and install lib/libc
9931.13Sdogcow
9941.142SdrochnerSymptom:usr.bin/config fails to build.
9951.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9961.13Sdogcow
9971.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9981.19ScgdFix:    Rebuild and install lib/libc
9991.24Sabs
10001.24SabsSymptom:lint does not understand the '-X' option
10011.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
10021.223Sjoerg
10031.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
10041.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
10051.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
10061.257Sapb
10071.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
10081.257Sapb	No such file or directory.
10091.257SapbCause:	If a directory is created by mistake, then it is sometimes
10101.257Sapb	deleted from the CVS repository using administrative commands
10111.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
10121.257Sapb	contains references to a directory that has been deleted on the
10131.257Sapb	server in this way, then "cvs update" reports this error.
10141.257SapbFix:	Recursively delete the affected directory from your working tree
10151.257Sapb	and try the update again.
1016