UPDATING revision 1.344
11.344Sgutterid$NetBSD: UPDATING,v 1.344 2023/09/24 16:33:41 gutteridge 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.343Sriastrad20230828:
231.343Sriastrad	If:
241.343Sriastrad        - you updated to current and ran postinstall between 20230826
251.343Sriastrad	  and 20230828 inclusive, and
261.343Sriastrad        - you are not using anything outside the base system to
271.343Sriastrad	  populate /etc/openssl/certs (e.g., manually adding
281.343Sriastrad	  certificates or using ca-certificates or mozilla-rootcerts or
291.343Sriastrad	  mozilla-rootcerts-openssl from pkgsrc),
301.343Sriastrad	delete /etc/openssl/certs and rerun postinstall or just
311.343Sriastrad	`certctl rehash'.
321.343Sriastrad
331.343Sriastrad	Otherwise, certctl(8) will think someone else has left
341.343Sriastrad	/etc/openssl/certs in the way and will avoid clobbering it on
351.343Sriastrad	upgrade from older NetBSD.
361.343Sriastrad
371.341Slukem20230718:
381.341Slukem	build.sh will use mk.conf in the same directory as build.sh instead
391.341Slukem	of /etc/mk.conf, unless MAKECONF is already defined in the environment.
401.341Slukem
411.342Smartin20230714:
421.342Smartin	Import of gcc 10.5 requires a clean build of at least tools/gcc
431.342Smartin	and external/gpl3/gcc* object directories. An update build
441.342Smartin	without cleaning will result in obscure failures in rare corner
451.342Smartin	cases.
461.342Smartin
471.339Smartin20230604:
481.339Smartin	Building native kernels with the installed make(1) instead of
491.339Smartin	the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland
501.339Smartin	has not been updated. Note that this is an unsupported build
511.339Smartin	configuration (but usually works if userland is -current enough).
521.338Slukem
531.338Slukem20230523:
541.338Slukem	ctfmerge was fixed as macOS host tool. This may require a clean tools
551.338Slukem	rebuild to detect the update to tools/compat/configure.
561.338Slukem
571.340Smartin20230515:
581.340Smartin	New openssl build requires removal of the crypto/external/bsd/openssl
591.340Smartin	and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierachy.
601.340Smartin	Otherwise test results may be wrong due to wrong "golden" output
611.340Smartin	files being installed.
621.340Smartin
631.337Smrg20230322:
641.337Smrg	Fixes for moved /lib/libisns* mean that builds will complain about
651.337Smrg	./usr/lib/libisns* being missing until src/lib/libisns is forced
661.337Smrg	to (re)install the files, including the symlinks.  The simplest
671.337Smrg	way is to clean this subdir before building.
681.337Smrg
691.336Smartin20230112:
701.336Smartin	New binutils require an updated ld.elf_so. If you are doing
711.336Smartin	(unsupported) in-place self builds (with the -E flag to build.sh),
721.336Smartin	make sure to have installed latest ld.elf_so before you rebuild
731.336Smartin	userland.
741.336Smartin
751.335Schs20221116:
761.335Schs	The addition to NetBSD's version of UFS2 of support for extended
771.335Schs	attributes broke backward compatibility with previous releases
781.335Schs	of NetBSD, so UFS2 has been restored to being compatible with
791.335Schs	previous NetBSD releases by disabling extended attributes.
801.335Schs	(Note that ACLs are implemented as extended attributes, so
811.335Schs	this changes disables ACLs as well.)
821.335Schs
831.335Schs	Support for UFS2 with extended attributes is now available in a new
841.335Schs	UFS variant called UFS2ea.  If you have created extended attributes
851.335Schs	in an original UFS2 file system then "fsck -p" will now fail due to
861.335Schs	the unexpected presence of extended attributes and "fsck -y" will
871.335Schs	remove all extended attributes.  If you wish to preserve extended
881.335Schs	attributes rather than delete them, there is a utility to convert
891.335Schs	a UFS2 file system to UFS2ea and leave extended attributes in place,
901.335Schs	but this should be used with caution since it will preserve any
911.335Schs	extended attributes that have been corrupted by the backward
921.335Schs	incompatibility too.
931.335Schs
941.335Schs	If you wish to use a UFS2ea file system as your root file system,
951.335Schs	then you will need to update your boot loader to a version that
961.335Schs	supports UFS2ea.
971.335Schs
981.335Schs	For more information, see:
991.335Schs	https://wiki.netbsd.org/features/UFS2ea
1001.335Schs
1011.334Smrg20221111:
1021.334Smrg	The new libdrm import worsened the conflict issues for the
1031.334Smrg	kdump/ktruss ioctl, and i915 now conflicts with base, and has
1041.334Smrg	been turned off.  This will cause update build issues like:
1051.334Smrg
1061.334Smrg		kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP'
1071.334Smrg		   undeclared here (not in a function);
1081.334Smrg		   did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'?
1091.334Smrg
1101.334Smrg	You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue.
1111.334Smrg
1121.331Sriastrad20220921:
1131.331Sriastrad	Since the kernel version was bumped to 9.99.100, the bootloader
1141.333Sriastrad	must be updated on x86 or EFI boot platforms in order to load
1151.333Sriastrad	modules from boot.cfg(5) or interactively at the bootloader
1161.333Sriastrad	prompt.
1171.333Sriastrad
1181.333Sriastrad	The kernel can still load modules at runtime, with modload(8)
1191.333Sriastrad	or modules.conf(5), with no bootloader update.  This will not
1201.333Sriastrad	affect release branches because it only applies to patch
1211.333Sriastrad	numbers >=100.
1221.333Sriastrad
1231.333Sriastrad	On x86 (i386 or amd64) with BIOS boot, this requires copying a
1241.333Sriastrad	new /usr/mdec/boot to /boot.  You can build this in the destdir
1251.333Sriastrad	by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
1261.333Sriastrad	sys/arch/i386/stand.
1271.333Sriastrad
1281.333Sriastrad	On platforms with EFI boot (including x86 with EFI boot), this
1291.333Sriastrad	requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/
1301.333Sriastrad	directory on the EFI system partition.  The boot*.efi file is:
1311.333Sriastrad
1321.333Sriastrad	aarch64	bootaa64.efi
1331.333Sriastrad	amd64	bootx64.efi
1341.333Sriastrad	arm	bootarm.efi	(32-bit arm)
1351.333Sriastrad	i386	bootx32.efi
1361.333Sriastrad
1371.333Sriastrad	You can build this in the destdir by running
1381.333Sriastrad	`$TOOLDIR/bin/nbmake-$ARCH dependall install' in
1391.333Sriastrad	sys/stand/efiboot/boot*.
1401.331Sriastrad
1411.330Slukem20220821:
1421.330Slukem	Support for building extsrc/ has been deprecated.
1431.330Slukem	EXTSRCSRCDIR and MKEXTSRC have been deprecated.
1441.330Slukem
1451.329Smrg20220714:
1461.329Smrg	Updates to xorg-server and associated drivers may cause builds to
1471.329Smrg	fail.  Cleaning both DESTDIR and the xorg build tree may be needed.
1481.329Smrg
1491.328Smartin20220628:
1501.328Smartin	Changes in the build of src/games/robots require a clean build
1511.328Smartin	of that program.
1521.328Smartin
1531.324Smartin20211116:
1541.324Smartin	Changes in the xorg build require clean obj dirs for external/mit/xorg
1551.325Smartin	(or a full clean/non-update build).
1561.324Smartin
1571.323Snia20211112:
1581.323Snia	Device tree sources were updated for evbarm.  Some device nodes
1591.323Snia	(in particular, ld(4) devices on the ROCKPro64) will be renumbered.
1601.323Snia
1611.322Smartin20211014:
1621.323Snia	MKPIE default for aarch64 has changed, a clean build is required.
1631.322Smartin
1641.321Schristos20210917:
1651.321Schristos	Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
1661.321Schristos	ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
1671.321Schristos	and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
1681.321Schristos
1691.319Smrg20210711:
1701.319Smrg	Updated GMP sources may require cleaning in tools/gmp and/or in
1711.319Smrg	external/lgpl3/gmp/lib, particularly if GCC itself does not build.
1721.319Smrg
1731.318Smrg20210417:
1741.318Smrg	GCC 10 was enabled for several platforms.  If builds fail in either
1751.318Smrg	tools/gcc or external/gpl/gcc, first try cleaning those objects and
1761.318Smrg	removing the $DESTDIR/usr/include/g++ subdirectory.
1771.318Smrg
1781.317Srillig20201230:
1791.317Srillig	lint1/ops.c is no longer autogenerated.  If this makes the build
1801.317Srillig	fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*.
1811.317Srillig
1821.316Smrg20201016:
1831.316Smrg	MIPS kernel modules have been disabled until they work.  This will
1841.316Smrg	turn up in extra files in the DESTDIR, which should be cleaned.
1851.316Smrg
1861.315Smrg20200925:
1871.315Smrg	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
1881.315Smrg	in both the tools and external dirs.
1891.315Smrg
1901.314Smrg20200912:
1911.314Smrg	GCC 9 has arrived for Arm and x86 platforms, and will be coming
1921.314Smrg	for several more, as will binutils 2.34.  Clean as required.
1931.314Smrg
1941.313Smrg20200907:
1951.313Smrg	GCC 9 is coming, and binutils has been updated for MIPS.  This
1961.313Smrg	probably requires cleaning the tools/binutils.
1971.313Smrg
1981.311Smrg20200811:
1991.312Smrg	GCC updates may require cleaning the objdir.  This may occur
2001.312Smrg	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
2011.312Smrg	GCC 9 upgrade.
2021.311Smrg
2031.309Schristos20200614:
2041.310Schristos	blacklist* has been renamed to blocklist*. postinstall(8)
2051.332Sgutterid	should handle the migration.
2061.309Schristos
2071.308Schristos20200601:
2081.308Schristos	Due to a mistake in LIBISPRIVATE handling, .so libraries were
2091.308Schristos	created in the build directories and need cleaning.
2101.308Schristos
2111.307Smrg20200311:
2121.307Smrg	GCC 8 ports will need cleaning in src/tools/gcc and
2131.307Smrg	src/external/gpl3/gcc due to GCC 8.4 update.
2141.307Smrg
2151.306Schristos20191118:
2161.306Schristos	More architectures were switched to gcc8:
2171.306Schristos	    i386, ia64 powerpc64, sparc, sparc64, arm
2181.306Schristos	The same comments as in 20191022 apply.
2191.306Schristos
2201.305Smartin20191112:
2211.305Smartin	The LLVM update requires a clean rebuild for all architectures using
2221.305Smartin	LLVM during the tools build phase (i386, amd64, aarch64).
2231.305Smartin
2241.304Smartin20191022:
2251.304Smartin	Ports amd64 and aarch64 switched to GCC 8.3 by default.
2261.304Smartin	In-place ("expert mode", build.sh -E) builds are not supported
2271.304Smartin	when going from a GCC 7 userland to GCC 8. Do a regular
2281.304Smartin	build to a different DESTDIR (or preferably: build.sh -U) at least
2291.306Schristos	once and install sets, or download comp.{tar.xz,tgz} from the
2301.304Smartin	daily builds and install that before doing the next in-place build.
2311.304Smartin
2321.303Smrg20191001:
2331.303Smrg	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
2341.303Smrg	old builds with GCC 7 output now uses GCC 8.  Clean this
2351.303Smrg	directory, and also clean src/external/gpl3/gcc.
2361.303Smrg
2371.302Sriastrad20190903:
2381.306Schristos	Files with names that coincide with existing files' names on
2391.302Sriastrad	case-insensitive file systems were inadvertently committed, for
2401.302Sriastrad	radeon GPU firmware.  We cannot mark these as obsolete for
2411.302Sriastrad	postinstall to fix, so if you updated src since 2019-08-26, and
2421.302Sriastrad	ran build.sh distribution or ran build.sh release, you must
2431.302Sriastrad	manually delete the following files in your DESTDIR (which is
2441.302Sriastrad	usually $OBJDIR/destir.$ARCH), or from / if you have installed
2451.302Sriastrad	them:
2461.302Sriastrad
2471.302Sriastrad		/libdata/firmware/radeon/bonaire_ce.bin
2481.302Sriastrad		/libdata/firmware/radeon/bonaire_mc.bin
2491.302Sriastrad		/libdata/firmware/radeon/bonaire_me.bin
2501.302Sriastrad		/libdata/firmware/radeon/bonaire_mec.bin
2511.302Sriastrad		/libdata/firmware/radeon/bonaire_pfp.bin
2521.302Sriastrad		/libdata/firmware/radeon/bonaire_rlc.bin
2531.302Sriastrad		/libdata/firmware/radeon/bonaire_sdma.bin
2541.302Sriastrad		/libdata/firmware/radeon/bonaire_smc.bin
2551.302Sriastrad		/libdata/firmware/radeon/bonaire_uvd.bin
2561.302Sriastrad		/libdata/firmware/radeon/hainan_ce.bin
2571.302Sriastrad		/libdata/firmware/radeon/hainan_mc.bin
2581.302Sriastrad		/libdata/firmware/radeon/hainan_me.bin
2591.302Sriastrad		/libdata/firmware/radeon/hainan_pfp.bin
2601.302Sriastrad		/libdata/firmware/radeon/hainan_rlc.bin
2611.302Sriastrad		/libdata/firmware/radeon/hainan_smc.bin
2621.302Sriastrad		/libdata/firmware/radeon/hawaii_ce.bin
2631.302Sriastrad		/libdata/firmware/radeon/hawaii_mc.bin
2641.302Sriastrad		/libdata/firmware/radeon/hawaii_me.bin
2651.302Sriastrad		/libdata/firmware/radeon/hawaii_mec.bin
2661.302Sriastrad		/libdata/firmware/radeon/hawaii_pfp.bin
2671.302Sriastrad		/libdata/firmware/radeon/hawaii_rlc.bin
2681.302Sriastrad		/libdata/firmware/radeon/hawaii_sdma.bin
2691.302Sriastrad		/libdata/firmware/radeon/hawaii_smc.bin
2701.302Sriastrad		/libdata/firmware/radeon/kabini_ce.bin
2711.302Sriastrad		/libdata/firmware/radeon/kabini_me.bin
2721.302Sriastrad		/libdata/firmware/radeon/kabini_mec.bin
2731.302Sriastrad		/libdata/firmware/radeon/kabini_pfp.bin
2741.302Sriastrad		/libdata/firmware/radeon/kabini_rlc.bin
2751.302Sriastrad		/libdata/firmware/radeon/kabini_sdma.bin
2761.302Sriastrad		/libdata/firmware/radeon/kaveri_ce.bin
2771.302Sriastrad		/libdata/firmware/radeon/kaveri_me.bin
2781.302Sriastrad		/libdata/firmware/radeon/kaveri_mec.bin
2791.302Sriastrad		/libdata/firmware/radeon/kaveri_mec2.bin
2801.302Sriastrad		/libdata/firmware/radeon/kaveri_pfp.bin
2811.302Sriastrad		/libdata/firmware/radeon/kaveri_rlc.bin
2821.302Sriastrad		/libdata/firmware/radeon/kaveri_sdma.bin
2831.302Sriastrad		/libdata/firmware/radeon/mullins_ce.bin
2841.302Sriastrad		/libdata/firmware/radeon/mullins_me.bin
2851.302Sriastrad		/libdata/firmware/radeon/mullins_mec.bin
2861.302Sriastrad		/libdata/firmware/radeon/mullins_pfp.bin
2871.302Sriastrad		/libdata/firmware/radeon/mullins_rlc.bin
2881.302Sriastrad		/libdata/firmware/radeon/mullins_sdma.bin
2891.302Sriastrad		/libdata/firmware/radeon/oland_ce.bin
2901.302Sriastrad		/libdata/firmware/radeon/oland_mc.bin
2911.302Sriastrad		/libdata/firmware/radeon/oland_me.bin
2921.302Sriastrad		/libdata/firmware/radeon/oland_pfp.bin
2931.302Sriastrad		/libdata/firmware/radeon/oland_rlc.bin
2941.302Sriastrad		/libdata/firmware/radeon/oland_smc.bin
2951.302Sriastrad		/libdata/firmware/radeon/pitcairn_ce.bin
2961.302Sriastrad		/libdata/firmware/radeon/pitcairn_mc.bin
2971.302Sriastrad		/libdata/firmware/radeon/pitcairn_me.bin
2981.302Sriastrad		/libdata/firmware/radeon/pitcairn_pfp.bin
2991.302Sriastrad		/libdata/firmware/radeon/pitcairn_rlc.bin
3001.302Sriastrad		/libdata/firmware/radeon/pitcairn_smc.bin
3011.302Sriastrad		/libdata/firmware/radeon/tahiti_ce.bin
3021.302Sriastrad		/libdata/firmware/radeon/tahiti_mc.bin
3031.302Sriastrad		/libdata/firmware/radeon/tahiti_me.bin
3041.302Sriastrad		/libdata/firmware/radeon/tahiti_pfp.bin
3051.302Sriastrad		/libdata/firmware/radeon/tahiti_rlc.bin
3061.302Sriastrad		/libdata/firmware/radeon/tahiti_smc.bin
3071.302Sriastrad		/libdata/firmware/radeon/verde_ce.bin
3081.302Sriastrad		/libdata/firmware/radeon/verde_mc.bin
3091.302Sriastrad		/libdata/firmware/radeon/verde_me.bin
3101.302Sriastrad		/libdata/firmware/radeon/verde_pfp.bin
3111.302Sriastrad		/libdata/firmware/radeon/verde_rlc.bin
3121.302Sriastrad		/libdata/firmware/radeon/verde_smc.bin
3131.302Sriastrad
3141.302Sriastrad	We will re-import these radeon firmware images another way
3151.302Sriastrad	later.
3161.302Sriastrad
3171.301Smartin20190727:
3181.301Smartin	The uefi bootloader has gained tftp support and needs a clean
3191.301Smartin	build. If you do update builds, manually clean its object
3201.301Smartin	directory by something like:
3211.301Smartin	cd sys/arch/i386/stand/efiboot && make clean
3221.301Smartin
3231.300Smartin20190723:
3241.344Sgutterid	The jemalloc allocator in libc is now built without extended
3251.300Smartin	debugging (for performance reasons). In update builds make sure
3261.326Sandvar	to rebuild it completely, by removing all affected object files,
3271.300Smartin	including compat builds, something like:
3281.300Smartin	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
3291.300Smartin
3301.299Smrg20190207:
3311.299Smrg	GCC 7 switched for many ports.  Update builds are likely to fail.
3321.299Smrg
3331.298Smartin20180924:
3341.298Smartin	A newer OpenSSL version has been imported. If you are doing
3351.298Smartin	update builds, make sure to remove all old obj dirs, like:
3361.298Smartin	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
3371.298Smartin
3381.297Sjoerg20180717:
3391.297Sjoerg	On aarch64 int64_t and related types have changed from long long
3401.297Sjoerg	to long. This requires recompiling all C++ binaries.
3411.297Sjoerg
3421.296Smartin20180713:
3431.296Smartin	On amd64 and i386 static binaries are now build position
3441.344Sgutterid	independent. This requires recompilation of all object
3451.296Smartin	files used to create the crunched /rescue binary.
3461.296Smartin	Clean the rescue directory in your obj directory before
3471.296Smartin	doing an update build, otherwise linking will fail.
3481.296Smartin
3491.293Sjakllsch20180414:
3501.293Sjakllsch	Existing binutils was migrated to binutils.old.  Manual
3511.293Sjakllsch	removal of tools/binutils objects directory may be required
3521.293Sjakllsch	to fix tools build failure.
3531.293Sjakllsch
3541.292Smrg20180311:
3551.292Smrg	bdftopcf was updated and may need cleaning in the
3561.292Smrg	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
3571.292Smrg	link errors.
3581.292Smrg
3591.291Smrg20180212:
3601.291Smrg	between OpenSSL and GCC updates, many things may fail to build.
3611.291Smrg	any failure that looks like GCC or openssl is best handled by
3621.291Smrg	a clean destdir and objdir.  Full cleandir and destdir deletion
3631.291Smrg	is recommended if build failures occur.
3641.291Smrg
3651.288Smartin20171225:
3661.288Smartin	removal of the vadvise syscall requires manual removal of all
3671.288Smartin	associated files from the libc build object directory (including
3681.289Schristos	the .depend files) - a command like:
3691.288Smartin		cd $OBJ && find . -type d -name libc | xargs rm -rf
3701.289Schristos	For architectures that support multiple "compat" binary targets,
3711.289Schristos	you'll need to cleanup both the regular libc directory and the
3721.290Smartin	compat ones (the above command will do that).
3731.288Smartin
3741.287Skre20171010:
3751.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
3761.287Skre	means that its objdir (or *.d and .depend at least) might need
3771.287Skre	to be manually removed - or a build done once without -u.
3781.287Skre
3791.286Smrg20170822:
3801.286Smrg	a new version of GMP has been imported and probably
3811.286Smrg	will break parts of builds related to themselves or GCC, both
3821.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
3831.286Smrg	and MPC objdirs or build once without -u.
3841.286Smrg
3851.285Smrg20170816:
3861.285Smrg	a new version of MPFR and MPC have been imported and probably
3871.285Smrg	will break parts of builds related to themselves or GCC, both
3881.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
3891.285Smrg	and MPC objdirs or build once without -u.
3901.285Smrg
3911.284Smartin20170402:
3921.284Smartin	a new version of dhcpcd has been imported, which does not support
3931.284Smartin	update builds from the previous version. Remove your
3941.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
3951.284Smartin
3961.281Sroy20170211:
3971.281Sroy	a new terminfo database has been imported.
3981.281Sroy	The structure of it has changed slightly from prior versions and
3991.281Sroy	an updated tic tool is required.
4001.281Sroy	If you build.sh, don't use -u
4011.281Sroy
4021.280Skre20170207:
4031.278Skre	various arch dependent libc/exect.S files were removed
4041.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
4051.279Skre	if it exists) or do a clean build.
4061.279Skre	(This is a bug in the make system, it should be corrected without
4071.279Skre	human intervention, but isn't.)
4081.278Skre
4091.277Smartin20170104:
4101.277Smartin	xinput build options have changed.
4111.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
4121.277Smartin	if you build.sh -u
4131.277Smartin
4141.276Smartin20170103:
4151.276Smartin	a new version of flex has been imported.
4161.276Smartin	Remove the file from obj (external/bsd/flex)
4171.276Smartin	if you build.sh -u
4181.276Smartin
4191.275Sspz20161014:
4201.275Sspz	a new version of OpenSSL has been imported.
4211.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
4221.275Sspz	if you build.sh -u
4231.275Sspz
4241.274Smartin20161009:
4251.274Smartin	a new version of dhcpcd has been imported with slightly changed
4261.274Smartin	build infrastructure. When doing a build.sh -u this requires
4271.274Smartin	pruning the external/bsd/dhcpcd objdir.
4281.274Smartin
4291.273Smrg20160914:
4301.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
4311.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
4321.273Smrg	and a clean objdir.
4331.273Smrg
4341.272Sdholland20160527:
4351.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
4361.272Sdholland	been enabled. (see the amd64 entry two down for further info)
4371.272Sdholland
4381.270Schristos20160418:
4391.270Schristos	libedit needs manual removal of all autogenerated files since
4401.271Schristos	some of them are not autogenerated anymore. Remember that there
4411.271Schristos	might be two copies of libedit if your platform builds "compat".
4421.270Schristos
4431.268Sriastrad20160410:
4441.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
4451.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
4461.268Sriastrad	executables, means all code, including executables and not just
4471.268Sriastrad	shared libraries, is position-independent and hence able to be
4481.268Sriastrad	relocated by ASLR, address space layout randomization.
4491.268Sriastrad
4501.268Sriastrad	The change was made in Makefile variables for compiler and
4511.268Sriastrad	linker flags, for which make(1) does not record dependencies,
4521.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
4531.268Sriastrad
4541.268Sriastrad	Partial rebuilds with some modified source files will likely
4551.268Sriastrad	fail when linking executables, since the linker refuses to mix
4561.268Sriastrad	position-independent code with position-dependent code in
4571.268Sriastrad	position-independent executables:
4581.268Sriastrad
4591.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
4601.268Sriastrad
4611.267Smrg20160401:
4621.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
4631.269Sdholland	Some people have found that cleandir is not sufficient, so if
4641.269Sdholland	in doubt delete the entire object directory tree for gcc.
4651.267Smrg
4661.266Saymeric20160306:
4671.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
4681.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
4691.265Saymeric	non-NetBSD hosts if linked with stale object files produced
4701.265Saymeric	while they included a non-NetBSD regex.h.
4711.265Saymeric	In any case, you should "make cleandir" at least these tools
4721.265Saymeric	before updating your toolchain.
4731.265Saymeric
4741.264Smartin20160125:
4751.264Smartin	Dtrace has been enabled by default on some architectures.
4761.264Smartin	When doing an update build, make sure to clean the etc/mtree
4771.264Smartin	object directory before starting the build - otherwise the
4781.264Smartin	needed directories in destdir will not be created.
4791.264Smartin	An easy way to do this is:
4801.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
4811.264Smartin
4821.263Sdholland20150818:
4831.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
4841.263Sdholland	again.
4851.263Sdholland
4861.262Schristos20150413:
4871.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
4881.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
4891.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
4901.262Schristos
4911.261Smartin20150404:
4921.261Smartin	Lint changes require a full rebuild of the tool, so make
4931.261Smartin	sure to build without -u option to build.sh, or manually
4941.261Smartin	do a make cleandir in src/tools/lint1 and
4951.261Smartin	src/usr.bin/xlint.
4961.261Smartin
4971.260Sskrll20150310:
4981.260Sskrll	Improvements to openssl for arm mean that update builds of
4991.260Sskrll	the openssl libraries will fail. A make cleandir in
5001.260Sskrll	external/bsd/openssl/lib is needed
5011.260Sskrll
5021.258Smartin20141026:
5031.259Smsaitoh	A mishap during the import of pppd may cause your corruption
5041.258Smartin	in your cvs directory if you happened to do a cvs update
5051.258Smartin	during a short period of time. To fix, just remove the
5061.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
5071.258Smartin	and let cvs restore it on next update.
5081.258Smartin
5091.256Sapb20140721:
5101.256Sapb	The src/external/mit/lua/src directory was accidentally created
5111.256Sapb	and then deleted in the CVS repository.  If you get errors like
5121.256Sapb
5131.256Sapb	cvs [update aborted]: cannot open directory
5141.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
5151.256Sapb
5161.256Sapb	then delete your local copy of that directory tree and try again.
5171.256Sapb
5181.255Sjoerg20140530:
5191.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
5201.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
5211.255Sjoerg
5221.251Smartin20140131:
5231.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
5241.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
5251.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
5261.251Smartin
5271.250Schristos20131227:
5281.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
5291.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
5301.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
5311.250Schristos	   statements to avoid being exposed.
5321.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
5331.250Schristos	   to make clean in libc
5341.250Schristos
5351.249Smrg20131129:
5361.249Smrg	The GMP sources were updated, and builds will likely fail without
5371.249Smrg	cleaning their build trees for both tools and in-tree, like below.
5381.249Smrg
5391.248Smrg20131128:
5401.248Smrg	The MPC and MPFR sources were updated, and builds may require their
5411.248Smrg	tools and in-tree directories cleaned for successful updates.
5421.248Smrg
5431.246Smartin20130605:
5441.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
5451.247Sspz	to IPSEC (and the older IPSEC version removed).
5461.247Sspz
5471.247Sspz20130605:
5481.320Sandvar	Previous freetype installations erroneously installed private
5491.246Smartin	header files. If you are building against a non-empty $DESTDIR,
5501.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
5511.246Smartin
5521.245Smrg20130531:
5531.245Smrg	The xdm update may cause build failure due to xdm.man being
5541.245Smrg	in the obj tree.  Make sure to ensure any like this:
5551.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
5561.245Smrg	is fixed by deleting the xdm.man in the obj tree.
5571.245Smrg
5581.244Smrg20130530:
5591.244Smrg	Updates of many xsrc packages will leave old .pc files around.
5601.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
5611.244Smrg
5621.242Schristos20130301:
5631.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
5641.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
5651.242Schristos
5661.238Sdholland20120726:
5671.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
5681.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
5691.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
5701.241Swiz	some cases may succeed and install broken OpenSSL libraries that
5711.240Sdholland	cause third-party software to link incorrectly and/or crash.
5721.238Sdholland
5731.237Swiz20120507:
5741.241Swiz	The database schema for makemandb was changed.  You will
5751.237Swiz	need to update the database using 'makemandb -f' or wait
5761.237Swiz	for the next weekly run to fix it.
5771.237Swiz
5781.236Sbsh20120319:
5791.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
5801.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
5811.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
5821.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
5831.236Sbsh	mk.conf.
5841.236Sbsh
5851.235Sjoerg20120216:
5861.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
5871.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
5881.239Sdholland	and 20120216, daily and weekly could have created an unreadable
5891.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
5901.235Sjoerg	the next run of weekly will fix it.
5911.233Sjoerg
5921.232Schristos20111227:
5931.232Schristos	If you built between 20111225 and 20111227 you need to remove
5941.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
5951.232Schristos	bump has been reverted.
5961.232Schristos
5971.231Stls20111125:
5981.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
5991.231Stls	means it should no longer be explicitly listed in kernel
6001.231Stls	configuration files.  The line "pseudo-device rnd" should be
6011.231Stls	removed from any custom kernel config files users may have.
6021.231Stls
6031.230Stls20111119:
6041.230Stls	A problem with the datastructures used by the rndctl(8)
6051.230Stls	utility (pointers in datastructures in an array, making 32->64
6061.230Stls	bit compatibility very painful) has been fixed in a
6071.230Stls	non-backwards-compatible way.  If you replace your kernel,
6081.230Stls	replace your rndctl executable too.
6091.241Swiz
6101.229Sjym20111001:
6111.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
6121.229Sjym	changed and their new version is not backward compatible with the old
6131.241Swiz	one.  So ensure that all consumers of these functions (currently:
6141.229Sjym	quota2 code and its tests) are updated together with the new lib.
6151.229Sjym
6161.228Smrg20110817:
6171.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
6181.228Smrg	DESTDIR for them should be deleted before updating.
6191.228Smrg
6201.227Sriastrad20110806:
6211.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
6221.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
6231.227Sriastrad
6241.226Smrg20110805:
6251.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
6261.226Smrg	the tree to be cleaned.  Best to delete both objdir and
6271.226Smrg	DESTDIR before running this update.  So far, only the
6281.226Smrg	sparc64, mips and powerpc platforms have changed.
6291.226Smrg
6301.225Smatt20110803:
6311.241Swiz	The layout of external/public-domain/xz has changed.  To do an
6321.225Smatt	update build you will have to remove the contents of the OBJDIR
6331.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
6341.225Smatt	is now a directory.
6351.225Smatt
6361.223Sjoerg20110410:
6371.241Swiz	The configuration of src/tools/gcc has changed.  To do an
6381.224Sdholland	update build you have to clean both tools/binutils and
6391.224Sdholland	tools/gcc by hand.
6401.223Sjoerg
6411.222Splunky20110328:
6421.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
6431.241Swiz	ordering issues with "make all".  It may be necessary to remove
6441.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
6451.222Splunky	if your update build fails, as the "Xorg" entry there is now a
6461.222Splunky	directory.
6471.222Splunky
6481.220Sjoerg20110121:
6491.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
6501.220Sjoerg	the build of individual parts of the tree.  This is handled
6511.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
6521.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
6531.218Sjoerg
6541.217Sjruoho20101217:
6551.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
6561.241Swiz	by default.  It may be necessary to manually update passwd(5) and
6571.217Sjruoho	group(5) in order to make the program work with existing setups.
6581.217Sjruoho
6591.216Schristos20101125:
6601.327Sandvar	The latest changes to setenv(3) disallow setting environment
6611.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
6621.241Swiz	assumed that this was allowed.  Installing a new libc with an
6631.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
6641.216Schristos	break which affects the autoconf tests for dependency finding,
6651.216Schristos	so building gcc will end up printing:
6661.216Schristos	    checking dependency style of gcc... none
6671.216Schristos	    configure: error: no usable dependency style found
6681.216Schristos	Fix it by rebuilding and re-installing env.
6691.138Slukem
6701.215Smrg20101119:
6711.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
6721.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
6731.215Smrg	have any build problems with xsrc, or problems with mismatched
6741.215Smrg	versions between xorg-server and drivers.
6751.215Smrg
6761.213Sjmmv20100604:
6771.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
6781.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
6791.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
6801.213Sjmmv	trees by hand.
6811.213Sjmmv
6821.211Stnozaki20100522:
6831.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
6841.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
6851.212Smrg	build problems with xsrc.
6861.212Smrg
6871.212Smrg20100522:
6881.320Sandvar	private section of <ctype.h> was split, and now mklocale(1)
6891.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
6901.211Stnozaki
6911.210Schristos20100520:
6921.241Swiz	The location of the xkb compiled descriptions has changed.  Please
6931.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
6941.210Schristos
6951.209Snjoly20100222:
6961.209Snjoly	The shared objects file extension has been changed from .so to
6971.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
6981.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
6991.209Snjoly	your object directories.
7001.209Snjoly
7011.208Sroy20100204:
7021.208Sroy	The termcap database has been removed from the sources,
7031.208Sroy	but has not been marked obsolete so it is not removed
7041.208Sroy	from the system when upgrading.
7051.208Sroy	As such, you will need to remove them from your object
7061.208Sroy	and destination directories.
7071.208Sroy
7081.203Sdyoung20091101:
7091.205Sdholland        After updating, it may be necessary to make the 'cleandir'
7101.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
7111.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
7121.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
7131.203Sdyoung
7141.202Smrg20091001:
7151.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
7161.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
7171.206Sdholland
7181.206Sdholland20091001:
7191.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
7201.202Smrg	symlink, failing the build.  Delete the link, and the subdir
7211.202Smrg	it is in, and retry your build.
7221.202Smrg
7231.201Sdsl20090718:
7241.201Sdsl	libc build changed so that strchr() provides the extra entry
7251.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
7261.201Sdsl	may fail because the archive contains the unwanted index.o.
7271.201Sdsl	(Similarly for strrchr() and rindex().)
7281.201Sdsl
7291.198Smrg20090709:
7301.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
7311.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
7321.198Smrg
7331.197Smrg20090616:
7341.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
7351.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
7361.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
7371.197Smrg	subdirectory has been changed into a file, and this needs to
7381.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
7391.197Smrg
7401.195Sperry20090501:
7411.195Sperry	Several new functions were added to string.h/libc, and this
7421.195Sperry	can cause autoconf problems during the tool build for people
7431.241Swiz	who fail to clean out their tools objects properly.  If you
7441.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
7451.195Sperry	failure during the tool build, clean out all your tools
7461.195Sperry	objects and start again.
7471.195Sperry
7481.194Smrg20090325:
7491.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
7501.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
7511.194Smrg
7521.192Sskrll20090126:
7531.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
7541.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
7551.207Smbalmer	to avoid using the old assembly stub.
7561.192Sskrll
7571.191Sjoerg20090202:
7581.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
7591.320Sandvar	detection.  It is recommended to rebuild the cache with
7601.191Sjoerg	``pkg_admin rebuild''.
7611.191Sjoerg
7621.184Schristos20090110:
7631.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
7641.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
7651.188Schristos	   This is needed even in the MODULAR kernel because there is
7661.188Schristos	   conditionally compiled code in rtsock.c.
7671.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
7681.184Schristos	   before installing.
7691.184Schristos	3. If you don't use build.sh and you build directly to root, and
7701.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
7711.184Schristos	   are installed properly, and start building libraries first libc
7721.184Schristos	   and libutil, install them and then continue building all the
7731.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
7741.184Schristos	   the new libraries are installed, you can restart the build.
7751.184Schristos	4. If you compile packages and you notice link time warnings,
7761.189Shubertf	   rebuild the required packages to update their shared libraries.
7771.189Shubertf	   Any package you rebuild will require rebuilding all the packages
7781.189Shubertf	   that depend on it.
7791.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
7801.186Schristos	   will be upgraded and it will not be backwards compatible.
7811.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
7821.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
7831.241Swiz	   for utmp.  You are better off removing the old files after
7841.190Sapb	   upgrading.  The automated clearing of /var/run during
7851.190Sapb	   boot, and the automated rotating of files in /var/log by
7861.190Sapb	   newsyslog(8), may mean that you do not have to remove the
7871.190Sapb	   files manually.
7881.190Sapb	7. The optional accounting file (/var/account/acct, see
7891.190Sapb	   accton(8)) has not been versioned, and will need to be
7901.190Sapb	   removed.  The automatic rotation of the accounting file by
7911.190Sapb	   /etc/daily limits the bad consequences of failure to remove
7921.190Sapb	   the file.
7931.196Sdholland	8. Application software that writes time_t to binary files on
7941.241Swiz	   disk will break or need attention.  Most notably: if you are
7951.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
7961.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
7971.185Sjmcneill
7981.183Spgoyette20081219:
7991.183Spgoyette	config(1) has been updated, and one of the files it creates -
8001.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
8011.183Spgoyette	(done automatically by build.sh) and then you need to rerun
8021.183Spgoyette	config on all kernel configuration files before rebuilding those
8031.183Spgoyette	kernels.
8041.183Spgoyette
8051.181Scube20081205:
8061.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
8071.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
8081.181Scube	set and will appear as extra files for MKX11=no update builds.
8091.178Slukem
8101.179Stsutsui20081122:
8111.182Stsutsui	On i386, various kernel options(4) in GENERIC including
8121.180Swiz	file systems have been disabled and moved into kernel modules.
8131.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
8141.179Stsutsui	following files as well as a new GENERIC kernel:
8151.179Stsutsui
8161.179Stsutsui	- build and install kernel modules from src/sys/modules
8171.179Stsutsui
8181.179Stsutsui	- install the latest bootloader, which will load a module
8191.180Swiz	  for the file system from which the kernel is loaded automatically
8201.179Stsutsui
8211.180Swiz	If you have to load your kernel from a file system which is not of
8221.180Swiz	the same type as the root file system, you have to load the necessary
8231.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
8241.179Stsutsui
8251.178Slukem20080827:
8261.178Slukem	If you built and installed a libc from sources between
8271.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
8281.178Slukem	which results in false errors reported by lint(1).
8291.178Slukem	Since this breaks the libc build itself, manual help is
8301.180Swiz	needed -- lint must be disabled temporarily, e.g.:
8311.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
8321.178Slukem
8331.177Schristos20080813:
8341.177Schristos	MKDEBUG build was broken because the .depend files did not know
8351.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
8361.177Schristos
8371.200Sdholland20080802:
8381.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
8391.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
8401.200Sdholland	for -current.
8411.200Sdholland
8421.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
8431.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
8441.200Sdholland	be recompiled.
8451.200Sdholland
8461.200Sdholland	One way to find affected pkgsrc packages:
8471.200Sdholland
8481.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
8491.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
8501.200Sdholland
8511.175Ssimonb20080731:
8521.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
8531.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
8541.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
8551.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
8561.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
8571.176Ssimonb	also requires the super block to be in the UFS2 format.  You
8581.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
8591.175Ssimonb
8601.174Slukem20080721:
8611.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
8621.174Slukem	isn't defined.
8631.174Slukem
8641.173Sfreza20080531:
8651.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
8661.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
8671.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
8681.241Swiz	won't work correctly.  The following sequence of commands:
8691.173Sfreza
8701.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
8711.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
8721.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
8731.173Sfreza
8741.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
8751.173Sfreza
8761.172Slukem20080503:
8771.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
8781.172Slukem
8791.171She20080521:
8801.171She	For a while, unprivileged UPDATE builds would fail to
8811.171She	succeed at the checkflist stage, complaining that
8821.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
8831.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
8841.171She	If you already hit this problem, update the .mk file,
8851.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
8861.171She
8871.174Slukem20080303:
8881.174Slukem	Linker warnings are now fatal if $WARNS>0.
8891.174Slukem
8901.170Schristos20080126:
8911.170Schristos	The posix_fadvise system call has been changed from an assembly
8921.241Swiz	stub, to a c file that calls an assembly stub.  You need to
8931.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
8941.170Schristos	avoid using the old assembly stub.
8951.170Schristos
8961.168Sjoerg20071209:
8971.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
8981.168Sjoerg	get ACPI errors before the attachment, please update your kernel
8991.169Swiz	configuration file appropriately or see GENERIC for more details.
9001.168Sjoerg
9011.166Sxtraeme20071115:
9021.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
9031.166Sxtraeme	argument specified in the kernel configuration file is not valid
9041.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
9051.241Swiz	rather than the EC address port.  Please update your kernel
9061.167Swiz	configuration file appropriately or see GENERIC for more details.
9071.166Sxtraeme
9081.165Sjmmv20071028:
9091.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
9101.165Sjmmv	You need to update any custom kernel configuration file you have
9111.165Sjmmv	to remove any references to pccons (which includes removing the
9121.165Sjmmv	now useless XSERVER option) and replace them with the correct
9131.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
9141.165Sjmmv	for more details.
9151.165Sjmmv
9161.164Sgdt20070913:
9171.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
9181.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
9191.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
9201.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
9211.164Sgdt	could not enumerate interfaces.  (These are noted because
9221.164Sgdt	normal kernel/userspace version matching hygiene is not
9231.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
9241.164Sgdt	and userland are from after 20070913.
9251.164Sgdt
9261.163Sjoerg20070703:
9271.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
9281.199Sdholland	calls the target-specific strip program, and the logic to pass
9291.199Sdholland	down STRIP from make has been removed.  This requires a
9301.199Sdholland	re-installation of tools.
9311.163Sjoerg
9321.161Sdsl20070422:
9331.161Sdsl	The way OS emulations lookup filenames inside the emulation root
9341.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
9351.161Sdsl	to userspace) namei() and lookup() directly check the emulation
9361.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
9371.167Swiz	root file system will be relative to that file system - unless they
9381.161Sdsl	start /../ this is useful when the emulated root is a real install
9391.161Sdsl	that has such links.
9401.161Sdsl	This might affect symlinks that have been added to reference outside
9411.161Sdsl	the emulated root.
9421.161Sdsl
9431.160Sjmcneill20070412:
9441.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
9451.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
9461.160Sjmcneill	example.
9471.160Sjmcneill
9481.159Sgdt20070319:
9491.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
9501.159Sgdt        on many platforms due to incorrect flags settings.  If you
9511.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
9521.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
9531.159Sgdt	rebuild of object files that might have been built
9541.159Sgdt	incorrectly, and ensure that you have at least
9551.159Sgdt	src/lib/libc/Makefile 1.130.
9561.159Sgdt
9571.241Swiz20070210:
9581.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
9591.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
9601.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
9611.158Sdbj        will allow dependencies on those files to get get rebuilt
9621.158Sdbj
9631.157Sapb20070209:
9641.157Sapb        The threading model was changed when the newlock2 branch
9651.157Sapb        was merged to NetBSD-current.  If you boot with a new
9661.157Sapb        kernel (version 4.99.10), then you also need a new pthread
9671.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
9681.157Sapb        an old kernel, then you need the old pthread library
9691.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
9701.157Sapb        the pthread library in sync, old threaded applications should
9711.157Sapb        continue to work with an old or new kernel.  Note that named(8)
9721.157Sapb	is the only threaded application in the base system.
9731.157Sapb
9741.154She20061214:
9751.154She	Following the move of string_to_flags() and flags_to_string()
9761.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
9771.154She	will need to do a "make cleandir" in
9781.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
9791.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
9801.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
9811.156She		as the installation images in distrib/
9821.154She	in order to excise stale references to the old stat_flags.h header
9831.154She	file in the ls sources -- stat_flags.h has been removed.
9841.154She
9851.152Schristos20061108:
9861.152Schristos	The configure script used in the src/tools/gcc compiler has been
9871.152Schristos	changed to indicate that our libc has ssp support built-in and
9881.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
9891.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
9901.152Schristos
9911.151Srpaulo20061009:
9921.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
9931.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
9941.151Srpaulo
9951.150Sbjh2120060814:
9961.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
9971.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
9981.150Sbjh21	kernel configuration for an example.  X servers from the last
9991.150Sbjh21	few years should cope.
10001.150Sbjh21
10011.149Schristos20060703:
10021.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
10031.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
10041.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
10051.149Schristos
10061.148Sdogcow20060627:
10071.148Sdogcow	socket(2) has changed, and its system call has been versioned.
10081.148Sdogcow	For userlands with the old version of socket(2), make sure that
10091.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
10101.148Sdogcow	errors will result.
10111.148Sdogcow
10121.1SabsHints for a more successful build:
10131.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10141.123Sjmc    Use build.sh, but do not use its "expert mode":
10151.132Sjmmv	This will automatically build the tools in the
10161.123Sjmc	   correct order, and it will keep the tools and the
10171.123Sjmc	   new build products from interfering with the running
10181.123Sjmc	   system.  This will allow you to ignore most of the
10191.123Sjmc	   other advice in this file.
10201.2Smrg    Build a new kernel first:
10211.2Smrg	This makes sure that any new system calls or features
10221.2Smrg	   expected by the new userland will be present.  This
10231.2Smrg	   helps to avoid critical errors when upgrading.
10241.1Sabs    Use object directories:
10251.1Sabs	This helps to keep stale object
10261.1Sabs	   files from polluting the build if a Makefile "forgets"
10271.1Sabs	   about one.  It also makes it easier to clean up after
10281.1Sabs	   a build.  It's also necessary if you want to use the
10291.1Sabs	   same source tree for multiple machines.
10301.123Sjmc	   To use object directories with build.sh:
10311.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
10321.123Sjmc	   To use object directories without using build.sh:
10331.1Sabs	    a) cd /usr/src ; make cleandir
10341.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
10351.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
10361.1Sabs	    d) cd /usr/src ; make build
10371.2Smrg	   Note that running "make obj" in a directory will create
10381.2Smrg	   in obj.$MACHINE directory.
10391.1Sabs    Build to a DESTDIR:
10401.123Sjmc	This helps to keep old installed files (especially libraries)
10411.123Sjmc	   from interfering with the new build.
10421.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
10431.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
10441.123Sjmc	   environment variable before running make build.  It should be
10451.123Sjmc	   set to the pathname of an initially empty directory.
10461.123Sjmc	   Problems: if you do not use build.sh, you might need to
10471.123Sjmc		update critical utilities without using DESTDIR since
10481.123Sjmc		nothing is executed from what is installed in DESTDIR.
10491.123Sjmc		(See critical utils, below.)
10501.1Sabs    Build often:
10511.1Sabs	This keeps critical utilities current enough to not choke
10521.1Sabs	on any other part of the source tree that depends on up to
10531.123Sjmc	date functionality.  If you use build.sh, you should not have
10541.123Sjmc	this problem.
10551.241Swiz
10561.1SabsWhat to do if things don't work:
10571.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10581.230StlsWhen things don't work there are usually a few things that commonly
10591.1Sabsshould be done.
10601.1Sabs    1)	make includes
10611.1Sabs	This should be done automatically by make build.
10621.1Sabs    2)  cd share/mk && make install
10631.1Sabs	Again, automatically done by make build.
10641.1Sabs
10651.1SabsFailsafe rebuild of a small part of the tree:
10661.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10671.1SabsTo make sure you rebuild something correctly you want to do
10681.1Sabssomething like the following:
10691.1Sabs    1)  Make sure the includes and .mk files are up to date.
10701.1Sabs    2)  Make sure any program used to build the particular
10711.1Sabs	utility is up to date.  (yacc, lex, etc...)
10721.1Sabs    3)  cd ...path/to/util...
10731.1Sabs	make cleandir
10741.1Sabs	rm ...all obj directories...
10751.1Sabs	make cleandir			# yes, again
10761.1Sabs	make obj
10771.1Sabs	make depend && make
10781.1Sabs
10791.1SabsFailsafe rebuild of the entire tree:
10801.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10811.1SabsIf you really want to make sure the source tree is clean and
10821.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
10831.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
10841.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
10851.1Sabs
10861.1Sabs---cut here---
10871.1Sabs#!/bin/sh
10881.1Sabs. /etc/mk.conf
10891.1Sabs
10901.58Slukemif [ -z $NETBSDSRCDIR ] ; then
10911.58Slukem    NETBSDSRCDIR=/usr/src
10921.1Sabsfi
10931.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
10941.1Sabs    echo Unable to find sources
10951.1Sabs    exit 1
10961.1Sabsfi
10971.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
10981.1Sabs
10991.1Sabsif [ -z $BSDOBJDIR ] ; then
11001.1Sabs    BSDOBJDIR=/usr/obj
11011.1Sabsfi
11021.1Sabsif [ -d $BSDOBJDIR ] ; then
11031.1Sabs    rm -rf $BSDOBJDIR
11041.1Sabsfi
11051.1Sabs
11061.58Slukemcd $NETBSDSRCDIR && make cleandir
11071.1Sabs
11081.1Sabs---cut here---
11091.1Sabs
11101.1SabsCritical utilities:
11111.1Sabs^^^^^^^^^^^^^^^^^^^
11121.3Sitojun	usr.bin/compile_et
11131.1Sabs	usr.bin/make
11141.1Sabs	usr.bin/yacc
11151.1Sabs	usr.bin/lex
11161.11Slukem	usr.bin/xlint
11171.142Sdrochner	usr.bin/config
11181.1Sabs
11191.34SsimonbOther problems and possible solutions:
11201.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
11211.1SabsSymptom:Complaints involving a Makefile.
11221.17SerhFix:	Rebuild usr.bin/make:
11231.17Serh	cd usr.bin/make && make && make install
11241.111Ssimonb	Or, a failsafe method if that doesn't work:
11251.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
11261.17Serh
11271.1SabsFix:	Make sure .mk files are up to date.
11281.1Sabs	cd share/mk && make install
11291.2Smrg
11301.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
11311.142SdrochnerFix:	Rebuild usr.bin/config
11321.1Sabs
11331.1SabsSymptom:
11341.1SabsFix:	Rebuild usr.bin/yacc
11351.1Sabs
11361.1SabsSymptom:
11371.1SabsFix:	Rebuild usr.bin/lex
11381.1Sabs
11391.1SabsSymptom:
11401.1SabsFix:	rm /usr/lib/libbfd.a
11411.4Sitojun
11421.4SitojunSymptom:Obsolete intermediate files are used during compilation
11431.4SitojunFix:	Try the following sequence of commands in the directory in question.
11441.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
11451.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
11461.4Sitojun	may remain.  The command tries to clean everything up)
11471.5Swiz
11481.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
11491.207Smbalmer	pointer type
11501.5SwizFix:	Rebuild and install usr.bin/menuc
11511.12Sitojun
11521.12SitojunSymptom:mklocale not found during build in share/locale/ctype
11531.12SitojunFix:	Build and install usr.bin/mklocale
11541.13Sdogcow
11551.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
11561.13SdogcowFix:    Rebuild and install lib/libc
11571.13Sdogcow
11581.142SdrochnerSymptom:usr.bin/config fails to build.
11591.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
11601.13Sdogcow
11611.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
11621.19ScgdFix:    Rebuild and install lib/libc
11631.24Sabs
11641.24SabsSymptom:lint does not understand the '-X' option
11651.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
11661.223Sjoerg
11671.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
11681.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
11691.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
11701.257Sapb
11711.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
11721.257Sapb	No such file or directory.
11731.257SapbCause:	If a directory is created by mistake, then it is sometimes
11741.257Sapb	deleted from the CVS repository using administrative commands
11751.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
11761.257Sapb	contains references to a directory that has been deleted on the
11771.257Sapb	server in this way, then "cvs update" reports this error.
11781.257SapbFix:	Recursively delete the affected directory from your working tree
11791.257Sapb	and try the update again.
1180