UPDATING revision 1.333
11.333Sriastrad$NetBSD: UPDATING,v 1.333 2022/10/08 08:21:56 riastradh 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.331Sriastrad20220921:
231.331Sriastrad	Since the kernel version was bumped to 9.99.100, the bootloader
241.333Sriastrad	must be updated on x86 or EFI boot platforms in order to load
251.333Sriastrad	modules from boot.cfg(5) or interactively at the bootloader
261.333Sriastrad	prompt.
271.333Sriastrad
281.333Sriastrad	The kernel can still load modules at runtime, with modload(8)
291.333Sriastrad	or modules.conf(5), with no bootloader update.  This will not
301.333Sriastrad	affect release branches because it only applies to patch
311.333Sriastrad	numbers >=100.
321.333Sriastrad
331.333Sriastrad	On x86 (i386 or amd64) with BIOS boot, this requires copying a
341.333Sriastrad	new /usr/mdec/boot to /boot.  You can build this in the destdir
351.333Sriastrad	by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
361.333Sriastrad	sys/arch/i386/stand.
371.333Sriastrad
381.333Sriastrad	On platforms with EFI boot (including x86 with EFI boot), this
391.333Sriastrad	requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/
401.333Sriastrad	directory on the EFI system partition.  The boot*.efi file is:
411.333Sriastrad
421.333Sriastrad	aarch64	bootaa64.efi
431.333Sriastrad	amd64	bootx64.efi
441.333Sriastrad	arm	bootarm.efi	(32-bit arm)
451.333Sriastrad	i386	bootx32.efi
461.333Sriastrad
471.333Sriastrad	You can build this in the destdir by running
481.333Sriastrad	`$TOOLDIR/bin/nbmake-$ARCH dependall install' in
491.333Sriastrad	sys/stand/efiboot/boot*.
501.331Sriastrad
511.330Slukem20220821:
521.330Slukem	Support for building extsrc/ has been deprecated.
531.330Slukem	EXTSRCSRCDIR and MKEXTSRC have been deprecated.
541.330Slukem
551.329Smrg20220714:
561.329Smrg	Updates to xorg-server and associated drivers may cause builds to
571.329Smrg	fail.  Cleaning both DESTDIR and the xorg build tree may be needed.
581.329Smrg
591.328Smartin20220628:
601.328Smartin	Changes in the build of src/games/robots require a clean build
611.328Smartin	of that program.
621.328Smartin
631.324Smartin20211116:
641.324Smartin	Changes in the xorg build require clean obj dirs for external/mit/xorg
651.325Smartin	(or a full clean/non-update build).
661.324Smartin
671.323Snia20211112:
681.323Snia	Device tree sources were updated for evbarm.  Some device nodes
691.323Snia	(in particular, ld(4) devices on the ROCKPro64) will be renumbered.
701.323Snia
711.322Smartin20211014:
721.323Snia	MKPIE default for aarch64 has changed, a clean build is required.
731.322Smartin
741.321Schristos20210917:
751.321Schristos	Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
761.321Schristos	ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
771.321Schristos	and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
781.321Schristos
791.319Smrg20210711:
801.319Smrg	Updated GMP sources may require cleaning in tools/gmp and/or in
811.319Smrg	external/lgpl3/gmp/lib, particularly if GCC itself does not build.
821.319Smrg
831.318Smrg20210417:
841.318Smrg	GCC 10 was enabled for several platforms.  If builds fail in either
851.318Smrg	tools/gcc or external/gpl/gcc, first try cleaning those objects and
861.318Smrg	removing the $DESTDIR/usr/include/g++ subdirectory.
871.318Smrg
881.317Srillig20201230:
891.317Srillig	lint1/ops.c is no longer autogenerated.  If this makes the build
901.317Srillig	fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*.
911.317Srillig
921.316Smrg20201016:
931.316Smrg	MIPS kernel modules have been disabled until they work.  This will
941.316Smrg	turn up in extra files in the DESTDIR, which should be cleaned.
951.316Smrg
961.315Smrg20200925:
971.315Smrg	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
981.315Smrg	in both the tools and external dirs.
991.315Smrg
1001.314Smrg20200912:
1011.314Smrg	GCC 9 has arrived for Arm and x86 platforms, and will be coming
1021.314Smrg	for several more, as will binutils 2.34.  Clean as required.
1031.314Smrg
1041.313Smrg20200907:
1051.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
1061.313Smrg	probably requires cleaning the tools/binutils.
1071.313Smrg
1081.311Smrg20200811:
1091.312Smrg	GCC updates may require cleaning the objdir.  This may occur
1101.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
1111.312Smrg	GCC 9 upgrade.
1121.311Smrg
1131.309Schristos20200614:
1141.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
1151.332Sgutterid	should handle the migration.
1161.309Schristos
1171.308Schristos20200601:
1181.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
1191.308Schristos	created in the build directories and need cleaning.
1201.308Schristos
1211.307Smrg20200311:
1221.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
1231.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
1241.307Smrg
1251.306Schristos20191118:
1261.306Schristos	More architectures were switched to gcc8:
1271.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
1281.306Schristos	The same comments as in 20191022 apply.
1291.306Schristos
1301.305Smartin20191112:
1311.305Smartin	The LLVM update requires a clean rebuild for all architectures using
1321.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
1331.305Smartin
1341.304Smartin20191022:
1351.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
1361.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
1371.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
1381.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
1391.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
1401.304Smartin	daily builds and install that before doing the next in-place build.
1411.304Smartin
1421.303Smrg20191001:
1431.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
1441.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
1451.303Smrg	directory, and also clean src/external/gpl3/gcc.
1461.303Smrg
1471.302Sriastrad20190903:
1481.306Schristos	Files with names that coincide with existing files' names on
1491.302Sriastrad	case-insensitive file systems were inadvertently committed, for
1501.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
1511.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
1521.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
1531.302Sriastrad	manually delete the following files in your DESTDIR (which is
1541.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
1551.302Sriastrad	them:
1561.302Sriastrad
1571.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
1581.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
1591.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
1601.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
1611.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
1621.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
1631.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
1641.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
1651.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
1661.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
1671.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
1681.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
1691.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
1701.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
1711.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
1721.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
1731.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
1741.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
1751.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
1761.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
1771.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
1781.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
1791.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
1801.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
1811.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
1821.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
1831.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
1841.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
1851.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
1861.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
1871.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
1881.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
1891.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
1901.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
1911.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
1921.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
1931.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
1941.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
1951.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
1961.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
1971.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
1981.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
1991.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
2001.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
2011.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
2021.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
2031.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
2041.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
2051.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
2061.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
2071.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
2081.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
2091.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
2101.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
2111.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
2121.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
2131.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
2141.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
2151.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
2161.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
2171.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
2181.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
2191.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
2201.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
2211.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
2221.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
2231.302Sriastrad
2241.302Sriastrad	We will re-import these radeon firmware images another way
2251.302Sriastrad	later.
2261.302Sriastrad
2271.301Smartin20190727:
2281.301Smartin	The uefi bootloader has gained tftp support and needs a clean
2291.301Smartin	build. If you do update builds, manually clean its object
2301.301Smartin	directory by something like:
2311.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
2321.301Smartin
2331.300Smartin20190723:
2341.300Smartin	The jemalloc allocator in libc is now build without extended
2351.300Smartin	debugging (for performance reasons). In update builds make sure
2361.326Sandvar	to rebuild it completely, by removing all affected object files,
2371.300Smartin	including compat builds, something like:
2381.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
2391.300Smartin
2401.299Smrg20190207:
2411.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
2421.299Smrg
2431.298Smartin20180924:
2441.298Smartin	A newer OpenSSL version has been imported. If you are doing
2451.298Smartin	update builds, make sure to remove all old obj dirs, like:
2461.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
2471.298Smartin
2481.297Sjoerg20180717:
2491.297Sjoerg	On aarch64 int64_t and related types have changed from long long
2501.297Sjoerg	to long. This requires recompiling all C++ binaries.
2511.297Sjoerg
2521.296Smartin20180713:
2531.296Smartin	On amd64 and i386 static binaries are now build position
2541.296Smartin	independend. This requires recompilation of all object
2551.296Smartin	files used to create the crunched /rescue binary.
2561.296Smartin	Clean the rescue directory in your obj directory before
2571.296Smartin	doing an update build, otherwise linking will fail.
2581.296Smartin
2591.293Sjakllsch20180414:
2601.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
2611.293Sjakllsch	removal of tools/binutils objects directory may be required
2621.293Sjakllsch	to fix tools build failure.
2631.293Sjakllsch
2641.292Smrg20180311:
2651.292Smrg	bdftopcf was updated and may need cleaning in the
2661.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
2671.292Smrg	link errors.
2681.292Smrg
2691.291Smrg20180212:
2701.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
2711.291Smrg	any failure that looks like GCC or openssl is best handled by
2721.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
2731.291Smrg	is recommended if build failures occur.
2741.291Smrg
2751.288Smartin20171225:
2761.288Smartin	removal of the vadvise syscall requires manual removal of all
2771.288Smartin	associated files from the libc build object directory (including
2781.289Schristos	the .depend files) - a command like:
2791.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
2801.289Schristos	For architectures that support multiple "compat" binary targets,
2811.289Schristos	you'll need to cleanup both the regular libc directory and the
2821.290Smartin	compat ones (the above command will do that).
2831.288Smartin
2841.287Skre20171010:
2851.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
2861.287Skre	means that its objdir (or *.d and .depend at least) might need
2871.287Skre	to be manually removed - or a build done once without -u.
2881.287Skre
2891.286Smrg20170822:
2901.286Smrg	a new version of GMP has been imported and probably
2911.286Smrg	will break parts of builds related to themselves or GCC, both
2921.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2931.286Smrg	and MPC objdirs or build once without -u.
2941.286Smrg
2951.285Smrg20170816:
2961.285Smrg	a new version of MPFR and MPC have been imported and probably
2971.285Smrg	will break parts of builds related to themselves or GCC, both
2981.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
2991.285Smrg	and MPC objdirs or build once without -u.
3001.285Smrg
3011.284Smartin20170402:
3021.284Smartin	a new version of dhcpcd has been imported, which does not support
3031.284Smartin	update builds from the previous version. Remove your
3041.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
3051.284Smartin
3061.281Sroy20170211:
3071.281Sroy	a new terminfo database has been imported.
3081.281Sroy	The structure of it has changed slightly from prior versions and
3091.281Sroy	an updated tic tool is required.
3101.281Sroy	If you build.sh, don't use -u
3111.281Sroy
3121.280Skre20170207:
3131.278Skre	various arch dependent libc/exect.S files were removed
3141.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
3151.279Skre	if it exists) or do a clean build.
3161.279Skre	(This is a bug in the make system, it should be corrected without
3171.279Skre	human intervention, but isn't.)
3181.278Skre
3191.277Smartin20170104:
3201.277Smartin	xinput build options have changed.
3211.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
3221.277Smartin	if you build.sh -u
3231.277Smartin
3241.276Smartin20170103:
3251.276Smartin	a new version of flex has been imported.
3261.276Smartin	Remove the file from obj (external/bsd/flex)
3271.276Smartin	if you build.sh -u
3281.276Smartin
3291.275Sspz20161014:
3301.275Sspz	a new version of OpenSSL has been imported.
3311.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
3321.275Sspz	if you build.sh -u
3331.275Sspz
3341.274Smartin20161009:
3351.274Smartin	a new version of dhcpcd has been imported with slightly changed
3361.274Smartin	build infrastructure. When doing a build.sh -u this requires
3371.274Smartin	pruning the external/bsd/dhcpcd objdir.
3381.274Smartin
3391.273Smrg20160914:
3401.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
3411.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
3421.273Smrg	and a clean objdir.
3431.273Smrg
3441.272Sdholland20160527:
3451.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
3461.272Sdholland	been enabled. (see the amd64 entry two down for further info)
3471.272Sdholland
3481.270Schristos20160418:
3491.270Schristos	libedit needs manual removal of all autogenerated files since
3501.271Schristos	some of them are not autogenerated anymore. Remember that there
3511.271Schristos	might be two copies of libedit if your platform builds "compat".
3521.270Schristos
3531.268Sriastrad20160410:
3541.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
3551.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
3561.268Sriastrad	executables, means all code, including executables and not just
3571.268Sriastrad	shared libraries, is position-independent and hence able to be
3581.268Sriastrad	relocated by ASLR, address space layout randomization.
3591.268Sriastrad
3601.268Sriastrad	The change was made in Makefile variables for compiler and
3611.268Sriastrad	linker flags, for which make(1) does not record dependencies,
3621.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
3631.268Sriastrad
3641.268Sriastrad	Partial rebuilds with some modified source files will likely
3651.268Sriastrad	fail when linking executables, since the linker refuses to mix
3661.268Sriastrad	position-independent code with position-dependent code in
3671.268Sriastrad	position-independent executables:
3681.268Sriastrad
3691.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
3701.268Sriastrad
3711.267Smrg20160401:
3721.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
3731.269Sdholland	Some people have found that cleandir is not sufficient, so if
3741.269Sdholland	in doubt delete the entire object directory tree for gcc.
3751.267Smrg
3761.266Saymeric20160306:
3771.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
3781.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
3791.265Saymeric	non-NetBSD hosts if linked with stale object files produced
3801.265Saymeric	while they included a non-NetBSD regex.h.
3811.265Saymeric	In any case, you should "make cleandir" at least these tools
3821.265Saymeric	before updating your toolchain.
3831.265Saymeric
3841.264Smartin20160125:
3851.264Smartin	Dtrace has been enabled by default on some architectures.
3861.264Smartin	When doing an update build, make sure to clean the etc/mtree
3871.264Smartin	object directory before starting the build - otherwise the
3881.264Smartin	needed directories in destdir will not be created.
3891.264Smartin	An easy way to do this is:
3901.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
3911.264Smartin
3921.263Sdholland20150818:
3931.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
3941.263Sdholland	again.
3951.263Sdholland
3961.262Schristos20150413:
3971.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
3981.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
3991.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
4001.262Schristos
4011.261Smartin20150404:
4021.261Smartin	Lint changes require a full rebuild of the tool, so make
4031.261Smartin	sure to build without -u option to build.sh, or manually
4041.261Smartin	do a make cleandir in src/tools/lint1 and
4051.261Smartin	src/usr.bin/xlint.
4061.261Smartin
4071.260Sskrll20150310:
4081.260Sskrll	Improvements to openssl for arm mean that update builds of
4091.260Sskrll	the openssl libraries will fail. A make cleandir in
4101.260Sskrll	external/bsd/openssl/lib is needed
4111.260Sskrll
4121.258Smartin20141026:
4131.259Smsaitoh	A mishap during the import of pppd may cause your corruption
4141.258Smartin	in your cvs directory if you happened to do a cvs update
4151.258Smartin	during a short period of time. To fix, just remove the
4161.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
4171.258Smartin	and let cvs restore it on next update.
4181.258Smartin
4191.256Sapb20140721:
4201.256Sapb	The src/external/mit/lua/src directory was accidentally created
4211.256Sapb	and then deleted in the CVS repository.  If you get errors like
4221.256Sapb
4231.256Sapb	cvs [update aborted]: cannot open directory
4241.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
4251.256Sapb
4261.256Sapb	then delete your local copy of that directory tree and try again.
4271.256Sapb
4281.255Sjoerg20140530:
4291.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
4301.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
4311.255Sjoerg
4321.251Smartin20140131:
4331.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
4341.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
4351.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
4361.251Smartin
4371.250Schristos20131227:
4381.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
4391.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
4401.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
4411.250Schristos	   statements to avoid being exposed.
4421.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
4431.250Schristos	   to make clean in libc
4441.250Schristos
4451.249Smrg20131129:
4461.249Smrg	The GMP sources were updated, and builds will likely fail without
4471.249Smrg	cleaning their build trees for both tools and in-tree, like below.
4481.249Smrg
4491.248Smrg20131128:
4501.248Smrg	The MPC and MPFR sources were updated, and builds may require their
4511.248Smrg	tools and in-tree directories cleaned for successful updates.
4521.248Smrg
4531.246Smartin20130605:
4541.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
4551.247Sspz	to IPSEC (and the older IPSEC version removed).
4561.247Sspz
4571.247Sspz20130605:
4581.320Sandvar	Previous freetype installations erroneously installed private
4591.246Smartin	header files. If you are building against a non-empty $DESTDIR,
4601.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
4611.246Smartin
4621.245Smrg20130531:
4631.245Smrg	The xdm update may cause build failure due to xdm.man being
4641.245Smrg	in the obj tree.  Make sure to ensure any like this:
4651.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
4661.245Smrg	is fixed by deleting the xdm.man in the obj tree.
4671.245Smrg
4681.244Smrg20130530:
4691.244Smrg	Updates of many xsrc packages will leave old .pc files around.
4701.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
4711.244Smrg
4721.242Schristos20130301:
4731.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
4741.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
4751.242Schristos
4761.238Sdholland20120726:
4771.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
4781.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
4791.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
4801.241Swiz	some cases may succeed and install broken OpenSSL libraries that
4811.240Sdholland	cause third-party software to link incorrectly and/or crash.
4821.238Sdholland
4831.237Swiz20120507:
4841.241Swiz	The database schema for makemandb was changed.  You will
4851.237Swiz	need to update the database using 'makemandb -f' or wait
4861.237Swiz	for the next weekly run to fix it.
4871.237Swiz
4881.236Sbsh20120319:
4891.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
4901.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
4911.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
4921.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
4931.236Sbsh	mk.conf.
4941.236Sbsh
4951.235Sjoerg20120216:
4961.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
4971.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
4981.239Sdholland	and 20120216, daily and weekly could have created an unreadable
4991.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
5001.235Sjoerg	the next run of weekly will fix it.
5011.233Sjoerg
5021.232Schristos20111227:
5031.232Schristos	If you built between 20111225 and 20111227 you need to remove
5041.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
5051.232Schristos	bump has been reverted.
5061.232Schristos
5071.231Stls20111125:
5081.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
5091.231Stls	means it should no longer be explicitly listed in kernel
5101.231Stls	configuration files.  The line "pseudo-device rnd" should be
5111.231Stls	removed from any custom kernel config files users may have.
5121.231Stls
5131.230Stls20111119:
5141.230Stls	A problem with the datastructures used by the rndctl(8)
5151.230Stls	utility (pointers in datastructures in an array, making 32->64
5161.230Stls	bit compatibility very painful) has been fixed in a
5171.230Stls	non-backwards-compatible way.  If you replace your kernel,
5181.230Stls	replace your rndctl executable too.
5191.241Swiz
5201.229Sjym20111001:
5211.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
5221.229Sjym	changed and their new version is not backward compatible with the old
5231.241Swiz	one.  So ensure that all consumers of these functions (currently:
5241.229Sjym	quota2 code and its tests) are updated together with the new lib.
5251.229Sjym
5261.228Smrg20110817:
5271.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
5281.228Smrg	DESTDIR for them should be deleted before updating.
5291.228Smrg
5301.227Sriastrad20110806:
5311.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
5321.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
5331.227Sriastrad
5341.226Smrg20110805:
5351.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
5361.226Smrg	the tree to be cleaned.  Best to delete both objdir and
5371.226Smrg	DESTDIR before running this update.  So far, only the
5381.226Smrg	sparc64, mips and powerpc platforms have changed.
5391.226Smrg
5401.225Smatt20110803:
5411.241Swiz	The layout of external/public-domain/xz has changed.  To do an
5421.225Smatt	update build you will have to remove the contents of the OBJDIR
5431.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
5441.225Smatt	is now a directory.
5451.225Smatt
5461.223Sjoerg20110410:
5471.241Swiz	The configuration of src/tools/gcc has changed.  To do an
5481.224Sdholland	update build you have to clean both tools/binutils and
5491.224Sdholland	tools/gcc by hand.
5501.223Sjoerg
5511.222Splunky20110328:
5521.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
5531.241Swiz	ordering issues with "make all".  It may be necessary to remove
5541.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
5551.222Splunky	if your update build fails, as the "Xorg" entry there is now a
5561.222Splunky	directory.
5571.222Splunky
5581.220Sjoerg20110121:
5591.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
5601.220Sjoerg	the build of individual parts of the tree.  This is handled
5611.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
5621.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
5631.218Sjoerg
5641.217Sjruoho20101217:
5651.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
5661.241Swiz	by default.  It may be necessary to manually update passwd(5) and
5671.217Sjruoho	group(5) in order to make the program work with existing setups.
5681.217Sjruoho
5691.216Schristos20101125:
5701.327Sandvar	The latest changes to setenv(3) disallow setting environment
5711.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
5721.241Swiz	assumed that this was allowed.  Installing a new libc with an
5731.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
5741.216Schristos	break which affects the autoconf tests for dependency finding,
5751.216Schristos	so building gcc will end up printing:
5761.216Schristos	    checking dependency style of gcc... none
5771.216Schristos	    configure: error: no usable dependency style found
5781.216Schristos	Fix it by rebuilding and re-installing env.
5791.138Slukem
5801.215Smrg20101119:
5811.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
5821.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
5831.215Smrg	have any build problems with xsrc, or problems with mismatched
5841.215Smrg	versions between xorg-server and drivers.
5851.215Smrg
5861.213Sjmmv20100604:
5871.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
5881.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
5891.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
5901.213Sjmmv	trees by hand.
5911.213Sjmmv
5921.211Stnozaki20100522:
5931.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
5941.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
5951.212Smrg	build problems with xsrc.
5961.212Smrg
5971.212Smrg20100522:
5981.320Sandvar	private section of <ctype.h> was split, and now mklocale(1)
5991.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
6001.211Stnozaki
6011.210Schristos20100520:
6021.241Swiz	The location of the xkb compiled descriptions has changed.  Please
6031.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
6041.210Schristos
6051.209Snjoly20100222:
6061.209Snjoly	The shared objects file extension has been changed from .so to
6071.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
6081.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
6091.209Snjoly	your object directories.
6101.209Snjoly
6111.208Sroy20100204:
6121.208Sroy	The termcap database has been removed from the sources,
6131.208Sroy	but has not been marked obsolete so it is not removed
6141.208Sroy	from the system when upgrading.
6151.208Sroy	As such, you will need to remove them from your object
6161.208Sroy	and destination directories.
6171.208Sroy
6181.203Sdyoung20091101:
6191.205Sdholland        After updating, it may be necessary to make the 'cleandir'
6201.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
6211.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
6221.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
6231.203Sdyoung
6241.202Smrg20091001:
6251.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
6261.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
6271.206Sdholland
6281.206Sdholland20091001:
6291.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
6301.202Smrg	symlink, failing the build.  Delete the link, and the subdir
6311.202Smrg	it is in, and retry your build.
6321.202Smrg
6331.201Sdsl20090718:
6341.201Sdsl	libc build changed so that strchr() provides the extra entry
6351.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
6361.201Sdsl	may fail because the archive contains the unwanted index.o.
6371.201Sdsl	(Similarly for strrchr() and rindex().)
6381.201Sdsl
6391.198Smrg20090709:
6401.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
6411.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
6421.198Smrg
6431.197Smrg20090616:
6441.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
6451.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
6461.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
6471.197Smrg	subdirectory has been changed into a file, and this needs to
6481.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
6491.197Smrg
6501.195Sperry20090501:
6511.195Sperry	Several new functions were added to string.h/libc, and this
6521.195Sperry	can cause autoconf problems during the tool build for people
6531.241Swiz	who fail to clean out their tools objects properly.  If you
6541.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
6551.195Sperry	failure during the tool build, clean out all your tools
6561.195Sperry	objects and start again.
6571.195Sperry
6581.194Smrg20090325:
6591.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
6601.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
6611.194Smrg
6621.192Sskrll20090126:
6631.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
6641.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
6651.207Smbalmer	to avoid using the old assembly stub.
6661.192Sskrll
6671.191Sjoerg20090202:
6681.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
6691.320Sandvar	detection.  It is recommended to rebuild the cache with
6701.191Sjoerg	``pkg_admin rebuild''.
6711.191Sjoerg
6721.184Schristos20090110:
6731.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
6741.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
6751.188Schristos	   This is needed even in the MODULAR kernel because there is
6761.188Schristos	   conditionally compiled code in rtsock.c.
6771.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
6781.184Schristos	   before installing.
6791.184Schristos	3. If you don't use build.sh and you build directly to root, and
6801.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
6811.184Schristos	   are installed properly, and start building libraries first libc
6821.184Schristos	   and libutil, install them and then continue building all the
6831.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
6841.184Schristos	   the new libraries are installed, you can restart the build.
6851.184Schristos	4. If you compile packages and you notice link time warnings,
6861.189Shubertf	   rebuild the required packages to update their shared libraries.
6871.189Shubertf	   Any package you rebuild will require rebuilding all the packages
6881.189Shubertf	   that depend on it.
6891.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
6901.186Schristos	   will be upgraded and it will not be backwards compatible.
6911.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
6921.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
6931.241Swiz	   for utmp.  You are better off removing the old files after
6941.190Sapb	   upgrading.  The automated clearing of /var/run during
6951.190Sapb	   boot, and the automated rotating of files in /var/log by
6961.190Sapb	   newsyslog(8), may mean that you do not have to remove the
6971.190Sapb	   files manually.
6981.190Sapb	7. The optional accounting file (/var/account/acct, see
6991.190Sapb	   accton(8)) has not been versioned, and will need to be
7001.190Sapb	   removed.  The automatic rotation of the accounting file by
7011.190Sapb	   /etc/daily limits the bad consequences of failure to remove
7021.190Sapb	   the file.
7031.196Sdholland	8. Application software that writes time_t to binary files on
7041.241Swiz	   disk will break or need attention.  Most notably: if you are
7051.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
7061.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
7071.185Sjmcneill
7081.183Spgoyette20081219:
7091.183Spgoyette	config(1) has been updated, and one of the files it creates -
7101.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
7111.183Spgoyette	(done automatically by build.sh) and then you need to rerun
7121.183Spgoyette	config on all kernel configuration files before rebuilding those
7131.183Spgoyette	kernels.
7141.183Spgoyette
7151.181Scube20081205:
7161.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
7171.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
7181.181Scube	set and will appear as extra files for MKX11=no update builds.
7191.178Slukem
7201.179Stsutsui20081122:
7211.182Stsutsui	On i386, various kernel options(4) in GENERIC including
7221.180Swiz	file systems have been disabled and moved into kernel modules.
7231.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
7241.179Stsutsui	following files as well as a new GENERIC kernel:
7251.179Stsutsui
7261.179Stsutsui	- build and install kernel modules from src/sys/modules
7271.179Stsutsui
7281.179Stsutsui	- install the latest bootloader, which will load a module
7291.180Swiz	  for the file system from which the kernel is loaded automatically
7301.179Stsutsui
7311.180Swiz	If you have to load your kernel from a file system which is not of
7321.180Swiz	the same type as the root file system, you have to load the necessary
7331.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
7341.179Stsutsui
7351.178Slukem20080827:
7361.178Slukem	If you built and installed a libc from sources between
7371.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
7381.178Slukem	which results in false errors reported by lint(1).
7391.178Slukem	Since this breaks the libc build itself, manual help is
7401.180Swiz	needed -- lint must be disabled temporarily, e.g.:
7411.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
7421.178Slukem
7431.177Schristos20080813:
7441.177Schristos	MKDEBUG build was broken because the .depend files did not know
7451.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
7461.177Schristos
7471.200Sdholland20080802:
7481.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
7491.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
7501.200Sdholland	for -current.
7511.200Sdholland
7521.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
7531.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
7541.200Sdholland	be recompiled.
7551.200Sdholland
7561.200Sdholland	One way to find affected pkgsrc packages:
7571.200Sdholland
7581.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
7591.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
7601.200Sdholland
7611.175Ssimonb20080731:
7621.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
7631.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
7641.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
7651.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
7661.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
7671.176Ssimonb	also requires the super block to be in the UFS2 format.  You
7681.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
7691.175Ssimonb
7701.174Slukem20080721:
7711.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
7721.174Slukem	isn't defined.
7731.174Slukem
7741.173Sfreza20080531:
7751.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
7761.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
7771.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
7781.241Swiz	won't work correctly.  The following sequence of commands:
7791.173Sfreza
7801.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
7811.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
7821.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
7831.173Sfreza
7841.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
7851.173Sfreza
7861.172Slukem20080503:
7871.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
7881.172Slukem
7891.171She20080521:
7901.171She	For a while, unprivileged UPDATE builds would fail to
7911.171She	succeed at the checkflist stage, complaining that
7921.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
7931.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
7941.171She	If you already hit this problem, update the .mk file,
7951.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
7961.171She
7971.174Slukem20080303:
7981.174Slukem	Linker warnings are now fatal if $WARNS>0.
7991.174Slukem
8001.170Schristos20080126:
8011.170Schristos	The posix_fadvise system call has been changed from an assembly
8021.241Swiz	stub, to a c file that calls an assembly stub.  You need to
8031.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
8041.170Schristos	avoid using the old assembly stub.
8051.170Schristos
8061.168Sjoerg20071209:
8071.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
8081.168Sjoerg	get ACPI errors before the attachment, please update your kernel
8091.169Swiz	configuration file appropriately or see GENERIC for more details.
8101.168Sjoerg
8111.166Sxtraeme20071115:
8121.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
8131.166Sxtraeme	argument specified in the kernel configuration file is not valid
8141.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
8151.241Swiz	rather than the EC address port.  Please update your kernel
8161.167Swiz	configuration file appropriately or see GENERIC for more details.
8171.166Sxtraeme
8181.165Sjmmv20071028:
8191.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
8201.165Sjmmv	You need to update any custom kernel configuration file you have
8211.165Sjmmv	to remove any references to pccons (which includes removing the
8221.165Sjmmv	now useless XSERVER option) and replace them with the correct
8231.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
8241.165Sjmmv	for more details.
8251.165Sjmmv
8261.164Sgdt20070913:
8271.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
8281.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
8291.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
8301.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
8311.164Sgdt	could not enumerate interfaces.  (These are noted because
8321.164Sgdt	normal kernel/userspace version matching hygiene is not
8331.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
8341.164Sgdt	and userland are from after 20070913.
8351.164Sgdt
8361.163Sjoerg20070703:
8371.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
8381.199Sdholland	calls the target-specific strip program, and the logic to pass
8391.199Sdholland	down STRIP from make has been removed.  This requires a
8401.199Sdholland	re-installation of tools.
8411.163Sjoerg
8421.161Sdsl20070422:
8431.161Sdsl	The way OS emulations lookup filenames inside the emulation root
8441.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
8451.161Sdsl	to userspace) namei() and lookup() directly check the emulation
8461.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
8471.167Swiz	root file system will be relative to that file system - unless they
8481.161Sdsl	start /../ this is useful when the emulated root is a real install
8491.161Sdsl	that has such links.
8501.161Sdsl	This might affect symlinks that have been added to reference outside
8511.161Sdsl	the emulated root.
8521.161Sdsl
8531.160Sjmcneill20070412:
8541.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
8551.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
8561.160Sjmcneill	example.
8571.160Sjmcneill
8581.159Sgdt20070319:
8591.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
8601.159Sgdt        on many platforms due to incorrect flags settings.  If you
8611.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
8621.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
8631.159Sgdt	rebuild of object files that might have been built
8641.159Sgdt	incorrectly, and ensure that you have at least
8651.159Sgdt	src/lib/libc/Makefile 1.130.
8661.159Sgdt
8671.241Swiz20070210:
8681.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
8691.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
8701.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
8711.158Sdbj        will allow dependencies on those files to get get rebuilt
8721.158Sdbj
8731.157Sapb20070209:
8741.157Sapb        The threading model was changed when the newlock2 branch
8751.157Sapb        was merged to NetBSD-current.  If you boot with a new
8761.157Sapb        kernel (version 4.99.10), then you also need a new pthread
8771.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
8781.157Sapb        an old kernel, then you need the old pthread library
8791.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
8801.157Sapb        the pthread library in sync, old threaded applications should
8811.157Sapb        continue to work with an old or new kernel.  Note that named(8)
8821.157Sapb	is the only threaded application in the base system.
8831.157Sapb
8841.154She20061214:
8851.154She	Following the move of string_to_flags() and flags_to_string()
8861.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
8871.154She	will need to do a "make cleandir" in
8881.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
8891.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
8901.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
8911.156She		as the installation images in distrib/
8921.154She	in order to excise stale references to the old stat_flags.h header
8931.154She	file in the ls sources -- stat_flags.h has been removed.
8941.154She
8951.152Schristos20061108:
8961.152Schristos	The configure script used in the src/tools/gcc compiler has been
8971.152Schristos	changed to indicate that our libc has ssp support built-in and
8981.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
8991.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
9001.152Schristos
9011.151Srpaulo20061009:
9021.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
9031.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
9041.151Srpaulo
9051.150Sbjh2120060814:
9061.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
9071.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
9081.150Sbjh21	kernel configuration for an example.  X servers from the last
9091.150Sbjh21	few years should cope.
9101.150Sbjh21
9111.149Schristos20060703:
9121.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
9131.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
9141.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
9151.149Schristos
9161.148Sdogcow20060627:
9171.148Sdogcow	socket(2) has changed, and its system call has been versioned.
9181.148Sdogcow	For userlands with the old version of socket(2), make sure that
9191.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
9201.148Sdogcow	errors will result.
9211.148Sdogcow
9221.1SabsHints for a more successful build:
9231.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9241.123Sjmc    Use build.sh, but do not use its "expert mode":
9251.132Sjmmv	This will automatically build the tools in the
9261.123Sjmc	   correct order, and it will keep the tools and the
9271.123Sjmc	   new build products from interfering with the running
9281.123Sjmc	   system.  This will allow you to ignore most of the
9291.123Sjmc	   other advice in this file.
9301.2Smrg    Build a new kernel first:
9311.2Smrg	This makes sure that any new system calls or features
9321.2Smrg	   expected by the new userland will be present.  This
9331.2Smrg	   helps to avoid critical errors when upgrading.
9341.1Sabs    Use object directories:
9351.1Sabs	This helps to keep stale object
9361.1Sabs	   files from polluting the build if a Makefile "forgets"
9371.1Sabs	   about one.  It also makes it easier to clean up after
9381.1Sabs	   a build.  It's also necessary if you want to use the
9391.1Sabs	   same source tree for multiple machines.
9401.123Sjmc	   To use object directories with build.sh:
9411.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
9421.123Sjmc	   To use object directories without using build.sh:
9431.1Sabs	    a) cd /usr/src ; make cleandir
9441.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
9451.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
9461.1Sabs	    d) cd /usr/src ; make build
9471.2Smrg	   Note that running "make obj" in a directory will create
9481.2Smrg	   in obj.$MACHINE directory.
9491.1Sabs    Build to a DESTDIR:
9501.123Sjmc	This helps to keep old installed files (especially libraries)
9511.123Sjmc	   from interfering with the new build.
9521.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
9531.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
9541.123Sjmc	   environment variable before running make build.  It should be
9551.123Sjmc	   set to the pathname of an initially empty directory.
9561.123Sjmc	   Problems: if you do not use build.sh, you might need to
9571.123Sjmc		update critical utilities without using DESTDIR since
9581.123Sjmc		nothing is executed from what is installed in DESTDIR.
9591.123Sjmc		(See critical utils, below.)
9601.1Sabs    Build often:
9611.1Sabs	This keeps critical utilities current enough to not choke
9621.1Sabs	on any other part of the source tree that depends on up to
9631.123Sjmc	date functionality.  If you use build.sh, you should not have
9641.123Sjmc	this problem.
9651.241Swiz
9661.1SabsWhat to do if things don't work:
9671.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9681.230StlsWhen things don't work there are usually a few things that commonly
9691.1Sabsshould be done.
9701.1Sabs    1)	make includes
9711.1Sabs	This should be done automatically by make build.
9721.1Sabs    2)  cd share/mk && make install
9731.1Sabs	Again, automatically done by make build.
9741.1Sabs
9751.1SabsFailsafe rebuild of a small part of the tree:
9761.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9771.1SabsTo make sure you rebuild something correctly you want to do
9781.1Sabssomething like the following:
9791.1Sabs    1)  Make sure the includes and .mk files are up to date.
9801.1Sabs    2)  Make sure any program used to build the particular
9811.1Sabs	utility is up to date.  (yacc, lex, etc...)
9821.1Sabs    3)  cd ...path/to/util...
9831.1Sabs	make cleandir
9841.1Sabs	rm ...all obj directories...
9851.1Sabs	make cleandir			# yes, again
9861.1Sabs	make obj
9871.1Sabs	make depend && make
9881.1Sabs
9891.1SabsFailsafe rebuild of the entire tree:
9901.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9911.1SabsIf you really want to make sure the source tree is clean and
9921.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
9931.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
9941.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
9951.1Sabs
9961.1Sabs---cut here---
9971.1Sabs#!/bin/sh
9981.1Sabs. /etc/mk.conf
9991.1Sabs
10001.58Slukemif [ -z $NETBSDSRCDIR ] ; then
10011.58Slukem    NETBSDSRCDIR=/usr/src
10021.1Sabsfi
10031.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
10041.1Sabs    echo Unable to find sources
10051.1Sabs    exit 1
10061.1Sabsfi
10071.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
10081.1Sabs
10091.1Sabsif [ -z $BSDOBJDIR ] ; then
10101.1Sabs    BSDOBJDIR=/usr/obj
10111.1Sabsfi
10121.1Sabsif [ -d $BSDOBJDIR ] ; then
10131.1Sabs    rm -rf $BSDOBJDIR
10141.1Sabsfi
10151.1Sabs
10161.58Slukemcd $NETBSDSRCDIR && make cleandir
10171.1Sabs
10181.1Sabs---cut here---
10191.1Sabs
10201.1SabsCritical utilities:
10211.1Sabs^^^^^^^^^^^^^^^^^^^
10221.3Sitojun	usr.bin/compile_et
10231.1Sabs	usr.bin/make
10241.1Sabs	usr.bin/yacc
10251.1Sabs	usr.bin/lex
10261.11Slukem	usr.bin/xlint
10271.142Sdrochner	usr.bin/config
10281.1Sabs
10291.34SsimonbOther problems and possible solutions:
10301.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10311.1SabsSymptom:Complaints involving a Makefile.
10321.17SerhFix:	Rebuild usr.bin/make:
10331.17Serh	cd usr.bin/make && make && make install
10341.111Ssimonb	Or, a failsafe method if that doesn't work:
10351.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
10361.17Serh
10371.1SabsFix:	Make sure .mk files are up to date.
10381.1Sabs	cd share/mk && make install
10391.2Smrg
10401.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
10411.142SdrochnerFix:	Rebuild usr.bin/config
10421.1Sabs
10431.1SabsSymptom:
10441.1SabsFix:	Rebuild usr.bin/yacc
10451.1Sabs
10461.1SabsSymptom:
10471.1SabsFix:	Rebuild usr.bin/lex
10481.1Sabs
10491.1SabsSymptom:
10501.1SabsFix:	rm /usr/lib/libbfd.a
10511.4Sitojun
10521.4SitojunSymptom:Obsolete intermediate files are used during compilation
10531.4SitojunFix:	Try the following sequence of commands in the directory in question.
10541.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
10551.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
10561.4Sitojun	may remain.  The command tries to clean everything up)
10571.5Swiz
10581.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
10591.207Smbalmer	pointer type
10601.5SwizFix:	Rebuild and install usr.bin/menuc
10611.12Sitojun
10621.12SitojunSymptom:mklocale not found during build in share/locale/ctype
10631.12SitojunFix:	Build and install usr.bin/mklocale
10641.13Sdogcow
10651.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
10661.13SdogcowFix:    Rebuild and install lib/libc
10671.13Sdogcow
10681.142SdrochnerSymptom:usr.bin/config fails to build.
10691.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
10701.13Sdogcow
10711.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
10721.19ScgdFix:    Rebuild and install lib/libc
10731.24Sabs
10741.24SabsSymptom:lint does not understand the '-X' option
10751.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
10761.223Sjoerg
10771.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
10781.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
10791.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
10801.257Sapb
10811.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
10821.257Sapb	No such file or directory.
10831.257SapbCause:	If a directory is created by mistake, then it is sometimes
10841.257Sapb	deleted from the CVS repository using administrative commands
10851.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
10861.257Sapb	contains references to a directory that has been deleted on the
10871.257Sapb	server in this way, then "cvs update" reports this error.
10881.257SapbFix:	Recursively delete the affected directory from your working tree
10891.257Sapb	and try the update again.
1090