UPDATING revision 1.212
11.212Smrg$NetBSD: UPDATING,v 1.212 2010/05/22 11:10:59 mrg 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.211Stnozaki20100522:
201.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
211.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
221.212Smrg	build problems with xsrc.
231.212Smrg
241.212Smrg20100522:
251.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
261.211Stnozaki	include ctype_local.h, so you have to make cleandir tools/mklocale.
271.211Stnozaki
281.210Schristos20100520:
291.210Schristos	The location of the xkb compiled descriptions has changed. Please
301.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
311.210Schristos
321.209Snjoly20100222:
331.209Snjoly	The shared objects file extension has been changed from .so to
341.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
351.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
361.209Snjoly	your object directories.
371.209Snjoly
381.208Sroy20100204:
391.208Sroy	The termcap database has been removed from the sources,
401.208Sroy	but has not been marked obsolete so it is not removed
411.208Sroy	from the system when upgrading.
421.208Sroy	As such, you will need to remove them from your object
431.208Sroy	and destination directories.
441.208Sroy
451.203Sdyoung20091101:
461.205Sdholland        After updating, it may be necessary to make the 'cleandir'
471.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
481.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
491.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
501.203Sdyoung
511.202Smrg20091001:
521.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
531.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
541.206Sdholland
551.206Sdholland20091001:
561.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
571.202Smrg	symlink, failing the build.  Delete the link, and the subdir
581.202Smrg	it is in, and retry your build.
591.202Smrg
601.201Sdsl20090718:
611.201Sdsl	libc build changed so that strchr() provides the extra entry
621.201Sdsl	point for index(). Update build of libc.a (and libc_pic.a)
631.201Sdsl	may fail because the archive contains the unwanted index.o.
641.201Sdsl	(Similarly for strrchr() and rindex().)
651.201Sdsl
661.198Smrg20090709:
671.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
681.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
691.198Smrg
701.197Smrg20090616:
711.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
721.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
731.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
741.197Smrg	subdirectory has been changed into a file, and this needs to
751.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
761.197Smrg
771.195Sperry20090501:
781.195Sperry	Several new functions were added to string.h/libc, and this
791.195Sperry	can cause autoconf problems during the tool build for people
801.195Sperry	who fail to clean out their tools objects properly. If you
811.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
821.195Sperry	failure during the tool build, clean out all your tools
831.195Sperry	objects and start again.
841.195Sperry
851.194Smrg20090325:
861.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
871.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
881.194Smrg
891.192Sskrll20090126:
901.207Smbalmer	The __posix_fadvise50 system call changed assembly stub type. You
911.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
921.207Smbalmer	to avoid using the old assembly stub.
931.192Sskrll
941.191Sjoerg20090202:
951.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
961.191Sjoerg	detection.  It is recommented to rebuild the cache with
971.191Sjoerg	``pkg_admin rebuild''.
981.191Sjoerg
991.184Schristos20090110:
1001.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
1011.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
1021.188Schristos	   This is needed even in the MODULAR kernel because there is
1031.188Schristos	   conditionally compiled code in rtsock.c.
1041.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
1051.184Schristos	   before installing.
1061.184Schristos	3. If you don't use build.sh and you build directly to root, and
1071.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
1081.184Schristos	   are installed properly, and start building libraries first libc
1091.184Schristos	   and libutil, install them and then continue building all the
1101.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
1111.184Schristos	   the new libraries are installed, you can restart the build.
1121.184Schristos	4. If you compile packages and you notice link time warnings,
1131.189Shubertf	   rebuild the required packages to update their shared libraries.
1141.189Shubertf	   Any package you rebuild will require rebuilding all the packages
1151.189Shubertf	   that depend on it.
1161.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
1171.186Schristos	   will be upgraded and it will not be backwards compatible.
1181.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
1191.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
1201.190Sapb	   for utmp. You are better off removing the old files after
1211.190Sapb	   upgrading.  The automated clearing of /var/run during
1221.190Sapb	   boot, and the automated rotating of files in /var/log by
1231.190Sapb	   newsyslog(8), may mean that you do not have to remove the
1241.190Sapb	   files manually.
1251.190Sapb	7. The optional accounting file (/var/account/acct, see
1261.190Sapb	   accton(8)) has not been versioned, and will need to be
1271.190Sapb	   removed.  The automatic rotation of the accounting file by
1281.190Sapb	   /etc/daily limits the bad consequences of failure to remove
1291.190Sapb	   the file.
1301.196Sdholland	8. Application software that writes time_t to binary files on
1311.196Sdholland	   disk will break or need attention. Most notably: if you are
1321.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
1331.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
1341.185Sjmcneill
1351.183Spgoyette20081219:
1361.183Spgoyette	config(1) has been updated, and one of the files it creates -
1371.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
1381.183Spgoyette	(done automatically by build.sh) and then you need to rerun
1391.183Spgoyette	config on all kernel configuration files before rebuilding those
1401.183Spgoyette	kernels.
1411.183Spgoyette
1421.181Scube20081205:
1431.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
1441.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
1451.181Scube	set and will appear as extra files for MKX11=no update builds.
1461.178Slukem
1471.179Stsutsui20081122:
1481.182Stsutsui	On i386, various kernel options(4) in GENERIC including
1491.180Swiz	file systems have been disabled and moved into kernel modules.
1501.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
1511.179Stsutsui	following files as well as a new GENERIC kernel:
1521.179Stsutsui
1531.179Stsutsui	- build and install kernel modules from src/sys/modules
1541.179Stsutsui
1551.179Stsutsui	- install the latest bootloader, which will load a module
1561.180Swiz	  for the file system from which the kernel is loaded automatically
1571.179Stsutsui
1581.180Swiz	If you have to load your kernel from a file system which is not of
1591.180Swiz	the same type as the root file system, you have to load the necessary
1601.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
1611.179Stsutsui
1621.178Slukem20080827:
1631.178Slukem	If you built and installed a libc from sources between
1641.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
1651.178Slukem	which results in false errors reported by lint(1).
1661.178Slukem	Since this breaks the libc build itself, manual help is
1671.180Swiz	needed -- lint must be disabled temporarily, e.g.:
1681.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
1691.178Slukem
1701.177Schristos20080813:
1711.177Schristos	MKDEBUG build was broken because the .depend files did not know
1721.177Schristos	about .go files. You need to remove all .depend files and rebuild.
1731.177Schristos
1741.200Sdholland20080802:
1751.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
1761.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
1771.200Sdholland	for -current.
1781.200Sdholland
1791.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
1801.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
1811.200Sdholland	be recompiled.
1821.200Sdholland
1831.200Sdholland	One way to find affected pkgsrc packages:
1841.200Sdholland
1851.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
1861.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
1871.200Sdholland
1881.175Ssimonb20080731:
1891.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
1901.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
1911.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
1921.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
1931.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
1941.176Ssimonb	also requires the super block to be in the UFS2 format.  You
1951.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
1961.175Ssimonb
1971.174Slukem20080721:
1981.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
1991.174Slukem	isn't defined.
2001.174Slukem
2011.173Sfreza20080531:
2021.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
2031.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
2041.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
2051.173Sfreza	won't work correctly. The following sequence of commands:
2061.173Sfreza
2071.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
2081.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
2091.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
2101.173Sfreza
2111.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
2121.173Sfreza
2131.172Slukem20080503:
2141.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
2151.172Slukem
2161.171She20080521:
2171.171She	For a while, unprivileged UPDATE builds would fail to
2181.171She	succeed at the checkflist stage, complaining that
2191.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
2201.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
2211.171She	If you already hit this problem, update the .mk file,
2221.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
2231.171She
2241.174Slukem20080303:
2251.174Slukem	Linker warnings are now fatal if $WARNS>0.
2261.174Slukem
2271.170Schristos20080126:
2281.170Schristos	The posix_fadvise system call has been changed from an assembly
2291.170Schristos	stub, to a c file that calls an assembly stub. You need to
2301.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
2311.170Schristos	avoid using the old assembly stub.
2321.170Schristos
2331.168Sjoerg20071209:
2341.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
2351.168Sjoerg	get ACPI errors before the attachment, please update your kernel
2361.169Swiz	configuration file appropriately or see GENERIC for more details.
2371.168Sjoerg
2381.166Sxtraeme20071115:
2391.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
2401.166Sxtraeme	argument specified in the kernel configuration file is not valid
2411.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
2421.166Sxtraeme	rather than the EC address port. Please update your kernel
2431.167Swiz	configuration file appropriately or see GENERIC for more details.
2441.166Sxtraeme
2451.165Sjmmv20071028:
2461.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
2471.165Sjmmv	You need to update any custom kernel configuration file you have
2481.165Sjmmv	to remove any references to pccons (which includes removing the
2491.165Sjmmv	now useless XSERVER option) and replace them with the correct
2501.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
2511.165Sjmmv	for more details.
2521.165Sjmmv
2531.164Sgdt20070913:
2541.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
2551.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
2561.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
2571.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
2581.164Sgdt	could not enumerate interfaces.  (These are noted because
2591.164Sgdt	normal kernel/userspace version matching hygiene is not
2601.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
2611.164Sgdt	and userland are from after 20070913.
2621.164Sgdt
2631.163Sjoerg20070703:
2641.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
2651.199Sdholland	calls the target-specific strip program, and the logic to pass
2661.199Sdholland	down STRIP from make has been removed.  This requires a
2671.199Sdholland	re-installation of tools.
2681.163Sjoerg
2691.161Sdsl20070422:
2701.161Sdsl	The way OS emulations lookup filenames inside the emulation root
2711.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
2721.161Sdsl	to userspace) namei() and lookup() directly check the emulation
2731.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
2741.167Swiz	root file system will be relative to that file system - unless they
2751.161Sdsl	start /../ this is useful when the emulated root is a real install
2761.161Sdsl	that has such links.
2771.161Sdsl	This might affect symlinks that have been added to reference outside
2781.161Sdsl	the emulated root.
2791.161Sdsl
2801.160Sjmcneill20070412:
2811.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
2821.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
2831.160Sjmcneill	example.
2841.160Sjmcneill
2851.159Sgdt20070319:
2861.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
2871.159Sgdt        on many platforms due to incorrect flags settings.  If you
2881.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
2891.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
2901.159Sgdt	rebuild of object files that might have been built
2911.159Sgdt	incorrectly, and ensure that you have at least
2921.159Sgdt	src/lib/libc/Makefile 1.130.
2931.159Sgdt
2941.158Sdbj20070210: 
2951.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
2961.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
2971.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
2981.158Sdbj        will allow dependencies on those files to get get rebuilt
2991.158Sdbj
3001.157Sapb20070209:
3011.157Sapb        The threading model was changed when the newlock2 branch
3021.157Sapb        was merged to NetBSD-current.  If you boot with a new
3031.157Sapb        kernel (version 4.99.10), then you also need a new pthread
3041.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
3051.157Sapb        an old kernel, then you need the old pthread library
3061.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
3071.157Sapb        the pthread library in sync, old threaded applications should
3081.157Sapb        continue to work with an old or new kernel.  Note that named(8)
3091.157Sapb	is the only threaded application in the base system.
3101.157Sapb
3111.154She20061214:
3121.154She	Following the move of string_to_flags() and flags_to_string()
3131.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
3141.154She	will need to do a "make cleandir" in
3151.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
3161.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
3171.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
3181.156She		as the installation images in distrib/
3191.154She	in order to excise stale references to the old stat_flags.h header
3201.154She	file in the ls sources -- stat_flags.h has been removed.
3211.154She
3221.152Schristos20061108:
3231.152Schristos	The configure script used in the src/tools/gcc compiler has been
3241.152Schristos	changed to indicate that our libc has ssp support built-in and
3251.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
3261.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
3271.152Schristos
3281.151Srpaulo20061009:
3291.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
3301.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
3311.151Srpaulo
3321.150Sbjh2120060814:
3331.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
3341.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
3351.150Sbjh21	kernel configuration for an example.  X servers from the last
3361.150Sbjh21	few years should cope.
3371.150Sbjh21
3381.149Schristos20060703:
3391.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
3401.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
3411.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
3421.149Schristos
3431.148Sdogcow20060627:
3441.148Sdogcow	socket(2) has changed, and its system call has been versioned.
3451.148Sdogcow	For userlands with the old version of socket(2), make sure that
3461.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
3471.148Sdogcow	errors will result.
3481.148Sdogcow
3491.1SabsHints for a more successful build:
3501.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3511.123Sjmc    Use build.sh, but do not use its "expert mode":
3521.132Sjmmv	This will automatically build the tools in the
3531.123Sjmc	   correct order, and it will keep the tools and the
3541.123Sjmc	   new build products from interfering with the running
3551.123Sjmc	   system.  This will allow you to ignore most of the
3561.123Sjmc	   other advice in this file.
3571.2Smrg    Build a new kernel first:
3581.2Smrg	This makes sure that any new system calls or features
3591.2Smrg	   expected by the new userland will be present.  This
3601.2Smrg	   helps to avoid critical errors when upgrading.
3611.1Sabs    Use object directories:
3621.1Sabs	This helps to keep stale object
3631.1Sabs	   files from polluting the build if a Makefile "forgets"
3641.1Sabs	   about one.  It also makes it easier to clean up after
3651.1Sabs	   a build.  It's also necessary if you want to use the
3661.1Sabs	   same source tree for multiple machines.
3671.123Sjmc	   To use object directories with build.sh:
3681.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
3691.123Sjmc	   To use object directories without using build.sh:
3701.1Sabs	    a) cd /usr/src ; make cleandir
3711.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
3721.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
3731.1Sabs	    d) cd /usr/src ; make build
3741.2Smrg	   Note that running "make obj" in a directory will create
3751.2Smrg	   in obj.$MACHINE directory.
3761.1Sabs    Build to a DESTDIR:
3771.123Sjmc	This helps to keep old installed files (especially libraries)
3781.123Sjmc	   from interfering with the new build.
3791.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
3801.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
3811.123Sjmc	   environment variable before running make build.  It should be
3821.123Sjmc	   set to the pathname of an initially empty directory.
3831.123Sjmc	   Problems: if you do not use build.sh, you might need to
3841.123Sjmc		update critical utilities without using DESTDIR since
3851.123Sjmc		nothing is executed from what is installed in DESTDIR.
3861.123Sjmc		(See critical utils, below.)
3871.1Sabs    Build often:
3881.1Sabs	This keeps critical utilities current enough to not choke
3891.1Sabs	on any other part of the source tree that depends on up to
3901.123Sjmc	date functionality.  If you use build.sh, you should not have
3911.123Sjmc	this problem.
3921.1Sabs 
3931.1SabsWhat to do if things don't work:
3941.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3951.1SabsWhen things don't work there is usually a few things that commonly
3961.1Sabsshould be done.
3971.1Sabs    1)	make includes
3981.1Sabs	This should be done automatically by make build.
3991.1Sabs    2)  cd share/mk && make install
4001.1Sabs	Again, automatically done by make build.
4011.1Sabs
4021.1SabsFailsafe rebuild of a small part of the tree:
4031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4041.1SabsTo make sure you rebuild something correctly you want to do
4051.1Sabssomething like the following:
4061.1Sabs    1)  Make sure the includes and .mk files are up to date.
4071.1Sabs    2)  Make sure any program used to build the particular
4081.1Sabs	utility is up to date.  (yacc, lex, etc...)
4091.1Sabs    3)  cd ...path/to/util...
4101.1Sabs	make cleandir
4111.1Sabs	rm ...all obj directories...
4121.1Sabs	make cleandir			# yes, again
4131.1Sabs	make obj
4141.1Sabs	make depend && make
4151.1Sabs
4161.1SabsFailsafe rebuild of the entire tree:
4171.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4181.1SabsIf you really want to make sure the source tree is clean and
4191.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
4201.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
4211.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
4221.1Sabs
4231.1Sabs---cut here---
4241.1Sabs#!/bin/sh
4251.1Sabs. /etc/mk.conf
4261.1Sabs
4271.58Slukemif [ -z $NETBSDSRCDIR ] ; then
4281.58Slukem    NETBSDSRCDIR=/usr/src
4291.1Sabsfi
4301.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
4311.1Sabs    echo Unable to find sources
4321.1Sabs    exit 1
4331.1Sabsfi
4341.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
4351.1Sabs
4361.1Sabsif [ -z $BSDOBJDIR ] ; then
4371.1Sabs    BSDOBJDIR=/usr/obj
4381.1Sabsfi
4391.1Sabsif [ -d $BSDOBJDIR ] ; then
4401.1Sabs    rm -rf $BSDOBJDIR
4411.1Sabsfi
4421.1Sabs
4431.58Slukemcd $NETBSDSRCDIR && make cleandir
4441.1Sabs
4451.1Sabs---cut here---
4461.1Sabs
4471.1SabsCritical utilities:
4481.1Sabs^^^^^^^^^^^^^^^^^^^
4491.3Sitojun	usr.bin/compile_et
4501.1Sabs	usr.bin/make
4511.1Sabs	usr.bin/yacc
4521.1Sabs	usr.bin/lex
4531.11Slukem	usr.bin/xlint
4541.142Sdrochner	usr.bin/config
4551.1Sabs
4561.34SsimonbOther problems and possible solutions:
4571.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4581.1SabsSymptom:Complaints involving a Makefile.
4591.17SerhFix:	Rebuild usr.bin/make:
4601.17Serh	cd usr.bin/make && make && make install
4611.111Ssimonb	Or, a failsafe method if that doesn't work:
4621.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
4631.17Serh
4641.1SabsFix:	Make sure .mk files are up to date.
4651.1Sabs	cd share/mk && make install
4661.2Smrg
4671.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
4681.142SdrochnerFix:	Rebuild usr.bin/config
4691.1Sabs
4701.1SabsSymptom:
4711.1SabsFix:	Rebuild usr.bin/yacc
4721.1Sabs
4731.1SabsSymptom:
4741.1SabsFix:	Rebuild usr.bin/lex
4751.1Sabs
4761.1SabsSymptom:
4771.1SabsFix:	rm /usr/lib/libbfd.a
4781.4Sitojun
4791.4SitojunSymptom:Obsolete intermediate files are used during compilation
4801.4SitojunFix:	Try the following sequence of commands in the directory in question.
4811.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
4821.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
4831.4Sitojun	may remain.  The command tries to clean everything up)
4841.5Swiz
4851.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
4861.207Smbalmer	pointer type
4871.5SwizFix:	Rebuild and install usr.bin/menuc
4881.12Sitojun
4891.12SitojunSymptom:mklocale not found during build in share/locale/ctype
4901.12SitojunFix:	Build and install usr.bin/mklocale
4911.13Sdogcow
4921.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
4931.13SdogcowFix:    Rebuild and install lib/libc
4941.13Sdogcow
4951.142SdrochnerSymptom:usr.bin/config fails to build.
4961.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
4971.13Sdogcow
4981.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
4991.19ScgdFix:    Rebuild and install lib/libc
5001.24Sabs
5011.24SabsSymptom:lint does not understand the '-X' option
5021.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
503