UPDATING revision 1.275
1$NetBSD: UPDATING,v 1.275 2016/10/14 16:39:05 spz 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
2220161014:
23	a new version of OpenSSL has been imported.
24	Remove the files from obj (crypto/external/bsd/openssl) 
25	if you build.sh -u
26
2720161009:
28	a new version of dhcpcd has been imported with slightly changed
29	build infrastructure. When doing a build.sh -u this requires
30	pruning the external/bsd/dhcpcd objdir.
31
3220160914:
33	i386, amd64, shark, ofppc and macppc have joined shark and x68k
34	ports in using xorg-server 1.18. This requires a clean destdir
35	and a clean objdir.
36
3720160527:
38	i386 needs a full cleandir or objdir deletion because PIE has
39	been enabled. (see the amd64 entry two down for further info)
40
4120160418:
42	libedit needs manual removal of all autogenerated files since
43	some of them are not autogenerated anymore. Remember that there
44	might be two copies of libedit if your platform builds "compat".
45
4620160410:
47	amd64 needs full "make cleandir" or deletion of objdir now that
48	PIE has been enabled for amd64.  PIE, or position-independent
49	executables, means all code, including executables and not just
50	shared libraries, is position-independent and hence able to be
51	relocated by ASLR, address space layout randomization.
52
53	The change was made in Makefile variables for compiler and
54	linker flags, for which make(1) does not record dependencies,
55	hence it is unable to detect that all .o files need rebuilding.
56
57	Partial rebuilds with some modified source files will likely
58	fail when linking executables, since the linker refuses to mix
59	position-independent code with position-dependent code in
60	position-independent executables:
61
62		.../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC
63
6420160401:
65	Ports switching to GCC 5.3 will need a full "make cleandir".
66	Some people have found that cleandir is not sufficient, so if
67	in doubt delete the entire object directory tree for gcc.
68
6920160306:
70	NetBSD's regexp implementation is now part of libnbcompat.
71	Nblex, nbm4, nbpax, nbsed use it and they may crash on
72	non-NetBSD hosts if linked with stale object files produced
73	while they included a non-NetBSD regex.h.
74	In any case, you should "make cleandir" at least these tools
75	before updating your toolchain.
76
7720160125:
78	Dtrace has been enabled by default on some architectures.
79	When doing an update build, make sure to clean the etc/mtree
80	object directory before starting the build - otherwise the
81	needed directories in destdir will not be created.
82	An easy way to do this is:
83	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
84
8520150818:
86	New acpica requires "make cleandir" in src/external/bsd/acpica
87	again.
88
8920150413:
90	New acpica requires "make cleandir" and reinstalling yacc
91	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
92	also "make cleandir" in /usr/src/external/bsd/acpica.
93
9420150404:
95	Lint changes require a full rebuild of the tool, so make
96	sure to build without -u option to build.sh, or manually
97	do a make cleandir in src/tools/lint1 and
98	src/usr.bin/xlint.
99
10020150310:
101	Improvements to openssl for arm mean that update builds of
102	the openssl libraries will fail. A make cleandir in
103	external/bsd/openssl/lib is needed
104
10520141026:
106	A mishap during the import of pppd may cause your corruption
107	in your cvs directory if you happened to do a cvs update
108	during a short period of time. To fix, just remove the
109	directory src/external/bsd/ppp/dist/pppd completely
110	and let cvs restore it on next update.
111
11220140721:
113	The src/external/mit/lua/src directory was accidentally created
114	and then deleted in the CVS repository.  If you get errors like
115
116	cvs [update aborted]: cannot open directory
117	/cvsroot/src/external/mit/lua/src: No such file or directory
118
119	then delete your local copy of that directory tree and try again.
120
12120140530:
122	ARM eABI switched to DWARF based exception handling. This requires
123	rebuilding all C++ code. It is strongly advised to do a clean build.
124
12520140131:
126	The new compiler_rt/libc integration moved a few things. It is strongly
127	advised to do a clean build. At least lib/libc, the compat version(s)
128	of libc, libkern, rump and the kernels need to be cleaned.
129
13020131227:
131	1. The new ntpd runs in a restricted mode to prevent amplification
132	   attacks. If you need ntpdc to work you need to explicitly enable
133	   mode7 in your config file. Make sure you put the necessary restrict
134	   statements to avoid being exposed.
135	2. strncat has moved from lib/libc to common/lib/libc; you might need
136	   to make clean in libc
137
13820131129:
139	The GMP sources were updated, and builds will likely fail without
140	cleaning their build trees for both tools and in-tree, like below.
141
14220131128:
143	The MPC and MPFR sources were updated, and builds may require their
144	tools and in-tree directories cleaned for successful updates.
145
14620130605:
147	The kernel option FAST_IPSEC no longer exists, it's been renamed
148	to IPSEC (and the older IPSEC version removed).
149
15020130605:
151	Previous freetype installations eroneously installed private
152	header files. If you are building against a non-empty $DESTDIR,
153	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
154
15520130531:
156	The xdm update may cause build failure due to xdm.man being
157	in the obj tree.  Make sure to ensure any like this:
158		nbmake: nbmake: don't know how to make xdm.man. Stop
159	is fixed by deleting the xdm.man in the obj tree.
160
16120130530:
162	Updates of many xsrc packages will leave old .pc files around.
163	Best to clean out the xsrc objdir entirely before rebuilds.
164
16520130301:
166	The removal of netiso requires manual removal of /usr/include/netiso
167	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
168
16920120726:
170	The update of OpenSSL requires cleaning both the OpenSSL build
171	directory and DESTDIR.  *Even non-update builds require cleaning
172	DESTDIR.* Builds done without taking these steps may fail, or in
173	some cases may succeed and install broken OpenSSL libraries that
174	cause third-party software to link incorrectly and/or crash.
175
17620120507:
177	The database schema for makemandb was changed.  You will
178	need to update the database using 'makemandb -f' or wait
179	for the next weekly run to fix it.
180
18120120319:
182	sys/conf/Makefile.kern.inc has been modified to adjust the
183	size of db_symtab automatically.  You need to update dbsym in
184	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
185	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
186	mk.conf.
187
18820120216:
189	Default for MKCATPAGES changed to NO.  Update builds will fail
190	unless DESTDIR is cleaned manually.  If you built between 20120207
191	and 20120216, daily and weekly could have created an unreadable
192	/var/db/man.db index for apropos.  Running makemandb -f or
193	the next run of weekly will fix it.
194
19520111227:
196	If you built between 20111225 and 20111227 you need to remove
197	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
198	bump has been reverted.
199
20020111125:
201	The "rnd" pseudodevice has been added to sys/conf/std, which
202	means it should no longer be explicitly listed in kernel
203	configuration files.  The line "pseudo-device rnd" should be
204	removed from any custom kernel config files users may have.
205
20620111119:
207	A problem with the datastructures used by the rndctl(8)
208	utility (pointers in datastructures in an array, making 32->64
209	bit compatibility very painful) has been fixed in a
210	non-backwards-compatible way.  If you replace your kernel,
211	replace your rndctl executable too.
212
21320111001:
214	the prop_*_send_syscall() functions from proplib(3) have been
215	changed and their new version is not backward compatible with the old
216	one.  So ensure that all consumers of these functions (currently:
217	quota2 code and its tests) are updated together with the new lib.
218
21920110817:
220	sparc has been changed to use GCC 4.5.3, so any objdir or
221	DESTDIR for them should be deleted before updating.
222
22320110806:
224	i386 and amd64 have been changed to use GCC 4.5.3, so any
225	objdir or DESTDIR for them should be deleted before updating.
226
22720110805:
228	The update to GCC 4.5.3 requires a non-trivial portion of
229	the tree to be cleaned.  Best to delete both objdir and
230	DESTDIR before running this update.  So far, only the
231	sparc64, mips and powerpc platforms have changed.
232
23320110803:
234	The layout of external/public-domain/xz has changed.  To do an
235	update build you will have to remove the contents of the OBJDIR
236	for external/public-domain/xz/bin by hand as the xz entry there
237	is now a directory.
238
23920110410:
240	The configuration of src/tools/gcc has changed.  To do an
241	update build you have to clean both tools/binutils and
242	tools/gcc by hand.
243
24420110328:
245	Building the Xorg binary was moved into a subdirectory to fix
246	ordering issues with "make all".  It may be necessary to remove
247	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
248	if your update build fails, as the "Xorg" entry there is now a
249	directory.
250
25120110121:
252	Assembler files no longer use -traditional-cpp.  This can break
253	the build of individual parts of the tree.  This is handled
254	correctly by build.sh.  Manual builds have to update /usr/share/mk
255	and re-run config(1) for any kernel configurations as needed.
256
25720101217:
258	The tcpdump(8) program was changed to drop privileges and chroot(2)
259	by default.  It may be necessary to manually update passwd(5) and
260	group(5) in order to make the program work with existing setups.
261
26220101125:
263	The latest changes to setenv(3) dissallow setting environment
264	variables with names that contain '='.  Revision 1.18 of env.c
265	assumed that this was allowed.  Installing a new libc with an
266	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
267	break which affects the autoconf tests for dependency finding,
268	so building gcc will end up printing:
269	    checking dependency style of gcc... none
270	    configure: error: no usable dependency style found
271	Fix it by rebuilding and re-installing env.
272
27320101119:
274	Recent Xorg updates in xsrc/external/mit/ may cause various build
275	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
276	have any build problems with xsrc, or problems with mismatched
277	versions between xorg-server and drivers.
278
27920100604:
280	The update of ATF to 0.9 causes old tests written in shell to fail
281	unless they are rebuilt.  If you are building with MKUPDATE=yes,
282	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
283	trees by hand.
284
28520100522:
286	Recent Xorg updates in xsrc/external/mit/ will cause various build
287	problems.  Delete your entire DESTDIR and OBJDIR if you have any
288	build problems with xsrc.
289
29020100522:
291	private section of <ctype.h> was splitted, and now mklocale(1)
292	include ctype_local.h, so you have to make cleandir in tools/mklocale.
293
29420100520:
295	The location of the xkb compiled descriptions has changed.  Please
296	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
297
29820100222:
299	The shared objects file extension has been changed from .so to
300	.pico, in order to avoid conflicts with shared libraries names
301	libXX.so.  All now stale regular .so files can be removed from
302	your object directories.
303
30420100204:
305	The termcap database has been removed from the sources,
306	but has not been marked obsolete so it is not removed
307	from the system when upgrading.
308	As such, you will need to remove them from your object
309	and destination directories.
310
31120091101:
312        After updating, it may be necessary to make the 'cleandir'
313        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
314        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
315        src/tools/lex/ and src/usr.bin/lex/.
316
31720091001:
318	On amd64 you must rebuild tools (to get the new binutils)
319	before building a kernel, or the build fails on cpufunc.S.
320
32120091001:
322	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
323	symlink, failing the build.  Delete the link, and the subdir
324	it is in, and retry your build.
325
32620090718:
327	libc build changed so that strchr() provides the extra entry
328	point for index().  Update build of libc.a (and libc_pic.a)
329	may fail because the archive contains the unwanted index.o.
330	(Similarly for strrchr() and rindex().)
331
33220090709:
333	Native Xorg was upgraded again.  Builds will probably fail again
334	without a clean objdir, at least for src/external/mit/xorg.
335
33620090616:
337	Native Xorg was upgraded.  Builds will need a clean objdir for
338	src/external/mit/xorg.  Upgrading a system from sets will not
339	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
340	subdirectory has been changed into a file, and this needs to
341	be manually "rm -r"'ed before installing xbase.tgz.
342
34320090501:
344	Several new functions were added to string.h/libc, and this
345	can cause autoconf problems during the tool build for people
346	who fail to clean out their tools objects properly.  If you
347	note messages about stpcpy, stpncpy or strnlen accompanying a
348	failure during the tool build, clean out all your tools
349	objects and start again.
350
35120090325:
352	The i386 port was switched to i486 default toolchain.  This requires
353	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
354
35520090126:
356	The __posix_fadvise50 system call changed assembly stub type.  You
357	need to 'rm -f __posix_fadvise50.*' in the libc build directory
358	to avoid using the old assembly stub.
359
36020090202:
361	pkg_install now depends on the pkgdb cache for automatic conflict
362	detection.  It is recommented to rebuild the cache with
363	``pkg_admin rebuild''.
364
36520090110:
366	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
367	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
368	   This is needed even in the MODULAR kernel because there is
369	   conditionally compiled code in rtsock.c.
370	2. make sure build.sh completes and the binaries in a chroot work
371	   before installing.
372	3. If you don't use build.sh and you build directly to root, and
373	   your build breaks in the middle, don't despair.  Make sure headers
374	   are installed properly, and start building libraries first libc
375	   and libutil, install them and then continue building all the
376	   libraries in src/lib and src/gnu/lib and install them.  Once
377	   the new libraries are installed, you can restart the build.
378	4. If you compile packages and you notice link time warnings,
379	   rebuild the required packages to update their shared libraries.
380	   Any package you rebuild will require rebuilding all the packages
381	   that depend on it.
382	5. Next time you run pwd_mkdb with the new binary, the file
383	   will be upgraded and it will not be backwards compatible.
384	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
385	   lastlogx(5)) have been versioned, and there is a heuristic
386	   for utmp.  You are better off removing the old files after
387	   upgrading.  The automated clearing of /var/run during
388	   boot, and the automated rotating of files in /var/log by
389	   newsyslog(8), may mean that you do not have to remove the
390	   files manually.
391	7. The optional accounting file (/var/account/acct, see
392	   accton(8)) has not been versioned, and will need to be
393	   removed.  The automatic rotation of the accounting file by
394	   /etc/daily limits the bad consequences of failure to remove
395	   the file.
396	8. Application software that writes time_t to binary files on
397	   disk will break or need attention.  Most notably: if you are
398	   using PostgreSQL < 8.4, you need to dump your databases,
399	   rebuild PostgreSQL with the new time_t, then restore.
400
40120081219:
402	config(1) has been updated, and one of the files it creates -
403	swapnetbsd.o - has changed format.  You need to rebuild config
404	(done automatically by build.sh) and then you need to rerun
405	config on all kernel configuration files before rebuilding those
406	kernels.
407
40820081205:
409	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
410	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
411	set and will appear as extra files for MKX11=no update builds.
412
41320081122:
414	On i386, various kernel options(4) in GENERIC including
415	file systems have been disabled and moved into kernel modules.
416	Before trying a new GENERIC kernel, you have to prepare the
417	following files as well as a new GENERIC kernel:
418
419	- build and install kernel modules from src/sys/modules
420
421	- install the latest bootloader, which will load a module
422	  for the file system from which the kernel is loaded automatically
423
424	If you have to load your kernel from a file system which is not of
425	the same type as the root file system, you have to load the necessary
426	file system module manually on the boot prompt or in the boot.cfg file.
427
42820080827:
429	If you built and installed a libc from sources between
430	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
431	which results in false errors reported by lint(1).
432	Since this breaks the libc build itself, manual help is
433	needed -- lint must be disabled temporarily, e.g.:
434	  $ (cd lib/libc && make MKLINT=no dependall install)
435
43620080813:
437	MKDEBUG build was broken because the .depend files did not know
438	about .go files.  You need to remove all .depend files and rebuild.
439
44020080802:
441	A regression in binary compatibility for pthread_mutex_t has
442	been fixed.  Unfortunately, the price is breaking compatibility
443	for -current.
444
445	Threaded programs (using libpthread) and C++ programs (using
446	libstdc++) compiled after 20070907 and before 20080802 need to
447	be recompiled.
448
449	One way to find affected pkgsrc packages:
450
451	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
452	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
453
45420080731:
455	WAPBL (metadata journaling support) has been added, but at this
456	time isn't backwards compatible with pre-WAPBL aware kernels
457	and userland (fsck_ffs in particular).  Please make sure you
458	don't use a journaled filesystem with an older kernel/userland,
459	especially an uncleanly mounted journaled filesystem.  WAPBL
460	also requires the super block to be in the UFS2 format.  You
461	can use fsck_ffs -c 4 to update the superblock format.
462
46320080721:
464	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
465	isn't defined.
466
46720080531:
468	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
469	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
470	utility needs to be rebuilt and reinstalled as older binaries
471	won't work correctly.  The following sequence of commands:
472
473	  $ (cd sys/sys/ && nbmake-$arch includes)
474	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
475	  $ (cd sbin/drvctl/ && nbmake-$arch all)
476
477	leaves new drvctl utility in sbin/drvctl build directory.
478
47920080503:
480	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
481
48220080521:
483	For a while, unprivileged UPDATE builds would fail to
484	succeed at the checkflist stage, complaining that
485	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
486	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
487	If you already hit this problem, update the .mk file,
488	remove ${DESTDIR}/stand/<arch>, and re-run the build.
489
49020080303:
491	Linker warnings are now fatal if $WARNS>0.
492
49320080126:
494	The posix_fadvise system call has been changed from an assembly
495	stub, to a c file that calls an assembly stub.  You need to
496	'rm -f posix_fadvise.* .depend' in the libc build directory to
497	avoid using the old assembly stub.
498
49920071209:
500	The acpiec(4) driver has been split into two attachments.  If you
501	get ACPI errors before the attachment, please update your kernel
502	configuration file appropriately or see GENERIC for more details.
503
50420071115:
505	The it(4) driver has been renamed to itesio(4) and the old port
506	argument specified in the kernel configuration file is not valid
507	anymore.  The itesio(4) driver now uses the Super I/O address port
508	rather than the EC address port.  Please update your kernel
509	configuration file appropriately or see GENERIC for more details.
510
51120071028:
512	The pccons(4) driver has been removed from the NetBSD/shark port.
513	You need to update any custom kernel configuration file you have
514	to remove any references to pccons (which includes removing the
515	now useless XSERVER option) and replace them with the correct
516	entries for the wscons driver.  See the GENERIC configuration file
517	for more details.
518
51920070913:
520	A latent bug in dhclient/dhcpd that caused it to be unable to
521	enumerate interfaces was fixed.  The bug began to cause
522	problems after 20070911 when the kernel's SIOCGIFCONF
523	implementation was repaired.  From 20070529 to 20070911 racoon
524	could not enumerate interfaces.  (These are noted because
525	normal kernel/userspace version matching hygiene is not
526	sufficient to avoid this problem.)  Ensure that both kernel
527	and userland are from after 20070913.
528
52920070703:
530	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
531	calls the target-specific strip program, and the logic to pass
532	down STRIP from make has been removed.  This requires a
533	re-installation of tools.
534
53520070422:
536	The way OS emulations lookup filenames inside the emulation root
537	has been changed.  Rather than modify the pathname (and copy back
538	to userspace) namei() and lookup() directly check the emulation
539	root.  One side effect is that absolute symlinks inside the emulated
540	root file system will be relative to that file system - unless they
541	start /../ this is useful when the emulated root is a real install
542	that has such links.
543	This might affect symlinks that have been added to reference outside
544	the emulated root.
545
54620070412:
547	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
548	instead.  See the GENERIC32_IP3x kernel configuration for an
549	example.
550
55120070319:
552        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
553        on many platforms due to incorrect flags settings.  If you
554        updated and built after about 20070315, do "nbmake-$arch
555	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
556	rebuild of object files that might have been built
557	incorrectly, and ensure that you have at least
558	src/lib/libc/Makefile 1.130.
559
56020070210:
561        src/sys/sys/{sa.h,savar.h} were removed.
562          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
563              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
564        will allow dependencies on those files to get get rebuilt
565
56620070209:
567        The threading model was changed when the newlock2 branch
568        was merged to NetBSD-current.  If you boot with a new
569        kernel (version 4.99.10), then you also need a new pthread
570        library (/usr/lib/libpthread.so.0.7).  If you boot with
571        an old kernel, then you need the old pthread library
572        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
573        the pthread library in sync, old threaded applications should
574        continue to work with an old or new kernel.  Note that named(8)
575	is the only threaded application in the base system.
576
57720061214:
578	Following the move of string_to_flags() and flags_to_string()
579	from the bin/ls/ sources to libutil, users doing UPDATE builds
580	will need to do a "make cleandir" in
581		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
582		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
583		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
584		as the installation images in distrib/
585	in order to excise stale references to the old stat_flags.h header
586	file in the ls sources -- stat_flags.h has been removed.
587
58820061108:
589	The configure script used in the src/tools/gcc compiler has been
590	changed to indicate that our libc has ssp support built-in and
591	does not depend on -lssp and -lssp-nonshared.  You'll need to
592	make clean in src/tools/gcc first to rebuild the compiler.
593
59420061009:
595	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
596	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
597
59820060814:
599	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
600	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
601	kernel configuration for an example.  X servers from the last
602	few years should cope.
603
60420060703:
605	MPACPI is no more.  We always configure PCI interrupts using ACPI
606	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
607	to ACPI_SCANPCI.  Thanks to work from fvdl.
608
60920060627:
610	socket(2) has changed, and its system call has been versioned.
611	For userlands with the old version of socket(2), make sure that
612	your kernel has 'options COMPAT_30' set, or else 'bad system call'
613	errors will result.
614
615Hints for a more successful build:
616^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
617    Use build.sh, but do not use its "expert mode":
618	This will automatically build the tools in the
619	   correct order, and it will keep the tools and the
620	   new build products from interfering with the running
621	   system.  This will allow you to ignore most of the
622	   other advice in this file.
623    Build a new kernel first:
624	This makes sure that any new system calls or features
625	   expected by the new userland will be present.  This
626	   helps to avoid critical errors when upgrading.
627    Use object directories:
628	This helps to keep stale object
629	   files from polluting the build if a Makefile "forgets"
630	   about one.  It also makes it easier to clean up after
631	   a build.  It's also necessary if you want to use the
632	   same source tree for multiple machines.
633	   To use object directories with build.sh:
634	    a) invoke build.sh with the "-M" or "-O" options.
635	   To use object directories without using build.sh:
636	    a) cd /usr/src ; make cleandir
637	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
638	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
639	    d) cd /usr/src ; make build
640	   Note that running "make obj" in a directory will create
641	   in obj.$MACHINE directory.
642    Build to a DESTDIR:
643	This helps to keep old installed files (especially libraries)
644	   from interfering with the new build.
645	   To build to a DESTDIR with build.sh, use the "-D" option.
646	   To build to a DESTDIR without using build.sh, set the DESTDIR
647	   environment variable before running make build.  It should be
648	   set to the pathname of an initially empty directory.
649	   Problems: if you do not use build.sh, you might need to
650		update critical utilities without using DESTDIR since
651		nothing is executed from what is installed in DESTDIR.
652		(See critical utils, below.)
653    Build often:
654	This keeps critical utilities current enough to not choke
655	on any other part of the source tree that depends on up to
656	date functionality.  If you use build.sh, you should not have
657	this problem.
658
659What to do if things don't work:
660^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
661When things don't work there are usually a few things that commonly
662should be done.
663    1)	make includes
664	This should be done automatically by make build.
665    2)  cd share/mk && make install
666	Again, automatically done by make build.
667
668Failsafe rebuild of a small part of the tree:
669^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
670To make sure you rebuild something correctly you want to do
671something like the following:
672    1)  Make sure the includes and .mk files are up to date.
673    2)  Make sure any program used to build the particular
674	utility is up to date.  (yacc, lex, etc...)
675    3)  cd ...path/to/util...
676	make cleandir
677	rm ...all obj directories...
678	make cleandir			# yes, again
679	make obj
680	make depend && make
681
682Failsafe rebuild of the entire tree:
683^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
684If you really want to make sure the source tree is clean and
685ready for a build try the following.  Note that sourcing /etc/mk.conf
686(a make(1) Makefile) in this manner is not right, and will not work
687for anyone who uses any make(1) features in /etc/mk.conf.
688
689---cut here---
690#!/bin/sh
691. /etc/mk.conf
692
693if [ -z $NETBSDSRCDIR ] ; then
694    NETBSDSRCDIR=/usr/src
695fi
696if [ \! -d $NETBSDSRCDIR ] ; then
697    echo Unable to find sources
698    exit 1
699fi
700find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
701
702if [ -z $BSDOBJDIR ] ; then
703    BSDOBJDIR=/usr/obj
704fi
705if [ -d $BSDOBJDIR ] ; then
706    rm -rf $BSDOBJDIR
707fi
708
709cd $NETBSDSRCDIR && make cleandir
710
711---cut here---
712
713Critical utilities:
714^^^^^^^^^^^^^^^^^^^
715	usr.bin/compile_et
716	usr.bin/make
717	usr.bin/yacc
718	usr.bin/lex
719	usr.bin/xlint
720	usr.bin/config
721
722Other problems and possible solutions:
723^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
724Symptom:Complaints involving a Makefile.
725Fix:	Rebuild usr.bin/make:
726	cd usr.bin/make && make && make install
727	Or, a failsafe method if that doesn't work:
728	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
729
730Fix:	Make sure .mk files are up to date.
731	cd share/mk && make install
732
733Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
734Fix:	Rebuild usr.bin/config
735
736Symptom:
737Fix:	Rebuild usr.bin/yacc
738
739Symptom:
740Fix:	Rebuild usr.bin/lex
741
742Symptom:
743Fix:	rm /usr/lib/libbfd.a
744
745Symptom:Obsolete intermediate files are used during compilation
746Fix:	Try the following sequence of commands in the directory in question.
747	make cleandir; rm `make print-objdir`; make cleandir; make obj
748	(If you built the tree without "make obj" in the past, obsolete files
749	may remain.  The command tries to clean everything up)
750
751Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
752	pointer type
753Fix:	Rebuild and install usr.bin/menuc
754
755Symptom:mklocale not found during build in share/locale/ctype
756Fix:	Build and install usr.bin/mklocale
757
758Symptom:undefined reference to `__assert13' or `__unsetenv13'
759Fix:    Rebuild and install lib/libc
760
761Symptom:usr.bin/config fails to build.
762Fix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
763
764Symptom:undefined reference to `getprogname' or `setprogname'
765Fix:    Rebuild and install lib/libc
766
767Symptom:lint does not understand the '-X' option
768Fix:    May need to build & install libs with NOLINT=1 before rebuilding lint
769
770Symptom:Update build fails in src/tools/gcc complaining that a variable
771	(e.g. CPPFLAGS) has changed since the previous run.
772Fix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
773
774Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
775	No such file or directory.
776Cause:	If a directory is created by mistake, then it is sometimes
777	deleted from the CVS repository using administrative commands
778	that bypass the normal cvs access controls.  If your cvs working tree
779	contains references to a directory that has been deleted on the
780	server in this way, then "cvs update" reports this error.
781Fix:	Recursively delete the affected directory from your working tree
782	and try the update again.
783