UPDATING revision 1.346
1$NetBSD: UPDATING,v 1.346 2024/04/11 02:15:39 riastradh Exp $
2
3This file (UPDATING) is intended to be a brief reference to recent
4changes that might cause problems in the build process, and a guide for
5what to do if something doesn't work.
6
7For a more detailed description of the recommended way to build NetBSD
8using build.sh, see the BUILDING file.
9
10Note that much of the advice in this UPDATING file was written before
11build.sh existed.  Nevertheless, the advice here may be useful for
12working around specific problems with build.sh.
13
14Sections are marked with "^^^^^".  After the section on "Recent changes"
15are several sections containing more general information.
16
17See also: BUILDING, build.sh, Makefile.
18
19Recent changes:
20^^^^^^^^^^^^^^^
21
2220240410:
23	Update builds may require manually deleting
24	$DESTDIR/var/run/named (and, potentially,
25	$DESTDIR/var/run/lwresd) in order to avoid checkflist failure.
26
2720230828:
28	If:
29        - you updated to current and ran postinstall between 20230826
30	  and 20230828 inclusive, and
31        - you are not using anything outside the base system to
32	  populate /etc/openssl/certs (e.g., manually adding
33	  certificates or using ca-certificates or mozilla-rootcerts or
34	  mozilla-rootcerts-openssl from pkgsrc),
35	delete /etc/openssl/certs and rerun postinstall or just
36	`certctl rehash'.
37
38	Otherwise, certctl(8) will think someone else has left
39	/etc/openssl/certs in the way and will avoid clobbering it on
40	upgrade from older NetBSD.
41
4220230718:
43	build.sh will use mk.conf in the same directory as build.sh instead
44	of /etc/mk.conf, unless MAKECONF is already defined in the environment.
45
4620230714:
47	Import of gcc 10.5 requires a clean build of at least tools/gcc
48	and external/gpl3/gcc* object directories. An update build
49	without cleaning will result in obscure failures in rare corner
50	cases.
51
5220230604:
53	Building native kernels with the installed make(1) instead of
54	the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland
55	has not been updated. Note that this is an unsupported build
56	configuration (but usually works if userland is -current enough).
57
5820230523:
59	ctfmerge was fixed as macOS host tool. This may require a clean tools
60	rebuild to detect the update to tools/compat/configure.
61
6220230515:
63	New openssl build requires removal of the crypto/external/bsd/openssl
64	and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierarchy.
65	Otherwise test results may be wrong due to wrong "golden" output
66	files being installed.
67
6820230322:
69	Fixes for moved /lib/libisns* mean that builds will complain about
70	./usr/lib/libisns* being missing until src/lib/libisns is forced
71	to (re)install the files, including the symlinks.  The simplest
72	way is to clean this subdir before building.
73
7420230112:
75	New binutils require an updated ld.elf_so. If you are doing
76	(unsupported) in-place self builds (with the -E flag to build.sh),
77	make sure to have installed latest ld.elf_so before you rebuild
78	userland.
79
8020221116:
81	The addition to NetBSD's version of UFS2 of support for extended
82	attributes broke backward compatibility with previous releases
83	of NetBSD, so UFS2 has been restored to being compatible with
84	previous NetBSD releases by disabling extended attributes.
85	(Note that ACLs are implemented as extended attributes, so
86	this changes disables ACLs as well.)
87
88	Support for UFS2 with extended attributes is now available in a new
89	UFS variant called UFS2ea.  If you have created extended attributes
90	in an original UFS2 file system then "fsck -p" will now fail due to
91	the unexpected presence of extended attributes and "fsck -y" will
92	remove all extended attributes.  If you wish to preserve extended
93	attributes rather than delete them, there is a utility to convert
94	a UFS2 file system to UFS2ea and leave extended attributes in place,
95	but this should be used with caution since it will preserve any
96	extended attributes that have been corrupted by the backward
97	incompatibility too.
98
99	If you wish to use a UFS2ea file system as your root file system,
100	then you will need to update your boot loader to a version that
101	supports UFS2ea.
102
103	For more information, see:
104	https://wiki.netbsd.org/features/UFS2ea
105
10620221111:
107	The new libdrm import worsened the conflict issues for the
108	kdump/ktruss ioctl, and i915 now conflicts with base, and has
109	been turned off.  This will cause update build issues like:
110
111		kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP'
112		   undeclared here (not in a function);
113		   did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'?
114
115	You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue.
116
11720220921:
118	Since the kernel version was bumped to 9.99.100, the bootloader
119	must be updated on x86 or EFI boot platforms in order to load
120	modules from boot.cfg(5) or interactively at the bootloader
121	prompt.
122
123	The kernel can still load modules at runtime, with modload(8)
124	or modules.conf(5), with no bootloader update.  This will not
125	affect release branches because it only applies to patch
126	numbers >=100.
127
128	On x86 (i386 or amd64) with BIOS boot, this requires copying a
129	new /usr/mdec/boot to /boot.  You can build this in the destdir
130	by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
131	sys/arch/i386/stand.
132
133	On platforms with EFI boot (including x86 with EFI boot), this
134	requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/
135	directory on the EFI system partition.  The boot*.efi file is:
136
137	aarch64	bootaa64.efi
138	amd64	bootx64.efi
139	arm	bootarm.efi	(32-bit arm)
140	i386	bootx32.efi
141
142	You can build this in the destdir by running
143	`$TOOLDIR/bin/nbmake-$ARCH dependall install' in
144	sys/stand/efiboot/boot*.
145
14620220821:
147	Support for building extsrc/ has been deprecated.
148	EXTSRCSRCDIR and MKEXTSRC have been deprecated.
149
15020220714:
151	Updates to xorg-server and associated drivers may cause builds to
152	fail.  Cleaning both DESTDIR and the xorg build tree may be needed.
153
15420220628:
155	Changes in the build of src/games/robots require a clean build
156	of that program.
157
15820211116:
159	Changes in the xorg build require clean obj dirs for external/mit/xorg
160	(or a full clean/non-update build).
161
16220211112:
163	Device tree sources were updated for evbarm.  Some device nodes
164	(in particular, ld(4) devices on the ROCKPro64) will be renumbered.
165
16620211014:
167	MKPIE default for aarch64 has changed, a clean build is required.
168
16920210917:
170	Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
171	ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
172	and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
173
17420210711:
175	Updated GMP sources may require cleaning in tools/gmp and/or in
176	external/lgpl3/gmp/lib, particularly if GCC itself does not build.
177
17820210417:
179	GCC 10 was enabled for several platforms.  If builds fail in either
180	tools/gcc or external/gpl/gcc, first try cleaning those objects and
181	removing the $DESTDIR/usr/include/g++ subdirectory.
182
18320201230:
184	lint1/ops.c is no longer autogenerated.  If this makes the build
185	fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*.
186
18720201016:
188	MIPS kernel modules have been disabled until they work.  This will
189	turn up in extra files in the DESTDIR, which should be cleaned.
190
19120200925:
192	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
193	in both the tools and external dirs.
194
19520200912:
196	GCC 9 has arrived for Arm and x86 platforms, and will be coming
197	for several more, as will binutils 2.34.  Clean as required.
198
19920200907:
200	GCC 9 is coming, and binutils has been updated for MIPS.  This
201	probably requires cleaning the tools/binutils.
202
20320200811:
204	GCC updates may require cleaning the objdir.  This may occur
205	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
206	GCC 9 upgrade.
207
20820200614:
209	blacklist* has been renamed to blocklist*. postinstall(8)
210	should handle the migration.
211
21220200601:
213	Due to a mistake in LIBISPRIVATE handling, .so libraries were
214	created in the build directories and need cleaning.
215
21620200311:
217	GCC 8 ports will need cleaning in src/tools/gcc and
218	src/external/gpl3/gcc due to GCC 8.4 update.
219
22020191118:
221	More architectures were switched to gcc8:
222	    i386, ia64 powerpc64, sparc, sparc64, arm
223	The same comments as in 20191022 apply.
224
22520191112:
226	The LLVM update requires a clean rebuild for all architectures using
227	LLVM during the tools build phase (i386, amd64, aarch64).
228
22920191022:
230	Ports amd64 and aarch64 switched to GCC 8.3 by default.
231	In-place ("expert mode", build.sh -E) builds are not supported
232	when going from a GCC 7 userland to GCC 8. Do a regular
233	build to a different DESTDIR (or preferably: build.sh -U) at least
234	once and install sets, or download comp.{tar.xz,tgz} from the
235	daily builds and install that before doing the next in-place build.
236
23720191001:
238	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
239	old builds with GCC 7 output now uses GCC 8.  Clean this
240	directory, and also clean src/external/gpl3/gcc.
241
24220190903:
243	Files with names that coincide with existing files' names on
244	case-insensitive file systems were inadvertently committed, for
245	radeon GPU firmware.  We cannot mark these as obsolete for
246	postinstall to fix, so if you updated src since 2019-08-26, and
247	ran build.sh distribution or ran build.sh release, you must
248	manually delete the following files in your DESTDIR (which is
249	usually $OBJDIR/destir.$ARCH), or from / if you have installed
250	them:
251
252		/libdata/firmware/radeon/bonaire_ce.bin
253		/libdata/firmware/radeon/bonaire_mc.bin
254		/libdata/firmware/radeon/bonaire_me.bin
255		/libdata/firmware/radeon/bonaire_mec.bin
256		/libdata/firmware/radeon/bonaire_pfp.bin
257		/libdata/firmware/radeon/bonaire_rlc.bin
258		/libdata/firmware/radeon/bonaire_sdma.bin
259		/libdata/firmware/radeon/bonaire_smc.bin
260		/libdata/firmware/radeon/bonaire_uvd.bin
261		/libdata/firmware/radeon/hainan_ce.bin
262		/libdata/firmware/radeon/hainan_mc.bin
263		/libdata/firmware/radeon/hainan_me.bin
264		/libdata/firmware/radeon/hainan_pfp.bin
265		/libdata/firmware/radeon/hainan_rlc.bin
266		/libdata/firmware/radeon/hainan_smc.bin
267		/libdata/firmware/radeon/hawaii_ce.bin
268		/libdata/firmware/radeon/hawaii_mc.bin
269		/libdata/firmware/radeon/hawaii_me.bin
270		/libdata/firmware/radeon/hawaii_mec.bin
271		/libdata/firmware/radeon/hawaii_pfp.bin
272		/libdata/firmware/radeon/hawaii_rlc.bin
273		/libdata/firmware/radeon/hawaii_sdma.bin
274		/libdata/firmware/radeon/hawaii_smc.bin
275		/libdata/firmware/radeon/kabini_ce.bin
276		/libdata/firmware/radeon/kabini_me.bin
277		/libdata/firmware/radeon/kabini_mec.bin
278		/libdata/firmware/radeon/kabini_pfp.bin
279		/libdata/firmware/radeon/kabini_rlc.bin
280		/libdata/firmware/radeon/kabini_sdma.bin
281		/libdata/firmware/radeon/kaveri_ce.bin
282		/libdata/firmware/radeon/kaveri_me.bin
283		/libdata/firmware/radeon/kaveri_mec.bin
284		/libdata/firmware/radeon/kaveri_mec2.bin
285		/libdata/firmware/radeon/kaveri_pfp.bin
286		/libdata/firmware/radeon/kaveri_rlc.bin
287		/libdata/firmware/radeon/kaveri_sdma.bin
288		/libdata/firmware/radeon/mullins_ce.bin
289		/libdata/firmware/radeon/mullins_me.bin
290		/libdata/firmware/radeon/mullins_mec.bin
291		/libdata/firmware/radeon/mullins_pfp.bin
292		/libdata/firmware/radeon/mullins_rlc.bin
293		/libdata/firmware/radeon/mullins_sdma.bin
294		/libdata/firmware/radeon/oland_ce.bin
295		/libdata/firmware/radeon/oland_mc.bin
296		/libdata/firmware/radeon/oland_me.bin
297		/libdata/firmware/radeon/oland_pfp.bin
298		/libdata/firmware/radeon/oland_rlc.bin
299		/libdata/firmware/radeon/oland_smc.bin
300		/libdata/firmware/radeon/pitcairn_ce.bin
301		/libdata/firmware/radeon/pitcairn_mc.bin
302		/libdata/firmware/radeon/pitcairn_me.bin
303		/libdata/firmware/radeon/pitcairn_pfp.bin
304		/libdata/firmware/radeon/pitcairn_rlc.bin
305		/libdata/firmware/radeon/pitcairn_smc.bin
306		/libdata/firmware/radeon/tahiti_ce.bin
307		/libdata/firmware/radeon/tahiti_mc.bin
308		/libdata/firmware/radeon/tahiti_me.bin
309		/libdata/firmware/radeon/tahiti_pfp.bin
310		/libdata/firmware/radeon/tahiti_rlc.bin
311		/libdata/firmware/radeon/tahiti_smc.bin
312		/libdata/firmware/radeon/verde_ce.bin
313		/libdata/firmware/radeon/verde_mc.bin
314		/libdata/firmware/radeon/verde_me.bin
315		/libdata/firmware/radeon/verde_pfp.bin
316		/libdata/firmware/radeon/verde_rlc.bin
317		/libdata/firmware/radeon/verde_smc.bin
318
319	We will re-import these radeon firmware images another way
320	later.
321
32220190727:
323	The uefi bootloader has gained tftp support and needs a clean
324	build. If you do update builds, manually clean its object
325	directory by something like:
326	cd sys/arch/i386/stand/efiboot && make clean
327
32820190723:
329	The jemalloc allocator in libc is now built without extended
330	debugging (for performance reasons). In update builds make sure
331	to rebuild it completely, by removing all affected object files,
332	including compat builds, something like:
333	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
334
33520190207:
336	GCC 7 switched for many ports.  Update builds are likely to fail.
337
33820180924:
339	A newer OpenSSL version has been imported. If you are doing
340	update builds, make sure to remove all old obj dirs, like:
341	cd /usr/obj && find . -type d -name openssl | xargs rm -rf
342
34320180717:
344	On aarch64 int64_t and related types have changed from long long
345	to long. This requires recompiling all C++ binaries.
346
34720180713:
348	On amd64 and i386 static binaries are now build position
349	independent. This requires recompilation of all object
350	files used to create the crunched /rescue binary.
351	Clean the rescue directory in your obj directory before
352	doing an update build, otherwise linking will fail.
353
35420180414:
355	Existing binutils was migrated to binutils.old.  Manual
356	removal of tools/binutils objects directory may be required
357	to fix tools build failure.
358
35920180311:
360	bdftopcf was updated and may need cleaning in the
361	src/external/mit/xorg/tools/bdftopcf subdirectory if there are
362	link errors.
363
36420180212:
365	between OpenSSL and GCC updates, many things may fail to build.
366	any failure that looks like GCC or openssl is best handled by
367	a clean destdir and objdir.  Full cleandir and destdir deletion
368	is recommended if build failures occur.
369
37020171225:
371	removal of the vadvise syscall requires manual removal of all
372	associated files from the libc build object directory (including
373	the .depend files) - a command like:
374		cd $OBJ && find . -type d -name libc | xargs rm -rf
375	For architectures that support multiple "compat" binary targets,
376	you'll need to cleanup both the regular libc directory and the
377	compat ones (the above command will do that).
378
37920171010:
380	a change to the build structure of external/bsd/acpica/bin/iasl
381	means that its objdir (or *.d and .depend at least) might need
382	to be manually removed - or a build done once without -u.
383
38420170822:
385	a new version of GMP has been imported and probably
386	will break parts of builds related to themselves or GCC, both
387	in the tools and the native section.  Remove all GCC, GMP, MPFR
388	and MPC objdirs or build once without -u.
389
39020170816:
391	a new version of MPFR and MPC have been imported and probably
392	will break parts of builds related to themselves or GCC, both
393	in the tools and the native section.  Remove all GCC, GMP, MPFR
394	and MPC objdirs or build once without -u.
395
39620170402:
397	a new version of dhcpcd has been imported, which does not support
398	update builds from the previous version. Remove your
399	external/bsd/dhcpcd object dir or build once without -u.
400
40120170211:
402	a new terminfo database has been imported.
403	The structure of it has changed slightly from prior versions and
404	an updated tic tool is required.
405	If you build.sh, don't use -u
406
40720170207:
408	various arch dependent libc/exect.S files were removed
409	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
410	if it exists) or do a clean build.
411	(This is a bug in the make system, it should be corrected without
412	human intervention, but isn't.)
413
41420170104:
415	xinput build options have changed.
416	Remove the obj directory (external/mit/xorg/bin/xinput)
417	if you build.sh -u
418
41920170103:
420	a new version of flex has been imported.
421	Remove the file from obj (external/bsd/flex)
422	if you build.sh -u
423
42420161014:
425	a new version of OpenSSL has been imported.
426	Remove the files from obj (crypto/external/bsd/openssl) 
427	if you build.sh -u
428
42920161009:
430	a new version of dhcpcd has been imported with slightly changed
431	build infrastructure. When doing a build.sh -u this requires
432	pruning the external/bsd/dhcpcd objdir.
433
43420160914:
435	i386, amd64, shark, ofppc and macppc have joined shark and x68k
436	ports in using xorg-server 1.18. This requires a clean destdir
437	and a clean objdir.
438
43920160527:
440	i386 needs a full cleandir or objdir deletion because PIE has
441	been enabled. (see the amd64 entry two down for further info)
442
44320160418:
444	libedit needs manual removal of all autogenerated files since
445	some of them are not autogenerated anymore. Remember that there
446	might be two copies of libedit if your platform builds "compat".
447
44820160410:
449	amd64 needs full "make cleandir" or deletion of objdir now that
450	PIE has been enabled for amd64.  PIE, or position-independent
451	executables, means all code, including executables and not just
452	shared libraries, is position-independent and hence able to be
453	relocated by ASLR, address space layout randomization.
454
455	The change was made in Makefile variables for compiler and
456	linker flags, for which make(1) does not record dependencies,
457	hence it is unable to detect that all .o files need rebuilding.
458
459	Partial rebuilds with some modified source files will likely
460	fail when linking executables, since the linker refuses to mix
461	position-independent code with position-dependent code in
462	position-independent executables:
463
464		.../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC
465
46620160401:
467	Ports switching to GCC 5.3 will need a full "make cleandir".
468	Some people have found that cleandir is not sufficient, so if
469	in doubt delete the entire object directory tree for gcc.
470
47120160306:
472	NetBSD's regexp implementation is now part of libnbcompat.
473	Nblex, nbm4, nbpax, nbsed use it and they may crash on
474	non-NetBSD hosts if linked with stale object files produced
475	while they included a non-NetBSD regex.h.
476	In any case, you should "make cleandir" at least these tools
477	before updating your toolchain.
478
47920160125:
480	Dtrace has been enabled by default on some architectures.
481	When doing an update build, make sure to clean the etc/mtree
482	object directory before starting the build - otherwise the
483	needed directories in destdir will not be created.
484	An easy way to do this is:
485	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
486
48720150818:
488	New acpica requires "make cleandir" in src/external/bsd/acpica
489	again.
490
49120150413:
492	New acpica requires "make cleandir" and reinstalling yacc
493	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
494	also "make cleandir" in /usr/src/external/bsd/acpica.
495
49620150404:
497	Lint changes require a full rebuild of the tool, so make
498	sure to build without -u option to build.sh, or manually
499	do a make cleandir in src/tools/lint1 and
500	src/usr.bin/xlint.
501
50220150310:
503	Improvements to openssl for arm mean that update builds of
504	the openssl libraries will fail. A make cleandir in
505	external/bsd/openssl/lib is needed
506
50720141026:
508	A mishap during the import of pppd may cause your corruption
509	in your cvs directory if you happened to do a cvs update
510	during a short period of time. To fix, just remove the
511	directory src/external/bsd/ppp/dist/pppd completely
512	and let cvs restore it on next update.
513
51420140721:
515	The src/external/mit/lua/src directory was accidentally created
516	and then deleted in the CVS repository.  If you get errors like
517
518	cvs [update aborted]: cannot open directory
519	/cvsroot/src/external/mit/lua/src: No such file or directory
520
521	then delete your local copy of that directory tree and try again.
522
52320140530:
524	ARM eABI switched to DWARF based exception handling. This requires
525	rebuilding all C++ code. It is strongly advised to do a clean build.
526
52720140131:
528	The new compiler_rt/libc integration moved a few things. It is strongly
529	advised to do a clean build. At least lib/libc, the compat version(s)
530	of libc, libkern, rump and the kernels need to be cleaned.
531
53220131227:
533	1. The new ntpd runs in a restricted mode to prevent amplification
534	   attacks. If you need ntpdc to work you need to explicitly enable
535	   mode7 in your config file. Make sure you put the necessary restrict
536	   statements to avoid being exposed.
537	2. strncat has moved from lib/libc to common/lib/libc; you might need
538	   to make clean in libc
539
54020131129:
541	The GMP sources were updated, and builds will likely fail without
542	cleaning their build trees for both tools and in-tree, like below.
543
54420131128:
545	The MPC and MPFR sources were updated, and builds may require their
546	tools and in-tree directories cleaned for successful updates.
547
54820130605:
549	The kernel option FAST_IPSEC no longer exists, it's been renamed
550	to IPSEC (and the older IPSEC version removed).
551
55220130605:
553	Previous freetype installations erroneously installed private
554	header files. If you are building against a non-empty $DESTDIR,
555	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
556
55720130531:
558	The xdm update may cause build failure due to xdm.man being
559	in the obj tree.  Make sure to ensure any like this:
560		nbmake: nbmake: don't know how to make xdm.man. Stop
561	is fixed by deleting the xdm.man in the obj tree.
562
56320130530:
564	Updates of many xsrc packages will leave old .pc files around.
565	Best to clean out the xsrc objdir entirely before rebuilds.
566
56720130301:
568	The removal of netiso requires manual removal of /usr/include/netiso
569	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
570
57120120726:
572	The update of OpenSSL requires cleaning both the OpenSSL build
573	directory and DESTDIR.  *Even non-update builds require cleaning
574	DESTDIR.* Builds done without taking these steps may fail, or in
575	some cases may succeed and install broken OpenSSL libraries that
576	cause third-party software to link incorrectly and/or crash.
577
57820120507:
579	The database schema for makemandb was changed.  You will
580	need to update the database using 'makemandb -f' or wait
581	for the next weekly run to fix it.
582
58320120319:
584	sys/conf/Makefile.kern.inc has been modified to adjust the
585	size of db_symtab automatically.  You need to update dbsym in
586	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
587	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
588	mk.conf.
589
59020120216:
591	Default for MKCATPAGES changed to NO.  Update builds will fail
592	unless DESTDIR is cleaned manually.  If you built between 20120207
593	and 20120216, daily and weekly could have created an unreadable
594	/var/db/man.db index for apropos.  Running makemandb -f or
595	the next run of weekly will fix it.
596
59720111227:
598	If you built between 20111225 and 20111227 you need to remove
599	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
600	bump has been reverted.
601
60220111125:
603	The "rnd" pseudodevice has been added to sys/conf/std, which
604	means it should no longer be explicitly listed in kernel
605	configuration files.  The line "pseudo-device rnd" should be
606	removed from any custom kernel config files users may have.
607
60820111119:
609	A problem with the datastructures used by the rndctl(8)
610	utility (pointers in datastructures in an array, making 32->64
611	bit compatibility very painful) has been fixed in a
612	non-backwards-compatible way.  If you replace your kernel,
613	replace your rndctl executable too.
614
61520111001:
616	the prop_*_send_syscall() functions from proplib(3) have been
617	changed and their new version is not backward compatible with the old
618	one.  So ensure that all consumers of these functions (currently:
619	quota2 code and its tests) are updated together with the new lib.
620
62120110817:
622	sparc has been changed to use GCC 4.5.3, so any objdir or
623	DESTDIR for them should be deleted before updating.
624
62520110806:
626	i386 and amd64 have been changed to use GCC 4.5.3, so any
627	objdir or DESTDIR for them should be deleted before updating.
628
62920110805:
630	The update to GCC 4.5.3 requires a non-trivial portion of
631	the tree to be cleaned.  Best to delete both objdir and
632	DESTDIR before running this update.  So far, only the
633	sparc64, mips and powerpc platforms have changed.
634
63520110803:
636	The layout of external/public-domain/xz has changed.  To do an
637	update build you will have to remove the contents of the OBJDIR
638	for external/public-domain/xz/bin by hand as the xz entry there
639	is now a directory.
640
64120110410:
642	The configuration of src/tools/gcc has changed.  To do an
643	update build you have to clean both tools/binutils and
644	tools/gcc by hand.
645
64620110328:
647	Building the Xorg binary was moved into a subdirectory to fix
648	ordering issues with "make all".  It may be necessary to remove
649	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
650	if your update build fails, as the "Xorg" entry there is now a
651	directory.
652
65320110121:
654	Assembler files no longer use -traditional-cpp.  This can break
655	the build of individual parts of the tree.  This is handled
656	correctly by build.sh.  Manual builds have to update /usr/share/mk
657	and re-run config(1) for any kernel configurations as needed.
658
65920101217:
660	The tcpdump(8) program was changed to drop privileges and chroot(2)
661	by default.  It may be necessary to manually update passwd(5) and
662	group(5) in order to make the program work with existing setups.
663
66420101125:
665	The latest changes to setenv(3) disallow setting environment
666	variables with names that contain '='.  Revision 1.18 of env.c
667	assumed that this was allowed.  Installing a new libc with an
668	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
669	break which affects the autoconf tests for dependency finding,
670	so building gcc will end up printing:
671	    checking dependency style of gcc... none
672	    configure: error: no usable dependency style found
673	Fix it by rebuilding and re-installing env.
674
67520101119:
676	Recent Xorg updates in xsrc/external/mit/ may cause various build
677	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
678	have any build problems with xsrc, or problems with mismatched
679	versions between xorg-server and drivers.
680
68120100604:
682	The update of ATF to 0.9 causes old tests written in shell to fail
683	unless they are rebuilt.  If you are building with MKUPDATE=yes,
684	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
685	trees by hand.
686
68720100522:
688	Recent Xorg updates in xsrc/external/mit/ will cause various build
689	problems.  Delete your entire DESTDIR and OBJDIR if you have any
690	build problems with xsrc.
691
69220100522:
693	private section of <ctype.h> was split, and now mklocale(1)
694	include ctype_local.h, so you have to make cleandir in tools/mklocale.
695
69620100520:
697	The location of the xkb compiled descriptions has changed.  Please
698	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
699
70020100222:
701	The shared objects file extension has been changed from .so to
702	.pico, in order to avoid conflicts with shared libraries names
703	libXX.so.  All now stale regular .so files can be removed from
704	your object directories.
705
70620100204:
707	The termcap database has been removed from the sources,
708	but has not been marked obsolete so it is not removed
709	from the system when upgrading.
710	As such, you will need to remove them from your object
711	and destination directories.
712
71320091101:
714        After updating, it may be necessary to make the 'cleandir'
715        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
716        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
717        src/tools/lex/ and src/usr.bin/lex/.
718
71920091001:
720	On amd64 you must rebuild tools (to get the new binutils)
721	before building a kernel, or the build fails on cpufunc.S.
722
72320091001:
724	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
725	symlink, failing the build.  Delete the link, and the subdir
726	it is in, and retry your build.
727
72820090718:
729	libc build changed so that strchr() provides the extra entry
730	point for index().  Update build of libc.a (and libc_pic.a)
731	may fail because the archive contains the unwanted index.o.
732	(Similarly for strrchr() and rindex().)
733
73420090709:
735	Native Xorg was upgraded again.  Builds will probably fail again
736	without a clean objdir, at least for src/external/mit/xorg.
737
73820090616:
739	Native Xorg was upgraded.  Builds will need a clean objdir for
740	src/external/mit/xorg.  Upgrading a system from sets will not
741	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
742	subdirectory has been changed into a file, and this needs to
743	be manually "rm -r"'ed before installing xbase.tgz.
744
74520090501:
746	Several new functions were added to string.h/libc, and this
747	can cause autoconf problems during the tool build for people
748	who fail to clean out their tools objects properly.  If you
749	note messages about stpcpy, stpncpy or strnlen accompanying a
750	failure during the tool build, clean out all your tools
751	objects and start again.
752
75320090325:
754	The i386 port was switched to i486 default toolchain.  This requires
755	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
756
75720090126:
758	The __posix_fadvise50 system call changed assembly stub type.  You
759	need to 'rm -f __posix_fadvise50.*' in the libc build directory
760	to avoid using the old assembly stub.
761
76220090202:
763	pkg_install now depends on the pkgdb cache for automatic conflict
764	detection.  It is recommended to rebuild the cache with
765	``pkg_admin rebuild''.
766
76720090110:
768	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
769	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
770	   This is needed even in the MODULAR kernel because there is
771	   conditionally compiled code in rtsock.c.
772	2. make sure build.sh completes and the binaries in a chroot work
773	   before installing.
774	3. If you don't use build.sh and you build directly to root, and
775	   your build breaks in the middle, don't despair.  Make sure headers
776	   are installed properly, and start building libraries first libc
777	   and libutil, install them and then continue building all the
778	   libraries in src/lib and src/gnu/lib and install them.  Once
779	   the new libraries are installed, you can restart the build.
780	4. If you compile packages and you notice link time warnings,
781	   rebuild the required packages to update their shared libraries.
782	   Any package you rebuild will require rebuilding all the packages
783	   that depend on it.
784	5. Next time you run pwd_mkdb with the new binary, the file
785	   will be upgraded and it will not be backwards compatible.
786	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
787	   lastlogx(5)) have been versioned, and there is a heuristic
788	   for utmp.  You are better off removing the old files after
789	   upgrading.  The automated clearing of /var/run during
790	   boot, and the automated rotating of files in /var/log by
791	   newsyslog(8), may mean that you do not have to remove the
792	   files manually.
793	7. The optional accounting file (/var/account/acct, see
794	   accton(8)) has not been versioned, and will need to be
795	   removed.  The automatic rotation of the accounting file by
796	   /etc/daily limits the bad consequences of failure to remove
797	   the file.
798	8. Application software that writes time_t to binary files on
799	   disk will break or need attention.  Most notably: if you are
800	   using PostgreSQL < 8.4, you need to dump your databases,
801	   rebuild PostgreSQL with the new time_t, then restore.
802
80320081219:
804	config(1) has been updated, and one of the files it creates -
805	swapnetbsd.o - has changed format.  You need to rebuild config
806	(done automatically by build.sh) and then you need to rerun
807	config on all kernel configuration files before rebuilding those
808	kernels.
809
81020081205:
811	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
812	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
813	set and will appear as extra files for MKX11=no update builds.
814
81520081122:
816	On i386, various kernel options(4) in GENERIC including
817	file systems have been disabled and moved into kernel modules.
818	Before trying a new GENERIC kernel, you have to prepare the
819	following files as well as a new GENERIC kernel:
820
821	- build and install kernel modules from src/sys/modules
822
823	- install the latest bootloader, which will load a module
824	  for the file system from which the kernel is loaded automatically
825
826	If you have to load your kernel from a file system which is not of
827	the same type as the root file system, you have to load the necessary
828	file system module manually on the boot prompt or in the boot.cfg file.
829
83020080827:
831	If you built and installed a libc from sources between
832	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
833	which results in false errors reported by lint(1).
834	Since this breaks the libc build itself, manual help is
835	needed -- lint must be disabled temporarily, e.g.:
836	  $ (cd lib/libc && make MKLINT=no dependall install)
837
83820080813:
839	MKDEBUG build was broken because the .depend files did not know
840	about .go files.  You need to remove all .depend files and rebuild.
841
84220080802:
843	A regression in binary compatibility for pthread_mutex_t has
844	been fixed.  Unfortunately, the price is breaking compatibility
845	for -current.
846
847	Threaded programs (using libpthread) and C++ programs (using
848	libstdc++) compiled after 20070907 and before 20080802 need to
849	be recompiled.
850
851	One way to find affected pkgsrc packages:
852
853	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
854	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
855
85620080731:
857	WAPBL (metadata journaling support) has been added, but at this
858	time isn't backwards compatible with pre-WAPBL aware kernels
859	and userland (fsck_ffs in particular).  Please make sure you
860	don't use a journaled filesystem with an older kernel/userland,
861	especially an uncleanly mounted journaled filesystem.  WAPBL
862	also requires the super block to be in the UFS2 format.  You
863	can use fsck_ffs -c 4 to update the superblock format.
864
86520080721:
866	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
867	isn't defined.
868
86920080531:
870	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
871	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
872	utility needs to be rebuilt and reinstalled as older binaries
873	won't work correctly.  The following sequence of commands:
874
875	  $ (cd sys/sys/ && nbmake-$arch includes)
876	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
877	  $ (cd sbin/drvctl/ && nbmake-$arch all)
878
879	leaves new drvctl utility in sbin/drvctl build directory.
880
88120080503:
882	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
883
88420080521:
885	For a while, unprivileged UPDATE builds would fail to
886	succeed at the checkflist stage, complaining that
887	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
888	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
889	If you already hit this problem, update the .mk file,
890	remove ${DESTDIR}/stand/<arch>, and re-run the build.
891
89220080303:
893	Linker warnings are now fatal if $WARNS>0.
894
89520080126:
896	The posix_fadvise system call has been changed from an assembly
897	stub, to a c file that calls an assembly stub.  You need to
898	'rm -f posix_fadvise.* .depend' in the libc build directory to
899	avoid using the old assembly stub.
900
90120071209:
902	The acpiec(4) driver has been split into two attachments.  If you
903	get ACPI errors before the attachment, please update your kernel
904	configuration file appropriately or see GENERIC for more details.
905
90620071115:
907	The it(4) driver has been renamed to itesio(4) and the old port
908	argument specified in the kernel configuration file is not valid
909	anymore.  The itesio(4) driver now uses the Super I/O address port
910	rather than the EC address port.  Please update your kernel
911	configuration file appropriately or see GENERIC for more details.
912
91320071028:
914	The pccons(4) driver has been removed from the NetBSD/shark port.
915	You need to update any custom kernel configuration file you have
916	to remove any references to pccons (which includes removing the
917	now useless XSERVER option) and replace them with the correct
918	entries for the wscons driver.  See the GENERIC configuration file
919	for more details.
920
92120070913:
922	A latent bug in dhclient/dhcpd that caused it to be unable to
923	enumerate interfaces was fixed.  The bug began to cause
924	problems after 20070911 when the kernel's SIOCGIFCONF
925	implementation was repaired.  From 20070529 to 20070911 racoon
926	could not enumerate interfaces.  (These are noted because
927	normal kernel/userspace version matching hygiene is not
928	sufficient to avoid this problem.)  Ensure that both kernel
929	and userland are from after 20070913.
930
93120070703:
932	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
933	calls the target-specific strip program, and the logic to pass
934	down STRIP from make has been removed.  This requires a
935	re-installation of tools.
936
93720070422:
938	The way OS emulations lookup filenames inside the emulation root
939	has been changed.  Rather than modify the pathname (and copy back
940	to userspace) namei() and lookup() directly check the emulation
941	root.  One side effect is that absolute symlinks inside the emulated
942	root file system will be relative to that file system - unless they
943	start /../ this is useful when the emulated root is a real install
944	that has such links.
945	This might affect symlinks that have been added to reference outside
946	the emulated root.
947
94820070412:
949	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
950	instead.  See the GENERIC32_IP3x kernel configuration for an
951	example.
952
95320070319:
954        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
955        on many platforms due to incorrect flags settings.  If you
956        updated and built after about 20070315, do "nbmake-$arch
957	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
958	rebuild of object files that might have been built
959	incorrectly, and ensure that you have at least
960	src/lib/libc/Makefile 1.130.
961
96220070210:
963        src/sys/sys/{sa.h,savar.h} were removed.
964          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
965              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
966        will allow dependencies on those files to get get rebuilt
967
96820070209:
969        The threading model was changed when the newlock2 branch
970        was merged to NetBSD-current.  If you boot with a new
971        kernel (version 4.99.10), then you also need a new pthread
972        library (/usr/lib/libpthread.so.0.7).  If you boot with
973        an old kernel, then you need the old pthread library
974        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
975        the pthread library in sync, old threaded applications should
976        continue to work with an old or new kernel.  Note that named(8)
977	is the only threaded application in the base system.
978
97920061214:
980	Following the move of string_to_flags() and flags_to_string()
981	from the bin/ls/ sources to libutil, users doing UPDATE builds
982	will need to do a "make cleandir" in
983		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
984		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
985		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
986		as the installation images in distrib/
987	in order to excise stale references to the old stat_flags.h header
988	file in the ls sources -- stat_flags.h has been removed.
989
99020061108:
991	The configure script used in the src/tools/gcc compiler has been
992	changed to indicate that our libc has ssp support built-in and
993	does not depend on -lssp and -lssp-nonshared.  You'll need to
994	make clean in src/tools/gcc first to rebuild the compiler.
995
99620061009:
997	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
998	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
999
100020060814:
1001	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
1002	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
1003	kernel configuration for an example.  X servers from the last
1004	few years should cope.
1005
100620060703:
1007	MPACPI is no more.  We always configure PCI interrupts using ACPI
1008	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
1009	to ACPI_SCANPCI.  Thanks to work from fvdl.
1010
101120060627:
1012	socket(2) has changed, and its system call has been versioned.
1013	For userlands with the old version of socket(2), make sure that
1014	your kernel has 'options COMPAT_30' set, or else 'bad system call'
1015	errors will result.
1016
1017Hints for a more successful build:
1018^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1019    Use build.sh, but do not use its "expert mode":
1020	This will automatically build the tools in the
1021	   correct order, and it will keep the tools and the
1022	   new build products from interfering with the running
1023	   system.  This will allow you to ignore most of the
1024	   other advice in this file.
1025    Build a new kernel first:
1026	This makes sure that any new system calls or features
1027	   expected by the new userland will be present.  This
1028	   helps to avoid critical errors when upgrading.
1029    Use object directories:
1030	This helps to keep stale object
1031	   files from polluting the build if a Makefile "forgets"
1032	   about one.  It also makes it easier to clean up after
1033	   a build.  It's also necessary if you want to use the
1034	   same source tree for multiple machines.
1035	   To use object directories with build.sh:
1036	    a) invoke build.sh with the "-M" or "-O" options.
1037	   To use object directories without using build.sh:
1038	    a) cd /usr/src ; make cleandir
1039	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
1040	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
1041	    d) cd /usr/src ; make build
1042	   Note that running "make obj" in a directory will create
1043	   in obj.$MACHINE directory.
1044    Build to a DESTDIR:
1045	This helps to keep old installed files (especially libraries)
1046	   from interfering with the new build.
1047	   To build to a DESTDIR with build.sh, use the "-D" option.
1048	   To build to a DESTDIR without using build.sh, set the DESTDIR
1049	   environment variable before running make build.  It should be
1050	   set to the pathname of an initially empty directory.
1051	   Problems: if you do not use build.sh, you might need to
1052		update critical utilities without using DESTDIR since
1053		nothing is executed from what is installed in DESTDIR.
1054		(See critical utils, below.)
1055    Build often:
1056	This keeps critical utilities current enough to not choke
1057	on any other part of the source tree that depends on up to
1058	date functionality.  If you use build.sh, you should not have
1059	this problem.
1060
1061What to do if things don't work:
1062^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1063When things don't work there are usually a few things that commonly
1064should be done.
1065    1)	make includes
1066	This should be done automatically by make build.
1067    2)  cd share/mk && make install
1068	Again, automatically done by make build.
1069
1070Failsafe rebuild of a small part of the tree:
1071^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1072To make sure you rebuild something correctly you want to do
1073something like the following:
1074    1)  Make sure the includes and .mk files are up to date.
1075    2)  Make sure any program used to build the particular
1076	utility is up to date.  (yacc, lex, etc...)
1077    3)  cd ...path/to/util...
1078	make cleandir
1079	rm ...all obj directories...
1080	make cleandir			# yes, again
1081	make obj
1082	make depend && make
1083
1084Failsafe rebuild of the entire tree:
1085^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1086If you really want to make sure the source tree is clean and
1087ready for a build try the following.  Note that sourcing /etc/mk.conf
1088(a make(1) Makefile) in this manner is not right, and will not work
1089for anyone who uses any make(1) features in /etc/mk.conf.
1090
1091---cut here---
1092#!/bin/sh
1093. /etc/mk.conf
1094
1095if [ -z $NETBSDSRCDIR ] ; then
1096    NETBSDSRCDIR=/usr/src
1097fi
1098if [ \! -d $NETBSDSRCDIR ] ; then
1099    echo Unable to find sources
1100    exit 1
1101fi
1102find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
1103
1104if [ -z $BSDOBJDIR ] ; then
1105    BSDOBJDIR=/usr/obj
1106fi
1107if [ -d $BSDOBJDIR ] ; then
1108    rm -rf $BSDOBJDIR
1109fi
1110
1111cd $NETBSDSRCDIR && make cleandir
1112
1113---cut here---
1114
1115Critical utilities:
1116^^^^^^^^^^^^^^^^^^^
1117	usr.bin/compile_et
1118	usr.bin/make
1119	usr.bin/yacc
1120	usr.bin/lex
1121	usr.bin/xlint
1122	usr.bin/config
1123
1124Other problems and possible solutions:
1125^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1126Symptom:Complaints involving a Makefile.
1127Fix:	Rebuild usr.bin/make:
1128	cd usr.bin/make && make && make install
1129	Or, a failsafe method if that doesn't work:
1130	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
1131
1132Fix:	Make sure .mk files are up to date.
1133	cd share/mk && make install
1134
1135Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
1136Fix:	Rebuild usr.bin/config
1137
1138Symptom:
1139Fix:	Rebuild usr.bin/yacc
1140
1141Symptom:
1142Fix:	Rebuild usr.bin/lex
1143
1144Symptom:
1145Fix:	rm /usr/lib/libbfd.a
1146
1147Symptom:Obsolete intermediate files are used during compilation
1148Fix:	Try the following sequence of commands in the directory in question.
1149	make cleandir; rm `make print-objdir`; make cleandir; make obj
1150	(If you built the tree without "make obj" in the past, obsolete files
1151	may remain.  The command tries to clean everything up)
1152
1153Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
1154	pointer type
1155Fix:	Rebuild and install usr.bin/menuc
1156
1157Symptom:mklocale not found during build in share/locale/ctype
1158Fix:	Build and install usr.bin/mklocale
1159
1160Symptom:undefined reference to `__assert13' or `__unsetenv13'
1161Fix:    Rebuild and install lib/libc
1162
1163Symptom:usr.bin/config fails to build.
1164Fix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
1165
1166Symptom:undefined reference to `getprogname' or `setprogname'
1167Fix:    Rebuild and install lib/libc
1168
1169Symptom:lint does not understand the '-X' option
1170Fix:    May need to build & install libs with NOLINT=1 before rebuilding lint
1171
1172Symptom:Update build fails in src/tools/gcc complaining that a variable
1173	(e.g. CPPFLAGS) has changed since the previous run.
1174Fix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
1175
1176Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
1177	No such file or directory.
1178Cause:	If a directory is created by mistake, then it is sometimes
1179	deleted from the CVS repository using administrative commands
1180	that bypass the normal cvs access controls.  If your cvs working tree
1181	contains references to a directory that has been deleted on the
1182	server in this way, then "cvs update" reports this error.
1183Fix:	Recursively delete the affected directory from your working tree
1184	and try the update again.
1185