UPDATING revision 1.196
11.196Sdholland$NetBSD: UPDATING,v 1.196 2009/05/27 18:02:57 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.195Sperry20090501:
201.195Sperry	Several new functions were added to string.h/libc, and this
211.195Sperry	can cause autoconf problems during the tool build for people
221.195Sperry	who fail to clean out their tools objects properly. If you
231.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
241.195Sperry	failure during the tool build, clean out all your tools
251.195Sperry	objects and start again.
261.195Sperry
271.194Smrg20090325:
281.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
291.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
301.194Smrg
311.192Sskrll20090126:
321.193Sskrll	The __posix_fadvise50 system call changed assembly stub type. You need to
331.193Sskrll	'rm -f __posix_fadvise50.*' in the libc build directory to avoid using
341.192Sskrll	the old assembly stub.
351.192Sskrll
361.191Sjoerg20090202:
371.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
381.191Sjoerg	detection.  It is recommented to rebuild the cache with
391.191Sjoerg	``pkg_admin rebuild''.
401.191Sjoerg
411.184Schristos20090110:
421.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
431.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
441.188Schristos	   This is needed even in the MODULAR kernel because there is
451.188Schristos	   conditionally compiled code in rtsock.c.
461.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
471.184Schristos	   before installing.
481.184Schristos	3. If you don't use build.sh and you build directly to root, and
491.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
501.184Schristos	   are installed properly, and start building libraries first libc
511.184Schristos	   and libutil, install them and then continue building all the
521.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
531.184Schristos	   the new libraries are installed, you can restart the build.
541.184Schristos	4. If you compile packages and you notice link time warnings,
551.189Shubertf	   rebuild the required packages to update their shared libraries.
561.189Shubertf	   Any package you rebuild will require rebuilding all the packages
571.189Shubertf	   that depend on it.
581.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
591.186Schristos	   will be upgraded and it will not be backwards compatible.
601.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
611.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
621.190Sapb	   for utmp. You are better off removing the old files after
631.190Sapb	   upgrading.  The automated clearing of /var/run during
641.190Sapb	   boot, and the automated rotating of files in /var/log by
651.190Sapb	   newsyslog(8), may mean that you do not have to remove the
661.190Sapb	   files manually.
671.190Sapb	7. The optional accounting file (/var/account/acct, see
681.190Sapb	   accton(8)) has not been versioned, and will need to be
691.190Sapb	   removed.  The automatic rotation of the accounting file by
701.190Sapb	   /etc/daily limits the bad consequences of failure to remove
711.190Sapb	   the file.
721.196Sdholland	8. Application software that writes time_t to binary files on
731.196Sdholland	   disk will break or need attention. Most notably: if you are
741.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
751.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
761.185Sjmcneill
771.183Spgoyette20081219:
781.183Spgoyette	config(1) has been updated, and one of the files it creates -
791.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
801.183Spgoyette	(done automatically by build.sh) and then you need to rerun
811.183Spgoyette	config on all kernel configuration files before rebuilding those
821.183Spgoyette	kernels.
831.183Spgoyette
841.181Scube20081205:
851.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
861.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
871.181Scube	set and will appear as extra files for MKX11=no update builds.
881.178Slukem
891.179Stsutsui20081122:
901.182Stsutsui	On i386, various kernel options(4) in GENERIC including
911.180Swiz	file systems have been disabled and moved into kernel modules.
921.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
931.179Stsutsui	following files as well as a new GENERIC kernel:
941.179Stsutsui
951.179Stsutsui	- build and install kernel modules from src/sys/modules
961.179Stsutsui
971.179Stsutsui	- install the latest bootloader, which will load a module
981.180Swiz	  for the file system from which the kernel is loaded automatically
991.179Stsutsui
1001.180Swiz	If you have to load your kernel from a file system which is not of
1011.180Swiz	the same type as the root file system, you have to load the necessary
1021.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
1031.179Stsutsui
1041.178Slukem20080827:
1051.178Slukem	If you built and installed a libc from sources between
1061.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
1071.178Slukem	which results in false errors reported by lint(1).
1081.178Slukem	Since this breaks the libc build itself, manual help is
1091.180Swiz	needed -- lint must be disabled temporarily, e.g.:
1101.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
1111.178Slukem
1121.177Schristos20080813:
1131.177Schristos	MKDEBUG build was broken because the .depend files did not know
1141.177Schristos	about .go files. You need to remove all .depend files and rebuild.
1151.177Schristos
1161.175Ssimonb20080731:
1171.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
1181.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
1191.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
1201.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
1211.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
1221.176Ssimonb	also requires the super block to be in the UFS2 format.  You
1231.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
1241.175Ssimonb
1251.174Slukem20080721:
1261.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
1271.174Slukem	isn't defined.
1281.174Slukem
1291.173Sfreza20080531:
1301.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
1311.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
1321.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
1331.173Sfreza	won't work correctly. The following sequence of commands:
1341.173Sfreza
1351.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
1361.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
1371.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
1381.173Sfreza
1391.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
1401.173Sfreza
1411.172Slukem20080503:
1421.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
1431.172Slukem
1441.171She20080521:
1451.171She	For a while, unprivileged UPDATE builds would fail to
1461.171She	succeed at the checkflist stage, complaining that
1471.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
1481.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
1491.171She	If you already hit this problem, update the .mk file,
1501.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
1511.171She
1521.174Slukem20080303:
1531.174Slukem	Linker warnings are now fatal if $WARNS>0.
1541.174Slukem
1551.170Schristos20080126:
1561.170Schristos	The posix_fadvise system call has been changed from an assembly
1571.170Schristos	stub, to a c file that calls an assembly stub. You need to
1581.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
1591.170Schristos	avoid using the old assembly stub.
1601.170Schristos
1611.168Sjoerg20071209:
1621.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
1631.168Sjoerg	get ACPI errors before the attachment, please update your kernel
1641.169Swiz	configuration file appropriately or see GENERIC for more details.
1651.168Sjoerg
1661.166Sxtraeme20071115:
1671.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
1681.166Sxtraeme	argument specified in the kernel configuration file is not valid
1691.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
1701.166Sxtraeme	rather than the EC address port. Please update your kernel
1711.167Swiz	configuration file appropriately or see GENERIC for more details.
1721.166Sxtraeme
1731.165Sjmmv20071028:
1741.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
1751.165Sjmmv	You need to update any custom kernel configuration file you have
1761.165Sjmmv	to remove any references to pccons (which includes removing the
1771.165Sjmmv	now useless XSERVER option) and replace them with the correct
1781.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
1791.165Sjmmv	for more details.
1801.165Sjmmv
1811.164Sgdt20070913:
1821.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
1831.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
1841.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
1851.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
1861.164Sgdt	could not enumerate interfaces.  (These are noted because
1871.164Sgdt	normal kernel/userspace version matching hygiene is not
1881.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
1891.164Sgdt	and userland are from after 20070913.
1901.164Sgdt
1911.163Sjoerg20070703:
1921.163Sjoerg	nbinstall has been renamed as it calls the target specific and
1931.163Sjoerg	the logic to pass down STRIP from mk been removed.  This forces
1941.163Sjoerg	a re-installation of tools.
1951.163Sjoerg
1961.161Sdsl20070422:
1971.161Sdsl	The way OS emulations lookup filenames inside the emulation root
1981.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
1991.161Sdsl	to userspace) namei() and lookup() directly check the emulation
2001.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
2011.167Swiz	root file system will be relative to that file system - unless they
2021.161Sdsl	start /../ this is useful when the emulated root is a real install
2031.161Sdsl	that has such links.
2041.161Sdsl	This might affect symlinks that have been added to reference outside
2051.161Sdsl	the emulated root.
2061.161Sdsl
2071.160Sjmcneill20070412:
2081.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
2091.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
2101.160Sjmcneill	example.
2111.160Sjmcneill
2121.159Sgdt20070319:
2131.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
2141.159Sgdt        on many platforms due to incorrect flags settings.  If you
2151.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
2161.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
2171.159Sgdt	rebuild of object files that might have been built
2181.159Sgdt	incorrectly, and ensure that you have at least
2191.159Sgdt	src/lib/libc/Makefile 1.130.
2201.159Sgdt
2211.158Sdbj20070210: 
2221.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
2231.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
2241.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
2251.158Sdbj        will allow dependencies on those files to get get rebuilt
2261.158Sdbj
2271.157Sapb20070209:
2281.157Sapb        The threading model was changed when the newlock2 branch
2291.157Sapb        was merged to NetBSD-current.  If you boot with a new
2301.157Sapb        kernel (version 4.99.10), then you also need a new pthread
2311.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
2321.157Sapb        an old kernel, then you need the old pthread library
2331.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
2341.157Sapb        the pthread library in sync, old threaded applications should
2351.157Sapb        continue to work with an old or new kernel.  Note that named(8)
2361.157Sapb	is the only threaded application in the base system.
2371.157Sapb
2381.154She20061214:
2391.154She	Following the move of string_to_flags() and flags_to_string()
2401.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
2411.154She	will need to do a "make cleandir" in
2421.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
2431.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
2441.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
2451.156She		as the installation images in distrib/
2461.154She	in order to excise stale references to the old stat_flags.h header
2471.154She	file in the ls sources -- stat_flags.h has been removed.
2481.154She
2491.152Schristos20061108:
2501.152Schristos	The configure script used in the src/tools/gcc compiler has been
2511.152Schristos	changed to indicate that our libc has ssp support built-in and
2521.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
2531.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
2541.152Schristos
2551.151Srpaulo20061009:
2561.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
2571.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
2581.151Srpaulo
2591.150Sbjh2120060814:
2601.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
2611.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
2621.150Sbjh21	kernel configuration for an example.  X servers from the last
2631.150Sbjh21	few years should cope.
2641.150Sbjh21
2651.149Schristos20060703:
2661.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
2671.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
2681.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
2691.149Schristos
2701.148Sdogcow20060627:
2711.148Sdogcow	socket(2) has changed, and its system call has been versioned.
2721.148Sdogcow	For userlands with the old version of socket(2), make sure that
2731.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
2741.148Sdogcow	errors will result.
2751.148Sdogcow
2761.1SabsHints for a more successful build:
2771.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2781.123Sjmc    Use build.sh, but do not use its "expert mode":
2791.132Sjmmv	This will automatically build the tools in the
2801.123Sjmc	   correct order, and it will keep the tools and the
2811.123Sjmc	   new build products from interfering with the running
2821.123Sjmc	   system.  This will allow you to ignore most of the
2831.123Sjmc	   other advice in this file.
2841.2Smrg    Build a new kernel first:
2851.2Smrg	This makes sure that any new system calls or features
2861.2Smrg	   expected by the new userland will be present.  This
2871.2Smrg	   helps to avoid critical errors when upgrading.
2881.1Sabs    Use object directories:
2891.1Sabs	This helps to keep stale object
2901.1Sabs	   files from polluting the build if a Makefile "forgets"
2911.1Sabs	   about one.  It also makes it easier to clean up after
2921.1Sabs	   a build.  It's also necessary if you want to use the
2931.1Sabs	   same source tree for multiple machines.
2941.123Sjmc	   To use object directories with build.sh:
2951.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
2961.123Sjmc	   To use object directories without using build.sh:
2971.1Sabs	    a) cd /usr/src ; make cleandir
2981.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
2991.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
3001.1Sabs	    d) cd /usr/src ; make build
3011.2Smrg	   Note that running "make obj" in a directory will create
3021.2Smrg	   in obj.$MACHINE directory.
3031.1Sabs    Build to a DESTDIR:
3041.123Sjmc	This helps to keep old installed files (especially libraries)
3051.123Sjmc	   from interfering with the new build.
3061.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
3071.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
3081.123Sjmc	   environment variable before running make build.  It should be
3091.123Sjmc	   set to the pathname of an initially empty directory.
3101.123Sjmc	   Problems: if you do not use build.sh, you might need to
3111.123Sjmc		update critical utilities without using DESTDIR since
3121.123Sjmc		nothing is executed from what is installed in DESTDIR.
3131.123Sjmc		(See critical utils, below.)
3141.1Sabs    Build often:
3151.1Sabs	This keeps critical utilities current enough to not choke
3161.1Sabs	on any other part of the source tree that depends on up to
3171.123Sjmc	date functionality.  If you use build.sh, you should not have
3181.123Sjmc	this problem.
3191.1Sabs 
3201.1SabsWhat to do if things don't work:
3211.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3221.1SabsWhen things don't work there is usually a few things that commonly
3231.1Sabsshould be done.
3241.1Sabs    1)	make includes
3251.1Sabs	This should be done automatically by make build.
3261.1Sabs    2)  cd share/mk && make install
3271.1Sabs	Again, automatically done by make build.
3281.1Sabs
3291.1SabsFailsafe rebuild of a small part of the tree:
3301.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3311.1SabsTo make sure you rebuild something correctly you want to do
3321.1Sabssomething like the following:
3331.1Sabs    1)  Make sure the includes and .mk files are up to date.
3341.1Sabs    2)  Make sure any program used to build the particular
3351.1Sabs	utility is up to date.  (yacc, lex, etc...)
3361.1Sabs    3)  cd ...path/to/util...
3371.1Sabs	make cleandir
3381.1Sabs	rm ...all obj directories...
3391.1Sabs	make cleandir			# yes, again
3401.1Sabs	make obj
3411.1Sabs	make depend && make
3421.1Sabs
3431.1SabsFailsafe rebuild of the entire tree:
3441.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3451.1SabsIf you really want to make sure the source tree is clean and
3461.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
3471.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
3481.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
3491.1Sabs
3501.1Sabs---cut here---
3511.1Sabs#!/bin/sh
3521.1Sabs. /etc/mk.conf
3531.1Sabs
3541.58Slukemif [ -z $NETBSDSRCDIR ] ; then
3551.58Slukem    NETBSDSRCDIR=/usr/src
3561.1Sabsfi
3571.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
3581.1Sabs    echo Unable to find sources
3591.1Sabs    exit 1
3601.1Sabsfi
3611.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
3621.1Sabs
3631.1Sabsif [ -z $BSDOBJDIR ] ; then
3641.1Sabs    BSDOBJDIR=/usr/obj
3651.1Sabsfi
3661.1Sabsif [ -d $BSDOBJDIR ] ; then
3671.1Sabs    rm -rf $BSDOBJDIR
3681.1Sabsfi
3691.1Sabs
3701.58Slukemcd $NETBSDSRCDIR && make cleandir
3711.1Sabs
3721.1Sabs---cut here---
3731.1Sabs
3741.1SabsCritical utilities:
3751.1Sabs^^^^^^^^^^^^^^^^^^^
3761.3Sitojun	usr.bin/compile_et
3771.1Sabs	usr.bin/make
3781.1Sabs	usr.bin/yacc
3791.1Sabs	usr.bin/lex
3801.11Slukem	usr.bin/xlint
3811.142Sdrochner	usr.bin/config
3821.1Sabs
3831.34SsimonbOther problems and possible solutions:
3841.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3851.1SabsSymptom:Complaints involving a Makefile.
3861.17SerhFix:	Rebuild usr.bin/make:
3871.17Serh	cd usr.bin/make && make && make install
3881.111Ssimonb	Or, a failsafe method if that doesn't work:
3891.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
3901.17Serh
3911.1SabsFix:	Make sure .mk files are up to date.
3921.1Sabs	cd share/mk && make install
3931.2Smrg
3941.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
3951.142SdrochnerFix:	Rebuild usr.bin/config
3961.1Sabs
3971.1SabsSymptom:
3981.1SabsFix:	Rebuild usr.bin/yacc
3991.1Sabs
4001.1SabsSymptom:
4011.1SabsFix:	Rebuild usr.bin/lex
4021.1Sabs
4031.1SabsSymptom:
4041.1SabsFix:	rm /usr/lib/libbfd.a
4051.4Sitojun
4061.4SitojunSymptom:Obsolete intermediate files are used during compilation
4071.4SitojunFix:	Try the following sequence of commands in the directory in question.
4081.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
4091.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
4101.4Sitojun	may remain.  The command tries to clean everything up)
4111.5Swiz
4121.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
4131.5SwizFix:	Rebuild and install usr.bin/menuc
4141.12Sitojun
4151.12SitojunSymptom:mklocale not found during build in share/locale/ctype
4161.12SitojunFix:	Build and install usr.bin/mklocale
4171.13Sdogcow
4181.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
4191.13SdogcowFix:    Rebuild and install lib/libc
4201.13Sdogcow
4211.142SdrochnerSymptom:usr.bin/config fails to build.
4221.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
4231.13Sdogcow
4241.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
4251.19ScgdFix:    Rebuild and install lib/libc
4261.24Sabs
4271.24SabsSymptom:lint does not understand the '-X' option
4281.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
429