UPDATING revision 1.222
11.222Splunky$NetBSD: UPDATING,v 1.222 2011/04/10 08:29:31 plunky 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.222Splunky20110328:
191.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
201.222Splunky	ordering issues with "make all". It may be necessary to remove
211.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
221.222Splunky	if your update build fails, as the "Xorg" entry there is now a
231.222Splunky	directory.
241.222Splunky
251.220Sjoerg20110121:
261.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
271.220Sjoerg	the build of individual parts of the tree.  This is handled
281.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
291.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
301.218Sjoerg
311.217Sjruoho20101217:
321.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
331.217Sjruoho	by default. It may be necessary to manually update passwd(5) and
341.217Sjruoho	group(5) in order to make the program work with existing setups.
351.217Sjruoho
361.216Schristos20101125:
371.216Schristos	The latest changes to setenv(3) dissallow setting environment
381.216Schristos	variables with names that contain '='. Revision 1.18 of env.c
391.216Schristos	assumed that this was allowed. Installing a new libc with an
401.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
411.216Schristos	break which affects the autoconf tests for dependency finding,
421.216Schristos	so building gcc will end up printing:
431.216Schristos	    checking dependency style of gcc... none
441.216Schristos	    configure: error: no usable dependency style found
451.216Schristos	Fix it by rebuilding and re-installing env.
461.138Slukem
471.215Smrg20101119:
481.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
491.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
501.215Smrg	have any build problems with xsrc, or problems with mismatched
511.215Smrg	versions between xorg-server and drivers.
521.215Smrg
531.213Sjmmv20100604:
541.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
551.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
561.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
571.213Sjmmv	trees by hand.
581.213Sjmmv
591.211Stnozaki20100522:
601.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
611.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
621.212Smrg	build problems with xsrc.
631.212Smrg
641.212Smrg20100522:
651.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
661.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
671.211Stnozaki
681.210Schristos20100520:
691.210Schristos	The location of the xkb compiled descriptions has changed. Please
701.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
711.210Schristos
721.209Snjoly20100222:
731.209Snjoly	The shared objects file extension has been changed from .so to
741.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
751.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
761.209Snjoly	your object directories.
771.209Snjoly
781.208Sroy20100204:
791.208Sroy	The termcap database has been removed from the sources,
801.208Sroy	but has not been marked obsolete so it is not removed
811.208Sroy	from the system when upgrading.
821.208Sroy	As such, you will need to remove them from your object
831.208Sroy	and destination directories.
841.208Sroy
851.203Sdyoung20091101:
861.205Sdholland        After updating, it may be necessary to make the 'cleandir'
871.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
881.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
891.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
901.203Sdyoung
911.202Smrg20091001:
921.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
931.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
941.206Sdholland
951.206Sdholland20091001:
961.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
971.202Smrg	symlink, failing the build.  Delete the link, and the subdir
981.202Smrg	it is in, and retry your build.
991.202Smrg
1001.201Sdsl20090718:
1011.201Sdsl	libc build changed so that strchr() provides the extra entry
1021.201Sdsl	point for index(). Update build of libc.a (and libc_pic.a)
1031.201Sdsl	may fail because the archive contains the unwanted index.o.
1041.201Sdsl	(Similarly for strrchr() and rindex().)
1051.201Sdsl
1061.198Smrg20090709:
1071.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
1081.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
1091.198Smrg
1101.197Smrg20090616:
1111.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
1121.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
1131.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
1141.197Smrg	subdirectory has been changed into a file, and this needs to
1151.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
1161.197Smrg
1171.195Sperry20090501:
1181.195Sperry	Several new functions were added to string.h/libc, and this
1191.195Sperry	can cause autoconf problems during the tool build for people
1201.195Sperry	who fail to clean out their tools objects properly. If you
1211.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
1221.195Sperry	failure during the tool build, clean out all your tools
1231.195Sperry	objects and start again.
1241.195Sperry
1251.194Smrg20090325:
1261.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
1271.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
1281.194Smrg
1291.192Sskrll20090126:
1301.207Smbalmer	The __posix_fadvise50 system call changed assembly stub type. You
1311.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
1321.207Smbalmer	to avoid using the old assembly stub.
1331.192Sskrll
1341.191Sjoerg20090202:
1351.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
1361.191Sjoerg	detection.  It is recommented to rebuild the cache with
1371.191Sjoerg	``pkg_admin rebuild''.
1381.191Sjoerg
1391.184Schristos20090110:
1401.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
1411.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
1421.188Schristos	   This is needed even in the MODULAR kernel because there is
1431.188Schristos	   conditionally compiled code in rtsock.c.
1441.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
1451.184Schristos	   before installing.
1461.184Schristos	3. If you don't use build.sh and you build directly to root, and
1471.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
1481.184Schristos	   are installed properly, and start building libraries first libc
1491.184Schristos	   and libutil, install them and then continue building all the
1501.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
1511.184Schristos	   the new libraries are installed, you can restart the build.
1521.184Schristos	4. If you compile packages and you notice link time warnings,
1531.189Shubertf	   rebuild the required packages to update their shared libraries.
1541.189Shubertf	   Any package you rebuild will require rebuilding all the packages
1551.189Shubertf	   that depend on it.
1561.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
1571.186Schristos	   will be upgraded and it will not be backwards compatible.
1581.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
1591.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
1601.190Sapb	   for utmp. You are better off removing the old files after
1611.190Sapb	   upgrading.  The automated clearing of /var/run during
1621.190Sapb	   boot, and the automated rotating of files in /var/log by
1631.190Sapb	   newsyslog(8), may mean that you do not have to remove the
1641.190Sapb	   files manually.
1651.190Sapb	7. The optional accounting file (/var/account/acct, see
1661.190Sapb	   accton(8)) has not been versioned, and will need to be
1671.190Sapb	   removed.  The automatic rotation of the accounting file by
1681.190Sapb	   /etc/daily limits the bad consequences of failure to remove
1691.190Sapb	   the file.
1701.196Sdholland	8. Application software that writes time_t to binary files on
1711.196Sdholland	   disk will break or need attention. Most notably: if you are
1721.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
1731.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
1741.185Sjmcneill
1751.183Spgoyette20081219:
1761.183Spgoyette	config(1) has been updated, and one of the files it creates -
1771.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
1781.183Spgoyette	(done automatically by build.sh) and then you need to rerun
1791.183Spgoyette	config on all kernel configuration files before rebuilding those
1801.183Spgoyette	kernels.
1811.183Spgoyette
1821.181Scube20081205:
1831.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
1841.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
1851.181Scube	set and will appear as extra files for MKX11=no update builds.
1861.178Slukem
1871.179Stsutsui20081122:
1881.182Stsutsui	On i386, various kernel options(4) in GENERIC including
1891.180Swiz	file systems have been disabled and moved into kernel modules.
1901.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
1911.179Stsutsui	following files as well as a new GENERIC kernel:
1921.179Stsutsui
1931.179Stsutsui	- build and install kernel modules from src/sys/modules
1941.179Stsutsui
1951.179Stsutsui	- install the latest bootloader, which will load a module
1961.180Swiz	  for the file system from which the kernel is loaded automatically
1971.179Stsutsui
1981.180Swiz	If you have to load your kernel from a file system which is not of
1991.180Swiz	the same type as the root file system, you have to load the necessary
2001.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
2011.179Stsutsui
2021.178Slukem20080827:
2031.178Slukem	If you built and installed a libc from sources between
2041.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
2051.178Slukem	which results in false errors reported by lint(1).
2061.178Slukem	Since this breaks the libc build itself, manual help is
2071.180Swiz	needed -- lint must be disabled temporarily, e.g.:
2081.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
2091.178Slukem
2101.177Schristos20080813:
2111.177Schristos	MKDEBUG build was broken because the .depend files did not know
2121.177Schristos	about .go files. You need to remove all .depend files and rebuild.
2131.177Schristos
2141.200Sdholland20080802:
2151.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
2161.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
2171.200Sdholland	for -current.
2181.200Sdholland
2191.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
2201.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
2211.200Sdholland	be recompiled.
2221.200Sdholland
2231.200Sdholland	One way to find affected pkgsrc packages:
2241.200Sdholland
2251.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
2261.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
2271.200Sdholland
2281.175Ssimonb20080731:
2291.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
2301.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
2311.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
2321.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
2331.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
2341.176Ssimonb	also requires the super block to be in the UFS2 format.  You
2351.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
2361.175Ssimonb
2371.174Slukem20080721:
2381.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
2391.174Slukem	isn't defined.
2401.174Slukem
2411.173Sfreza20080531:
2421.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
2431.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
2441.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
2451.173Sfreza	won't work correctly. The following sequence of commands:
2461.173Sfreza
2471.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
2481.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
2491.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
2501.173Sfreza
2511.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
2521.173Sfreza
2531.172Slukem20080503:
2541.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
2551.172Slukem
2561.171She20080521:
2571.171She	For a while, unprivileged UPDATE builds would fail to
2581.171She	succeed at the checkflist stage, complaining that
2591.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
2601.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
2611.171She	If you already hit this problem, update the .mk file,
2621.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
2631.171She
2641.174Slukem20080303:
2651.174Slukem	Linker warnings are now fatal if $WARNS>0.
2661.174Slukem
2671.170Schristos20080126:
2681.170Schristos	The posix_fadvise system call has been changed from an assembly
2691.170Schristos	stub, to a c file that calls an assembly stub. You need to
2701.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
2711.170Schristos	avoid using the old assembly stub.
2721.170Schristos
2731.168Sjoerg20071209:
2741.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
2751.168Sjoerg	get ACPI errors before the attachment, please update your kernel
2761.169Swiz	configuration file appropriately or see GENERIC for more details.
2771.168Sjoerg
2781.166Sxtraeme20071115:
2791.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
2801.166Sxtraeme	argument specified in the kernel configuration file is not valid
2811.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
2821.166Sxtraeme	rather than the EC address port. Please update your kernel
2831.167Swiz	configuration file appropriately or see GENERIC for more details.
2841.166Sxtraeme
2851.165Sjmmv20071028:
2861.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
2871.165Sjmmv	You need to update any custom kernel configuration file you have
2881.165Sjmmv	to remove any references to pccons (which includes removing the
2891.165Sjmmv	now useless XSERVER option) and replace them with the correct
2901.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
2911.165Sjmmv	for more details.
2921.165Sjmmv
2931.164Sgdt20070913:
2941.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
2951.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
2961.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
2971.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
2981.164Sgdt	could not enumerate interfaces.  (These are noted because
2991.164Sgdt	normal kernel/userspace version matching hygiene is not
3001.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
3011.164Sgdt	and userland are from after 20070913.
3021.164Sgdt
3031.163Sjoerg20070703:
3041.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
3051.199Sdholland	calls the target-specific strip program, and the logic to pass
3061.199Sdholland	down STRIP from make has been removed.  This requires a
3071.199Sdholland	re-installation of tools.
3081.163Sjoerg
3091.161Sdsl20070422:
3101.161Sdsl	The way OS emulations lookup filenames inside the emulation root
3111.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
3121.161Sdsl	to userspace) namei() and lookup() directly check the emulation
3131.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
3141.167Swiz	root file system will be relative to that file system - unless they
3151.161Sdsl	start /../ this is useful when the emulated root is a real install
3161.161Sdsl	that has such links.
3171.161Sdsl	This might affect symlinks that have been added to reference outside
3181.161Sdsl	the emulated root.
3191.161Sdsl
3201.160Sjmcneill20070412:
3211.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
3221.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
3231.160Sjmcneill	example.
3241.160Sjmcneill
3251.159Sgdt20070319:
3261.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
3271.159Sgdt        on many platforms due to incorrect flags settings.  If you
3281.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
3291.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
3301.159Sgdt	rebuild of object files that might have been built
3311.159Sgdt	incorrectly, and ensure that you have at least
3321.159Sgdt	src/lib/libc/Makefile 1.130.
3331.159Sgdt
3341.158Sdbj20070210: 
3351.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
3361.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
3371.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
3381.158Sdbj        will allow dependencies on those files to get get rebuilt
3391.158Sdbj
3401.157Sapb20070209:
3411.157Sapb        The threading model was changed when the newlock2 branch
3421.157Sapb        was merged to NetBSD-current.  If you boot with a new
3431.157Sapb        kernel (version 4.99.10), then you also need a new pthread
3441.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
3451.157Sapb        an old kernel, then you need the old pthread library
3461.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
3471.157Sapb        the pthread library in sync, old threaded applications should
3481.157Sapb        continue to work with an old or new kernel.  Note that named(8)
3491.157Sapb	is the only threaded application in the base system.
3501.157Sapb
3511.154She20061214:
3521.154She	Following the move of string_to_flags() and flags_to_string()
3531.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
3541.154She	will need to do a "make cleandir" in
3551.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
3561.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
3571.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
3581.156She		as the installation images in distrib/
3591.154She	in order to excise stale references to the old stat_flags.h header
3601.154She	file in the ls sources -- stat_flags.h has been removed.
3611.154She
3621.152Schristos20061108:
3631.152Schristos	The configure script used in the src/tools/gcc compiler has been
3641.152Schristos	changed to indicate that our libc has ssp support built-in and
3651.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
3661.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
3671.152Schristos
3681.151Srpaulo20061009:
3691.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
3701.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
3711.151Srpaulo
3721.150Sbjh2120060814:
3731.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
3741.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
3751.150Sbjh21	kernel configuration for an example.  X servers from the last
3761.150Sbjh21	few years should cope.
3771.150Sbjh21
3781.149Schristos20060703:
3791.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
3801.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
3811.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
3821.149Schristos
3831.148Sdogcow20060627:
3841.148Sdogcow	socket(2) has changed, and its system call has been versioned.
3851.148Sdogcow	For userlands with the old version of socket(2), make sure that
3861.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
3871.148Sdogcow	errors will result.
3881.148Sdogcow
3891.1SabsHints for a more successful build:
3901.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3911.123Sjmc    Use build.sh, but do not use its "expert mode":
3921.132Sjmmv	This will automatically build the tools in the
3931.123Sjmc	   correct order, and it will keep the tools and the
3941.123Sjmc	   new build products from interfering with the running
3951.123Sjmc	   system.  This will allow you to ignore most of the
3961.123Sjmc	   other advice in this file.
3971.2Smrg    Build a new kernel first:
3981.2Smrg	This makes sure that any new system calls or features
3991.2Smrg	   expected by the new userland will be present.  This
4001.2Smrg	   helps to avoid critical errors when upgrading.
4011.1Sabs    Use object directories:
4021.1Sabs	This helps to keep stale object
4031.1Sabs	   files from polluting the build if a Makefile "forgets"
4041.1Sabs	   about one.  It also makes it easier to clean up after
4051.1Sabs	   a build.  It's also necessary if you want to use the
4061.1Sabs	   same source tree for multiple machines.
4071.123Sjmc	   To use object directories with build.sh:
4081.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
4091.123Sjmc	   To use object directories without using build.sh:
4101.1Sabs	    a) cd /usr/src ; make cleandir
4111.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
4121.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
4131.1Sabs	    d) cd /usr/src ; make build
4141.2Smrg	   Note that running "make obj" in a directory will create
4151.2Smrg	   in obj.$MACHINE directory.
4161.1Sabs    Build to a DESTDIR:
4171.123Sjmc	This helps to keep old installed files (especially libraries)
4181.123Sjmc	   from interfering with the new build.
4191.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
4201.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
4211.123Sjmc	   environment variable before running make build.  It should be
4221.123Sjmc	   set to the pathname of an initially empty directory.
4231.123Sjmc	   Problems: if you do not use build.sh, you might need to
4241.123Sjmc		update critical utilities without using DESTDIR since
4251.123Sjmc		nothing is executed from what is installed in DESTDIR.
4261.123Sjmc		(See critical utils, below.)
4271.1Sabs    Build often:
4281.1Sabs	This keeps critical utilities current enough to not choke
4291.1Sabs	on any other part of the source tree that depends on up to
4301.123Sjmc	date functionality.  If you use build.sh, you should not have
4311.123Sjmc	this problem.
4321.1Sabs 
4331.1SabsWhat to do if things don't work:
4341.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4351.1SabsWhen things don't work there is usually a few things that commonly
4361.1Sabsshould be done.
4371.1Sabs    1)	make includes
4381.1Sabs	This should be done automatically by make build.
4391.1Sabs    2)  cd share/mk && make install
4401.1Sabs	Again, automatically done by make build.
4411.1Sabs
4421.1SabsFailsafe rebuild of a small part of the tree:
4431.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4441.1SabsTo make sure you rebuild something correctly you want to do
4451.1Sabssomething like the following:
4461.1Sabs    1)  Make sure the includes and .mk files are up to date.
4471.1Sabs    2)  Make sure any program used to build the particular
4481.1Sabs	utility is up to date.  (yacc, lex, etc...)
4491.1Sabs    3)  cd ...path/to/util...
4501.1Sabs	make cleandir
4511.1Sabs	rm ...all obj directories...
4521.1Sabs	make cleandir			# yes, again
4531.1Sabs	make obj
4541.1Sabs	make depend && make
4551.1Sabs
4561.1SabsFailsafe rebuild of the entire tree:
4571.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4581.1SabsIf you really want to make sure the source tree is clean and
4591.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
4601.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
4611.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
4621.1Sabs
4631.1Sabs---cut here---
4641.1Sabs#!/bin/sh
4651.1Sabs. /etc/mk.conf
4661.1Sabs
4671.58Slukemif [ -z $NETBSDSRCDIR ] ; then
4681.58Slukem    NETBSDSRCDIR=/usr/src
4691.1Sabsfi
4701.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
4711.1Sabs    echo Unable to find sources
4721.1Sabs    exit 1
4731.1Sabsfi
4741.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
4751.1Sabs
4761.1Sabsif [ -z $BSDOBJDIR ] ; then
4771.1Sabs    BSDOBJDIR=/usr/obj
4781.1Sabsfi
4791.1Sabsif [ -d $BSDOBJDIR ] ; then
4801.1Sabs    rm -rf $BSDOBJDIR
4811.1Sabsfi
4821.1Sabs
4831.58Slukemcd $NETBSDSRCDIR && make cleandir
4841.1Sabs
4851.1Sabs---cut here---
4861.1Sabs
4871.1SabsCritical utilities:
4881.1Sabs^^^^^^^^^^^^^^^^^^^
4891.3Sitojun	usr.bin/compile_et
4901.1Sabs	usr.bin/make
4911.1Sabs	usr.bin/yacc
4921.1Sabs	usr.bin/lex
4931.11Slukem	usr.bin/xlint
4941.142Sdrochner	usr.bin/config
4951.1Sabs
4961.34SsimonbOther problems and possible solutions:
4971.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4981.1SabsSymptom:Complaints involving a Makefile.
4991.17SerhFix:	Rebuild usr.bin/make:
5001.17Serh	cd usr.bin/make && make && make install
5011.111Ssimonb	Or, a failsafe method if that doesn't work:
5021.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
5031.17Serh
5041.1SabsFix:	Make sure .mk files are up to date.
5051.1Sabs	cd share/mk && make install
5061.2Smrg
5071.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
5081.142SdrochnerFix:	Rebuild usr.bin/config
5091.1Sabs
5101.1SabsSymptom:
5111.1SabsFix:	Rebuild usr.bin/yacc
5121.1Sabs
5131.1SabsSymptom:
5141.1SabsFix:	Rebuild usr.bin/lex
5151.1Sabs
5161.1SabsSymptom:
5171.1SabsFix:	rm /usr/lib/libbfd.a
5181.4Sitojun
5191.4SitojunSymptom:Obsolete intermediate files are used during compilation
5201.4SitojunFix:	Try the following sequence of commands in the directory in question.
5211.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
5221.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
5231.4Sitojun	may remain.  The command tries to clean everything up)
5241.5Swiz
5251.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
5261.207Smbalmer	pointer type
5271.5SwizFix:	Rebuild and install usr.bin/menuc
5281.12Sitojun
5291.12SitojunSymptom:mklocale not found during build in share/locale/ctype
5301.12SitojunFix:	Build and install usr.bin/mklocale
5311.13Sdogcow
5321.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
5331.13SdogcowFix:    Rebuild and install lib/libc
5341.13Sdogcow
5351.142SdrochnerSymptom:usr.bin/config fails to build.
5361.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
5371.13Sdogcow
5381.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
5391.19ScgdFix:    Rebuild and install lib/libc
5401.24Sabs
5411.24SabsSymptom:lint does not understand the '-X' option
5421.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
543