UPDATING revision 1.151
11.151Srpaulo$NetBSD: UPDATING,v 1.151 2006/10/09 18:57:30 rpaulo Exp $
21.1Sabs
31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent
41.123Sjmcchanges that might cause problems in the build process, and a guide for
51.123Sjmcwhat to do if something doesn't work.
61.1Sabs
71.123SjmcFor a more detailed description of the recommended way to build NetBSD
81.123Sjmcusing build.sh, see the BUILDING file.
91.123Sjmc
101.123SjmcNote that much of the advice in this UPDATING file was written before
111.123Sjmcbuild.sh existed.  Nevertheless, the advice here may be useful for
121.123Sjmcworking around specific problems with build.sh.
131.123Sjmc
141.123SjmcSee also: BUILDING, build.sh, Makefile.
151.1Sabs
161.1SabsRecent changes:
171.1Sabs^^^^^^^^^^^^^^^
181.138Slukem
191.151Srpaulo20061009:
201.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
211.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
221.151Srpaulo
231.150Sbjh2120060814:
241.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
251.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
261.150Sbjh21	kernel configuration for an example.  X servers from the last
271.150Sbjh21	few years should cope.
281.150Sbjh21
291.149Schristos20060703:
301.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
311.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
321.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
331.149Schristos
341.148Sdogcow20060627:
351.148Sdogcow	socket(2) has changed, and its system call has been versioned.
361.148Sdogcow	For userlands with the old version of socket(2), make sure that
371.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
381.148Sdogcow	errors will result.
391.148Sdogcow
401.146Spavel20060526:
411.147Schristos	The kernel linker scripts for i386 and xen 
421.147Schristos	(sys/arch/i386/conf/kern.ldscript*) were changed to set the
431.146Spavel	load address correctly, for the benefit of MULTIBOOT boot loaders
441.146Spavel	(like Grub). If you use a linker (ld) older than from 2006/04/17, it
451.147Schristos	will be unable to link the kernel because of a bug and ld will fail
461.147Schristos	with an error like:
471.147Schristos	    ../../../../arch/i386/conf/kern.ldscript:45 \
481.147Schristos		non constant expression for load base
491.147Schristos	You need to update at least src/gnu/dist/binutils/ld and recompile
501.147Schristos	and install the linker. If using the build.sh script, the easiest
511.147Schristos	way is with a "build.sh tools" command, with any other options
521.147Schristos	that you use normally. When using build.sh, the linker binary is
531.147Schristos	installed as ${TOOLDIR}/bin/i386--netbsdelf-ld.
541.147Schristos
551.145Smartin20060131:
561.145Smartin	the protocol between the sparc64 bootloader (ofwboot) and
571.145Smartin	the kernel was changed. Before installing a new kernel,
581.145Smartin	you need to update ofwboot. After a full build, just copy
591.145Smartin	/usr/mdec/ofwboot to /, or do a rebuild of
601.145Smartin	src/sys/arch/sparc/stand/ofwboot and install the result to /.
611.145Smartin
621.144Syamt20050917:
631.144Syamt	arch/*/conf/std.* was changed to include conf/std, which
641.144Syamt	contains MI options previously enabled by default.
651.144Syamt	If you have kernel config files which doesn't include
661.144Syamt	arch/*/conf/std.*, you need to edit them to include conf/std
671.144Syamt	to get the previous configuration.
681.144Syamt
691.143Slukem20050830:
701.143Slukem	named.conf was moved from /etc/namedb to /etc.
711.143Slukem	postinstall(8) migrates this during interactive use.
721.143Slukem	Users of MKUPDATE=yes will need to manually rectify
731.143Slukem	this in their DESTDIR.
741.143Slukem
751.142Sdrochner20050825:
761.142Sdrochner	Some data structures in sys/device.h, related to interface
771.142Sdrochner	attributes and locator names, were changed. config(1) was
781.142Sdrochner	modified to emit the new data structures.
791.142Sdrochner	Thus usr.bin/config must be updated (and run on the kernel
801.142Sdrochner	configuration file) before a new kernel can be built.
811.142Sdrochner
821.139Schristos20050531:
831.141Saugustss	genassym.sh(8) was moved to genassym(1). You need to either build
841.141Saugustss	tools first or install the version of genassym from /usr/bin before
851.139Schristos	you can build a kernel again.
861.139Schristos
871.140Syamt20050520:
881.140Syamt	Because a kernfs bug which xentools relies on was fixed,
891.140Syamt	xentools up to xentools20-2.0.3nb4 won't work with new kernel.
901.140Syamt
911.138Slukem20050417:
921.138Slukem	postinstall(8) was moved from /etc to /usr/sbin and made part
931.138Slukem	of the "base" set, to make it easier to invoke after an
941.138Slukem	upgrade.
951.138Slukem
961.136Scube20050325:
971.136Scube	pcppi(4) was separated in two devices, adding attimer(4).  Be sure
981.136Scube	to add a config line for an attimer(4) device in your kernel
991.136Scube	configuration, or you won't be able to set the pitch of the beep
1001.137Scube	with wsconsctl.  Depending on the default value for the pitch, you
1011.137Scube	might even not hear any more beep.  Also, it is advised to attach both
1021.137Scube	devices the same way (i.e., both on isa or both on acpi) or the
1031.137Scube	pcppi(4) device may fail to find the attimer(4) one.
1041.136Scube
1051.135Sjmc20050211:
1061.135Sjmc	Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in
1071.135Sjmc	some of the cross tools to fail if they use configure. Some configure's
1081.135Sjmc	cache the environment passed in and notice the new environment is
1091.135Sjmc	different and abort. Doing a clean in tools/ should be enough to
1101.135Sjmc	make a build continue.
1111.135Sjmc
1121.134Schristos20050109:
1131.134Schristos	Since su is using pam by default now, make sure that you have
1141.134Schristos	/etc/pam.d populated (postinstall will do that automatically
1151.134Schristos	for you). Otherwise su will fail open (i.e. will not require
1161.134Schristos	a password).
1171.134Schristos
1181.133Schristos20041229:
1191.133Schristos	Make had a path resolution bug that manifested itself as not
1201.133Schristos	being able to install openpam.3. This bug has been fixed, but
1211.133Schristos	you might need to rebuild make manually first to get through
1221.133Schristos	the build.
1231.133Schristos
1241.130Schristos20041201:
1251.130Schristos	Userland programs have been changed to use /dev/bpf instead of
1261.130Schristos	/dev/bpfX. You need to create that device by installing a new
1271.131Swiz	MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]*
1281.99Smrg
1291.129Sjmc20041006:
1301.129Sjmc
1311.129Sjmc	A bug was introduced into /bin/sh (var.c rev 1.35) which causes
1321.129Sjmc	variables to not export correctly to subshells in all cases. This
1331.129Sjmc	will cause builds to break if that version of /bin/sh is installed
1341.129Sjmc	on the system. The proper version of /bin/sh can be verified with:
1351.129Sjmc
1361.129Sjmc        ident /bin/sh | grep var
1371.129Sjmc
1381.129Sjmc	Any /bin/sh w. version 1.35 will not work and needs to be updated
1391.129Sjmc	before attempting a build.
1401.129Sjmc	
1411.127Schristos20041001:
1421.127Schristos	The ipfilter kernel sources moved from sys/netinet to
1431.127Schristos	dist/sys/ipf/netinet. Due to the move some Makefile
1441.127Schristos	dependencies are now dangling requiring a make cleandir
1451.128She	before they work again (kdump, ktruss, rescue, ipf, and
1461.128She	ftp-proxy are the victims).
1471.127Schristos
1481.125Satatat20040715:
1491.125Satatat	The rc.d/sendmail script now uses a heuristic to determine
1501.125Satatat	if sendmail should be started at boot time.  It checks the
1511.125Satatat	contents of /etc/mailer.conf, /etc/mail/submit.cf, and the
1521.125Satatat	owner and mode of the sendmail binary to see if any changes
1531.125Satatat	to the mail infrastructure have been made.  If no changes
1541.125Satatat	are detected, it will start an SMTP listener.
1551.125Satatat
1561.125Satatat	Setting sendmail=NO in /etc/rc.conf will override this.
1571.125Satatat
1581.125Satatat	If you are only using sendmail by default and only for
1591.125Satatat	local delivery, it is important that you also update your
1601.125Satatat	sendmail.cf so that the SMTP listener only listens on the
1611.125Satatat	loopback interface.
1621.125Satatat
1631.125Satatat20040715:
1641.125Satatat	The method by which athhal-elf.o gets pulled into i386
1651.125Satatat	kernel builds has been changed again.  The latest version
1661.125Satatat	of bsd.files.mk is no longer required.
1671.125Satatat
1681.124Sjmc20040621:
1691.124Sjmc	Due to the recent rototill of tools/compat it's crucial one starts
1701.124Sjmc	from a clean objdir under tools/*.
1711.124Sjmc
1721.124Sjmc	This is mostly due to generated files (yacc and lex sources) needing
1731.125Satatat	to be generated with new rules from bsd.hostprog.mk.
1741.124Sjmc
1751.124Sjmc	The safest course is to rm -rf all objects under tools before building.
1761.124Sjmc
1771.121Slukem20040516:
1781.121Slukem	The end-user modifiable X11 configuration has been moved
1791.121Slukem	from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.
1801.121Slukem	Ensure that src and xsrc is up to date, and run
1811.121Slukem	"make cleandir" in src/x11 before your next build.
1821.121Slukem
1831.126Slukem	postinstall currently doesn't migrate the files from
1841.126Slukem	/usr/X11R6/lib/X11/* to /etc/X11/* although it does
1851.126Slukem	detect that this needs to occur, so you'll have to
1861.126Slukem	manually move these files yourself.
1871.126Slukem
1881.119Satatat20040426:
1891.119Satatat	Support for the original dynamic sysctl node structure has
1901.119Satatat	been removed in favor of the newer layout.  This affects
1911.119Satatat	consumers of the create and delete interface, as well as
1921.119Satatat	the dynamic discovery mechanism.  This is believed only to
1931.119Satatat	be the sysctl(8) binary itself, at this point in time, so
1941.119Satatat	the only effect of this should be that a sysctl binary
1951.119Satatat	built from sources dated between 2003/12/04 and 2004/03/24
1961.119Satatat	will not work on a kernel built from sources dated after
1971.119Satatat	2004/04/25.  If you need a new sysctl binary but build.sh
1981.119Satatat	does not work, make sure that your revision of
1991.120Satatat	src/sys/sys/sysctl.h is 1.112 (or later), and then the
2001.120Satatat	do the following:
2011.119Satatat
2021.120Satatat	cd /usr/src (or wherever your source tree is)
2031.120Satatat	make USETOOLS=no includes
2041.120Satatat	cd lib/libc
2051.120Satatat	make USETOOLS=no dependall install
2061.120Satatat	cd ../../sbin/sysctl
2071.119Satatat	make USETOOLS=no dependall install
2081.119Satatat
2091.122Sitojun	If you are using older sysctl binary, GNU autoconf would fail to
2101.122Sitojun	identify your machine architecture, and tries to build binary for
2111.122Sitojun	"unknown-unknown-netbsd20F" or something like that.  if that happens,
2121.122Sitojun	make sure to follow the above steps.
2131.122Sitojun
2141.118Sdbj20040425:
2151.118Sdbj	The ffs superblock issues listed below under 20040109 and 20030402
2161.118Sdbj	are now automatically addressed by the /etc/rc.d/fixsb script or by
2171.118Sdbj	sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4
2181.118Sdbj	invocation mentioned below will continue to work and is now
2191.118Sdbj	automated by those scripts.  Note that under certain circumstances,
2201.118Sdbj	affected filesystems upgraded to a -current kernel first before
2211.118Sdbj	upgrading their userland with the fixsb and fsck_ffs fixes may
2221.118Sdbj	encounter a 'freeing free inode' panic when writing to the affected
2231.118Sdbj	filesystem, so it is a good idea to repair the filesystem as soon as
2241.118Sdbj	possible.  For more details on the fixsb script, see pr install/25138.
2251.118Sdbj
2261.115Schristos20040418:
2271.121Slukem	statfs(2) and friends have been replaced with statvfs(2). Before
2281.115Schristos	installing a newly build userland make sure that you are running
2291.115Schristos	a newly built kernel with COMPAT_20 set. In addition your libc
2301.115Schristos	build might not work (undefined SYS_statfs symbol) because make
2311.115Schristos	clean does not know how to remove files it does not know about
2321.116Schristos	anymore. Manually remove all generated .S sources and objects
2331.116Schristos	from the libc build directory.
2341.115Schristos
2351.114Sjmc20040326:
2361.114Sjmc	The method by which athhal-elf.o gets pulled into i386 kernel builds
2371.117Sjmc	has been changed. The file is now stored as a uuencoded file in CVS
2381.114Sjmc	and the generated Makefile will use the new .uue rules from bsd.file.mk
2391.114Sjmc	to build it.
2401.114Sjmc
2411.114Sjmc	This means you must have the latest bsd.files.mk installed when
2421.114Sjmc	building a kernel without USETOOLS=yes.
2431.114Sjmc
2441.113Sdan20040318:
2451.113Sdan	A bug in the cgd(4) blowfish code was corrected, without
2461.113Sdan	provision of backwards compatibility, after several public
2471.113Sdan	notices over several months. Users of cgd with blowfish cipher
2481.113Sdan	ONLY must dump their data before updating their kernels, and
2491.113Sdan	recreate cgd's and restore data using the new kernel. See
2501.113Sdan	(recent message to current-users, URL when mail-index has updated)
2511.113Sdan
2521.108Sbjh2120040313:
2531.108Sbjh21	On acorn32, the opms and qms drivers have been withdrawn, and
2541.108Sbjh21	the old wsqms driver is now called qms.  Kernel config files
2551.108Sbjh21	will need updating.  See the ones in sys/arch/acorn32/conf
2561.108Sbjh21	for examples.
2571.108Sbjh21
2581.106Sbjh2120040125:
2591.106Sbjh21	On acorn32, the beep and sysbeep devices are no longer
2601.106Sbjh21	needed, and will need to be deleted from kernel configuration
2611.106Sbjh21	files.
2621.105Sbjh21
2631.102Sdbj20040109:
2641.102Sdbj	Compatibility for old ffs superblock layouts has been
2651.102Sdbj	added, and the restrictive fsck checks have been reenabled
2661.102Sdbj	when using those layouts.  If you have been using -current
2671.102Sdbj	since 20030402, you may find that fsck again signals fatal
2681.110Sdbj	superblock mismatches.  To repair, make sure you have
2691.111Ssimonb	an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4
2701.109Sdbj	to complete the filesystem upgrade.  A message has
2711.111Ssimonb	been added to the kernel which should detect this problem.
2721.111Ssimonb	See the following discussion for more information:
2731.112Skeihan	http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
2741.102Sdbj
2751.99Smrg20031203:
2761.100Skeihan	New binutils builds may fail due to old dependencies.
2771.99Smrg	It's necessary to "make cleandir" to ensure that
2781.99Smrg	the dependencies will be rebuilt correctly.
2791.98Swiz
2801.98Swiz20031111:
2811.98Swiz	A newer mkdep is needed.  Error noting that is
2821.98Swiz		cc: Ambiguous abbreviation --
2831.97Slukem
2841.97Slukem20031008:
2851.97Slukem	/usr/include/sys/disklabel_mbr.h was removed.
2861.97Slukem	It's necessary to "make cleandir" to ensure that
2871.97Slukem	the dependencies will be rebuilt correctly.
2881.96Schristos
2891.109Sdbj20031007:
2901.111Ssimonb	A sign exension bug was fixed which set all the high bits
2911.111Ssimonb	of our newly expanded ffs fs_flags.  This should only
2921.111Ssimonb	affect users who installed or upgraded in September of 2003.
2931.109Sdbj	A small utility program was posted to tech-kern which
2941.111Ssimonb	should fix this problem, and a warning message was added
2951.111Ssimonb	to the kernel which should discover and warn about it.  See
2961.111Ssimonb	http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html
2971.109Sdbj
2981.96Schristos20030906:
2991.96Schristos	With the addition of siginfo support the old signal trampoline
3001.96Schristos	code has been deprecated to COMPAT_16. Make sure that your running
3011.96Schristos	kernel has COMPAT_16 enabled before building userland.
3021.94Schristos
3031.94Schristos20030801:
3041.95Swiz	With the new openssl, there is some header and library shuffling.
3051.94Schristos	rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \
3061.95Swiz	/usr/lib/libdes* before building.
3071.92Swiz
3081.92Swiz20030703:
3091.92Swiz	Texinfo was updated to 4.6.  To avoid failures when trying to
3101.92Swiz	build the included texinfo files, do:
3111.92Swiz
3121.92Swiz	cd src/gnu/usr.bin/texinfo
3131.92Swiz	make MKINFO=no dependall install
3141.90Swiz
3151.90Swiz20030630:
3161.101Sjunyoung	Groff was updated to 1.19; it's probably necessary to do
3171.91Swiz		cd share/mk && make install
3181.90Swiz		cd src/gnu/usr.bin/groff
3191.90Swiz		make MKMAN=no dependall install
3201.90Swiz	(untested).
3211.89Schristos
3221.89Schristos20030516:
3231.89Schristos	Due to bugs in the export handling code, invalid export lines
3241.89Schristos	were accepted before and caused the kernel to panic when
3251.89Schristos	mountd got restarted because it freed memory that had already
3261.89Schristos	been freed. This has been fixed and the kernel checks
3271.89Schristos	export addresses very strictly. If you upgrade your kernel,
3281.89Schristos	make sure you also upgrade mountd, because if your export
3291.89Schristos	file contains lines with an old inet4 address syntax (i.e.
3301.89Schristos	a.b.c or a.b or a), they will get rejected by the new kernel.
3311.87Sbjh21
3321.87Sbjh2120030402:
3331.87Sbjh21	The superblock layout for FFS was changed.  If you have 1.6
3341.87Sbjh21	fsck binaries, they will signal a fatal superblock mismatch
3351.87Sbjh21	with the first alternate, because they compare too many
3361.87Sbjh21	fields (even ones that aren't useful).  If possible, upgrade
3371.87Sbjh21	your fsck_ffs binary before using a new kernel.
3381.87Sbjh21	None of this signals actual filesystem damage.
3391.85Satatat
3401.85Satatat20030324:
3411.85Satatat	sendmail version 8.12.8 was imported.  Since sendmail is
3421.85Satatat	now setgid to the smmsp group, and runs in "collection"
3431.85Satatat	mode for most common activities, there is a new config
3441.85Satatat	file called submit.cf that needs to live in /etc/mail.
3451.85Satatat	The generic submit.cf sample in /usr/share/sendmail/cf
3461.85Satatat	is named netbsd-msp.cf.  Upgrading your regular sendmail
3471.85Satatat	configuration file is also strongly advised.
3481.85Satatat
3491.85Satatat	See the section named "MESSAGE SUBMISSION PROGRAM" in
3501.85Satatat	the updated /usr/share/sendmail/README file for more
3511.85Satatat	information.
3521.82Swiz
3531.82Swiz20030117:
3541.82Swiz	Texinfo was updated to 4.3.  To avoid failures when trying to
3551.82Swiz	build the included texinfo files, do:
3561.82Swiz
3571.82Swiz	cd src/gnu/usr.bin/texinfo
3581.82Swiz	make MKINFO=no dependall install
3591.81Slukem
3601.81Slukem20021223:
3611.81Slukem	The METALOG format changed slightly, to remove the leading
3621.81Slukem	"${DESTDIR}" from path names.
3631.81Slukem	This only affects people building with UNPRIVED.
3641.81Slukem	For complete safety, remove the DESTDIR entirely and
3651.81Slukem	update tools/mtree, before running make build.
3661.88Sitojun
3671.88Sitojun20021219:
3681.88Sitojun	CVS repository layout was changed.  See the following for details
3691.88Sitojun	if you are using (anonymous) cvs to update your tree.
3701.88Sitojun
3711.93Ssalo	http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html
3721.80Slukem
3731.80Slukem20021219:
3741.80Slukem	install(1) had a '-N dbdir' option added, to specify an
3751.80Slukem	alternate location to look up users & groups (instead
3761.80Slukem	of the host system passwd(5) and group(5) databases).
3771.80Slukem
3781.80Slukem	The build system was modified to take advantage of
3791.80Slukem	this option (using ${NETBSDSRCDIR}/etc), so if you
3801.83Skei	use USETOOLS==no, you may have to rebuild and
3811.80Slukem	reinstall usr.bin/xinstall first.
3821.78Slukem
3831.78Slukem20021130:
3841.78Slukem	fparseln(3) moved from libutil to libc.
3851.78Slukem	If building to DESTDIR=/, reinstall the includes
3861.78Slukem	and rebuild libc:
3871.78Slukem		make includes
3881.78Slukem		make do-lib-libc
3891.78Slukem	If using build.sh, "cd tools/compat && make clean"
3901.78Slukem	before rebuilding the tools.
3911.77Slukem
3921.77Slukem20021126:
3931.77Slukem	The mk.conf(5) variable SYS_INCLUDE has been deprecated,
3941.77Slukem	including the optional "SYS_INCLUDE=symlinks" support.
3951.77Slukem	All header files, including <sys/*.h> are copied into
3961.77Slukem	/usr/include.
3971.76Sthorpej
3981.76Sthorpej20021121:
3991.76Sthorpej	The C run-time support files crtbegin.o and crtend.o
4001.76Sthorpej	(and their companions crtbeginS.o and crtendS.o) were
4011.76Sthorpej	split up, with new crti.o and crtn.o files resulting.
4021.76Sthorpej	This means that libtool needs to be rebuilt once the
4031.76Sthorpej	new libraries are installed.  The process of rebuilding
4041.76Sthorpej	libtool will cause it to automatically notice the new
4051.76Sthorpej	required files, but it *must* be rebuilt in order to
4061.76Sthorpej	do this.
4071.76Sthorpej
4081.76Sthorpej	An out-of-date libtool will result in shared libraries
4091.76Sthorpej	which lack _init() and _fini() routines, which means that
4101.76Sthorpej	their global contructors/destructors will not be invoked.
4111.75Sthorpej
4121.75Sthorpej20021121:
4131.75Sthorpej	A bug related to how ARM ELF objects were tagged has been
4141.75Sthorpej	corrected.
4151.75Sthorpej
4161.75Sthorpej	NetBSD ARM ELF uses the soft-VFP floating point model by
4171.75Sthorpej	default.  However, the assembler lacked support for marking
4181.75Sthorpej	objects as using the VFP floating point format, and the
4191.79Swiz	compiler was not properly passing the flag indicating "soft-VFP"
4201.75Sthorpej	to the assembler.
4211.75Sthorpej
4221.75Sthorpej	Unfortunately, this means that the linker will now consider
4231.75Sthorpej	old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be
4241.75Sthorpej	incompatible with new (properly marked) objects.
4251.75Sthorpej
4261.75Sthorpej	The problem will only manifest itself if you attempt to compile
4271.75Sthorpej	a new program using the fixed toolchain, and link that program
4281.75Sthorpej	against old libraries which do not have the proper "softvfp"
4291.75Sthorpej	markings.  ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES
4301.75Sthorpej	WILL CONTINUE TO WORK PROPERLY.
4311.75Sthorpej
4321.75Sthorpej	The only work-around for the problem is to recompile all of
4331.75Sthorpej	the libraries on the system.  The easiest way to do this for
4341.79Swiz	system libraries is to install a binary snapshot; they are
4351.93Ssalo	generally available on releng.NetBSD.org.  Any packages you
4361.75Sthorpej	have installed which supply libraries will have to be recompiled
4371.75Sthorpej	if you wish to link new programs against those libraries.
4381.75Sthorpej
4391.75Sthorpej	If you have questions about this matter, please contact
4401.93Ssalo	port-arm@NetBSD.org.
4411.73Sprovos
4421.73Sprovos20021011:
4431.73Sprovos	Systrace has been improved to support privilege elevation.
4441.73Sprovos	Updating the kernel requires the userland part of systrace
4451.79Swiz	to be rebuilt.
4461.72Sthorpej
4471.72Sthorpej20021010:
4481.72Sthorpej	The config(8) grammar was changed to allow options to register
4491.72Sthorpej	dependencies on attributes, as well as other options.  Users
4501.72Sthorpej	must update and reinstall usr.sbin/config before building a new
4511.72Sthorpej	kernel.
4521.70Sthorpej
4531.70Sthorpej20021009:
4541.70Sthorpej	A new attribute dependency syntax was introduced to config(8),
4551.70Sthorpej	which is now used by the SCSI configuration description.  Users
4561.71Swiz	must update and reinstall usr.sbin/config before building a new
4571.70Sthorpej	kernel.
4581.69Sthorpej
4591.69Sthorpej20021003:
4601.69Sthorpej	Several changes have been made to the autoconfiguration
4611.69Sthorpej	framework.  Users must update and reinstall usr.sbin/config
4621.69Sthorpej	before building a new kernel.
4631.74Sjschauma
4641.74Sjschauma20021001:
4651.74Sjschauma	The i386mp branch has been merged.  To compile a kernel, users
4661.74Sjschauma	will need to add the option 'cpu* at mainbus?' to their configuration
4671.74Sjschauma	file.  Multiprocessor kernels will need
4681.74Sjschauma	ioapic*		at mainbus? apid ?
4691.74Sjschauma	options		MULTIPROCESSOR
4701.74Sjschauma	options		COM_MPLOCK
4711.68Slukem
4721.68Slukem20020922:
4731.68Slukem	MKDYNAMICROOT=yes enabled by default, which means that
4741.68Slukem	certain shared libraries are installed into /lib, the shared
4751.68Slukem	linker is installed into /libexec, and all programs in /bin
4761.68Slukem	and /sbin are dynamically linked.
4771.68Slukem	If you do not use "make build", you should ensure that
4781.68Slukem	you have the libraries and shared linker in the new locations,
4791.68Slukem	with:
4801.68Slukem		make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so
4811.67Slukem
4821.67Slukem20020917:
4831.67Slukem	USE_NEW_TOOLCHAIN has been replaced with:
4841.67Slukem	    -	TOOLCHAIN_MISSING -- set to "yes" on platforms for which
4851.67Slukem		there is no working in-tree toolchain (hppa, ns32k, sh5,
4861.67Slukem		x86_64).
4871.67Slukem	    -	EXTERNAL_TOOLCHAIN -- if defined by the user, points to the
4881.79Swiz		root of an external toolchain (e.g. /usr/local/gnu).  This
4891.67Slukem		enables the cross-build framework even for TOOLCHAIN_MISSING
4901.67Slukem		platforms.
4911.66Sgehenna
4921.66Sgehenna20020906:
4931.66Sgehenna	gehenna-devsw has been merged into the trunk. Need to update and
4941.79Swiz	reinstall usr.sbin/config before building the kernel.
4951.65Slukem
4961.65Slukem20020822:
4971.65Slukem	Crunched rescue tools (contents of /bin and /sbin, plus others)
4981.65Slukem	are now provided in /rescue.
4991.65Slukem
5001.65Slukem	To ensure that these are built statically linked (no matter
5011.65Slukem	what the setting of LDSTATIC is), use a crunchgen(1) built
5021.65Slukem	from sources newer than 20020820 (see the next entry).
5031.65Slukem
5041.65Slukem20020820:
5051.65Slukem	crunchgen(1) changed to ensure that the generated program
5061.65Slukem	is statically linked.
5071.65Slukem
5081.65Slukem	Solution: update and reinstall usr.bin/crunch
5091.84Sgrant
5101.84Sgrant20020605:
5111.84Sgrant	smmsp user/group has been added for sendmail.
5121.84Sgrant
5131.84Sgrant	Add the following into /etc/group:
5141.84Sgrant
5151.84Sgrant	smmsp:*:17:
5161.84Sgrant
5171.84Sgrant	and the following to /etc/master.passwd (via vipw):
5181.84Sgrant
5191.84Sgrant	smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin
5201.61Sitojun
5211.61Sitojun20020515:
5221.61Sitojun	sshd user/group has been added.  Need to hand add this in, or sshd
5231.61Sitojun	will not let you log in (with default, or UsePrivlegeSeparation=yes)
5241.61Sitojun
5251.61Sitojun	Add the following into /etc/group:
5261.61Sitojun
5271.61Sitojun	sshd:*:16:
5281.61Sitojun
5291.61Sitojun	and the following to /etc/master.passwd (via vipw):
5301.61Sitojun
5311.63Senami	sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin
5321.61Sitojun	
5331.79Swiz	Also /var/chroot/sshd directory needs to be present (digged as part of
5341.79Swiz	the build process).
5351.60Ssommerfe
5361.60Ssommerfe20020426:
5371.60Ssommerfe	NBUILDJOBS obsoleted in favor of just using -j.
5381.59Slukem
5391.59Slukem20020426:
5401.59Slukem	etc/postinstall added, which performs various checks for 
5411.59Slukem	configuration file updates and changes, and can fix most of
5421.59Slukem	the problems identified.
5431.59Slukem	This should make it much easier to upgrade a system's
5441.59Slukem	configuration from earlier systems (as far back as NetBSD 1.5).
5451.56Slukem
5461.56Slukem20020320:
5471.79Swiz	<bsd.lib.mk> needs a new install(1) for its "-a cmd" support.
5481.79Swiz	Build and install at usr.bin/xinstall before the build.
5491.56Slukem
5501.55Sitojun20020319:
5511.79Swiz	Raw IPv6 socket now makes strict checking for sa_family and sa_len
5521.79Swiz	on send(2) operation.  Be sure to have sbin/rtsol and usr.sbin/rtsold
5531.55Sitojun	newer than November 2001 when you upgrade the kernel.
5541.55Sitojun
5551.54Sitojun20020311:
5561.54Sitojun	ssh configuration files were moved from /etc to /etc/ssh.  Beware
5571.54Sitojun	if you restart your machine from remote.  Note that sshd.conf needs
5581.54Sitojun	to be changed (due to the use of "/etc" inside).
5591.54Sitojun
5601.54Sitojun20020223:
5611.53Smatt	Users of the VAX port will need to rebuild and install gas
5621.53Smatt	so it deal with the now present register prefix used in all
5631.53Smatt	the VAX assembly files.
5641.53Smatt
5651.50Sitojun20020118:
5661.50Sitojun	ntpd user/group has been added.  Need to hand add this in or builds
5671.50Sitojun	will break as mtree aborts early.
5681.50Sitojun
5691.50Sitojun	Add the following into /etc/group:
5701.50Sitojun
5711.50Sitojun	ntpd:*:15:
5721.50Sitojun
5731.50Sitojun	and the following to /etc/master.passwd (via vipw):
5741.50Sitojun
5751.50Sitojun	ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin
5761.50Sitojun
5771.49Sjmc20011207:
5781.49Sjmc	If you're attempting to build a snapshot on sparc64 and are getting
5791.49Sjmc	reloc errors from the toolchain groff binary this means your native
5801.49Sjmc	toolchain has some broken C++ bits.
5811.49Sjmc
5821.49Sjmc	To fix:
5831.49Sjmc
5841.49Sjmc	Build a new toolchain (i.e. build.sh -t)
5851.49Sjmc	Use the new toolchain to build and install natively (i.e. /usr/lib)
5861.49Sjmc
5871.49Sjmc	gnu/lib/libgcc
5881.51Spooka	gnu/lib/libstdc++
5891.49Sjmc
5901.49Sjmc	After this a snapshot will be able to be built.
5911.49Sjmc
5921.47Sjmc20011201:
5931.47Sjmc	In order for a sparc64 build to work you must have a working awk. If
5941.47Sjmc	you've built and installed a system with the new toolchain up to this
5951.52Swiz	point you do not have a working awk as its ability to do floating
5961.47Sjmc	point is broken. 
5971.47Sjmc
5981.47Sjmc	To build:
5991.47Sjmc
6001.47Sjmc	remake and install gnu/lib/libgcc
6011.47Sjmc	remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links
6021.48Sjmc	against the new libgcc.a)
6031.47Sjmc
6041.46Sthorpej20011128:
6051.46Sthorpej	Kernel config information was changed to use defflag in
6061.46Sthorpej	the various "files" files.  Bug fixes to config(8) are
6071.46Sthorpej	required in order for this to work properly.  Make sure
6081.46Sthorpej	to build and install in usr.sbin/config before attempting
6091.46Sthorpej	to build a new kernel.
6101.46Sthorpej
6111.45Syamt20011030:
6121.45Syamt	libc/locale/wcstod.c now needs new lint(1). Update lint(1)
6131.45Syamt	before building libc.
6141.43Smason
6151.44Stv20011029:
6161.44Stv	The new document BUILDING.mdoc (view with nroff | more, or
6171.44Stv	see pre-generated .txt and .html versions) describes the build
6181.44Stv	procedure in great detail.  BUILDING, and the USE_NEW_TOOLCHAIN
6191.44Stv	build process, are intended in the long run to replace this
6201.44Stv	manual update log.
6211.44Stv
6221.44Stv	Users building a USE_NEW_TOOLCHAIN system should read the
6231.44Stv	BUILDING document for caveats.  Generally, BUILDING supersedes
6241.44Stv	UPDATING for these systems, as tool updating is taken care of
6251.44Stv	by the new build system.
6261.42Sperry
6271.42Sperry20011028:
6281.42Sperry	src/etc/Makefile now needs install to be able to handle
6291.42Sperry	symlinks that point to nowhere. A bug in install that
6301.42Sperry	prevented this was corrected.
6311.42Sperry
6321.42Sperry	Solution: update and reinstall usr.bin/xinstall
6331.42Sperry	Better Solution: Use the new toolchain and it will just work
6341.42Sperry	for you.
6351.40Slukem
6361.40Slukem20011006:
6371.40Slukem	/etc/mtree/NetBSD.dist has been updated to take advantage of
6381.40Slukem	absolute path support added to mtree(8). Older mtree(8)s don't
6391.40Slukem	understand the format.
6401.40Slukem
6411.40Slukem	Solution: update and reinstall usr.sbin/mtree
6421.39Sjmc
6431.39Sjmc20011004:
6441.39Sjmc	Crunchgen has been updated to work via reach-over makefiles. Updating
6451.39Sjmc	is suggested before running a snapshot build
6461.36Stv
6471.35Sthorpej20010915:
6481.35Sthorpej	The new "ubcperf" code committed by Chuck Silvers removed
6491.35Sthorpej	a header file, uvm/uvm_vnode.h.  There may be stale .depend
6501.35Sthorpej	files that still reference this file.
6511.35Sthorpej
6521.35Sthorpej	Solution: "make cleandir && make dependall" in affected
6531.35Sthorpej	directories.
6541.31Senami
6551.31Senami20010803:
6561.31Senami	grep.info is now built from grep.texi using makeinfo.  Since it
6571.31Senami	requires makeinfo v4.0, you need to install new texinfo before
6581.31Senami	building gnu/usr.bin/grep.  To install new texinfo, please follow
6591.31Senami	the instruction described in 20010726 entry.
6601.30Senami
6611.64Ssommerfe20010803: 
6621.41Swiz	(i386 only): i386 kernel now uses new instructions like
6631.111Ssimonb	`fxsave' which old gas doesn't understand.  To build the
6641.64Ssommerfe	kernel successfully, you need to build and install a new toolchain, 
6651.64Ssommerfe	(i.e., build.sh -t) or 	(temporarily) comment out "options I686_CPU" 
6661.64Ssommerfe	from your kernel configuration until you rebuild your userland.
6671.64Ssommerfe	See 20011029 above and BUILDING file in this directory for more information.
6681.64Ssommerfe	[updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled]
6691.29Sbjh21
6701.29Sbjh2120010731:
6711.29Sbjh21	Bootloader update on ELF platforms.  DDB in kernels from before
6721.29Sbjh21	this will be unable to read symbol tables provided by newer
6731.29Sbjh21	bootloaders.
6741.27Sassar
6751.27Sassar20010726:
6761.27Sassar	Texinfo was updated to 4.0.  To avoid failures when trying to
6771.28Sassar	build the included texinfo files, do:
6781.28Sassar
6791.28Sassar	cd src/gnu/usr.bin/texinfo
6801.28Sassar	make MKINFO=no dependall install
6811.25Sthorpej
6821.25Sthorpej20010718:
6831.25Sthorpej	Enabled correct .init/.fini processing in crt0.  The way this
6841.25Sthorpej	was done was to change a -I directive to cc(1), which means
6851.25Sthorpej	make(1) will have a stale dependency (it will be checking the
6861.25Sthorpej	timestamp on the wrong "dot_init.h").
6871.25Sthorpej
6881.25Sthorpej	The symptom you will see is that new programs die with SIGSEGV
6891.25Sthorpej	if you have a stale dependency.
6901.25Sthorpej
6911.25Sthorpej	Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so
6921.25Sthorpej	before starting your build.
6931.26Sthorpej
6941.26Sthorpej20010628:
6951.26Sthorpej	A construct was added to uvm_page.h that uncovered a bug
6961.26Sthorpej	in lint(1).  If you get a warning/error about a non-portable
6971.26Sthorpej	bitfield, update your lint(1) before proceeding.
6981.21Sjmc
6991.21Sjmc20010226:
7001.22Sjmc	Added named user/group to system. Need to hand add this in or builds
7011.21Sjmc	will break as mtree aborts early.
7021.21Sjmc
7031.21Sjmc	To work around add by hand:
7041.21Sjmc
7051.21Sjmc	named:*:14:
7061.21Sjmc
7071.22Sjmc	to /etc/group and add:
7081.22Sjmc
7091.22Sjmc	named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin
7101.22Sjmc
7111.22Sjmc	to master.passwd (use vipw for instance if doing by hand).
7121.22Sjmc
7131.22Sjmc	Now a make build should progress.
7141.18Sjmc
7151.18Sjmc20010219:
7161.52Swiz	get/setprogname() added. Any hostprogs that may use this will need
7171.111Ssimonb	to be bootstrapped manually until the host system is current.
7181.18Sjmc
7191.111Ssimonb	Known problems: sys/arch/macppc/stand/fixcoff
7201.19Scgd			usr.sbin/config (adding -DMAKE_BOOTSTRAP to
7211.19Scgd			  CFLAGS and rebuilding should work)
7221.20Sjmc			usr.sbin/mdsetimage - Build a static copy if
7231.111Ssimonb			  building a snapshot before fully bootstrapped.
7241.15Schristos
7251.15Schristos20010204:
7261.15Schristos	prepare the code to compile with stricter gcc flags. in
7271.15Schristos	particular start eliminating redundant declarations. Yacc
7281.15Schristos	needs to be installed before make build.
7291.10Schristos
7301.10Schristos20010114:
7311.10Schristos	introduce .if commands(target) in make(1). You need to
7321.10Schristos	bring everything up-to-date first, then without installing
7331.23Stron	anything make and install in usr.bin/make, then proceed
7341.10Schristos	with make build.
7351.9Ssommerfe
7361.9Ssommerfe20010101:
7371.9Ssommerfe	bsd.subdir.mk committed 20001230 had a bug which caused
7381.9Ssommerfe	afterinstall targets to run too soon; update again.
7391.8Ssommerfe
7401.8Ssommerfe20001230:
7411.8Ssommerfe	New share/mk files needed to support .WAIT in SUBDIR variables.
7421.8Ssommerfe	If you get make errors, 
7431.8Ssommerfe		(cd share/mk; make install)
7441.8Ssommerfe	Also, PRINTOBJDIR has changed and is now used more heavily.
7451.6Sad
7461.6Sad20001019:
7471.7Sad	The `ca' device driver has been replaced by `ld'; although the
7481.6Sad	major and minor numbers haven't changed, you should update your /dev
7491.6Sad	directory.
7501.1Sabs
7511.4Sitojun20000929:
7521.4Sitojun	The following make directives are obsoleted.
7531.4Sitojun	MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 
7541.4Sitojun	By default, RSA is built into libcrypto.  IDEA and RC5 will not be
7551.16Swiz	built into libcrypto.  By using MKCRYPTO_{RC5,IDEA}, you can build
7561.4Sitojun	additional library libcrypto_{idea,rc5}.
7571.1Sabs
7581.1Sabs
7591.1SabsHints for a more successful build:
7601.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7611.123Sjmc    Use build.sh, but do not use its "expert mode":
7621.132Sjmmv	This will automatically build the tools in the
7631.123Sjmc	   correct order, and it will keep the tools and the
7641.123Sjmc	   new build products from interfering with the running
7651.123Sjmc	   system.  This will allow you to ignore most of the
7661.123Sjmc	   other advice in this file.
7671.2Smrg    Build a new kernel first:
7681.2Smrg	This makes sure that any new system calls or features
7691.2Smrg	   expected by the new userland will be present.  This
7701.2Smrg	   helps to avoid critical errors when upgrading.
7711.1Sabs    Use object directories:
7721.1Sabs	This helps to keep stale object
7731.1Sabs	   files from polluting the build if a Makefile "forgets"
7741.1Sabs	   about one.  It also makes it easier to clean up after
7751.1Sabs	   a build.  It's also necessary if you want to use the
7761.1Sabs	   same source tree for multiple machines.
7771.123Sjmc	   To use object directories with build.sh:
7781.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
7791.123Sjmc	   To use object directories without using build.sh:
7801.1Sabs	    a) cd /usr/src ; make cleandir
7811.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
7821.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
7831.1Sabs	    d) cd /usr/src ; make build
7841.2Smrg	   Note that running "make obj" in a directory will create
7851.2Smrg	   in obj.$MACHINE directory.
7861.1Sabs    Build to a DESTDIR:
7871.123Sjmc	This helps to keep old installed files (especially libraries)
7881.123Sjmc	   from interfering with the new build.
7891.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
7901.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
7911.123Sjmc	   environment variable before running make build.  It should be
7921.123Sjmc	   set to the pathname of an initially empty directory.
7931.123Sjmc	   Problems: if you do not use build.sh, you might need to
7941.123Sjmc		update critical utilities without using DESTDIR since
7951.123Sjmc		nothing is executed from what is installed in DESTDIR.
7961.123Sjmc		(See critical utils, below.)
7971.1Sabs    Build often:
7981.1Sabs	This keeps critical utilities current enough to not choke
7991.1Sabs	on any other part of the source tree that depends on up to
8001.123Sjmc	date functionality.  If you use build.sh, you should not have
8011.123Sjmc	this problem.
8021.1Sabs 
8031.1SabsWhat to do if things don't work:
8041.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8051.1SabsWhen things don't work there is usually a few things that commonly
8061.1Sabsshould be done.
8071.1Sabs    1)	make includes
8081.1Sabs	This should be done automatically by make build.
8091.1Sabs    2)  cd share/mk && make install
8101.1Sabs	Again, automatically done by make build.
8111.1Sabs
8121.1SabsFailsafe rebuild of a small part of the tree:
8131.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8141.1SabsTo make sure you rebuild something correctly you want to do
8151.1Sabssomething like the following:
8161.1Sabs    1)  Make sure the includes and .mk files are up to date.
8171.1Sabs    2)  Make sure any program used to build the particular
8181.1Sabs	utility is up to date.  (yacc, lex, etc...)
8191.1Sabs    3)  cd ...path/to/util...
8201.1Sabs	make cleandir
8211.1Sabs	rm ...all obj directories...
8221.1Sabs	make cleandir			# yes, again
8231.1Sabs	make obj
8241.1Sabs	make depend && make
8251.1Sabs
8261.1SabsFailsafe rebuild of the entire tree:
8271.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8281.1SabsIf you really want to make sure the source tree is clean and
8291.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
8301.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
8311.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
8321.1Sabs
8331.1Sabs---cut here---
8341.1Sabs#!/bin/sh
8351.1Sabs. /etc/mk.conf
8361.1Sabs
8371.58Slukemif [ -z $NETBSDSRCDIR ] ; then
8381.58Slukem    NETBSDSRCDIR=/usr/src
8391.1Sabsfi
8401.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
8411.1Sabs    echo Unable to find sources
8421.1Sabs    exit 1
8431.1Sabsfi
8441.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
8451.1Sabs
8461.1Sabsif [ -z $BSDOBJDIR ] ; then
8471.1Sabs    BSDOBJDIR=/usr/obj
8481.1Sabsfi
8491.1Sabsif [ -d $BSDOBJDIR ] ; then
8501.1Sabs    rm -rf $BSDOBJDIR
8511.1Sabsfi
8521.1Sabs
8531.58Slukemcd $NETBSDSRCDIR && make cleandir
8541.1Sabs
8551.1Sabs---cut here---
8561.1Sabs
8571.1SabsCritical utilities:
8581.1Sabs^^^^^^^^^^^^^^^^^^^
8591.3Sitojun	usr.bin/compile_et
8601.1Sabs	usr.bin/make
8611.1Sabs	usr.bin/yacc
8621.1Sabs	usr.bin/lex
8631.11Slukem	usr.bin/xlint
8641.142Sdrochner	usr.bin/config
8651.1Sabs
8661.34SsimonbOther problems and possible solutions:
8671.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8681.1SabsSymptom:Complaints involving a Makefile.
8691.17SerhFix:	Rebuild usr.bin/make:
8701.17Serh	cd usr.bin/make && make && make install
8711.111Ssimonb	Or, a failsafe method if that doesn't work:
8721.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
8731.17Serh
8741.1SabsFix:	Make sure .mk files are up to date.
8751.1Sabs	cd share/mk && make install
8761.2Smrg
8771.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
8781.142SdrochnerFix:	Rebuild usr.bin/config
8791.1Sabs
8801.1SabsSymptom:
8811.1SabsFix:	Rebuild usr.bin/yacc
8821.1Sabs
8831.1SabsSymptom:
8841.1SabsFix:	Rebuild usr.bin/lex
8851.1Sabs
8861.1SabsSymptom:
8871.1SabsFix:	rm /usr/lib/libbfd.a
8881.4Sitojun
8891.4SitojunSymptom:Obsolete intermediate files are used during compilation
8901.4SitojunFix:	Try the following sequence of commands in the directory in question.
8911.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
8921.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
8931.4Sitojun	may remain.  The command tries to clean everything up)
8941.5Swiz
8951.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
8961.5SwizFix:	Rebuild and install usr.bin/menuc
8971.12Sitojun
8981.12SitojunSymptom:mklocale not found during build in share/locale/ctype
8991.12SitojunFix:	Build and install usr.bin/mklocale
9001.13Sdogcow
9011.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9021.13SdogcowFix:    Rebuild and install lib/libc
9031.13Sdogcow
9041.142SdrochnerSymptom:usr.bin/config fails to build.
9051.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9061.13Sdogcow
9071.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9081.19ScgdFix:    Rebuild and install lib/libc
9091.24Sabs
9101.24SabsSymptom:lint does not understand the '-X' option
9111.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
912