UPDATING revision 1.213
11.213Sjmmv$NetBSD: UPDATING,v 1.213 2010/06/04 15:11:31 jmmv 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.213Sjmmv20100604:
201.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
211.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
221.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
231.213Sjmmv	trees by hand.
241.213Sjmmv
251.211Stnozaki20100522:
261.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
271.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
281.212Smrg	build problems with xsrc.
291.212Smrg
301.212Smrg20100522:
311.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
321.211Stnozaki	include ctype_local.h, so you have to make cleandir tools/mklocale.
331.211Stnozaki
341.210Schristos20100520:
351.210Schristos	The location of the xkb compiled descriptions has changed. Please
361.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
371.210Schristos
381.209Snjoly20100222:
391.209Snjoly	The shared objects file extension has been changed from .so to
401.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
411.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
421.209Snjoly	your object directories.
431.209Snjoly
441.208Sroy20100204:
451.208Sroy	The termcap database has been removed from the sources,
461.208Sroy	but has not been marked obsolete so it is not removed
471.208Sroy	from the system when upgrading.
481.208Sroy	As such, you will need to remove them from your object
491.208Sroy	and destination directories.
501.208Sroy
511.203Sdyoung20091101:
521.205Sdholland        After updating, it may be necessary to make the 'cleandir'
531.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
541.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
551.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
561.203Sdyoung
571.202Smrg20091001:
581.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
591.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
601.206Sdholland
611.206Sdholland20091001:
621.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
631.202Smrg	symlink, failing the build.  Delete the link, and the subdir
641.202Smrg	it is in, and retry your build.
651.202Smrg
661.201Sdsl20090718:
671.201Sdsl	libc build changed so that strchr() provides the extra entry
681.201Sdsl	point for index(). Update build of libc.a (and libc_pic.a)
691.201Sdsl	may fail because the archive contains the unwanted index.o.
701.201Sdsl	(Similarly for strrchr() and rindex().)
711.201Sdsl
721.198Smrg20090709:
731.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
741.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
751.198Smrg
761.197Smrg20090616:
771.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
781.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
791.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
801.197Smrg	subdirectory has been changed into a file, and this needs to
811.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
821.197Smrg
831.195Sperry20090501:
841.195Sperry	Several new functions were added to string.h/libc, and this
851.195Sperry	can cause autoconf problems during the tool build for people
861.195Sperry	who fail to clean out their tools objects properly. If you
871.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
881.195Sperry	failure during the tool build, clean out all your tools
891.195Sperry	objects and start again.
901.195Sperry
911.194Smrg20090325:
921.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
931.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
941.194Smrg
951.192Sskrll20090126:
961.207Smbalmer	The __posix_fadvise50 system call changed assembly stub type. You
971.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
981.207Smbalmer	to avoid using the old assembly stub.
991.192Sskrll
1001.191Sjoerg20090202:
1011.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
1021.191Sjoerg	detection.  It is recommented to rebuild the cache with
1031.191Sjoerg	``pkg_admin rebuild''.
1041.191Sjoerg
1051.184Schristos20090110:
1061.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
1071.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
1081.188Schristos	   This is needed even in the MODULAR kernel because there is
1091.188Schristos	   conditionally compiled code in rtsock.c.
1101.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
1111.184Schristos	   before installing.
1121.184Schristos	3. If you don't use build.sh and you build directly to root, and
1131.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
1141.184Schristos	   are installed properly, and start building libraries first libc
1151.184Schristos	   and libutil, install them and then continue building all the
1161.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
1171.184Schristos	   the new libraries are installed, you can restart the build.
1181.184Schristos	4. If you compile packages and you notice link time warnings,
1191.189Shubertf	   rebuild the required packages to update their shared libraries.
1201.189Shubertf	   Any package you rebuild will require rebuilding all the packages
1211.189Shubertf	   that depend on it.
1221.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
1231.186Schristos	   will be upgraded and it will not be backwards compatible.
1241.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
1251.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
1261.190Sapb	   for utmp. You are better off removing the old files after
1271.190Sapb	   upgrading.  The automated clearing of /var/run during
1281.190Sapb	   boot, and the automated rotating of files in /var/log by
1291.190Sapb	   newsyslog(8), may mean that you do not have to remove the
1301.190Sapb	   files manually.
1311.190Sapb	7. The optional accounting file (/var/account/acct, see
1321.190Sapb	   accton(8)) has not been versioned, and will need to be
1331.190Sapb	   removed.  The automatic rotation of the accounting file by
1341.190Sapb	   /etc/daily limits the bad consequences of failure to remove
1351.190Sapb	   the file.
1361.196Sdholland	8. Application software that writes time_t to binary files on
1371.196Sdholland	   disk will break or need attention. Most notably: if you are
1381.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
1391.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
1401.185Sjmcneill
1411.183Spgoyette20081219:
1421.183Spgoyette	config(1) has been updated, and one of the files it creates -
1431.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
1441.183Spgoyette	(done automatically by build.sh) and then you need to rerun
1451.183Spgoyette	config on all kernel configuration files before rebuilding those
1461.183Spgoyette	kernels.
1471.183Spgoyette
1481.181Scube20081205:
1491.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
1501.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
1511.181Scube	set and will appear as extra files for MKX11=no update builds.
1521.178Slukem
1531.179Stsutsui20081122:
1541.182Stsutsui	On i386, various kernel options(4) in GENERIC including
1551.180Swiz	file systems have been disabled and moved into kernel modules.
1561.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
1571.179Stsutsui	following files as well as a new GENERIC kernel:
1581.179Stsutsui
1591.179Stsutsui	- build and install kernel modules from src/sys/modules
1601.179Stsutsui
1611.179Stsutsui	- install the latest bootloader, which will load a module
1621.180Swiz	  for the file system from which the kernel is loaded automatically
1631.179Stsutsui
1641.180Swiz	If you have to load your kernel from a file system which is not of
1651.180Swiz	the same type as the root file system, you have to load the necessary
1661.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
1671.179Stsutsui
1681.178Slukem20080827:
1691.178Slukem	If you built and installed a libc from sources between
1701.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
1711.178Slukem	which results in false errors reported by lint(1).
1721.178Slukem	Since this breaks the libc build itself, manual help is
1731.180Swiz	needed -- lint must be disabled temporarily, e.g.:
1741.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
1751.178Slukem
1761.177Schristos20080813:
1771.177Schristos	MKDEBUG build was broken because the .depend files did not know
1781.177Schristos	about .go files. You need to remove all .depend files and rebuild.
1791.177Schristos
1801.200Sdholland20080802:
1811.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
1821.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
1831.200Sdholland	for -current.
1841.200Sdholland
1851.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
1861.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
1871.200Sdholland	be recompiled.
1881.200Sdholland
1891.200Sdholland	One way to find affected pkgsrc packages:
1901.200Sdholland
1911.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
1921.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
1931.200Sdholland
1941.175Ssimonb20080731:
1951.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
1961.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
1971.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
1981.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
1991.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
2001.176Ssimonb	also requires the super block to be in the UFS2 format.  You
2011.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
2021.175Ssimonb
2031.174Slukem20080721:
2041.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
2051.174Slukem	isn't defined.
2061.174Slukem
2071.173Sfreza20080531:
2081.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
2091.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
2101.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
2111.173Sfreza	won't work correctly. The following sequence of commands:
2121.173Sfreza
2131.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
2141.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
2151.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
2161.173Sfreza
2171.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
2181.173Sfreza
2191.172Slukem20080503:
2201.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
2211.172Slukem
2221.171She20080521:
2231.171She	For a while, unprivileged UPDATE builds would fail to
2241.171She	succeed at the checkflist stage, complaining that
2251.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
2261.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
2271.171She	If you already hit this problem, update the .mk file,
2281.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
2291.171She
2301.174Slukem20080303:
2311.174Slukem	Linker warnings are now fatal if $WARNS>0.
2321.174Slukem
2331.170Schristos20080126:
2341.170Schristos	The posix_fadvise system call has been changed from an assembly
2351.170Schristos	stub, to a c file that calls an assembly stub. You need to
2361.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
2371.170Schristos	avoid using the old assembly stub.
2381.170Schristos
2391.168Sjoerg20071209:
2401.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
2411.168Sjoerg	get ACPI errors before the attachment, please update your kernel
2421.169Swiz	configuration file appropriately or see GENERIC for more details.
2431.168Sjoerg
2441.166Sxtraeme20071115:
2451.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
2461.166Sxtraeme	argument specified in the kernel configuration file is not valid
2471.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
2481.166Sxtraeme	rather than the EC address port. Please update your kernel
2491.167Swiz	configuration file appropriately or see GENERIC for more details.
2501.166Sxtraeme
2511.165Sjmmv20071028:
2521.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
2531.165Sjmmv	You need to update any custom kernel configuration file you have
2541.165Sjmmv	to remove any references to pccons (which includes removing the
2551.165Sjmmv	now useless XSERVER option) and replace them with the correct
2561.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
2571.165Sjmmv	for more details.
2581.165Sjmmv
2591.164Sgdt20070913:
2601.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
2611.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
2621.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
2631.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
2641.164Sgdt	could not enumerate interfaces.  (These are noted because
2651.164Sgdt	normal kernel/userspace version matching hygiene is not
2661.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
2671.164Sgdt	and userland are from after 20070913.
2681.164Sgdt
2691.163Sjoerg20070703:
2701.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
2711.199Sdholland	calls the target-specific strip program, and the logic to pass
2721.199Sdholland	down STRIP from make has been removed.  This requires a
2731.199Sdholland	re-installation of tools.
2741.163Sjoerg
2751.161Sdsl20070422:
2761.161Sdsl	The way OS emulations lookup filenames inside the emulation root
2771.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
2781.161Sdsl	to userspace) namei() and lookup() directly check the emulation
2791.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
2801.167Swiz	root file system will be relative to that file system - unless they
2811.161Sdsl	start /../ this is useful when the emulated root is a real install
2821.161Sdsl	that has such links.
2831.161Sdsl	This might affect symlinks that have been added to reference outside
2841.161Sdsl	the emulated root.
2851.161Sdsl
2861.160Sjmcneill20070412:
2871.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
2881.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
2891.160Sjmcneill	example.
2901.160Sjmcneill
2911.159Sgdt20070319:
2921.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
2931.159Sgdt        on many platforms due to incorrect flags settings.  If you
2941.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
2951.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
2961.159Sgdt	rebuild of object files that might have been built
2971.159Sgdt	incorrectly, and ensure that you have at least
2981.159Sgdt	src/lib/libc/Makefile 1.130.
2991.159Sgdt
3001.158Sdbj20070210: 
3011.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
3021.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
3031.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
3041.158Sdbj        will allow dependencies on those files to get get rebuilt
3051.158Sdbj
3061.157Sapb20070209:
3071.157Sapb        The threading model was changed when the newlock2 branch
3081.157Sapb        was merged to NetBSD-current.  If you boot with a new
3091.157Sapb        kernel (version 4.99.10), then you also need a new pthread
3101.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
3111.157Sapb        an old kernel, then you need the old pthread library
3121.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
3131.157Sapb        the pthread library in sync, old threaded applications should
3141.157Sapb        continue to work with an old or new kernel.  Note that named(8)
3151.157Sapb	is the only threaded application in the base system.
3161.157Sapb
3171.154She20061214:
3181.154She	Following the move of string_to_flags() and flags_to_string()
3191.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
3201.154She	will need to do a "make cleandir" in
3211.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
3221.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
3231.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
3241.156She		as the installation images in distrib/
3251.154She	in order to excise stale references to the old stat_flags.h header
3261.154She	file in the ls sources -- stat_flags.h has been removed.
3271.154She
3281.152Schristos20061108:
3291.152Schristos	The configure script used in the src/tools/gcc compiler has been
3301.152Schristos	changed to indicate that our libc has ssp support built-in and
3311.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
3321.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
3331.152Schristos
3341.151Srpaulo20061009:
3351.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
3361.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
3371.151Srpaulo
3381.150Sbjh2120060814:
3391.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
3401.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
3411.150Sbjh21	kernel configuration for an example.  X servers from the last
3421.150Sbjh21	few years should cope.
3431.150Sbjh21
3441.149Schristos20060703:
3451.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
3461.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
3471.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
3481.149Schristos
3491.148Sdogcow20060627:
3501.148Sdogcow	socket(2) has changed, and its system call has been versioned.
3511.148Sdogcow	For userlands with the old version of socket(2), make sure that
3521.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
3531.148Sdogcow	errors will result.
3541.148Sdogcow
3551.1SabsHints for a more successful build:
3561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3571.123Sjmc    Use build.sh, but do not use its "expert mode":
3581.132Sjmmv	This will automatically build the tools in the
3591.123Sjmc	   correct order, and it will keep the tools and the
3601.123Sjmc	   new build products from interfering with the running
3611.123Sjmc	   system.  This will allow you to ignore most of the
3621.123Sjmc	   other advice in this file.
3631.2Smrg    Build a new kernel first:
3641.2Smrg	This makes sure that any new system calls or features
3651.2Smrg	   expected by the new userland will be present.  This
3661.2Smrg	   helps to avoid critical errors when upgrading.
3671.1Sabs    Use object directories:
3681.1Sabs	This helps to keep stale object
3691.1Sabs	   files from polluting the build if a Makefile "forgets"
3701.1Sabs	   about one.  It also makes it easier to clean up after
3711.1Sabs	   a build.  It's also necessary if you want to use the
3721.1Sabs	   same source tree for multiple machines.
3731.123Sjmc	   To use object directories with build.sh:
3741.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
3751.123Sjmc	   To use object directories without using build.sh:
3761.1Sabs	    a) cd /usr/src ; make cleandir
3771.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
3781.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
3791.1Sabs	    d) cd /usr/src ; make build
3801.2Smrg	   Note that running "make obj" in a directory will create
3811.2Smrg	   in obj.$MACHINE directory.
3821.1Sabs    Build to a DESTDIR:
3831.123Sjmc	This helps to keep old installed files (especially libraries)
3841.123Sjmc	   from interfering with the new build.
3851.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
3861.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
3871.123Sjmc	   environment variable before running make build.  It should be
3881.123Sjmc	   set to the pathname of an initially empty directory.
3891.123Sjmc	   Problems: if you do not use build.sh, you might need to
3901.123Sjmc		update critical utilities without using DESTDIR since
3911.123Sjmc		nothing is executed from what is installed in DESTDIR.
3921.123Sjmc		(See critical utils, below.)
3931.1Sabs    Build often:
3941.1Sabs	This keeps critical utilities current enough to not choke
3951.1Sabs	on any other part of the source tree that depends on up to
3961.123Sjmc	date functionality.  If you use build.sh, you should not have
3971.123Sjmc	this problem.
3981.1Sabs 
3991.1SabsWhat to do if things don't work:
4001.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4011.1SabsWhen things don't work there is usually a few things that commonly
4021.1Sabsshould be done.
4031.1Sabs    1)	make includes
4041.1Sabs	This should be done automatically by make build.
4051.1Sabs    2)  cd share/mk && make install
4061.1Sabs	Again, automatically done by make build.
4071.1Sabs
4081.1SabsFailsafe rebuild of a small part of the tree:
4091.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4101.1SabsTo make sure you rebuild something correctly you want to do
4111.1Sabssomething like the following:
4121.1Sabs    1)  Make sure the includes and .mk files are up to date.
4131.1Sabs    2)  Make sure any program used to build the particular
4141.1Sabs	utility is up to date.  (yacc, lex, etc...)
4151.1Sabs    3)  cd ...path/to/util...
4161.1Sabs	make cleandir
4171.1Sabs	rm ...all obj directories...
4181.1Sabs	make cleandir			# yes, again
4191.1Sabs	make obj
4201.1Sabs	make depend && make
4211.1Sabs
4221.1SabsFailsafe rebuild of the entire tree:
4231.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4241.1SabsIf you really want to make sure the source tree is clean and
4251.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
4261.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
4271.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
4281.1Sabs
4291.1Sabs---cut here---
4301.1Sabs#!/bin/sh
4311.1Sabs. /etc/mk.conf
4321.1Sabs
4331.58Slukemif [ -z $NETBSDSRCDIR ] ; then
4341.58Slukem    NETBSDSRCDIR=/usr/src
4351.1Sabsfi
4361.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
4371.1Sabs    echo Unable to find sources
4381.1Sabs    exit 1
4391.1Sabsfi
4401.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
4411.1Sabs
4421.1Sabsif [ -z $BSDOBJDIR ] ; then
4431.1Sabs    BSDOBJDIR=/usr/obj
4441.1Sabsfi
4451.1Sabsif [ -d $BSDOBJDIR ] ; then
4461.1Sabs    rm -rf $BSDOBJDIR
4471.1Sabsfi
4481.1Sabs
4491.58Slukemcd $NETBSDSRCDIR && make cleandir
4501.1Sabs
4511.1Sabs---cut here---
4521.1Sabs
4531.1SabsCritical utilities:
4541.1Sabs^^^^^^^^^^^^^^^^^^^
4551.3Sitojun	usr.bin/compile_et
4561.1Sabs	usr.bin/make
4571.1Sabs	usr.bin/yacc
4581.1Sabs	usr.bin/lex
4591.11Slukem	usr.bin/xlint
4601.142Sdrochner	usr.bin/config
4611.1Sabs
4621.34SsimonbOther problems and possible solutions:
4631.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4641.1SabsSymptom:Complaints involving a Makefile.
4651.17SerhFix:	Rebuild usr.bin/make:
4661.17Serh	cd usr.bin/make && make && make install
4671.111Ssimonb	Or, a failsafe method if that doesn't work:
4681.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
4691.17Serh
4701.1SabsFix:	Make sure .mk files are up to date.
4711.1Sabs	cd share/mk && make install
4721.2Smrg
4731.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
4741.142SdrochnerFix:	Rebuild usr.bin/config
4751.1Sabs
4761.1SabsSymptom:
4771.1SabsFix:	Rebuild usr.bin/yacc
4781.1Sabs
4791.1SabsSymptom:
4801.1SabsFix:	Rebuild usr.bin/lex
4811.1Sabs
4821.1SabsSymptom:
4831.1SabsFix:	rm /usr/lib/libbfd.a
4841.4Sitojun
4851.4SitojunSymptom:Obsolete intermediate files are used during compilation
4861.4SitojunFix:	Try the following sequence of commands in the directory in question.
4871.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
4881.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
4891.4Sitojun	may remain.  The command tries to clean everything up)
4901.5Swiz
4911.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
4921.207Smbalmer	pointer type
4931.5SwizFix:	Rebuild and install usr.bin/menuc
4941.12Sitojun
4951.12SitojunSymptom:mklocale not found during build in share/locale/ctype
4961.12SitojunFix:	Build and install usr.bin/mklocale
4971.13Sdogcow
4981.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
4991.13SdogcowFix:    Rebuild and install lib/libc
5001.13Sdogcow
5011.142SdrochnerSymptom:usr.bin/config fails to build.
5021.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
5031.13Sdogcow
5041.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
5051.19ScgdFix:    Rebuild and install lib/libc
5061.24Sabs
5071.24SabsSymptom:lint does not understand the '-X' option
5081.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
509