UPDATING revision 1.385
1$NetBSD: UPDATING,v 1.385 2025/11/03 10:03:10 martin 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
2220251028:
23	libpthread had it's shared library version go back (from 1.7 to
24	1.6). This may cause fallout during update builds, remove the
25	libpthread obj dir and all libpthread.so.1.7\* files in the
26	dest dir.
27
2820251019:
29	Changes to how libcrypto got linked (libpthread not required
30	any more) cause failures in update builds. To fix, run
31	(as your build user) a "make cleandir" in the following
32	subdirectories:
33
34	crypto/external/apache2/openssl
35	crypto/external/bsd/heimdal
36	crypto/external/bsd/netpgp
37	crypto/external/bsd/openssh
38	external/bsd/libfido2
39	external/bsd/nsd
40	external/bsd/ntp
41	external/bsd/pam-u2f
42	external/bsd/ppp
43	external/bsd/tcpdump
44	external/bsd/wpa
45	games/factor
46	libexec/httpd
47	tests/crypto/libcrypto
48	tests/lib/libc/hash
49	usr.bin/dc
50	usr.bin/ftp
51	usr.bin/moduli
52	usr.bin/nbsvtool
53	usr.sbin/plainrsa-gen
54	usr.sbin/syslogd
55
5620250721:
57	GCC 12.5 was imported and there may be weird build issues.
58	Clean any GCC build dirs if you encounter weird things.
59
6020250720:
61	New openssl and old objects for tests for libcrypto may
62	cause spurious test failure, clean the src/tests/crypto/libcrypto
63	object dirs.
64
6520250528:
66	Changes in the tools build require removing all config.cache
67	files in the object tools directories.
68
6920250427:
70	The KERNEL_DIR option to build.sh is now functional.  Set it
71	with ``-V KERNEL_DIR=yes'' on your build.sh command.
72	With this, you can now colocate kernel and associated modules
73	in /netbsd/{kernel,kernel.dbg,modules} instead of having the
74	kernel in / but modules in /stand.
75
76	Note that you'll need new bootstrap code to use this feature.
77
78	This completes work begun many years ago by christos@ :-)
79
8020250413:
81	A change to bsd.lib.mk requires a clean build of all libraries.
82
8320250131:
84	The switch to the new jemalloc requires cleaning in libc.
85
8620241122:
87	Changes to various libraries' build options require cleaning
88	their objdirs in update builds:
89
90	cd external/bsd/file/lib && $TOOLDIR/bin/nbmake-$ARCH clean
91	cd external/bsd/libarchive/lib && $TOOLDIR/bin/nbmake-$ARCH clean
92	cd external/public-domain/xz/lib && $TOOLDIR/bin/nbmake-$ARCH clean
93
94	Also, for architectures with MKCOMPAT, it is necessary to clean
95	the compat objdirs too.  The easiest way is:
96
97	rm -rf OBJDIR/compat/*/*/external/bsd/file/lib
98	rm -rf OBJDIR/compat/*/*/external/bsd/libarchive/lib
99	rm -rf OBJDIR/compat/*/*/external/public-domain/xz/lib
100
101	Changes to bsd.lib.mk to improve detecting differences in
102	shared library symbol exports may cause some .actsym files in
103	the objdir to become stale in update builds.
104
105	To work around this, delete all files matching `*.actsym' in
106	the objdir.  For example:
107
108	find OBJDIR -name '*.actsym' -type f -print0 | xargs -0 rm
109
11020241104:
111	Changes around the integration of the zstd compression
112	library may require manual deletion of some object directories
113	if you update from a build from a few days ago:
114	rm -rf DESTDIR/usr/lib/*/libarchive*
115	rm -rf DESTDIR/usr/lib/*/libmagic*
116	rm -rf DESTDIR/usr/lib/*/libzstd*
117	rm -rf DESTDIR/usr/lib/libarchive*
118	rm -rf DESTDIR/usr/lib/libmagic*
119	rm -rf DESTDIR/usr/lib/libzstd*
120	rm -rf OBJDIR/compat/*/*/external/bsd/file/
121	rm -rf OBJDIR/compat/*/*/external/bsd/libarchive/
122	rm -rf OBJDIR/compat/*/*/external/bsd/zstd/
123	rm -rf OBJDIR/external/bsd/file/
124	rm -rf OBJDIR/external/bsd/libarchive/
125	rm -rf OBJDIR/external/bsd/zstd/
126	rm -rf OBJDIR/external/gpl3/gcc/
127	rm -rf OBJDIR/tools/gcc/
128
12920240926:
130	Building -current when running on amd64 from about 20240924
131	to about 20240926 will not work due to a "malloc_np.h"
132	error. Please downgrade to a version from 20240924 or older,
133	or upgrade to a newer version e.g. using a binary release from
134	the NetBSD build servers.
135
13620240923:
137	Update builds will require cleaning the object directories for
138	jemalloc (like: "rm -rf $OBJ/external/bsd/jemalloc*") and the
139	libc dependency files (like: "rm $OBJ/lib/libc/jemalloc.*").
140	On architectures with COMPAT libs, those also have to be cleaned,
141	e.g. on sparc64: "rm -rf $OBJ/compat/sparc64/sparc/external/bsd/jemalloc*"
142	and "rm $OBJ/compat/sparc64/sparc/lib/libc/jemalloc.*".
143
14420240920:
145	Update builds will require cleaning in src/external/historical/nawk/bin
146	in order to remove the awk subdirectory since there is now a binary
147	called awk.
148
14920240817:
150	Update builds will require cleaning in src/external/historical/nawk/bin
151	in order to remove the awk binary since now there is a subdirectory
152	called awk.
153
15420240812:
155	Update builds will require removing the tools objdir for gdb
156	if building with MKCROSSGDB=yes. All architectures use gdb.old
157	now.
158
15920240630:
160	Update builds will require removing the tools objdir for binutils
161	(as most architectures should use binutils.old now).
162
16320240610:
164	Update builds are likely to require removing the objdir for
165	distrib/<arch>/cdroms - or at least references to libarchive
166	from within there after the recent libarchive update.
167
16820240504:
169	Update builds on x86 require making the `cleandir' target in
170	lib/libm, or deleting the objdir for lib/libm.
171
17220240423:
173	Update builds with x11 may fail after switching to Mesa 21.
174
17520240410:
176	Update builds may require manually deleting
177	$DESTDIR/var/run/named (and, potentially,
178	$DESTDIR/var/run/lwresd) in order to avoid checkflist failure.
179
18020240409:
181	32-bit compatibility libraries were moved into the base32
182	and debug32 sets.  HTML man pages were moved into the manhtml set.
183
18420230828:
185	If:
186        - you updated to current and ran postinstall between 20230826
187	  and 20230828 inclusive, and
188        - you are not using anything outside the base system to
189	  populate /etc/openssl/certs (e.g., manually adding
190	  certificates or using ca-certificates or mozilla-rootcerts or
191	  mozilla-rootcerts-openssl from pkgsrc),
192	delete /etc/openssl/certs and rerun postinstall or just
193	`certctl rehash'.
194
195	Otherwise, certctl(8) will think someone else has left
196	/etc/openssl/certs in the way and will avoid clobbering it on
197	upgrade from older NetBSD.
198
19920230718:
200	build.sh will use mk.conf in the same directory as build.sh instead
201	of /etc/mk.conf, unless MAKECONF is already defined in the environment.
202
20320230714:
204	Import of gcc 10.5 requires a clean build of at least tools/gcc
205	and external/gpl3/gcc* object directories. An update build
206	without cleaning will result in obscure failures in rare corner
207	cases.
208
20920230604:
210	Building native kernels with the installed make(1) instead of
211	the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland
212	has not been updated. Note that this is an unsupported build
213	configuration (but usually works if userland is -current enough).
214
21520230523:
216	ctfmerge was fixed as macOS host tool. This may require a clean tools
217	rebuild to detect the update to tools/compat/configure.
218
21920230515:
220	New openssl build requires removal of the crypto/external/bsd/openssl
221	and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierarchy.
222	Otherwise test results may be wrong due to wrong "golden" output
223	files being installed.
224
22520230322:
226	Fixes for moved /lib/libisns* mean that builds will complain about
227	./usr/lib/libisns* being missing until src/lib/libisns is forced
228	to (re)install the files, including the symlinks.  The simplest
229	way is to clean this subdir before building.
230
23120230112:
232	New binutils require an updated ld.elf_so. If you are doing
233	(unsupported) in-place self builds (with the -E flag to build.sh),
234	make sure to have installed latest ld.elf_so before you rebuild
235	userland.
236
23720221116:
238	The addition to NetBSD's version of UFS2 of support for extended
239	attributes broke backward compatibility with previous releases
240	of NetBSD, so UFS2 has been restored to being compatible with
241	previous NetBSD releases by disabling extended attributes.
242	(Note that ACLs are implemented as extended attributes, so
243	this changes disables ACLs as well.)
244
245	Support for UFS2 with extended attributes is now available in a new
246	UFS variant called UFS2ea.  If you have created extended attributes
247	in an original UFS2 file system then "fsck -p" will now fail due to
248	the unexpected presence of extended attributes and "fsck -y" will
249	remove all extended attributes.  If you wish to preserve extended
250	attributes rather than delete them, there is a utility to convert
251	a UFS2 file system to UFS2ea and leave extended attributes in place,
252	but this should be used with caution since it will preserve any
253	extended attributes that have been corrupted by the backward
254	incompatibility too.
255
256	If you wish to use a UFS2ea file system as your root file system,
257	then you will need to update your boot loader to a version that
258	supports UFS2ea.
259
260	For more information, see:
261	https://wiki.netbsd.org/features/UFS2ea
262
26320221111:
264	The new libdrm import worsened the conflict issues for the
265	kdump/ktruss ioctl, and i915 now conflicts with base, and has
266	been turned off.  This will cause update build issues like:
267
268		kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP'
269		   undeclared here (not in a function);
270		   did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'?
271
272	You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue.
273
27420220921:
275	Since the kernel version was bumped to 9.99.100, the bootloader
276	must be updated on x86 or EFI boot platforms in order to load
277	modules from boot.cfg(5) or interactively at the bootloader
278	prompt.
279
280	The kernel can still load modules at runtime, with modload(8)
281	or modules.conf(5), with no bootloader update.  This will not
282	affect release branches because it only applies to patch
283	numbers >=100.
284
285	On x86 (i386 or amd64) with BIOS boot, this requires copying a
286	new /usr/mdec/boot to /boot.  You can build this in the destdir
287	by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
288	sys/arch/i386/stand.
289
290	On platforms with EFI boot (including x86 with EFI boot), this
291	requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/
292	directory on the EFI system partition.  The boot*.efi file is:
293
294	aarch64	bootaa64.efi
295	amd64	bootx64.efi
296	arm	bootarm.efi	(32-bit arm)
297	i386	bootx32.efi
298
299	You can build this in the destdir by running
300	`$TOOLDIR/bin/nbmake-$ARCH dependall install' in
301	sys/stand/efiboot/boot*.
302
30320220821:
304	Support for building extsrc/ has been deprecated.
305	EXTSRCSRCDIR and MKEXTSRC have been deprecated.
306
30720220714:
308	Updates to xorg-server and associated drivers may cause builds to
309	fail.  Cleaning both DESTDIR and the xorg build tree may be needed.
310
31120220628:
312	Changes in the build of src/games/robots require a clean build
313	of that program.
314
31520211116:
316	Changes in the xorg build require clean obj dirs for external/mit/xorg
317	(or a full clean/non-update build).
318
31920211112:
320	Device tree sources were updated for evbarm.  Some device nodes
321	(in particular, ld(4) devices on the ROCKPro64) will be renumbered.
322
32320211014:
324	MKPIE default for aarch64 has changed, a clean build is required.
325
32620210917:
327	Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
328	ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
329	and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
330
33120210711:
332	Updated GMP sources may require cleaning in tools/gmp and/or in
333	external/lgpl3/gmp/lib, particularly if GCC itself does not build.
334
33520210417:
336	GCC 10 was enabled for several platforms.  If builds fail in either
337	tools/gcc or external/gpl3/gcc, first try cleaning those objects and
338	removing the $DESTDIR/usr/include/g++ subdirectory.
339
34020201016:
341	MIPS kernel modules have been disabled until they work.  This will
342	turn up in extra files in the DESTDIR, which should be cleaned.
343
34420200925:
345	GNU MPC and MPFR have been updated.  At least MPFR needs cleaning
346	in both the tools and external dirs.
347
34820200912:
349	GCC 9 has arrived for Arm and x86 platforms, and will be coming
350	for several more, as will binutils 2.34.  Clean as required.
351
35220200907:
353	GCC 9 is coming, and binutils has been updated for MIPS.  This
354	probably requires cleaning the tools/binutils.
355
35620200811:
357	GCC updates may require cleaning the objdir.  This may occur
358	due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
359	GCC 9 upgrade.
360
36120200614:
362	blacklist* has been renamed to blocklist*. postinstall(8)
363	should handle the migration.
364
36520200601:
366	Due to a mistake in LIBISPRIVATE handling, .so libraries were
367	created in the build directories and need cleaning.
368
36920200311:
370	GCC 8 ports will need cleaning in src/tools/gcc and
371	src/external/gpl3/gcc due to GCC 8.4 update.
372
37320191118:
374	More architectures were switched to gcc8:
375	    i386, ia64 powerpc64, sparc, sparc64, arm
376	The same comments as in 20191022 apply.
377
37820191112:
379	The LLVM update requires a clean rebuild for all architectures using
380	LLVM during the tools build phase (i386, amd64, aarch64).
381
38220191022:
383	Ports amd64 and aarch64 switched to GCC 8.3 by default.
384	In-place ("expert mode", build.sh -E) builds are not supported
385	when going from a GCC 7 userland to GCC 8. Do a regular
386	build to a different DESTDIR (or preferably: build.sh -U) at least
387	once and install sets, or download comp.{tar.xz,tgz} from the
388	daily builds and install that before doing the next in-place build.
389
39020191001:
391	GCC 8.3 was imported.  Builds of src/tools/gcc may fail if
392	old builds with GCC 7 output now uses GCC 8.  Clean this
393	directory, and also clean src/external/gpl3/gcc.
394
39520190903:
396	Files with names that coincide with existing files' names on
397	case-insensitive file systems were inadvertently committed, for
398	radeon GPU firmware.  We cannot mark these as obsolete for
399	postinstall to fix, so if you updated src since 2019-08-26, and
400	ran build.sh distribution or ran build.sh release, you must
401	manually delete the following files in your DESTDIR (which is
402	usually $OBJDIR/destir.$ARCH), or from / if you have installed
403	them:
404
405		/libdata/firmware/radeon/bonaire_ce.bin
406		/libdata/firmware/radeon/bonaire_mc.bin
407		/libdata/firmware/radeon/bonaire_me.bin
408		/libdata/firmware/radeon/bonaire_mec.bin
409		/libdata/firmware/radeon/bonaire_pfp.bin
410		/libdata/firmware/radeon/bonaire_rlc.bin
411		/libdata/firmware/radeon/bonaire_sdma.bin
412		/libdata/firmware/radeon/bonaire_smc.bin
413		/libdata/firmware/radeon/bonaire_uvd.bin
414		/libdata/firmware/radeon/hainan_ce.bin
415		/libdata/firmware/radeon/hainan_mc.bin
416		/libdata/firmware/radeon/hainan_me.bin
417		/libdata/firmware/radeon/hainan_pfp.bin
418		/libdata/firmware/radeon/hainan_rlc.bin
419		/libdata/firmware/radeon/hainan_smc.bin
420		/libdata/firmware/radeon/hawaii_ce.bin
421		/libdata/firmware/radeon/hawaii_mc.bin
422		/libdata/firmware/radeon/hawaii_me.bin
423		/libdata/firmware/radeon/hawaii_mec.bin
424		/libdata/firmware/radeon/hawaii_pfp.bin
425		/libdata/firmware/radeon/hawaii_rlc.bin
426		/libdata/firmware/radeon/hawaii_sdma.bin
427		/libdata/firmware/radeon/hawaii_smc.bin
428		/libdata/firmware/radeon/kabini_ce.bin
429		/libdata/firmware/radeon/kabini_me.bin
430		/libdata/firmware/radeon/kabini_mec.bin
431		/libdata/firmware/radeon/kabini_pfp.bin
432		/libdata/firmware/radeon/kabini_rlc.bin
433		/libdata/firmware/radeon/kabini_sdma.bin
434		/libdata/firmware/radeon/kaveri_ce.bin
435		/libdata/firmware/radeon/kaveri_me.bin
436		/libdata/firmware/radeon/kaveri_mec.bin
437		/libdata/firmware/radeon/kaveri_mec2.bin
438		/libdata/firmware/radeon/kaveri_pfp.bin
439		/libdata/firmware/radeon/kaveri_rlc.bin
440		/libdata/firmware/radeon/kaveri_sdma.bin
441		/libdata/firmware/radeon/mullins_ce.bin
442		/libdata/firmware/radeon/mullins_me.bin
443		/libdata/firmware/radeon/mullins_mec.bin
444		/libdata/firmware/radeon/mullins_pfp.bin
445		/libdata/firmware/radeon/mullins_rlc.bin
446		/libdata/firmware/radeon/mullins_sdma.bin
447		/libdata/firmware/radeon/oland_ce.bin
448		/libdata/firmware/radeon/oland_mc.bin
449		/libdata/firmware/radeon/oland_me.bin
450		/libdata/firmware/radeon/oland_pfp.bin
451		/libdata/firmware/radeon/oland_rlc.bin
452		/libdata/firmware/radeon/oland_smc.bin
453		/libdata/firmware/radeon/pitcairn_ce.bin
454		/libdata/firmware/radeon/pitcairn_mc.bin
455		/libdata/firmware/radeon/pitcairn_me.bin
456		/libdata/firmware/radeon/pitcairn_pfp.bin
457		/libdata/firmware/radeon/pitcairn_rlc.bin
458		/libdata/firmware/radeon/pitcairn_smc.bin
459		/libdata/firmware/radeon/tahiti_ce.bin
460		/libdata/firmware/radeon/tahiti_mc.bin
461		/libdata/firmware/radeon/tahiti_me.bin
462		/libdata/firmware/radeon/tahiti_pfp.bin
463		/libdata/firmware/radeon/tahiti_rlc.bin
464		/libdata/firmware/radeon/tahiti_smc.bin
465		/libdata/firmware/radeon/verde_ce.bin
466		/libdata/firmware/radeon/verde_mc.bin
467		/libdata/firmware/radeon/verde_me.bin
468		/libdata/firmware/radeon/verde_pfp.bin
469		/libdata/firmware/radeon/verde_rlc.bin
470		/libdata/firmware/radeon/verde_smc.bin
471
472	We will re-import these radeon firmware images another way
473	later.
474
47520190727:
476	The uefi bootloader has gained tftp support and needs a clean
477	build. If you do update builds, manually clean its object
478	directory by something like:
479	cd sys/arch/i386/stand/efiboot && make clean
480
48120190723:
482	The jemalloc allocator in libc is now built without extended
483	debugging (for performance reasons). In update builds make sure
484	to rebuild it completely, by removing all affected object files,
485	including compat builds, something like:
486	cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
487
48820190207:
489	GCC 7 switched for many ports.  Update builds are likely to fail.
490
491Hints for a more successful build:
492^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
493    Use build.sh, but do not use its "expert mode":
494	This will automatically build the tools in the
495	   correct order, and it will keep the tools and the
496	   new build products from interfering with the running
497	   system.  This will allow you to ignore most of the
498	   other advice in this file.
499    Build a new kernel first:
500	This makes sure that any new system calls or features
501	   expected by the new userland will be present.  This
502	   helps to avoid critical errors when upgrading.
503    Use object directories:
504	This helps to keep stale object
505	   files from polluting the build if a Makefile "forgets"
506	   about one.  It also makes it easier to clean up after
507	   a build.  It's also necessary if you want to use the
508	   same source tree for multiple machines.
509	   To use object directories with build.sh:
510	    a) invoke build.sh with the "-M" or "-O" options.
511	   To use object directories without using build.sh:
512	    a) cd /usr/src ; make cleandir
513	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
514	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
515	    d) cd /usr/src ; make build
516	   Note that running "make obj" in a directory will create
517	   in obj.$MACHINE directory.
518    Build to a DESTDIR:
519	This helps to keep old installed files (especially libraries)
520	   from interfering with the new build.
521	   To build to a DESTDIR with build.sh, use the "-D" option.
522	   To build to a DESTDIR without using build.sh, set the DESTDIR
523	   environment variable before running make build.  It should be
524	   set to the pathname of an initially empty directory.
525	   Problems: if you do not use build.sh, you might need to
526		update critical utilities without using DESTDIR since
527		nothing is executed from what is installed in DESTDIR.
528		(See critical utils, below.)
529    Build often:
530	This keeps critical utilities current enough to not choke
531	on any other part of the source tree that depends on up to
532	date functionality.  If you use build.sh, you should not have
533	this problem.
534
535What to do if things don't work:
536^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
537When things don't work there are usually a few things that commonly
538should be done.
539    1)	make includes
540	This should be done automatically by make build.
541    2)  cd share/mk && make install
542	Again, automatically done by make build.
543
544Failsafe rebuild of a small part of the tree:
545^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
546To make sure you rebuild something correctly you want to do
547something like the following:
548    1)  Make sure the includes and .mk files are up to date.
549    2)  Make sure any program used to build the particular
550	utility is up to date.  (yacc, lex, etc...)
551    3)  cd ...path/to/util...
552	make cleandir
553	rm ...all obj directories...
554	make cleandir			# yes, again
555	make obj
556	make depend && make
557
558Failsafe rebuild of the entire tree:
559^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
560If you really want to make sure the source tree is clean and
561ready for a build try the following.  Note that sourcing /etc/mk.conf
562(a make(1) Makefile) in this manner is not right, and will not work
563for anyone who uses any make(1) features in /etc/mk.conf.
564
565---cut here---
566#!/bin/sh
567. /etc/mk.conf
568
569if [ -z $NETBSDSRCDIR ] ; then
570    NETBSDSRCDIR=/usr/src
571fi
572if [ \! -d $NETBSDSRCDIR ] ; then
573    echo Unable to find sources
574    exit 1
575fi
576find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
577
578if [ -z $BSDOBJDIR ] ; then
579    BSDOBJDIR=/usr/obj
580fi
581if [ -d $BSDOBJDIR ] ; then
582    rm -rf $BSDOBJDIR
583fi
584
585cd $NETBSDSRCDIR && make cleandir
586
587---cut here---
588
589Critical utilities:
590^^^^^^^^^^^^^^^^^^^
591	usr.bin/make
592	usr.bin/yacc
593	usr.bin/lex
594	usr.bin/xlint
595	usr.bin/config
596
597Other problems and possible solutions:
598^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
599Symptom:Complaints involving a Makefile.
600Fix:	Rebuild usr.bin/make:
601	cd usr.bin/make && make && make install
602	Or, a failsafe method if that doesn't work:
603	cd usr.bin/make && cc -DMAKE_NATIVE *.c -I. -o make \
604	&& install make /usr/bin
605
606Fix:	Make sure .mk files are up to date.
607	cd share/mk && make install
608
609Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
610Fix:	Rebuild usr.bin/config
611
612Symptom:Obsolete intermediate files are used during compilation
613Fix:	Try the following sequence of commands in the directory in question.
614	make cleandir; rm `make print-objdir`; make cleandir; make obj
615	(If you built the tree without "make obj" in the past, obsolete files
616	may remain.  The command tries to clean everything up)
617
618Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
619	pointer type
620Fix:	Rebuild and install usr.bin/menuc
621
622Symptom:mklocale not found during build in share/locale/ctype
623Fix:	Build and install usr.bin/mklocale
624
625Symptom:undefined reference to `__assert13' or `__unsetenv13'
626Fix:    Rebuild and install lib/libc
627
628Symptom:usr.bin/config fails to build.
629Fix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
630
631Symptom:undefined reference to `getprogname' or `setprogname'
632Fix:    Rebuild and install lib/libc
633
634Symptom:Update build fails in src/tools/gcc complaining that a variable
635	(e.g. CPPFLAGS) has changed since the previous run.
636Fix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
637
638Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
639	No such file or directory.
640Cause:	If a directory is created by mistake, then it is sometimes
641	deleted from the CVS repository using administrative commands
642	that bypass the normal cvs access controls.  If your cvs working tree
643	contains references to a directory that has been deleted on the
644	server in this way, then "cvs update" reports this error.
645Fix:	Recursively delete the affected directory from your working tree
646	and try the update again.
647