UPDATING revision 1.329
11.329Smrg$NetBSD: UPDATING,v 1.329 2022/07/15 05:26:08 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.329Smrg20220714:
231.329Smrg	Updates to xorg-server and associated drivers may cause builds to
241.329Smrg	fail.  Cleaning both DESTDIR and the xorg build tree may be needed.
251.329Smrg
261.328Smartin20220628:
271.328Smartin	Changes in the build of src/games/robots require a clean build
281.328Smartin	of that program.
291.328Smartin
301.324Smartin20211116:
311.324Smartin	Changes in the xorg build require clean obj dirs for external/mit/xorg
321.325Smartin	(or a full clean/non-update build).
331.324Smartin
341.323Snia20211112:
351.323Snia	Device tree sources were updated for evbarm.  Some device nodes
361.323Snia	(in particular, ld(4) devices on the ROCKPro64) will be renumbered.
371.323Snia
381.322Smartin20211014:
391.323Snia	MKPIE default for aarch64 has changed, a clean build is required.
401.322Smartin
411.321Schristos20210917:
421.321Schristos	Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
431.321Schristos	ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
441.321Schristos	and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
451.321Schristos
461.319Smrg20210711:
471.319Smrg	Updated GMP sources may require cleaning in tools/gmp and/or in
481.319Smrg	external/lgpl3/gmp/lib, particularly if GCC itself does not build.
491.319Smrg
501.318Smrg20210417:
511.318Smrg	GCC 10 was enabled for several platforms.  If builds fail in either
521.318Smrg	tools/gcc or external/gpl/gcc, first try cleaning those objects and
531.318Smrg	removing the $DESTDIR/usr/include/g++ subdirectory.
541.318Smrg
551.317Srillig20201230:
561.317Srillig	lint1/ops.c is no longer autogenerated.  If this makes the build
571.317Srillig	fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*.
581.317Srillig
591.316Smrg20201016:
601.316Smrg	MIPS kernel modules have been disabled until they work.  This will
611.316Smrg	turn up in extra files in the DESTDIR, which should be cleaned.
621.316Smrg
631.315Smrg20200925:
641.315Smrg	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
651.315Smrg	in both the tools and external dirs.
661.315Smrg
671.314Smrg20200912:
681.314Smrg	GCC 9 has arrived for Arm and x86 platforms, and will be coming
691.314Smrg	for several more, as will binutils 2.34.  Clean as required.
701.314Smrg
711.313Smrg20200907:
721.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
731.313Smrg	probably requires cleaning the tools/binutils.
741.313Smrg
751.311Smrg20200811:
761.312Smrg	GCC updates may require cleaning the objdir.  This may occur
771.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
781.312Smrg	GCC 9 upgrade.
791.311Smrg
801.309Schristos20200614:
811.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
821.310Schristos	should handle the migration
831.309Schristos
841.308Schristos20200601:
851.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
861.308Schristos	created in the build directories and need cleaning.
871.308Schristos
881.307Smrg20200311:
891.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
901.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
911.307Smrg
921.306Schristos20191118:
931.306Schristos	More architectures were switched to gcc8:
941.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
951.306Schristos	The same comments as in 20191022 apply.
961.306Schristos
971.305Smartin20191112:
981.305Smartin	The LLVM update requires a clean rebuild for all architectures using
991.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
1001.305Smartin
1011.304Smartin20191022:
1021.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
1031.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
1041.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
1051.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
1061.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
1071.304Smartin	daily builds and install that before doing the next in-place build.
1081.304Smartin
1091.303Smrg20191001:
1101.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
1111.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
1121.303Smrg	directory, and also clean src/external/gpl3/gcc.
1131.303Smrg
1141.302Sriastrad20190903:
1151.306Schristos	Files with names that coincide with existing files' names on
1161.302Sriastrad	case-insensitive file systems were inadvertently committed, for
1171.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
1181.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
1191.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
1201.302Sriastrad	manually delete the following files in your DESTDIR (which is
1211.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
1221.302Sriastrad	them:
1231.302Sriastrad
1241.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
1251.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
1261.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
1271.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
1281.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
1291.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
1301.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
1311.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
1321.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
1331.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
1341.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
1351.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
1361.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
1371.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
1381.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
1391.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
1401.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
1411.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
1421.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
1431.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
1441.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
1451.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
1461.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
1471.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
1481.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
1491.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
1501.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
1511.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
1521.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
1531.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
1541.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
1551.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
1561.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
1571.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
1581.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
1591.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
1601.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
1611.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
1621.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
1631.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
1641.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
1651.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
1661.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
1671.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
1681.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
1691.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
1701.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
1711.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
1721.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
1731.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
1741.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
1751.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
1761.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
1771.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
1781.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
1791.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
1801.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
1811.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
1821.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
1831.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
1841.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
1851.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
1861.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
1871.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
1881.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
1891.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
1901.302Sriastrad
1911.302Sriastrad	We will re-import these radeon firmware images another way
1921.302Sriastrad	later.
1931.302Sriastrad
1941.301Smartin20190727:
1951.301Smartin	The uefi bootloader has gained tftp support and needs a clean
1961.301Smartin	build. If you do update builds, manually clean its object
1971.301Smartin	directory by something like:
1981.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
1991.301Smartin
2001.300Smartin20190723:
2011.300Smartin	The jemalloc allocator in libc is now build without extended
2021.300Smartin	debugging (for performance reasons). In update builds make sure
2031.326Sandvar	to rebuild it completely, by removing all affected object files,
2041.300Smartin	including compat builds, something like:
2051.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
2061.300Smartin
2071.299Smrg20190207:
2081.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
2091.299Smrg
2101.298Smartin20180924:
2111.298Smartin	A newer OpenSSL version has been imported. If you are doing
2121.298Smartin	update builds, make sure to remove all old obj dirs, like:
2131.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
2141.298Smartin
2151.297Sjoerg20180717:
2161.297Sjoerg	On aarch64 int64_t and related types have changed from long long
2171.297Sjoerg	to long. This requires recompiling all C++ binaries.
2181.297Sjoerg
2191.296Smartin20180713:
2201.296Smartin	On amd64 and i386 static binaries are now build position
2211.296Smartin	independend. This requires recompilation of all object
2221.296Smartin	files used to create the crunched /rescue binary.
2231.296Smartin	Clean the rescue directory in your obj directory before
2241.296Smartin	doing an update build, otherwise linking will fail.
2251.296Smartin
2261.293Sjakllsch20180414:
2271.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
2281.293Sjakllsch	removal of tools/binutils objects directory may be required
2291.293Sjakllsch	to fix tools build failure.
2301.293Sjakllsch
2311.292Smrg20180311:
2321.292Smrg	bdftopcf was updated and may need cleaning in the
2331.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
2341.292Smrg	link errors.
2351.292Smrg
2361.291Smrg20180212:
2371.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
2381.291Smrg	any failure that looks like GCC or openssl is best handled by
2391.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
2401.291Smrg	is recommended if build failures occur.
2411.291Smrg
2421.288Smartin20171225:
2431.288Smartin	removal of the vadvise syscall requires manual removal of all
2441.288Smartin	associated files from the libc build object directory (including
2451.289Schristos	the .depend files) - a command like:
2461.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
2471.289Schristos	For architectures that support multiple "compat" binary targets,
2481.289Schristos	you'll need to cleanup both the regular libc directory and the
2491.290Smartin	compat ones (the above command will do that).
2501.288Smartin
2511.287Skre20171010:
2521.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
2531.287Skre	means that its objdir (or *.d and .depend at least) might need
2541.287Skre	to be manually removed - or a build done once without -u.
2551.287Skre
2561.286Smrg20170822:
2571.286Smrg	a new version of GMP has been imported and probably
2581.286Smrg	will break parts of builds related to themselves or GCC, both
2591.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2601.286Smrg	and MPC objdirs or build once without -u.
2611.286Smrg
2621.285Smrg20170816:
2631.285Smrg	a new version of MPFR and MPC have been imported and probably
2641.285Smrg	will break parts of builds related to themselves or GCC, both
2651.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2661.285Smrg	and MPC objdirs or build once without -u.
2671.285Smrg
2681.284Smartin20170402:
2691.284Smartin	a new version of dhcpcd has been imported, which does not support
2701.284Smartin	update builds from the previous version. Remove your
2711.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
2721.284Smartin
2731.281Sroy20170211:
2741.281Sroy	a new terminfo database has been imported.
2751.281Sroy	The structure of it has changed slightly from prior versions and
2761.281Sroy	an updated tic tool is required.
2771.281Sroy	If you build.sh, don't use -u
2781.281Sroy
2791.280Skre20170207:
2801.278Skre	various arch dependent libc/exect.S files were removed
2811.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
2821.279Skre	if it exists) or do a clean build.
2831.279Skre	(This is a bug in the make system, it should be corrected without
2841.279Skre	human intervention, but isn't.)
2851.278Skre
2861.277Smartin20170104:
2871.277Smartin	xinput build options have changed.
2881.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
2891.277Smartin	if you build.sh -u
2901.277Smartin
2911.276Smartin20170103:
2921.276Smartin	a new version of flex has been imported.
2931.276Smartin	Remove the file from obj (external/bsd/flex)
2941.276Smartin	if you build.sh -u
2951.276Smartin
2961.275Sspz20161014:
2971.275Sspz	a new version of OpenSSL has been imported.
2981.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
2991.275Sspz	if you build.sh -u
3001.275Sspz
3011.274Smartin20161009:
3021.274Smartin	a new version of dhcpcd has been imported with slightly changed
3031.274Smartin	build infrastructure. When doing a build.sh -u this requires
3041.274Smartin	pruning the external/bsd/dhcpcd objdir.
3051.274Smartin
3061.273Smrg20160914:
3071.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
3081.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
3091.273Smrg	and a clean objdir.
3101.273Smrg
3111.272Sdholland20160527:
3121.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
3131.272Sdholland	been enabled. (see the amd64 entry two down for further info)
3141.272Sdholland
3151.270Schristos20160418:
3161.270Schristos	libedit needs manual removal of all autogenerated files since
3171.271Schristos	some of them are not autogenerated anymore. Remember that there
3181.271Schristos	might be two copies of libedit if your platform builds "compat".
3191.270Schristos
3201.268Sriastrad20160410:
3211.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
3221.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
3231.268Sriastrad	executables, means all code, including executables and not just
3241.268Sriastrad	shared libraries, is position-independent and hence able to be
3251.268Sriastrad	relocated by ASLR, address space layout randomization.
3261.268Sriastrad
3271.268Sriastrad	The change was made in Makefile variables for compiler and
3281.268Sriastrad	linker flags, for which make(1) does not record dependencies,
3291.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
3301.268Sriastrad
3311.268Sriastrad	Partial rebuilds with some modified source files will likely
3321.268Sriastrad	fail when linking executables, since the linker refuses to mix
3331.268Sriastrad	position-independent code with position-dependent code in
3341.268Sriastrad	position-independent executables:
3351.268Sriastrad
3361.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
3371.268Sriastrad
3381.267Smrg20160401:
3391.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
3401.269Sdholland	Some people have found that cleandir is not sufficient, so if
3411.269Sdholland	in doubt delete the entire object directory tree for gcc.
3421.267Smrg
3431.266Saymeric20160306:
3441.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
3451.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
3461.265Saymeric	non-NetBSD hosts if linked with stale object files produced
3471.265Saymeric	while they included a non-NetBSD regex.h.
3481.265Saymeric	In any case, you should "make cleandir" at least these tools
3491.265Saymeric	before updating your toolchain.
3501.265Saymeric
3511.264Smartin20160125:
3521.264Smartin	Dtrace has been enabled by default on some architectures.
3531.264Smartin	When doing an update build, make sure to clean the etc/mtree
3541.264Smartin	object directory before starting the build - otherwise the
3551.264Smartin	needed directories in destdir will not be created.
3561.264Smartin	An easy way to do this is:
3571.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
3581.264Smartin
3591.263Sdholland20150818:
3601.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
3611.263Sdholland	again.
3621.263Sdholland
3631.262Schristos20150413:
3641.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
3651.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
3661.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
3671.262Schristos
3681.261Smartin20150404:
3691.261Smartin	Lint changes require a full rebuild of the tool, so make
3701.261Smartin	sure to build without -u option to build.sh, or manually
3711.261Smartin	do a make cleandir in src/tools/lint1 and
3721.261Smartin	src/usr.bin/xlint.
3731.261Smartin
3741.260Sskrll20150310:
3751.260Sskrll	Improvements to openssl for arm mean that update builds of
3761.260Sskrll	the openssl libraries will fail. A make cleandir in
3771.260Sskrll	external/bsd/openssl/lib is needed
3781.260Sskrll
3791.258Smartin20141026:
3801.259Smsaitoh	A mishap during the import of pppd may cause your corruption
3811.258Smartin	in your cvs directory if you happened to do a cvs update
3821.258Smartin	during a short period of time. To fix, just remove the
3831.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
3841.258Smartin	and let cvs restore it on next update.
3851.258Smartin
3861.256Sapb20140721:
3871.256Sapb	The src/external/mit/lua/src directory was accidentally created
3881.256Sapb	and then deleted in the CVS repository.  If you get errors like
3891.256Sapb
3901.256Sapb	cvs [update aborted]: cannot open directory
3911.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
3921.256Sapb
3931.256Sapb	then delete your local copy of that directory tree and try again.
3941.256Sapb
3951.255Sjoerg20140530:
3961.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
3971.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
3981.255Sjoerg
3991.251Smartin20140131:
4001.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
4011.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
4021.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
4031.251Smartin
4041.250Schristos20131227:
4051.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
4061.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
4071.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
4081.250Schristos	   statements to avoid being exposed.
4091.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
4101.250Schristos	   to make clean in libc
4111.250Schristos
4121.249Smrg20131129:
4131.249Smrg	The GMP sources were updated, and builds will likely fail without
4141.249Smrg	cleaning their build trees for both tools and in-tree, like below.
4151.249Smrg
4161.248Smrg20131128:
4171.248Smrg	The MPC and MPFR sources were updated, and builds may require their
4181.248Smrg	tools and in-tree directories cleaned for successful updates.
4191.248Smrg
4201.246Smartin20130605:
4211.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
4221.247Sspz	to IPSEC (and the older IPSEC version removed).
4231.247Sspz
4241.247Sspz20130605:
4251.320Sandvar	Previous freetype installations erroneously installed private
4261.246Smartin	header files. If you are building against a non-empty $DESTDIR,
4271.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
4281.246Smartin
4291.245Smrg20130531:
4301.245Smrg	The xdm update may cause build failure due to xdm.man being
4311.245Smrg	in the obj tree.  Make sure to ensure any like this:
4321.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
4331.245Smrg	is fixed by deleting the xdm.man in the obj tree.
4341.245Smrg
4351.244Smrg20130530:
4361.244Smrg	Updates of many xsrc packages will leave old .pc files around.
4371.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
4381.244Smrg
4391.242Schristos20130301:
4401.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
4411.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
4421.242Schristos
4431.238Sdholland20120726:
4441.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
4451.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
4461.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
4471.241Swiz	some cases may succeed and install broken OpenSSL libraries that
4481.240Sdholland	cause third-party software to link incorrectly and/or crash.
4491.238Sdholland
4501.237Swiz20120507:
4511.241Swiz	The database schema for makemandb was changed.  You will
4521.237Swiz	need to update the database using 'makemandb -f' or wait
4531.237Swiz	for the next weekly run to fix it.
4541.237Swiz
4551.236Sbsh20120319:
4561.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
4571.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
4581.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
4591.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
4601.236Sbsh	mk.conf.
4611.236Sbsh
4621.235Sjoerg20120216:
4631.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
4641.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
4651.239Sdholland	and 20120216, daily and weekly could have created an unreadable
4661.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
4671.235Sjoerg	the next run of weekly will fix it.
4681.233Sjoerg
4691.232Schristos20111227:
4701.232Schristos	If you built between 20111225 and 20111227 you need to remove
4711.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
4721.232Schristos	bump has been reverted.
4731.232Schristos
4741.231Stls20111125:
4751.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
4761.231Stls	means it should no longer be explicitly listed in kernel
4771.231Stls	configuration files.  The line "pseudo-device rnd" should be
4781.231Stls	removed from any custom kernel config files users may have.
4791.231Stls
4801.230Stls20111119:
4811.230Stls	A problem with the datastructures used by the rndctl(8)
4821.230Stls	utility (pointers in datastructures in an array, making 32->64
4831.230Stls	bit compatibility very painful) has been fixed in a
4841.230Stls	non-backwards-compatible way.  If you replace your kernel,
4851.230Stls	replace your rndctl executable too.
4861.241Swiz
4871.229Sjym20111001:
4881.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
4891.229Sjym	changed and their new version is not backward compatible with the old
4901.241Swiz	one.  So ensure that all consumers of these functions (currently:
4911.229Sjym	quota2 code and its tests) are updated together with the new lib.
4921.229Sjym
4931.228Smrg20110817:
4941.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
4951.228Smrg	DESTDIR for them should be deleted before updating.
4961.228Smrg
4971.227Sriastrad20110806:
4981.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
4991.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
5001.227Sriastrad
5011.226Smrg20110805:
5021.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
5031.226Smrg	the tree to be cleaned.  Best to delete both objdir and
5041.226Smrg	DESTDIR before running this update.  So far, only the
5051.226Smrg	sparc64, mips and powerpc platforms have changed.
5061.226Smrg
5071.225Smatt20110803:
5081.241Swiz	The layout of external/public-domain/xz has changed.  To do an
5091.225Smatt	update build you will have to remove the contents of the OBJDIR
5101.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
5111.225Smatt	is now a directory.
5121.225Smatt
5131.223Sjoerg20110410:
5141.241Swiz	The configuration of src/tools/gcc has changed.  To do an
5151.224Sdholland	update build you have to clean both tools/binutils and
5161.224Sdholland	tools/gcc by hand.
5171.223Sjoerg
5181.222Splunky20110328:
5191.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
5201.241Swiz	ordering issues with "make all".  It may be necessary to remove
5211.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
5221.222Splunky	if your update build fails, as the "Xorg" entry there is now a
5231.222Splunky	directory.
5241.222Splunky
5251.220Sjoerg20110121:
5261.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
5271.220Sjoerg	the build of individual parts of the tree.  This is handled
5281.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
5291.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
5301.218Sjoerg
5311.217Sjruoho20101217:
5321.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
5331.241Swiz	by default.  It may be necessary to manually update passwd(5) and
5341.217Sjruoho	group(5) in order to make the program work with existing setups.
5351.217Sjruoho
5361.216Schristos20101125:
5371.327Sandvar	The latest changes to setenv(3) disallow setting environment
5381.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
5391.241Swiz	assumed that this was allowed.  Installing a new libc with an
5401.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
5411.216Schristos	break which affects the autoconf tests for dependency finding,
5421.216Schristos	so building gcc will end up printing:
5431.216Schristos	    checking dependency style of gcc... none
5441.216Schristos	    configure: error: no usable dependency style found
5451.216Schristos	Fix it by rebuilding and re-installing env.
5461.138Slukem
5471.215Smrg20101119:
5481.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
5491.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
5501.215Smrg	have any build problems with xsrc, or problems with mismatched
5511.215Smrg	versions between xorg-server and drivers.
5521.215Smrg
5531.213Sjmmv20100604:
5541.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
5551.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
5561.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
5571.213Sjmmv	trees by hand.
5581.213Sjmmv
5591.211Stnozaki20100522:
5601.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
5611.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
5621.212Smrg	build problems with xsrc.
5631.212Smrg
5641.212Smrg20100522:
5651.320Sandvar	private section of <ctype.h> was split, and now mklocale(1)
5661.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
5671.211Stnozaki
5681.210Schristos20100520:
5691.241Swiz	The location of the xkb compiled descriptions has changed.  Please
5701.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
5711.210Schristos
5721.209Snjoly20100222:
5731.209Snjoly	The shared objects file extension has been changed from .so to
5741.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
5751.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
5761.209Snjoly	your object directories.
5771.209Snjoly
5781.208Sroy20100204:
5791.208Sroy	The termcap database has been removed from the sources,
5801.208Sroy	but has not been marked obsolete so it is not removed
5811.208Sroy	from the system when upgrading.
5821.208Sroy	As such, you will need to remove them from your object
5831.208Sroy	and destination directories.
5841.208Sroy
5851.203Sdyoung20091101:
5861.205Sdholland        After updating, it may be necessary to make the 'cleandir'
5871.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
5881.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
5891.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
5901.203Sdyoung
5911.202Smrg20091001:
5921.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
5931.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
5941.206Sdholland
5951.206Sdholland20091001:
5961.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
5971.202Smrg	symlink, failing the build.  Delete the link, and the subdir
5981.202Smrg	it is in, and retry your build.
5991.202Smrg
6001.201Sdsl20090718:
6011.201Sdsl	libc build changed so that strchr() provides the extra entry
6021.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
6031.201Sdsl	may fail because the archive contains the unwanted index.o.
6041.201Sdsl	(Similarly for strrchr() and rindex().)
6051.201Sdsl
6061.198Smrg20090709:
6071.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
6081.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
6091.198Smrg
6101.197Smrg20090616:
6111.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
6121.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
6131.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
6141.197Smrg	subdirectory has been changed into a file, and this needs to
6151.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
6161.197Smrg
6171.195Sperry20090501:
6181.195Sperry	Several new functions were added to string.h/libc, and this
6191.195Sperry	can cause autoconf problems during the tool build for people
6201.241Swiz	who fail to clean out their tools objects properly.  If you
6211.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
6221.195Sperry	failure during the tool build, clean out all your tools
6231.195Sperry	objects and start again.
6241.195Sperry
6251.194Smrg20090325:
6261.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
6271.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
6281.194Smrg
6291.192Sskrll20090126:
6301.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
6311.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
6321.207Smbalmer	to avoid using the old assembly stub.
6331.192Sskrll
6341.191Sjoerg20090202:
6351.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
6361.320Sandvar	detection.  It is recommended to rebuild the cache with
6371.191Sjoerg	``pkg_admin rebuild''.
6381.191Sjoerg
6391.184Schristos20090110:
6401.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
6411.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
6421.188Schristos	   This is needed even in the MODULAR kernel because there is
6431.188Schristos	   conditionally compiled code in rtsock.c.
6441.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
6451.184Schristos	   before installing.
6461.184Schristos	3. If you don't use build.sh and you build directly to root, and
6471.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
6481.184Schristos	   are installed properly, and start building libraries first libc
6491.184Schristos	   and libutil, install them and then continue building all the
6501.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
6511.184Schristos	   the new libraries are installed, you can restart the build.
6521.184Schristos	4. If you compile packages and you notice link time warnings,
6531.189Shubertf	   rebuild the required packages to update their shared libraries.
6541.189Shubertf	   Any package you rebuild will require rebuilding all the packages
6551.189Shubertf	   that depend on it.
6561.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
6571.186Schristos	   will be upgraded and it will not be backwards compatible.
6581.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
6591.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
6601.241Swiz	   for utmp.  You are better off removing the old files after
6611.190Sapb	   upgrading.  The automated clearing of /var/run during
6621.190Sapb	   boot, and the automated rotating of files in /var/log by
6631.190Sapb	   newsyslog(8), may mean that you do not have to remove the
6641.190Sapb	   files manually.
6651.190Sapb	7. The optional accounting file (/var/account/acct, see
6661.190Sapb	   accton(8)) has not been versioned, and will need to be
6671.190Sapb	   removed.  The automatic rotation of the accounting file by
6681.190Sapb	   /etc/daily limits the bad consequences of failure to remove
6691.190Sapb	   the file.
6701.196Sdholland	8. Application software that writes time_t to binary files on
6711.241Swiz	   disk will break or need attention.  Most notably: if you are
6721.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
6731.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
6741.185Sjmcneill
6751.183Spgoyette20081219:
6761.183Spgoyette	config(1) has been updated, and one of the files it creates -
6771.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
6781.183Spgoyette	(done automatically by build.sh) and then you need to rerun
6791.183Spgoyette	config on all kernel configuration files before rebuilding those
6801.183Spgoyette	kernels.
6811.183Spgoyette
6821.181Scube20081205:
6831.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
6841.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
6851.181Scube	set and will appear as extra files for MKX11=no update builds.
6861.178Slukem
6871.179Stsutsui20081122:
6881.182Stsutsui	On i386, various kernel options(4) in GENERIC including
6891.180Swiz	file systems have been disabled and moved into kernel modules.
6901.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
6911.179Stsutsui	following files as well as a new GENERIC kernel:
6921.179Stsutsui
6931.179Stsutsui	- build and install kernel modules from src/sys/modules
6941.179Stsutsui
6951.179Stsutsui	- install the latest bootloader, which will load a module
6961.180Swiz	  for the file system from which the kernel is loaded automatically
6971.179Stsutsui
6981.180Swiz	If you have to load your kernel from a file system which is not of
6991.180Swiz	the same type as the root file system, you have to load the necessary
7001.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
7011.179Stsutsui
7021.178Slukem20080827:
7031.178Slukem	If you built and installed a libc from sources between
7041.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
7051.178Slukem	which results in false errors reported by lint(1).
7061.178Slukem	Since this breaks the libc build itself, manual help is
7071.180Swiz	needed -- lint must be disabled temporarily, e.g.:
7081.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
7091.178Slukem
7101.177Schristos20080813:
7111.177Schristos	MKDEBUG build was broken because the .depend files did not know
7121.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
7131.177Schristos
7141.200Sdholland20080802:
7151.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
7161.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
7171.200Sdholland	for -current.
7181.200Sdholland
7191.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
7201.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
7211.200Sdholland	be recompiled.
7221.200Sdholland
7231.200Sdholland	One way to find affected pkgsrc packages:
7241.200Sdholland
7251.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
7261.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
7271.200Sdholland
7281.175Ssimonb20080731:
7291.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
7301.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
7311.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
7321.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
7331.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
7341.176Ssimonb	also requires the super block to be in the UFS2 format.  You
7351.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
7361.175Ssimonb
7371.174Slukem20080721:
7381.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
7391.174Slukem	isn't defined.
7401.174Slukem
7411.173Sfreza20080531:
7421.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
7431.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
7441.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
7451.241Swiz	won't work correctly.  The following sequence of commands:
7461.173Sfreza
7471.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
7481.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
7491.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
7501.173Sfreza
7511.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
7521.173Sfreza
7531.172Slukem20080503:
7541.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
7551.172Slukem
7561.171She20080521:
7571.171She	For a while, unprivileged UPDATE builds would fail to
7581.171She	succeed at the checkflist stage, complaining that
7591.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
7601.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
7611.171She	If you already hit this problem, update the .mk file,
7621.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
7631.171She
7641.174Slukem20080303:
7651.174Slukem	Linker warnings are now fatal if $WARNS>0.
7661.174Slukem
7671.170Schristos20080126:
7681.170Schristos	The posix_fadvise system call has been changed from an assembly
7691.241Swiz	stub, to a c file that calls an assembly stub.  You need to
7701.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
7711.170Schristos	avoid using the old assembly stub.
7721.170Schristos
7731.168Sjoerg20071209:
7741.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
7751.168Sjoerg	get ACPI errors before the attachment, please update your kernel
7761.169Swiz	configuration file appropriately or see GENERIC for more details.
7771.168Sjoerg
7781.166Sxtraeme20071115:
7791.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
7801.166Sxtraeme	argument specified in the kernel configuration file is not valid
7811.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
7821.241Swiz	rather than the EC address port.  Please update your kernel
7831.167Swiz	configuration file appropriately or see GENERIC for more details.
7841.166Sxtraeme
7851.165Sjmmv20071028:
7861.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
7871.165Sjmmv	You need to update any custom kernel configuration file you have
7881.165Sjmmv	to remove any references to pccons (which includes removing the
7891.165Sjmmv	now useless XSERVER option) and replace them with the correct
7901.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
7911.165Sjmmv	for more details.
7921.165Sjmmv
7931.164Sgdt20070913:
7941.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
7951.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
7961.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
7971.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
7981.164Sgdt	could not enumerate interfaces.  (These are noted because
7991.164Sgdt	normal kernel/userspace version matching hygiene is not
8001.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
8011.164Sgdt	and userland are from after 20070913.
8021.164Sgdt
8031.163Sjoerg20070703:
8041.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
8051.199Sdholland	calls the target-specific strip program, and the logic to pass
8061.199Sdholland	down STRIP from make has been removed.  This requires a
8071.199Sdholland	re-installation of tools.
8081.163Sjoerg
8091.161Sdsl20070422:
8101.161Sdsl	The way OS emulations lookup filenames inside the emulation root
8111.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
8121.161Sdsl	to userspace) namei() and lookup() directly check the emulation
8131.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
8141.167Swiz	root file system will be relative to that file system - unless they
8151.161Sdsl	start /../ this is useful when the emulated root is a real install
8161.161Sdsl	that has such links.
8171.161Sdsl	This might affect symlinks that have been added to reference outside
8181.161Sdsl	the emulated root.
8191.161Sdsl
8201.160Sjmcneill20070412:
8211.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
8221.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
8231.160Sjmcneill	example.
8241.160Sjmcneill
8251.159Sgdt20070319:
8261.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
8271.159Sgdt        on many platforms due to incorrect flags settings.  If you
8281.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
8291.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
8301.159Sgdt	rebuild of object files that might have been built
8311.159Sgdt	incorrectly, and ensure that you have at least
8321.159Sgdt	src/lib/libc/Makefile 1.130.
8331.159Sgdt
8341.241Swiz20070210:
8351.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
8361.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
8371.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
8381.158Sdbj        will allow dependencies on those files to get get rebuilt
8391.158Sdbj
8401.157Sapb20070209:
8411.157Sapb        The threading model was changed when the newlock2 branch
8421.157Sapb        was merged to NetBSD-current.  If you boot with a new
8431.157Sapb        kernel (version 4.99.10), then you also need a new pthread
8441.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
8451.157Sapb        an old kernel, then you need the old pthread library
8461.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
8471.157Sapb        the pthread library in sync, old threaded applications should
8481.157Sapb        continue to work with an old or new kernel.  Note that named(8)
8491.157Sapb	is the only threaded application in the base system.
8501.157Sapb
8511.154She20061214:
8521.154She	Following the move of string_to_flags() and flags_to_string()
8531.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
8541.154She	will need to do a "make cleandir" in
8551.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
8561.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
8571.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
8581.156She		as the installation images in distrib/
8591.154She	in order to excise stale references to the old stat_flags.h header
8601.154She	file in the ls sources -- stat_flags.h has been removed.
8611.154She
8621.152Schristos20061108:
8631.152Schristos	The configure script used in the src/tools/gcc compiler has been
8641.152Schristos	changed to indicate that our libc has ssp support built-in and
8651.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
8661.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
8671.152Schristos
8681.151Srpaulo20061009:
8691.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
8701.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
8711.151Srpaulo
8721.150Sbjh2120060814:
8731.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
8741.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
8751.150Sbjh21	kernel configuration for an example.  X servers from the last
8761.150Sbjh21	few years should cope.
8771.150Sbjh21
8781.149Schristos20060703:
8791.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
8801.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
8811.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
8821.149Schristos
8831.148Sdogcow20060627:
8841.148Sdogcow	socket(2) has changed, and its system call has been versioned.
8851.148Sdogcow	For userlands with the old version of socket(2), make sure that
8861.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
8871.148Sdogcow	errors will result.
8881.148Sdogcow
8891.1SabsHints for a more successful build:
8901.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8911.123Sjmc    Use build.sh, but do not use its "expert mode":
8921.132Sjmmv	This will automatically build the tools in the
8931.123Sjmc	   correct order, and it will keep the tools and the
8941.123Sjmc	   new build products from interfering with the running
8951.123Sjmc	   system.  This will allow you to ignore most of the
8961.123Sjmc	   other advice in this file.
8971.2Smrg    Build a new kernel first:
8981.2Smrg	This makes sure that any new system calls or features
8991.2Smrg	   expected by the new userland will be present.  This
9001.2Smrg	   helps to avoid critical errors when upgrading.
9011.1Sabs    Use object directories:
9021.1Sabs	This helps to keep stale object
9031.1Sabs	   files from polluting the build if a Makefile "forgets"
9041.1Sabs	   about one.  It also makes it easier to clean up after
9051.1Sabs	   a build.  It's also necessary if you want to use the
9061.1Sabs	   same source tree for multiple machines.
9071.123Sjmc	   To use object directories with build.sh:
9081.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
9091.123Sjmc	   To use object directories without using build.sh:
9101.1Sabs	    a) cd /usr/src ; make cleandir
9111.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
9121.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
9131.1Sabs	    d) cd /usr/src ; make build
9141.2Smrg	   Note that running "make obj" in a directory will create
9151.2Smrg	   in obj.$MACHINE directory.
9161.1Sabs    Build to a DESTDIR:
9171.123Sjmc	This helps to keep old installed files (especially libraries)
9181.123Sjmc	   from interfering with the new build.
9191.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
9201.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
9211.123Sjmc	   environment variable before running make build.  It should be
9221.123Sjmc	   set to the pathname of an initially empty directory.
9231.123Sjmc	   Problems: if you do not use build.sh, you might need to
9241.123Sjmc		update critical utilities without using DESTDIR since
9251.123Sjmc		nothing is executed from what is installed in DESTDIR.
9261.123Sjmc		(See critical utils, below.)
9271.1Sabs    Build often:
9281.1Sabs	This keeps critical utilities current enough to not choke
9291.1Sabs	on any other part of the source tree that depends on up to
9301.123Sjmc	date functionality.  If you use build.sh, you should not have
9311.123Sjmc	this problem.
9321.241Swiz
9331.1SabsWhat to do if things don't work:
9341.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9351.230StlsWhen things don't work there are usually a few things that commonly
9361.1Sabsshould be done.
9371.1Sabs    1)	make includes
9381.1Sabs	This should be done automatically by make build.
9391.1Sabs    2)  cd share/mk && make install
9401.1Sabs	Again, automatically done by make build.
9411.1Sabs
9421.1SabsFailsafe rebuild of a small part of the tree:
9431.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9441.1SabsTo make sure you rebuild something correctly you want to do
9451.1Sabssomething like the following:
9461.1Sabs    1)  Make sure the includes and .mk files are up to date.
9471.1Sabs    2)  Make sure any program used to build the particular
9481.1Sabs	utility is up to date.  (yacc, lex, etc...)
9491.1Sabs    3)  cd ...path/to/util...
9501.1Sabs	make cleandir
9511.1Sabs	rm ...all obj directories...
9521.1Sabs	make cleandir			# yes, again
9531.1Sabs	make obj
9541.1Sabs	make depend && make
9551.1Sabs
9561.1SabsFailsafe rebuild of the entire tree:
9571.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9581.1SabsIf you really want to make sure the source tree is clean and
9591.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
9601.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
9611.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
9621.1Sabs
9631.1Sabs---cut here---
9641.1Sabs#!/bin/sh
9651.1Sabs. /etc/mk.conf
9661.1Sabs
9671.58Slukemif [ -z $NETBSDSRCDIR ] ; then
9681.58Slukem    NETBSDSRCDIR=/usr/src
9691.1Sabsfi
9701.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
9711.1Sabs    echo Unable to find sources
9721.1Sabs    exit 1
9731.1Sabsfi
9741.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
9751.1Sabs
9761.1Sabsif [ -z $BSDOBJDIR ] ; then
9771.1Sabs    BSDOBJDIR=/usr/obj
9781.1Sabsfi
9791.1Sabsif [ -d $BSDOBJDIR ] ; then
9801.1Sabs    rm -rf $BSDOBJDIR
9811.1Sabsfi
9821.1Sabs
9831.58Slukemcd $NETBSDSRCDIR && make cleandir
9841.1Sabs
9851.1Sabs---cut here---
9861.1Sabs
9871.1SabsCritical utilities:
9881.1Sabs^^^^^^^^^^^^^^^^^^^
9891.3Sitojun	usr.bin/compile_et
9901.1Sabs	usr.bin/make
9911.1Sabs	usr.bin/yacc
9921.1Sabs	usr.bin/lex
9931.11Slukem	usr.bin/xlint
9941.142Sdrochner	usr.bin/config
9951.1Sabs
9961.34SsimonbOther problems and possible solutions:
9971.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9981.1SabsSymptom:Complaints involving a Makefile.
9991.17SerhFix:	Rebuild usr.bin/make:
10001.17Serh	cd usr.bin/make && make && make install
10011.111Ssimonb	Or, a failsafe method if that doesn't work:
10021.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
10031.17Serh
10041.1SabsFix:	Make sure .mk files are up to date.
10051.1Sabs	cd share/mk && make install
10061.2Smrg
10071.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
10081.142SdrochnerFix:	Rebuild usr.bin/config
10091.1Sabs
10101.1SabsSymptom:
10111.1SabsFix:	Rebuild usr.bin/yacc
10121.1Sabs
10131.1SabsSymptom:
10141.1SabsFix:	Rebuild usr.bin/lex
10151.1Sabs
10161.1SabsSymptom:
10171.1SabsFix:	rm /usr/lib/libbfd.a
10181.4Sitojun
10191.4SitojunSymptom:Obsolete intermediate files are used during compilation
10201.4SitojunFix:	Try the following sequence of commands in the directory in question.
10211.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
10221.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
10231.4Sitojun	may remain.  The command tries to clean everything up)
10241.5Swiz
10251.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
10261.207Smbalmer	pointer type
10271.5SwizFix:	Rebuild and install usr.bin/menuc
10281.12Sitojun
10291.12SitojunSymptom:mklocale not found during build in share/locale/ctype
10301.12SitojunFix:	Build and install usr.bin/mklocale
10311.13Sdogcow
10321.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
10331.13SdogcowFix:    Rebuild and install lib/libc
10341.13Sdogcow
10351.142SdrochnerSymptom:usr.bin/config fails to build.
10361.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
10371.13Sdogcow
10381.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
10391.19ScgdFix:    Rebuild and install lib/libc
10401.24Sabs
10411.24SabsSymptom:lint does not understand the '-X' option
10421.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
10431.223Sjoerg
10441.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
10451.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
10461.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
10471.257Sapb
10481.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
10491.257Sapb	No such file or directory.
10501.257SapbCause:	If a directory is created by mistake, then it is sometimes
10511.257Sapb	deleted from the CVS repository using administrative commands
10521.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
10531.257Sapb	contains references to a directory that has been deleted on the
10541.257Sapb	server in this way, then "cvs update" reports this error.
10551.257SapbFix:	Recursively delete the affected directory from your working tree
10561.257Sapb	and try the update again.
1057