UPDATING revision 1.152
11.152Schristos$NetBSD: UPDATING,v 1.152 2006/11/09 18:20:59 christos 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.152Schristos20061108:
201.152Schristos	The configure script used in the src/tools/gcc compiler has been
211.152Schristos	changed to indicate that our libc has ssp support built-in and
221.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
231.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
241.152Schristos
251.151Srpaulo20061009:
261.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
271.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
281.151Srpaulo
291.150Sbjh2120060814:
301.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
311.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
321.150Sbjh21	kernel configuration for an example.  X servers from the last
331.150Sbjh21	few years should cope.
341.150Sbjh21
351.149Schristos20060703:
361.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
371.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
381.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
391.149Schristos
401.148Sdogcow20060627:
411.148Sdogcow	socket(2) has changed, and its system call has been versioned.
421.148Sdogcow	For userlands with the old version of socket(2), make sure that
431.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
441.148Sdogcow	errors will result.
451.148Sdogcow
461.146Spavel20060526:
471.147Schristos	The kernel linker scripts for i386 and xen 
481.147Schristos	(sys/arch/i386/conf/kern.ldscript*) were changed to set the
491.146Spavel	load address correctly, for the benefit of MULTIBOOT boot loaders
501.146Spavel	(like Grub). If you use a linker (ld) older than from 2006/04/17, it
511.147Schristos	will be unable to link the kernel because of a bug and ld will fail
521.147Schristos	with an error like:
531.147Schristos	    ../../../../arch/i386/conf/kern.ldscript:45 \
541.147Schristos		non constant expression for load base
551.147Schristos	You need to update at least src/gnu/dist/binutils/ld and recompile
561.147Schristos	and install the linker. If using the build.sh script, the easiest
571.147Schristos	way is with a "build.sh tools" command, with any other options
581.147Schristos	that you use normally. When using build.sh, the linker binary is
591.147Schristos	installed as ${TOOLDIR}/bin/i386--netbsdelf-ld.
601.147Schristos
611.145Smartin20060131:
621.145Smartin	the protocol between the sparc64 bootloader (ofwboot) and
631.145Smartin	the kernel was changed. Before installing a new kernel,
641.145Smartin	you need to update ofwboot. After a full build, just copy
651.145Smartin	/usr/mdec/ofwboot to /, or do a rebuild of
661.145Smartin	src/sys/arch/sparc/stand/ofwboot and install the result to /.
671.145Smartin
681.144Syamt20050917:
691.144Syamt	arch/*/conf/std.* was changed to include conf/std, which
701.144Syamt	contains MI options previously enabled by default.
711.144Syamt	If you have kernel config files which doesn't include
721.144Syamt	arch/*/conf/std.*, you need to edit them to include conf/std
731.144Syamt	to get the previous configuration.
741.144Syamt
751.143Slukem20050830:
761.143Slukem	named.conf was moved from /etc/namedb to /etc.
771.143Slukem	postinstall(8) migrates this during interactive use.
781.143Slukem	Users of MKUPDATE=yes will need to manually rectify
791.143Slukem	this in their DESTDIR.
801.143Slukem
811.142Sdrochner20050825:
821.142Sdrochner	Some data structures in sys/device.h, related to interface
831.142Sdrochner	attributes and locator names, were changed. config(1) was
841.142Sdrochner	modified to emit the new data structures.
851.142Sdrochner	Thus usr.bin/config must be updated (and run on the kernel
861.142Sdrochner	configuration file) before a new kernel can be built.
871.142Sdrochner
881.139Schristos20050531:
891.141Saugustss	genassym.sh(8) was moved to genassym(1). You need to either build
901.141Saugustss	tools first or install the version of genassym from /usr/bin before
911.139Schristos	you can build a kernel again.
921.139Schristos
931.140Syamt20050520:
941.140Syamt	Because a kernfs bug which xentools relies on was fixed,
951.140Syamt	xentools up to xentools20-2.0.3nb4 won't work with new kernel.
961.140Syamt
971.138Slukem20050417:
981.138Slukem	postinstall(8) was moved from /etc to /usr/sbin and made part
991.138Slukem	of the "base" set, to make it easier to invoke after an
1001.138Slukem	upgrade.
1011.138Slukem
1021.136Scube20050325:
1031.136Scube	pcppi(4) was separated in two devices, adding attimer(4).  Be sure
1041.136Scube	to add a config line for an attimer(4) device in your kernel
1051.136Scube	configuration, or you won't be able to set the pitch of the beep
1061.137Scube	with wsconsctl.  Depending on the default value for the pitch, you
1071.137Scube	might even not hear any more beep.  Also, it is advised to attach both
1081.137Scube	devices the same way (i.e., both on isa or both on acpi) or the
1091.137Scube	pcppi(4) device may fail to find the attimer(4) one.
1101.136Scube
1111.135Sjmc20050211:
1121.135Sjmc	Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in
1131.135Sjmc	some of the cross tools to fail if they use configure. Some configure's
1141.135Sjmc	cache the environment passed in and notice the new environment is
1151.135Sjmc	different and abort. Doing a clean in tools/ should be enough to
1161.135Sjmc	make a build continue.
1171.135Sjmc
1181.134Schristos20050109:
1191.134Schristos	Since su is using pam by default now, make sure that you have
1201.134Schristos	/etc/pam.d populated (postinstall will do that automatically
1211.134Schristos	for you). Otherwise su will fail open (i.e. will not require
1221.134Schristos	a password).
1231.134Schristos
1241.133Schristos20041229:
1251.133Schristos	Make had a path resolution bug that manifested itself as not
1261.133Schristos	being able to install openpam.3. This bug has been fixed, but
1271.133Schristos	you might need to rebuild make manually first to get through
1281.133Schristos	the build.
1291.133Schristos
1301.130Schristos20041201:
1311.130Schristos	Userland programs have been changed to use /dev/bpf instead of
1321.130Schristos	/dev/bpfX. You need to create that device by installing a new
1331.131Swiz	MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]*
1341.99Smrg
1351.129Sjmc20041006:
1361.129Sjmc
1371.129Sjmc	A bug was introduced into /bin/sh (var.c rev 1.35) which causes
1381.129Sjmc	variables to not export correctly to subshells in all cases. This
1391.129Sjmc	will cause builds to break if that version of /bin/sh is installed
1401.129Sjmc	on the system. The proper version of /bin/sh can be verified with:
1411.129Sjmc
1421.129Sjmc        ident /bin/sh | grep var
1431.129Sjmc
1441.129Sjmc	Any /bin/sh w. version 1.35 will not work and needs to be updated
1451.129Sjmc	before attempting a build.
1461.129Sjmc	
1471.127Schristos20041001:
1481.127Schristos	The ipfilter kernel sources moved from sys/netinet to
1491.127Schristos	dist/sys/ipf/netinet. Due to the move some Makefile
1501.127Schristos	dependencies are now dangling requiring a make cleandir
1511.128She	before they work again (kdump, ktruss, rescue, ipf, and
1521.128She	ftp-proxy are the victims).
1531.127Schristos
1541.125Satatat20040715:
1551.125Satatat	The rc.d/sendmail script now uses a heuristic to determine
1561.125Satatat	if sendmail should be started at boot time.  It checks the
1571.125Satatat	contents of /etc/mailer.conf, /etc/mail/submit.cf, and the
1581.125Satatat	owner and mode of the sendmail binary to see if any changes
1591.125Satatat	to the mail infrastructure have been made.  If no changes
1601.125Satatat	are detected, it will start an SMTP listener.
1611.125Satatat
1621.125Satatat	Setting sendmail=NO in /etc/rc.conf will override this.
1631.125Satatat
1641.125Satatat	If you are only using sendmail by default and only for
1651.125Satatat	local delivery, it is important that you also update your
1661.125Satatat	sendmail.cf so that the SMTP listener only listens on the
1671.125Satatat	loopback interface.
1681.125Satatat
1691.125Satatat20040715:
1701.125Satatat	The method by which athhal-elf.o gets pulled into i386
1711.125Satatat	kernel builds has been changed again.  The latest version
1721.125Satatat	of bsd.files.mk is no longer required.
1731.125Satatat
1741.124Sjmc20040621:
1751.124Sjmc	Due to the recent rototill of tools/compat it's crucial one starts
1761.124Sjmc	from a clean objdir under tools/*.
1771.124Sjmc
1781.124Sjmc	This is mostly due to generated files (yacc and lex sources) needing
1791.125Satatat	to be generated with new rules from bsd.hostprog.mk.
1801.124Sjmc
1811.124Sjmc	The safest course is to rm -rf all objects under tools before building.
1821.124Sjmc
1831.121Slukem20040516:
1841.121Slukem	The end-user modifiable X11 configuration has been moved
1851.121Slukem	from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.
1861.121Slukem	Ensure that src and xsrc is up to date, and run
1871.121Slukem	"make cleandir" in src/x11 before your next build.
1881.121Slukem
1891.126Slukem	postinstall currently doesn't migrate the files from
1901.126Slukem	/usr/X11R6/lib/X11/* to /etc/X11/* although it does
1911.126Slukem	detect that this needs to occur, so you'll have to
1921.126Slukem	manually move these files yourself.
1931.126Slukem
1941.119Satatat20040426:
1951.119Satatat	Support for the original dynamic sysctl node structure has
1961.119Satatat	been removed in favor of the newer layout.  This affects
1971.119Satatat	consumers of the create and delete interface, as well as
1981.119Satatat	the dynamic discovery mechanism.  This is believed only to
1991.119Satatat	be the sysctl(8) binary itself, at this point in time, so
2001.119Satatat	the only effect of this should be that a sysctl binary
2011.119Satatat	built from sources dated between 2003/12/04 and 2004/03/24
2021.119Satatat	will not work on a kernel built from sources dated after
2031.119Satatat	2004/04/25.  If you need a new sysctl binary but build.sh
2041.119Satatat	does not work, make sure that your revision of
2051.120Satatat	src/sys/sys/sysctl.h is 1.112 (or later), and then the
2061.120Satatat	do the following:
2071.119Satatat
2081.120Satatat	cd /usr/src (or wherever your source tree is)
2091.120Satatat	make USETOOLS=no includes
2101.120Satatat	cd lib/libc
2111.120Satatat	make USETOOLS=no dependall install
2121.120Satatat	cd ../../sbin/sysctl
2131.119Satatat	make USETOOLS=no dependall install
2141.119Satatat
2151.122Sitojun	If you are using older sysctl binary, GNU autoconf would fail to
2161.122Sitojun	identify your machine architecture, and tries to build binary for
2171.122Sitojun	"unknown-unknown-netbsd20F" or something like that.  if that happens,
2181.122Sitojun	make sure to follow the above steps.
2191.122Sitojun
2201.118Sdbj20040425:
2211.118Sdbj	The ffs superblock issues listed below under 20040109 and 20030402
2221.118Sdbj	are now automatically addressed by the /etc/rc.d/fixsb script or by
2231.118Sdbj	sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4
2241.118Sdbj	invocation mentioned below will continue to work and is now
2251.118Sdbj	automated by those scripts.  Note that under certain circumstances,
2261.118Sdbj	affected filesystems upgraded to a -current kernel first before
2271.118Sdbj	upgrading their userland with the fixsb and fsck_ffs fixes may
2281.118Sdbj	encounter a 'freeing free inode' panic when writing to the affected
2291.118Sdbj	filesystem, so it is a good idea to repair the filesystem as soon as
2301.118Sdbj	possible.  For more details on the fixsb script, see pr install/25138.
2311.118Sdbj
2321.115Schristos20040418:
2331.121Slukem	statfs(2) and friends have been replaced with statvfs(2). Before
2341.115Schristos	installing a newly build userland make sure that you are running
2351.115Schristos	a newly built kernel with COMPAT_20 set. In addition your libc
2361.115Schristos	build might not work (undefined SYS_statfs symbol) because make
2371.115Schristos	clean does not know how to remove files it does not know about
2381.116Schristos	anymore. Manually remove all generated .S sources and objects
2391.116Schristos	from the libc build directory.
2401.115Schristos
2411.114Sjmc20040326:
2421.114Sjmc	The method by which athhal-elf.o gets pulled into i386 kernel builds
2431.117Sjmc	has been changed. The file is now stored as a uuencoded file in CVS
2441.114Sjmc	and the generated Makefile will use the new .uue rules from bsd.file.mk
2451.114Sjmc	to build it.
2461.114Sjmc
2471.114Sjmc	This means you must have the latest bsd.files.mk installed when
2481.114Sjmc	building a kernel without USETOOLS=yes.
2491.114Sjmc
2501.113Sdan20040318:
2511.113Sdan	A bug in the cgd(4) blowfish code was corrected, without
2521.113Sdan	provision of backwards compatibility, after several public
2531.113Sdan	notices over several months. Users of cgd with blowfish cipher
2541.113Sdan	ONLY must dump their data before updating their kernels, and
2551.113Sdan	recreate cgd's and restore data using the new kernel. See
2561.113Sdan	(recent message to current-users, URL when mail-index has updated)
2571.113Sdan
2581.108Sbjh2120040313:
2591.108Sbjh21	On acorn32, the opms and qms drivers have been withdrawn, and
2601.108Sbjh21	the old wsqms driver is now called qms.  Kernel config files
2611.108Sbjh21	will need updating.  See the ones in sys/arch/acorn32/conf
2621.108Sbjh21	for examples.
2631.108Sbjh21
2641.106Sbjh2120040125:
2651.106Sbjh21	On acorn32, the beep and sysbeep devices are no longer
2661.106Sbjh21	needed, and will need to be deleted from kernel configuration
2671.106Sbjh21	files.
2681.105Sbjh21
2691.102Sdbj20040109:
2701.102Sdbj	Compatibility for old ffs superblock layouts has been
2711.102Sdbj	added, and the restrictive fsck checks have been reenabled
2721.102Sdbj	when using those layouts.  If you have been using -current
2731.102Sdbj	since 20030402, you may find that fsck again signals fatal
2741.110Sdbj	superblock mismatches.  To repair, make sure you have
2751.111Ssimonb	an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4
2761.109Sdbj	to complete the filesystem upgrade.  A message has
2771.111Ssimonb	been added to the kernel which should detect this problem.
2781.111Ssimonb	See the following discussion for more information:
2791.112Skeihan	http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
2801.102Sdbj
2811.99Smrg20031203:
2821.100Skeihan	New binutils builds may fail due to old dependencies.
2831.99Smrg	It's necessary to "make cleandir" to ensure that
2841.99Smrg	the dependencies will be rebuilt correctly.
2851.98Swiz
2861.98Swiz20031111:
2871.98Swiz	A newer mkdep is needed.  Error noting that is
2881.98Swiz		cc: Ambiguous abbreviation --
2891.97Slukem
2901.97Slukem20031008:
2911.97Slukem	/usr/include/sys/disklabel_mbr.h was removed.
2921.97Slukem	It's necessary to "make cleandir" to ensure that
2931.97Slukem	the dependencies will be rebuilt correctly.
2941.96Schristos
2951.109Sdbj20031007:
2961.111Ssimonb	A sign exension bug was fixed which set all the high bits
2971.111Ssimonb	of our newly expanded ffs fs_flags.  This should only
2981.111Ssimonb	affect users who installed or upgraded in September of 2003.
2991.109Sdbj	A small utility program was posted to tech-kern which
3001.111Ssimonb	should fix this problem, and a warning message was added
3011.111Ssimonb	to the kernel which should discover and warn about it.  See
3021.111Ssimonb	http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html
3031.109Sdbj
3041.96Schristos20030906:
3051.96Schristos	With the addition of siginfo support the old signal trampoline
3061.96Schristos	code has been deprecated to COMPAT_16. Make sure that your running
3071.96Schristos	kernel has COMPAT_16 enabled before building userland.
3081.94Schristos
3091.94Schristos20030801:
3101.95Swiz	With the new openssl, there is some header and library shuffling.
3111.94Schristos	rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \
3121.95Swiz	/usr/lib/libdes* before building.
3131.92Swiz
3141.92Swiz20030703:
3151.92Swiz	Texinfo was updated to 4.6.  To avoid failures when trying to
3161.92Swiz	build the included texinfo files, do:
3171.92Swiz
3181.92Swiz	cd src/gnu/usr.bin/texinfo
3191.92Swiz	make MKINFO=no dependall install
3201.90Swiz
3211.90Swiz20030630:
3221.101Sjunyoung	Groff was updated to 1.19; it's probably necessary to do
3231.91Swiz		cd share/mk && make install
3241.90Swiz		cd src/gnu/usr.bin/groff
3251.90Swiz		make MKMAN=no dependall install
3261.90Swiz	(untested).
3271.89Schristos
3281.89Schristos20030516:
3291.89Schristos	Due to bugs in the export handling code, invalid export lines
3301.89Schristos	were accepted before and caused the kernel to panic when
3311.89Schristos	mountd got restarted because it freed memory that had already
3321.89Schristos	been freed. This has been fixed and the kernel checks
3331.89Schristos	export addresses very strictly. If you upgrade your kernel,
3341.89Schristos	make sure you also upgrade mountd, because if your export
3351.89Schristos	file contains lines with an old inet4 address syntax (i.e.
3361.89Schristos	a.b.c or a.b or a), they will get rejected by the new kernel.
3371.87Sbjh21
3381.87Sbjh2120030402:
3391.87Sbjh21	The superblock layout for FFS was changed.  If you have 1.6
3401.87Sbjh21	fsck binaries, they will signal a fatal superblock mismatch
3411.87Sbjh21	with the first alternate, because they compare too many
3421.87Sbjh21	fields (even ones that aren't useful).  If possible, upgrade
3431.87Sbjh21	your fsck_ffs binary before using a new kernel.
3441.87Sbjh21	None of this signals actual filesystem damage.
3451.85Satatat
3461.85Satatat20030324:
3471.85Satatat	sendmail version 8.12.8 was imported.  Since sendmail is
3481.85Satatat	now setgid to the smmsp group, and runs in "collection"
3491.85Satatat	mode for most common activities, there is a new config
3501.85Satatat	file called submit.cf that needs to live in /etc/mail.
3511.85Satatat	The generic submit.cf sample in /usr/share/sendmail/cf
3521.85Satatat	is named netbsd-msp.cf.  Upgrading your regular sendmail
3531.85Satatat	configuration file is also strongly advised.
3541.85Satatat
3551.85Satatat	See the section named "MESSAGE SUBMISSION PROGRAM" in
3561.85Satatat	the updated /usr/share/sendmail/README file for more
3571.85Satatat	information.
3581.82Swiz
3591.82Swiz20030117:
3601.82Swiz	Texinfo was updated to 4.3.  To avoid failures when trying to
3611.82Swiz	build the included texinfo files, do:
3621.82Swiz
3631.82Swiz	cd src/gnu/usr.bin/texinfo
3641.82Swiz	make MKINFO=no dependall install
3651.81Slukem
3661.81Slukem20021223:
3671.81Slukem	The METALOG format changed slightly, to remove the leading
3681.81Slukem	"${DESTDIR}" from path names.
3691.81Slukem	This only affects people building with UNPRIVED.
3701.81Slukem	For complete safety, remove the DESTDIR entirely and
3711.81Slukem	update tools/mtree, before running make build.
3721.88Sitojun
3731.88Sitojun20021219:
3741.88Sitojun	CVS repository layout was changed.  See the following for details
3751.88Sitojun	if you are using (anonymous) cvs to update your tree.
3761.88Sitojun
3771.93Ssalo	http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html
3781.80Slukem
3791.80Slukem20021219:
3801.80Slukem	install(1) had a '-N dbdir' option added, to specify an
3811.80Slukem	alternate location to look up users & groups (instead
3821.80Slukem	of the host system passwd(5) and group(5) databases).
3831.80Slukem
3841.80Slukem	The build system was modified to take advantage of
3851.80Slukem	this option (using ${NETBSDSRCDIR}/etc), so if you
3861.83Skei	use USETOOLS==no, you may have to rebuild and
3871.80Slukem	reinstall usr.bin/xinstall first.
3881.78Slukem
3891.78Slukem20021130:
3901.78Slukem	fparseln(3) moved from libutil to libc.
3911.78Slukem	If building to DESTDIR=/, reinstall the includes
3921.78Slukem	and rebuild libc:
3931.78Slukem		make includes
3941.78Slukem		make do-lib-libc
3951.78Slukem	If using build.sh, "cd tools/compat && make clean"
3961.78Slukem	before rebuilding the tools.
3971.77Slukem
3981.77Slukem20021126:
3991.77Slukem	The mk.conf(5) variable SYS_INCLUDE has been deprecated,
4001.77Slukem	including the optional "SYS_INCLUDE=symlinks" support.
4011.77Slukem	All header files, including <sys/*.h> are copied into
4021.77Slukem	/usr/include.
4031.76Sthorpej
4041.76Sthorpej20021121:
4051.76Sthorpej	The C run-time support files crtbegin.o and crtend.o
4061.76Sthorpej	(and their companions crtbeginS.o and crtendS.o) were
4071.76Sthorpej	split up, with new crti.o and crtn.o files resulting.
4081.76Sthorpej	This means that libtool needs to be rebuilt once the
4091.76Sthorpej	new libraries are installed.  The process of rebuilding
4101.76Sthorpej	libtool will cause it to automatically notice the new
4111.76Sthorpej	required files, but it *must* be rebuilt in order to
4121.76Sthorpej	do this.
4131.76Sthorpej
4141.76Sthorpej	An out-of-date libtool will result in shared libraries
4151.76Sthorpej	which lack _init() and _fini() routines, which means that
4161.76Sthorpej	their global contructors/destructors will not be invoked.
4171.75Sthorpej
4181.75Sthorpej20021121:
4191.75Sthorpej	A bug related to how ARM ELF objects were tagged has been
4201.75Sthorpej	corrected.
4211.75Sthorpej
4221.75Sthorpej	NetBSD ARM ELF uses the soft-VFP floating point model by
4231.75Sthorpej	default.  However, the assembler lacked support for marking
4241.75Sthorpej	objects as using the VFP floating point format, and the
4251.79Swiz	compiler was not properly passing the flag indicating "soft-VFP"
4261.75Sthorpej	to the assembler.
4271.75Sthorpej
4281.75Sthorpej	Unfortunately, this means that the linker will now consider
4291.75Sthorpej	old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be
4301.75Sthorpej	incompatible with new (properly marked) objects.
4311.75Sthorpej
4321.75Sthorpej	The problem will only manifest itself if you attempt to compile
4331.75Sthorpej	a new program using the fixed toolchain, and link that program
4341.75Sthorpej	against old libraries which do not have the proper "softvfp"
4351.75Sthorpej	markings.  ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES
4361.75Sthorpej	WILL CONTINUE TO WORK PROPERLY.
4371.75Sthorpej
4381.75Sthorpej	The only work-around for the problem is to recompile all of
4391.75Sthorpej	the libraries on the system.  The easiest way to do this for
4401.79Swiz	system libraries is to install a binary snapshot; they are
4411.93Ssalo	generally available on releng.NetBSD.org.  Any packages you
4421.75Sthorpej	have installed which supply libraries will have to be recompiled
4431.75Sthorpej	if you wish to link new programs against those libraries.
4441.75Sthorpej
4451.75Sthorpej	If you have questions about this matter, please contact
4461.93Ssalo	port-arm@NetBSD.org.
4471.73Sprovos
4481.73Sprovos20021011:
4491.73Sprovos	Systrace has been improved to support privilege elevation.
4501.73Sprovos	Updating the kernel requires the userland part of systrace
4511.79Swiz	to be rebuilt.
4521.72Sthorpej
4531.72Sthorpej20021010:
4541.72Sthorpej	The config(8) grammar was changed to allow options to register
4551.72Sthorpej	dependencies on attributes, as well as other options.  Users
4561.72Sthorpej	must update and reinstall usr.sbin/config before building a new
4571.72Sthorpej	kernel.
4581.70Sthorpej
4591.70Sthorpej20021009:
4601.70Sthorpej	A new attribute dependency syntax was introduced to config(8),
4611.70Sthorpej	which is now used by the SCSI configuration description.  Users
4621.71Swiz	must update and reinstall usr.sbin/config before building a new
4631.70Sthorpej	kernel.
4641.69Sthorpej
4651.69Sthorpej20021003:
4661.69Sthorpej	Several changes have been made to the autoconfiguration
4671.69Sthorpej	framework.  Users must update and reinstall usr.sbin/config
4681.69Sthorpej	before building a new kernel.
4691.74Sjschauma
4701.74Sjschauma20021001:
4711.74Sjschauma	The i386mp branch has been merged.  To compile a kernel, users
4721.74Sjschauma	will need to add the option 'cpu* at mainbus?' to their configuration
4731.74Sjschauma	file.  Multiprocessor kernels will need
4741.74Sjschauma	ioapic*		at mainbus? apid ?
4751.74Sjschauma	options		MULTIPROCESSOR
4761.74Sjschauma	options		COM_MPLOCK
4771.68Slukem
4781.68Slukem20020922:
4791.68Slukem	MKDYNAMICROOT=yes enabled by default, which means that
4801.68Slukem	certain shared libraries are installed into /lib, the shared
4811.68Slukem	linker is installed into /libexec, and all programs in /bin
4821.68Slukem	and /sbin are dynamically linked.
4831.68Slukem	If you do not use "make build", you should ensure that
4841.68Slukem	you have the libraries and shared linker in the new locations,
4851.68Slukem	with:
4861.68Slukem		make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so
4871.67Slukem
4881.67Slukem20020917:
4891.67Slukem	USE_NEW_TOOLCHAIN has been replaced with:
4901.67Slukem	    -	TOOLCHAIN_MISSING -- set to "yes" on platforms for which
4911.67Slukem		there is no working in-tree toolchain (hppa, ns32k, sh5,
4921.67Slukem		x86_64).
4931.67Slukem	    -	EXTERNAL_TOOLCHAIN -- if defined by the user, points to the
4941.79Swiz		root of an external toolchain (e.g. /usr/local/gnu).  This
4951.67Slukem		enables the cross-build framework even for TOOLCHAIN_MISSING
4961.67Slukem		platforms.
4971.66Sgehenna
4981.66Sgehenna20020906:
4991.66Sgehenna	gehenna-devsw has been merged into the trunk. Need to update and
5001.79Swiz	reinstall usr.sbin/config before building the kernel.
5011.65Slukem
5021.65Slukem20020822:
5031.65Slukem	Crunched rescue tools (contents of /bin and /sbin, plus others)
5041.65Slukem	are now provided in /rescue.
5051.65Slukem
5061.65Slukem	To ensure that these are built statically linked (no matter
5071.65Slukem	what the setting of LDSTATIC is), use a crunchgen(1) built
5081.65Slukem	from sources newer than 20020820 (see the next entry).
5091.65Slukem
5101.65Slukem20020820:
5111.65Slukem	crunchgen(1) changed to ensure that the generated program
5121.65Slukem	is statically linked.
5131.65Slukem
5141.65Slukem	Solution: update and reinstall usr.bin/crunch
5151.84Sgrant
5161.84Sgrant20020605:
5171.84Sgrant	smmsp user/group has been added for sendmail.
5181.84Sgrant
5191.84Sgrant	Add the following into /etc/group:
5201.84Sgrant
5211.84Sgrant	smmsp:*:17:
5221.84Sgrant
5231.84Sgrant	and the following to /etc/master.passwd (via vipw):
5241.84Sgrant
5251.84Sgrant	smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin
5261.61Sitojun
5271.61Sitojun20020515:
5281.61Sitojun	sshd user/group has been added.  Need to hand add this in, or sshd
5291.61Sitojun	will not let you log in (with default, or UsePrivlegeSeparation=yes)
5301.61Sitojun
5311.61Sitojun	Add the following into /etc/group:
5321.61Sitojun
5331.61Sitojun	sshd:*:16:
5341.61Sitojun
5351.61Sitojun	and the following to /etc/master.passwd (via vipw):
5361.61Sitojun
5371.63Senami	sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin
5381.61Sitojun	
5391.79Swiz	Also /var/chroot/sshd directory needs to be present (digged as part of
5401.79Swiz	the build process).
5411.60Ssommerfe
5421.60Ssommerfe20020426:
5431.60Ssommerfe	NBUILDJOBS obsoleted in favor of just using -j.
5441.59Slukem
5451.59Slukem20020426:
5461.59Slukem	etc/postinstall added, which performs various checks for 
5471.59Slukem	configuration file updates and changes, and can fix most of
5481.59Slukem	the problems identified.
5491.59Slukem	This should make it much easier to upgrade a system's
5501.59Slukem	configuration from earlier systems (as far back as NetBSD 1.5).
5511.56Slukem
5521.56Slukem20020320:
5531.79Swiz	<bsd.lib.mk> needs a new install(1) for its "-a cmd" support.
5541.79Swiz	Build and install at usr.bin/xinstall before the build.
5551.56Slukem
5561.55Sitojun20020319:
5571.79Swiz	Raw IPv6 socket now makes strict checking for sa_family and sa_len
5581.79Swiz	on send(2) operation.  Be sure to have sbin/rtsol and usr.sbin/rtsold
5591.55Sitojun	newer than November 2001 when you upgrade the kernel.
5601.55Sitojun
5611.54Sitojun20020311:
5621.54Sitojun	ssh configuration files were moved from /etc to /etc/ssh.  Beware
5631.54Sitojun	if you restart your machine from remote.  Note that sshd.conf needs
5641.54Sitojun	to be changed (due to the use of "/etc" inside).
5651.54Sitojun
5661.54Sitojun20020223:
5671.53Smatt	Users of the VAX port will need to rebuild and install gas
5681.53Smatt	so it deal with the now present register prefix used in all
5691.53Smatt	the VAX assembly files.
5701.53Smatt
5711.50Sitojun20020118:
5721.50Sitojun	ntpd user/group has been added.  Need to hand add this in or builds
5731.50Sitojun	will break as mtree aborts early.
5741.50Sitojun
5751.50Sitojun	Add the following into /etc/group:
5761.50Sitojun
5771.50Sitojun	ntpd:*:15:
5781.50Sitojun
5791.50Sitojun	and the following to /etc/master.passwd (via vipw):
5801.50Sitojun
5811.50Sitojun	ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin
5821.50Sitojun
5831.49Sjmc20011207:
5841.49Sjmc	If you're attempting to build a snapshot on sparc64 and are getting
5851.49Sjmc	reloc errors from the toolchain groff binary this means your native
5861.49Sjmc	toolchain has some broken C++ bits.
5871.49Sjmc
5881.49Sjmc	To fix:
5891.49Sjmc
5901.49Sjmc	Build a new toolchain (i.e. build.sh -t)
5911.49Sjmc	Use the new toolchain to build and install natively (i.e. /usr/lib)
5921.49Sjmc
5931.49Sjmc	gnu/lib/libgcc
5941.51Spooka	gnu/lib/libstdc++
5951.49Sjmc
5961.49Sjmc	After this a snapshot will be able to be built.
5971.49Sjmc
5981.47Sjmc20011201:
5991.47Sjmc	In order for a sparc64 build to work you must have a working awk. If
6001.47Sjmc	you've built and installed a system with the new toolchain up to this
6011.52Swiz	point you do not have a working awk as its ability to do floating
6021.47Sjmc	point is broken. 
6031.47Sjmc
6041.47Sjmc	To build:
6051.47Sjmc
6061.47Sjmc	remake and install gnu/lib/libgcc
6071.47Sjmc	remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links
6081.48Sjmc	against the new libgcc.a)
6091.47Sjmc
6101.46Sthorpej20011128:
6111.46Sthorpej	Kernel config information was changed to use defflag in
6121.46Sthorpej	the various "files" files.  Bug fixes to config(8) are
6131.46Sthorpej	required in order for this to work properly.  Make sure
6141.46Sthorpej	to build and install in usr.sbin/config before attempting
6151.46Sthorpej	to build a new kernel.
6161.46Sthorpej
6171.45Syamt20011030:
6181.45Syamt	libc/locale/wcstod.c now needs new lint(1). Update lint(1)
6191.45Syamt	before building libc.
6201.43Smason
6211.44Stv20011029:
6221.44Stv	The new document BUILDING.mdoc (view with nroff | more, or
6231.44Stv	see pre-generated .txt and .html versions) describes the build
6241.44Stv	procedure in great detail.  BUILDING, and the USE_NEW_TOOLCHAIN
6251.44Stv	build process, are intended in the long run to replace this
6261.44Stv	manual update log.
6271.44Stv
6281.44Stv	Users building a USE_NEW_TOOLCHAIN system should read the
6291.44Stv	BUILDING document for caveats.  Generally, BUILDING supersedes
6301.44Stv	UPDATING for these systems, as tool updating is taken care of
6311.44Stv	by the new build system.
6321.42Sperry
6331.42Sperry20011028:
6341.42Sperry	src/etc/Makefile now needs install to be able to handle
6351.42Sperry	symlinks that point to nowhere. A bug in install that
6361.42Sperry	prevented this was corrected.
6371.42Sperry
6381.42Sperry	Solution: update and reinstall usr.bin/xinstall
6391.42Sperry	Better Solution: Use the new toolchain and it will just work
6401.42Sperry	for you.
6411.40Slukem
6421.40Slukem20011006:
6431.40Slukem	/etc/mtree/NetBSD.dist has been updated to take advantage of
6441.40Slukem	absolute path support added to mtree(8). Older mtree(8)s don't
6451.40Slukem	understand the format.
6461.40Slukem
6471.40Slukem	Solution: update and reinstall usr.sbin/mtree
6481.39Sjmc
6491.39Sjmc20011004:
6501.39Sjmc	Crunchgen has been updated to work via reach-over makefiles. Updating
6511.39Sjmc	is suggested before running a snapshot build
6521.36Stv
6531.35Sthorpej20010915:
6541.35Sthorpej	The new "ubcperf" code committed by Chuck Silvers removed
6551.35Sthorpej	a header file, uvm/uvm_vnode.h.  There may be stale .depend
6561.35Sthorpej	files that still reference this file.
6571.35Sthorpej
6581.35Sthorpej	Solution: "make cleandir && make dependall" in affected
6591.35Sthorpej	directories.
6601.31Senami
6611.31Senami20010803:
6621.31Senami	grep.info is now built from grep.texi using makeinfo.  Since it
6631.31Senami	requires makeinfo v4.0, you need to install new texinfo before
6641.31Senami	building gnu/usr.bin/grep.  To install new texinfo, please follow
6651.31Senami	the instruction described in 20010726 entry.
6661.30Senami
6671.64Ssommerfe20010803: 
6681.41Swiz	(i386 only): i386 kernel now uses new instructions like
6691.111Ssimonb	`fxsave' which old gas doesn't understand.  To build the
6701.64Ssommerfe	kernel successfully, you need to build and install a new toolchain, 
6711.64Ssommerfe	(i.e., build.sh -t) or 	(temporarily) comment out "options I686_CPU" 
6721.64Ssommerfe	from your kernel configuration until you rebuild your userland.
6731.64Ssommerfe	See 20011029 above and BUILDING file in this directory for more information.
6741.64Ssommerfe	[updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled]
6751.29Sbjh21
6761.29Sbjh2120010731:
6771.29Sbjh21	Bootloader update on ELF platforms.  DDB in kernels from before
6781.29Sbjh21	this will be unable to read symbol tables provided by newer
6791.29Sbjh21	bootloaders.
6801.27Sassar
6811.27Sassar20010726:
6821.27Sassar	Texinfo was updated to 4.0.  To avoid failures when trying to
6831.28Sassar	build the included texinfo files, do:
6841.28Sassar
6851.28Sassar	cd src/gnu/usr.bin/texinfo
6861.28Sassar	make MKINFO=no dependall install
6871.25Sthorpej
6881.25Sthorpej20010718:
6891.25Sthorpej	Enabled correct .init/.fini processing in crt0.  The way this
6901.25Sthorpej	was done was to change a -I directive to cc(1), which means
6911.25Sthorpej	make(1) will have a stale dependency (it will be checking the
6921.25Sthorpej	timestamp on the wrong "dot_init.h").
6931.25Sthorpej
6941.25Sthorpej	The symptom you will see is that new programs die with SIGSEGV
6951.25Sthorpej	if you have a stale dependency.
6961.25Sthorpej
6971.25Sthorpej	Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so
6981.25Sthorpej	before starting your build.
6991.26Sthorpej
7001.26Sthorpej20010628:
7011.26Sthorpej	A construct was added to uvm_page.h that uncovered a bug
7021.26Sthorpej	in lint(1).  If you get a warning/error about a non-portable
7031.26Sthorpej	bitfield, update your lint(1) before proceeding.
7041.21Sjmc
7051.21Sjmc20010226:
7061.22Sjmc	Added named user/group to system. Need to hand add this in or builds
7071.21Sjmc	will break as mtree aborts early.
7081.21Sjmc
7091.21Sjmc	To work around add by hand:
7101.21Sjmc
7111.21Sjmc	named:*:14:
7121.21Sjmc
7131.22Sjmc	to /etc/group and add:
7141.22Sjmc
7151.22Sjmc	named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin
7161.22Sjmc
7171.22Sjmc	to master.passwd (use vipw for instance if doing by hand).
7181.22Sjmc
7191.22Sjmc	Now a make build should progress.
7201.18Sjmc
7211.18Sjmc20010219:
7221.52Swiz	get/setprogname() added. Any hostprogs that may use this will need
7231.111Ssimonb	to be bootstrapped manually until the host system is current.
7241.18Sjmc
7251.111Ssimonb	Known problems: sys/arch/macppc/stand/fixcoff
7261.19Scgd			usr.sbin/config (adding -DMAKE_BOOTSTRAP to
7271.19Scgd			  CFLAGS and rebuilding should work)
7281.20Sjmc			usr.sbin/mdsetimage - Build a static copy if
7291.111Ssimonb			  building a snapshot before fully bootstrapped.
7301.15Schristos
7311.15Schristos20010204:
7321.15Schristos	prepare the code to compile with stricter gcc flags. in
7331.15Schristos	particular start eliminating redundant declarations. Yacc
7341.15Schristos	needs to be installed before make build.
7351.10Schristos
7361.10Schristos20010114:
7371.10Schristos	introduce .if commands(target) in make(1). You need to
7381.10Schristos	bring everything up-to-date first, then without installing
7391.23Stron	anything make and install in usr.bin/make, then proceed
7401.10Schristos	with make build.
7411.9Ssommerfe
7421.9Ssommerfe20010101:
7431.9Ssommerfe	bsd.subdir.mk committed 20001230 had a bug which caused
7441.9Ssommerfe	afterinstall targets to run too soon; update again.
7451.8Ssommerfe
7461.8Ssommerfe20001230:
7471.8Ssommerfe	New share/mk files needed to support .WAIT in SUBDIR variables.
7481.8Ssommerfe	If you get make errors, 
7491.8Ssommerfe		(cd share/mk; make install)
7501.8Ssommerfe	Also, PRINTOBJDIR has changed and is now used more heavily.
7511.6Sad
7521.6Sad20001019:
7531.7Sad	The `ca' device driver has been replaced by `ld'; although the
7541.6Sad	major and minor numbers haven't changed, you should update your /dev
7551.6Sad	directory.
7561.1Sabs
7571.4Sitojun20000929:
7581.4Sitojun	The following make directives are obsoleted.
7591.4Sitojun	MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 
7601.4Sitojun	By default, RSA is built into libcrypto.  IDEA and RC5 will not be
7611.16Swiz	built into libcrypto.  By using MKCRYPTO_{RC5,IDEA}, you can build
7621.4Sitojun	additional library libcrypto_{idea,rc5}.
7631.1Sabs
7641.1Sabs
7651.1SabsHints for a more successful build:
7661.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7671.123Sjmc    Use build.sh, but do not use its "expert mode":
7681.132Sjmmv	This will automatically build the tools in the
7691.123Sjmc	   correct order, and it will keep the tools and the
7701.123Sjmc	   new build products from interfering with the running
7711.123Sjmc	   system.  This will allow you to ignore most of the
7721.123Sjmc	   other advice in this file.
7731.2Smrg    Build a new kernel first:
7741.2Smrg	This makes sure that any new system calls or features
7751.2Smrg	   expected by the new userland will be present.  This
7761.2Smrg	   helps to avoid critical errors when upgrading.
7771.1Sabs    Use object directories:
7781.1Sabs	This helps to keep stale object
7791.1Sabs	   files from polluting the build if a Makefile "forgets"
7801.1Sabs	   about one.  It also makes it easier to clean up after
7811.1Sabs	   a build.  It's also necessary if you want to use the
7821.1Sabs	   same source tree for multiple machines.
7831.123Sjmc	   To use object directories with build.sh:
7841.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
7851.123Sjmc	   To use object directories without using build.sh:
7861.1Sabs	    a) cd /usr/src ; make cleandir
7871.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
7881.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
7891.1Sabs	    d) cd /usr/src ; make build
7901.2Smrg	   Note that running "make obj" in a directory will create
7911.2Smrg	   in obj.$MACHINE directory.
7921.1Sabs    Build to a DESTDIR:
7931.123Sjmc	This helps to keep old installed files (especially libraries)
7941.123Sjmc	   from interfering with the new build.
7951.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
7961.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
7971.123Sjmc	   environment variable before running make build.  It should be
7981.123Sjmc	   set to the pathname of an initially empty directory.
7991.123Sjmc	   Problems: if you do not use build.sh, you might need to
8001.123Sjmc		update critical utilities without using DESTDIR since
8011.123Sjmc		nothing is executed from what is installed in DESTDIR.
8021.123Sjmc		(See critical utils, below.)
8031.1Sabs    Build often:
8041.1Sabs	This keeps critical utilities current enough to not choke
8051.1Sabs	on any other part of the source tree that depends on up to
8061.123Sjmc	date functionality.  If you use build.sh, you should not have
8071.123Sjmc	this problem.
8081.1Sabs 
8091.1SabsWhat to do if things don't work:
8101.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8111.1SabsWhen things don't work there is usually a few things that commonly
8121.1Sabsshould be done.
8131.1Sabs    1)	make includes
8141.1Sabs	This should be done automatically by make build.
8151.1Sabs    2)  cd share/mk && make install
8161.1Sabs	Again, automatically done by make build.
8171.1Sabs
8181.1SabsFailsafe rebuild of a small part of the tree:
8191.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8201.1SabsTo make sure you rebuild something correctly you want to do
8211.1Sabssomething like the following:
8221.1Sabs    1)  Make sure the includes and .mk files are up to date.
8231.1Sabs    2)  Make sure any program used to build the particular
8241.1Sabs	utility is up to date.  (yacc, lex, etc...)
8251.1Sabs    3)  cd ...path/to/util...
8261.1Sabs	make cleandir
8271.1Sabs	rm ...all obj directories...
8281.1Sabs	make cleandir			# yes, again
8291.1Sabs	make obj
8301.1Sabs	make depend && make
8311.1Sabs
8321.1SabsFailsafe rebuild of the entire tree:
8331.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8341.1SabsIf you really want to make sure the source tree is clean and
8351.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
8361.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
8371.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
8381.1Sabs
8391.1Sabs---cut here---
8401.1Sabs#!/bin/sh
8411.1Sabs. /etc/mk.conf
8421.1Sabs
8431.58Slukemif [ -z $NETBSDSRCDIR ] ; then
8441.58Slukem    NETBSDSRCDIR=/usr/src
8451.1Sabsfi
8461.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
8471.1Sabs    echo Unable to find sources
8481.1Sabs    exit 1
8491.1Sabsfi
8501.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
8511.1Sabs
8521.1Sabsif [ -z $BSDOBJDIR ] ; then
8531.1Sabs    BSDOBJDIR=/usr/obj
8541.1Sabsfi
8551.1Sabsif [ -d $BSDOBJDIR ] ; then
8561.1Sabs    rm -rf $BSDOBJDIR
8571.1Sabsfi
8581.1Sabs
8591.58Slukemcd $NETBSDSRCDIR && make cleandir
8601.1Sabs
8611.1Sabs---cut here---
8621.1Sabs
8631.1SabsCritical utilities:
8641.1Sabs^^^^^^^^^^^^^^^^^^^
8651.3Sitojun	usr.bin/compile_et
8661.1Sabs	usr.bin/make
8671.1Sabs	usr.bin/yacc
8681.1Sabs	usr.bin/lex
8691.11Slukem	usr.bin/xlint
8701.142Sdrochner	usr.bin/config
8711.1Sabs
8721.34SsimonbOther problems and possible solutions:
8731.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8741.1SabsSymptom:Complaints involving a Makefile.
8751.17SerhFix:	Rebuild usr.bin/make:
8761.17Serh	cd usr.bin/make && make && make install
8771.111Ssimonb	Or, a failsafe method if that doesn't work:
8781.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
8791.17Serh
8801.1SabsFix:	Make sure .mk files are up to date.
8811.1Sabs	cd share/mk && make install
8821.2Smrg
8831.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
8841.142SdrochnerFix:	Rebuild usr.bin/config
8851.1Sabs
8861.1SabsSymptom:
8871.1SabsFix:	Rebuild usr.bin/yacc
8881.1Sabs
8891.1SabsSymptom:
8901.1SabsFix:	Rebuild usr.bin/lex
8911.1Sabs
8921.1SabsSymptom:
8931.1SabsFix:	rm /usr/lib/libbfd.a
8941.4Sitojun
8951.4SitojunSymptom:Obsolete intermediate files are used during compilation
8961.4SitojunFix:	Try the following sequence of commands in the directory in question.
8971.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
8981.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
8991.4Sitojun	may remain.  The command tries to clean everything up)
9001.5Swiz
9011.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
9021.5SwizFix:	Rebuild and install usr.bin/menuc
9031.12Sitojun
9041.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9051.12SitojunFix:	Build and install usr.bin/mklocale
9061.13Sdogcow
9071.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9081.13SdogcowFix:    Rebuild and install lib/libc
9091.13Sdogcow
9101.142SdrochnerSymptom:usr.bin/config fails to build.
9111.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9121.13Sdogcow
9131.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9141.19ScgdFix:    Rebuild and install lib/libc
9151.24Sabs
9161.24SabsSymptom:lint does not understand the '-X' option
9171.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
918