UPDATING revision 1.200
11.200Sdholland$NetBSD: UPDATING,v 1.200 2009/07/09 08:04:32 dholland 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.198Smrg20090709:
201.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
211.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
221.198Smrg
231.197Smrg20090616:
241.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
251.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
261.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
271.197Smrg	subdirectory has been changed into a file, and this needs to
281.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
291.197Smrg
301.195Sperry20090501:
311.195Sperry	Several new functions were added to string.h/libc, and this
321.195Sperry	can cause autoconf problems during the tool build for people
331.195Sperry	who fail to clean out their tools objects properly. If you
341.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
351.195Sperry	failure during the tool build, clean out all your tools
361.195Sperry	objects and start again.
371.195Sperry
381.194Smrg20090325:
391.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
401.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
411.194Smrg
421.192Sskrll20090126:
431.193Sskrll	The __posix_fadvise50 system call changed assembly stub type. You need to
441.193Sskrll	'rm -f __posix_fadvise50.*' in the libc build directory to avoid using
451.192Sskrll	the old assembly stub.
461.192Sskrll
471.191Sjoerg20090202:
481.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
491.191Sjoerg	detection.  It is recommented to rebuild the cache with
501.191Sjoerg	``pkg_admin rebuild''.
511.191Sjoerg
521.184Schristos20090110:
531.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
541.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
551.188Schristos	   This is needed even in the MODULAR kernel because there is
561.188Schristos	   conditionally compiled code in rtsock.c.
571.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
581.184Schristos	   before installing.
591.184Schristos	3. If you don't use build.sh and you build directly to root, and
601.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
611.184Schristos	   are installed properly, and start building libraries first libc
621.184Schristos	   and libutil, install them and then continue building all the
631.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
641.184Schristos	   the new libraries are installed, you can restart the build.
651.184Schristos	4. If you compile packages and you notice link time warnings,
661.189Shubertf	   rebuild the required packages to update their shared libraries.
671.189Shubertf	   Any package you rebuild will require rebuilding all the packages
681.189Shubertf	   that depend on it.
691.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
701.186Schristos	   will be upgraded and it will not be backwards compatible.
711.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
721.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
731.190Sapb	   for utmp. You are better off removing the old files after
741.190Sapb	   upgrading.  The automated clearing of /var/run during
751.190Sapb	   boot, and the automated rotating of files in /var/log by
761.190Sapb	   newsyslog(8), may mean that you do not have to remove the
771.190Sapb	   files manually.
781.190Sapb	7. The optional accounting file (/var/account/acct, see
791.190Sapb	   accton(8)) has not been versioned, and will need to be
801.190Sapb	   removed.  The automatic rotation of the accounting file by
811.190Sapb	   /etc/daily limits the bad consequences of failure to remove
821.190Sapb	   the file.
831.196Sdholland	8. Application software that writes time_t to binary files on
841.196Sdholland	   disk will break or need attention. Most notably: if you are
851.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
861.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
871.185Sjmcneill
881.183Spgoyette20081219:
891.183Spgoyette	config(1) has been updated, and one of the files it creates -
901.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
911.183Spgoyette	(done automatically by build.sh) and then you need to rerun
921.183Spgoyette	config on all kernel configuration files before rebuilding those
931.183Spgoyette	kernels.
941.183Spgoyette
951.181Scube20081205:
961.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
971.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
981.181Scube	set and will appear as extra files for MKX11=no update builds.
991.178Slukem
1001.179Stsutsui20081122:
1011.182Stsutsui	On i386, various kernel options(4) in GENERIC including
1021.180Swiz	file systems have been disabled and moved into kernel modules.
1031.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
1041.179Stsutsui	following files as well as a new GENERIC kernel:
1051.179Stsutsui
1061.179Stsutsui	- build and install kernel modules from src/sys/modules
1071.179Stsutsui
1081.179Stsutsui	- install the latest bootloader, which will load a module
1091.180Swiz	  for the file system from which the kernel is loaded automatically
1101.179Stsutsui
1111.180Swiz	If you have to load your kernel from a file system which is not of
1121.180Swiz	the same type as the root file system, you have to load the necessary
1131.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
1141.179Stsutsui
1151.178Slukem20080827:
1161.178Slukem	If you built and installed a libc from sources between
1171.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
1181.178Slukem	which results in false errors reported by lint(1).
1191.178Slukem	Since this breaks the libc build itself, manual help is
1201.180Swiz	needed -- lint must be disabled temporarily, e.g.:
1211.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
1221.178Slukem
1231.177Schristos20080813:
1241.177Schristos	MKDEBUG build was broken because the .depend files did not know
1251.177Schristos	about .go files. You need to remove all .depend files and rebuild.
1261.177Schristos
1271.200Sdholland20080802:
1281.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
1291.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
1301.200Sdholland	for -current.
1311.200Sdholland
1321.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
1331.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
1341.200Sdholland	be recompiled.
1351.200Sdholland
1361.200Sdholland	One way to find affected pkgsrc packages:
1371.200Sdholland
1381.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
1391.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
1401.200Sdholland
1411.175Ssimonb20080731:
1421.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
1431.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
1441.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
1451.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
1461.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
1471.176Ssimonb	also requires the super block to be in the UFS2 format.  You
1481.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
1491.175Ssimonb
1501.174Slukem20080721:
1511.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
1521.174Slukem	isn't defined.
1531.174Slukem
1541.173Sfreza20080531:
1551.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
1561.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
1571.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
1581.173Sfreza	won't work correctly. The following sequence of commands:
1591.173Sfreza
1601.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
1611.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
1621.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
1631.173Sfreza
1641.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
1651.173Sfreza
1661.172Slukem20080503:
1671.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
1681.172Slukem
1691.171She20080521:
1701.171She	For a while, unprivileged UPDATE builds would fail to
1711.171She	succeed at the checkflist stage, complaining that
1721.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
1731.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
1741.171She	If you already hit this problem, update the .mk file,
1751.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
1761.171She
1771.174Slukem20080303:
1781.174Slukem	Linker warnings are now fatal if $WARNS>0.
1791.174Slukem
1801.170Schristos20080126:
1811.170Schristos	The posix_fadvise system call has been changed from an assembly
1821.170Schristos	stub, to a c file that calls an assembly stub. You need to
1831.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
1841.170Schristos	avoid using the old assembly stub.
1851.170Schristos
1861.168Sjoerg20071209:
1871.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
1881.168Sjoerg	get ACPI errors before the attachment, please update your kernel
1891.169Swiz	configuration file appropriately or see GENERIC for more details.
1901.168Sjoerg
1911.166Sxtraeme20071115:
1921.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
1931.166Sxtraeme	argument specified in the kernel configuration file is not valid
1941.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
1951.166Sxtraeme	rather than the EC address port. Please update your kernel
1961.167Swiz	configuration file appropriately or see GENERIC for more details.
1971.166Sxtraeme
1981.165Sjmmv20071028:
1991.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
2001.165Sjmmv	You need to update any custom kernel configuration file you have
2011.165Sjmmv	to remove any references to pccons (which includes removing the
2021.165Sjmmv	now useless XSERVER option) and replace them with the correct
2031.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
2041.165Sjmmv	for more details.
2051.165Sjmmv
2061.164Sgdt20070913:
2071.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
2081.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
2091.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
2101.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
2111.164Sgdt	could not enumerate interfaces.  (These are noted because
2121.164Sgdt	normal kernel/userspace version matching hygiene is not
2131.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
2141.164Sgdt	and userland are from after 20070913.
2151.164Sgdt
2161.163Sjoerg20070703:
2171.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
2181.199Sdholland	calls the target-specific strip program, and the logic to pass
2191.199Sdholland	down STRIP from make has been removed.  This requires a
2201.199Sdholland	re-installation of tools.
2211.163Sjoerg
2221.161Sdsl20070422:
2231.161Sdsl	The way OS emulations lookup filenames inside the emulation root
2241.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
2251.161Sdsl	to userspace) namei() and lookup() directly check the emulation
2261.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
2271.167Swiz	root file system will be relative to that file system - unless they
2281.161Sdsl	start /../ this is useful when the emulated root is a real install
2291.161Sdsl	that has such links.
2301.161Sdsl	This might affect symlinks that have been added to reference outside
2311.161Sdsl	the emulated root.
2321.161Sdsl
2331.160Sjmcneill20070412:
2341.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
2351.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
2361.160Sjmcneill	example.
2371.160Sjmcneill
2381.159Sgdt20070319:
2391.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
2401.159Sgdt        on many platforms due to incorrect flags settings.  If you
2411.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
2421.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
2431.159Sgdt	rebuild of object files that might have been built
2441.159Sgdt	incorrectly, and ensure that you have at least
2451.159Sgdt	src/lib/libc/Makefile 1.130.
2461.159Sgdt
2471.158Sdbj20070210: 
2481.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
2491.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
2501.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
2511.158Sdbj        will allow dependencies on those files to get get rebuilt
2521.158Sdbj
2531.157Sapb20070209:
2541.157Sapb        The threading model was changed when the newlock2 branch
2551.157Sapb        was merged to NetBSD-current.  If you boot with a new
2561.157Sapb        kernel (version 4.99.10), then you also need a new pthread
2571.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
2581.157Sapb        an old kernel, then you need the old pthread library
2591.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
2601.157Sapb        the pthread library in sync, old threaded applications should
2611.157Sapb        continue to work with an old or new kernel.  Note that named(8)
2621.157Sapb	is the only threaded application in the base system.
2631.157Sapb
2641.154She20061214:
2651.154She	Following the move of string_to_flags() and flags_to_string()
2661.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
2671.154She	will need to do a "make cleandir" in
2681.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
2691.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
2701.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
2711.156She		as the installation images in distrib/
2721.154She	in order to excise stale references to the old stat_flags.h header
2731.154She	file in the ls sources -- stat_flags.h has been removed.
2741.154She
2751.152Schristos20061108:
2761.152Schristos	The configure script used in the src/tools/gcc compiler has been
2771.152Schristos	changed to indicate that our libc has ssp support built-in and
2781.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
2791.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
2801.152Schristos
2811.151Srpaulo20061009:
2821.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
2831.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
2841.151Srpaulo
2851.150Sbjh2120060814:
2861.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
2871.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
2881.150Sbjh21	kernel configuration for an example.  X servers from the last
2891.150Sbjh21	few years should cope.
2901.150Sbjh21
2911.149Schristos20060703:
2921.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
2931.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
2941.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
2951.149Schristos
2961.148Sdogcow20060627:
2971.148Sdogcow	socket(2) has changed, and its system call has been versioned.
2981.148Sdogcow	For userlands with the old version of socket(2), make sure that
2991.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
3001.148Sdogcow	errors will result.
3011.148Sdogcow
3021.1SabsHints for a more successful build:
3031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3041.123Sjmc    Use build.sh, but do not use its "expert mode":
3051.132Sjmmv	This will automatically build the tools in the
3061.123Sjmc	   correct order, and it will keep the tools and the
3071.123Sjmc	   new build products from interfering with the running
3081.123Sjmc	   system.  This will allow you to ignore most of the
3091.123Sjmc	   other advice in this file.
3101.2Smrg    Build a new kernel first:
3111.2Smrg	This makes sure that any new system calls or features
3121.2Smrg	   expected by the new userland will be present.  This
3131.2Smrg	   helps to avoid critical errors when upgrading.
3141.1Sabs    Use object directories:
3151.1Sabs	This helps to keep stale object
3161.1Sabs	   files from polluting the build if a Makefile "forgets"
3171.1Sabs	   about one.  It also makes it easier to clean up after
3181.1Sabs	   a build.  It's also necessary if you want to use the
3191.1Sabs	   same source tree for multiple machines.
3201.123Sjmc	   To use object directories with build.sh:
3211.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
3221.123Sjmc	   To use object directories without using build.sh:
3231.1Sabs	    a) cd /usr/src ; make cleandir
3241.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
3251.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
3261.1Sabs	    d) cd /usr/src ; make build
3271.2Smrg	   Note that running "make obj" in a directory will create
3281.2Smrg	   in obj.$MACHINE directory.
3291.1Sabs    Build to a DESTDIR:
3301.123Sjmc	This helps to keep old installed files (especially libraries)
3311.123Sjmc	   from interfering with the new build.
3321.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
3331.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
3341.123Sjmc	   environment variable before running make build.  It should be
3351.123Sjmc	   set to the pathname of an initially empty directory.
3361.123Sjmc	   Problems: if you do not use build.sh, you might need to
3371.123Sjmc		update critical utilities without using DESTDIR since
3381.123Sjmc		nothing is executed from what is installed in DESTDIR.
3391.123Sjmc		(See critical utils, below.)
3401.1Sabs    Build often:
3411.1Sabs	This keeps critical utilities current enough to not choke
3421.1Sabs	on any other part of the source tree that depends on up to
3431.123Sjmc	date functionality.  If you use build.sh, you should not have
3441.123Sjmc	this problem.
3451.1Sabs 
3461.1SabsWhat to do if things don't work:
3471.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3481.1SabsWhen things don't work there is usually a few things that commonly
3491.1Sabsshould be done.
3501.1Sabs    1)	make includes
3511.1Sabs	This should be done automatically by make build.
3521.1Sabs    2)  cd share/mk && make install
3531.1Sabs	Again, automatically done by make build.
3541.1Sabs
3551.1SabsFailsafe rebuild of a small part of the tree:
3561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3571.1SabsTo make sure you rebuild something correctly you want to do
3581.1Sabssomething like the following:
3591.1Sabs    1)  Make sure the includes and .mk files are up to date.
3601.1Sabs    2)  Make sure any program used to build the particular
3611.1Sabs	utility is up to date.  (yacc, lex, etc...)
3621.1Sabs    3)  cd ...path/to/util...
3631.1Sabs	make cleandir
3641.1Sabs	rm ...all obj directories...
3651.1Sabs	make cleandir			# yes, again
3661.1Sabs	make obj
3671.1Sabs	make depend && make
3681.1Sabs
3691.1SabsFailsafe rebuild of the entire tree:
3701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3711.1SabsIf you really want to make sure the source tree is clean and
3721.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
3731.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
3741.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
3751.1Sabs
3761.1Sabs---cut here---
3771.1Sabs#!/bin/sh
3781.1Sabs. /etc/mk.conf
3791.1Sabs
3801.58Slukemif [ -z $NETBSDSRCDIR ] ; then
3811.58Slukem    NETBSDSRCDIR=/usr/src
3821.1Sabsfi
3831.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
3841.1Sabs    echo Unable to find sources
3851.1Sabs    exit 1
3861.1Sabsfi
3871.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
3881.1Sabs
3891.1Sabsif [ -z $BSDOBJDIR ] ; then
3901.1Sabs    BSDOBJDIR=/usr/obj
3911.1Sabsfi
3921.1Sabsif [ -d $BSDOBJDIR ] ; then
3931.1Sabs    rm -rf $BSDOBJDIR
3941.1Sabsfi
3951.1Sabs
3961.58Slukemcd $NETBSDSRCDIR && make cleandir
3971.1Sabs
3981.1Sabs---cut here---
3991.1Sabs
4001.1SabsCritical utilities:
4011.1Sabs^^^^^^^^^^^^^^^^^^^
4021.3Sitojun	usr.bin/compile_et
4031.1Sabs	usr.bin/make
4041.1Sabs	usr.bin/yacc
4051.1Sabs	usr.bin/lex
4061.11Slukem	usr.bin/xlint
4071.142Sdrochner	usr.bin/config
4081.1Sabs
4091.34SsimonbOther problems and possible solutions:
4101.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4111.1SabsSymptom:Complaints involving a Makefile.
4121.17SerhFix:	Rebuild usr.bin/make:
4131.17Serh	cd usr.bin/make && make && make install
4141.111Ssimonb	Or, a failsafe method if that doesn't work:
4151.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
4161.17Serh
4171.1SabsFix:	Make sure .mk files are up to date.
4181.1Sabs	cd share/mk && make install
4191.2Smrg
4201.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
4211.142SdrochnerFix:	Rebuild usr.bin/config
4221.1Sabs
4231.1SabsSymptom:
4241.1SabsFix:	Rebuild usr.bin/yacc
4251.1Sabs
4261.1SabsSymptom:
4271.1SabsFix:	Rebuild usr.bin/lex
4281.1Sabs
4291.1SabsSymptom:
4301.1SabsFix:	rm /usr/lib/libbfd.a
4311.4Sitojun
4321.4SitojunSymptom:Obsolete intermediate files are used during compilation
4331.4SitojunFix:	Try the following sequence of commands in the directory in question.
4341.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
4351.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
4361.4Sitojun	may remain.  The command tries to clean everything up)
4371.5Swiz
4381.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
4391.5SwizFix:	Rebuild and install usr.bin/menuc
4401.12Sitojun
4411.12SitojunSymptom:mklocale not found during build in share/locale/ctype
4421.12SitojunFix:	Build and install usr.bin/mklocale
4431.13Sdogcow
4441.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
4451.13SdogcowFix:    Rebuild and install lib/libc
4461.13Sdogcow
4471.142SdrochnerSymptom:usr.bin/config fails to build.
4481.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
4491.13Sdogcow
4501.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
4511.19ScgdFix:    Rebuild and install lib/libc
4521.24Sabs
4531.24SabsSymptom:lint does not understand the '-X' option
4541.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
455