UPDATING revision 1.209
11.209Snjoly$NetBSD: UPDATING,v 1.209 2010/02/22 12:35:32 njoly 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.209Snjoly20100222:
201.209Snjoly	The shared objects file extension has been changed from .so to
211.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
221.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
231.209Snjoly	your object directories.
241.209Snjoly
251.208Sroy20100204:
261.208Sroy	The termcap database has been removed from the sources,
271.208Sroy	but has not been marked obsolete so it is not removed
281.208Sroy	from the system when upgrading.
291.208Sroy	As such, you will need to remove them from your object
301.208Sroy	and destination directories.
311.208Sroy
321.203Sdyoung20091101:
331.205Sdholland        After updating, it may be necessary to make the 'cleandir'
341.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
351.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
361.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
371.203Sdyoung
381.202Smrg20091001:
391.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
401.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
411.206Sdholland
421.206Sdholland20091001:
431.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
441.202Smrg	symlink, failing the build.  Delete the link, and the subdir
451.202Smrg	it is in, and retry your build.
461.202Smrg
471.201Sdsl20090718:
481.201Sdsl	libc build changed so that strchr() provides the extra entry
491.201Sdsl	point for index(). Update build of libc.a (and libc_pic.a)
501.201Sdsl	may fail because the archive contains the unwanted index.o.
511.201Sdsl	(Similarly for strrchr() and rindex().)
521.201Sdsl
531.198Smrg20090709:
541.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
551.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
561.198Smrg
571.197Smrg20090616:
581.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
591.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
601.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
611.197Smrg	subdirectory has been changed into a file, and this needs to
621.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
631.197Smrg
641.195Sperry20090501:
651.195Sperry	Several new functions were added to string.h/libc, and this
661.195Sperry	can cause autoconf problems during the tool build for people
671.195Sperry	who fail to clean out their tools objects properly. If you
681.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
691.195Sperry	failure during the tool build, clean out all your tools
701.195Sperry	objects and start again.
711.195Sperry
721.194Smrg20090325:
731.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
741.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
751.194Smrg
761.192Sskrll20090126:
771.207Smbalmer	The __posix_fadvise50 system call changed assembly stub type. You
781.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
791.207Smbalmer	to avoid using the old assembly stub.
801.192Sskrll
811.191Sjoerg20090202:
821.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
831.191Sjoerg	detection.  It is recommented to rebuild the cache with
841.191Sjoerg	``pkg_admin rebuild''.
851.191Sjoerg
861.184Schristos20090110:
871.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
881.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
891.188Schristos	   This is needed even in the MODULAR kernel because there is
901.188Schristos	   conditionally compiled code in rtsock.c.
911.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
921.184Schristos	   before installing.
931.184Schristos	3. If you don't use build.sh and you build directly to root, and
941.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
951.184Schristos	   are installed properly, and start building libraries first libc
961.184Schristos	   and libutil, install them and then continue building all the
971.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
981.184Schristos	   the new libraries are installed, you can restart the build.
991.184Schristos	4. If you compile packages and you notice link time warnings,
1001.189Shubertf	   rebuild the required packages to update their shared libraries.
1011.189Shubertf	   Any package you rebuild will require rebuilding all the packages
1021.189Shubertf	   that depend on it.
1031.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
1041.186Schristos	   will be upgraded and it will not be backwards compatible.
1051.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
1061.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
1071.190Sapb	   for utmp. You are better off removing the old files after
1081.190Sapb	   upgrading.  The automated clearing of /var/run during
1091.190Sapb	   boot, and the automated rotating of files in /var/log by
1101.190Sapb	   newsyslog(8), may mean that you do not have to remove the
1111.190Sapb	   files manually.
1121.190Sapb	7. The optional accounting file (/var/account/acct, see
1131.190Sapb	   accton(8)) has not been versioned, and will need to be
1141.190Sapb	   removed.  The automatic rotation of the accounting file by
1151.190Sapb	   /etc/daily limits the bad consequences of failure to remove
1161.190Sapb	   the file.
1171.196Sdholland	8. Application software that writes time_t to binary files on
1181.196Sdholland	   disk will break or need attention. Most notably: if you are
1191.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
1201.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
1211.185Sjmcneill
1221.183Spgoyette20081219:
1231.183Spgoyette	config(1) has been updated, and one of the files it creates -
1241.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
1251.183Spgoyette	(done automatically by build.sh) and then you need to rerun
1261.183Spgoyette	config on all kernel configuration files before rebuilding those
1271.183Spgoyette	kernels.
1281.183Spgoyette
1291.181Scube20081205:
1301.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
1311.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
1321.181Scube	set and will appear as extra files for MKX11=no update builds.
1331.178Slukem
1341.179Stsutsui20081122:
1351.182Stsutsui	On i386, various kernel options(4) in GENERIC including
1361.180Swiz	file systems have been disabled and moved into kernel modules.
1371.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
1381.179Stsutsui	following files as well as a new GENERIC kernel:
1391.179Stsutsui
1401.179Stsutsui	- build and install kernel modules from src/sys/modules
1411.179Stsutsui
1421.179Stsutsui	- install the latest bootloader, which will load a module
1431.180Swiz	  for the file system from which the kernel is loaded automatically
1441.179Stsutsui
1451.180Swiz	If you have to load your kernel from a file system which is not of
1461.180Swiz	the same type as the root file system, you have to load the necessary
1471.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
1481.179Stsutsui
1491.178Slukem20080827:
1501.178Slukem	If you built and installed a libc from sources between
1511.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
1521.178Slukem	which results in false errors reported by lint(1).
1531.178Slukem	Since this breaks the libc build itself, manual help is
1541.180Swiz	needed -- lint must be disabled temporarily, e.g.:
1551.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
1561.178Slukem
1571.177Schristos20080813:
1581.177Schristos	MKDEBUG build was broken because the .depend files did not know
1591.177Schristos	about .go files. You need to remove all .depend files and rebuild.
1601.177Schristos
1611.200Sdholland20080802:
1621.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
1631.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
1641.200Sdholland	for -current.
1651.200Sdholland
1661.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
1671.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
1681.200Sdholland	be recompiled.
1691.200Sdholland
1701.200Sdholland	One way to find affected pkgsrc packages:
1711.200Sdholland
1721.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
1731.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
1741.200Sdholland
1751.175Ssimonb20080731:
1761.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
1771.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
1781.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
1791.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
1801.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
1811.176Ssimonb	also requires the super block to be in the UFS2 format.  You
1821.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
1831.175Ssimonb
1841.174Slukem20080721:
1851.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
1861.174Slukem	isn't defined.
1871.174Slukem
1881.173Sfreza20080531:
1891.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
1901.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
1911.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
1921.173Sfreza	won't work correctly. The following sequence of commands:
1931.173Sfreza
1941.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
1951.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
1961.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
1971.173Sfreza
1981.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
1991.173Sfreza
2001.172Slukem20080503:
2011.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
2021.172Slukem
2031.171She20080521:
2041.171She	For a while, unprivileged UPDATE builds would fail to
2051.171She	succeed at the checkflist stage, complaining that
2061.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
2071.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
2081.171She	If you already hit this problem, update the .mk file,
2091.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
2101.171She
2111.174Slukem20080303:
2121.174Slukem	Linker warnings are now fatal if $WARNS>0.
2131.174Slukem
2141.170Schristos20080126:
2151.170Schristos	The posix_fadvise system call has been changed from an assembly
2161.170Schristos	stub, to a c file that calls an assembly stub. You need to
2171.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
2181.170Schristos	avoid using the old assembly stub.
2191.170Schristos
2201.168Sjoerg20071209:
2211.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
2221.168Sjoerg	get ACPI errors before the attachment, please update your kernel
2231.169Swiz	configuration file appropriately or see GENERIC for more details.
2241.168Sjoerg
2251.166Sxtraeme20071115:
2261.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
2271.166Sxtraeme	argument specified in the kernel configuration file is not valid
2281.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
2291.166Sxtraeme	rather than the EC address port. Please update your kernel
2301.167Swiz	configuration file appropriately or see GENERIC for more details.
2311.166Sxtraeme
2321.165Sjmmv20071028:
2331.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
2341.165Sjmmv	You need to update any custom kernel configuration file you have
2351.165Sjmmv	to remove any references to pccons (which includes removing the
2361.165Sjmmv	now useless XSERVER option) and replace them with the correct
2371.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
2381.165Sjmmv	for more details.
2391.165Sjmmv
2401.164Sgdt20070913:
2411.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
2421.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
2431.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
2441.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
2451.164Sgdt	could not enumerate interfaces.  (These are noted because
2461.164Sgdt	normal kernel/userspace version matching hygiene is not
2471.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
2481.164Sgdt	and userland are from after 20070913.
2491.164Sgdt
2501.163Sjoerg20070703:
2511.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
2521.199Sdholland	calls the target-specific strip program, and the logic to pass
2531.199Sdholland	down STRIP from make has been removed.  This requires a
2541.199Sdholland	re-installation of tools.
2551.163Sjoerg
2561.161Sdsl20070422:
2571.161Sdsl	The way OS emulations lookup filenames inside the emulation root
2581.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
2591.161Sdsl	to userspace) namei() and lookup() directly check the emulation
2601.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
2611.167Swiz	root file system will be relative to that file system - unless they
2621.161Sdsl	start /../ this is useful when the emulated root is a real install
2631.161Sdsl	that has such links.
2641.161Sdsl	This might affect symlinks that have been added to reference outside
2651.161Sdsl	the emulated root.
2661.161Sdsl
2671.160Sjmcneill20070412:
2681.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
2691.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
2701.160Sjmcneill	example.
2711.160Sjmcneill
2721.159Sgdt20070319:
2731.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
2741.159Sgdt        on many platforms due to incorrect flags settings.  If you
2751.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
2761.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
2771.159Sgdt	rebuild of object files that might have been built
2781.159Sgdt	incorrectly, and ensure that you have at least
2791.159Sgdt	src/lib/libc/Makefile 1.130.
2801.159Sgdt
2811.158Sdbj20070210: 
2821.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
2831.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
2841.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
2851.158Sdbj        will allow dependencies on those files to get get rebuilt
2861.158Sdbj
2871.157Sapb20070209:
2881.157Sapb        The threading model was changed when the newlock2 branch
2891.157Sapb        was merged to NetBSD-current.  If you boot with a new
2901.157Sapb        kernel (version 4.99.10), then you also need a new pthread
2911.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
2921.157Sapb        an old kernel, then you need the old pthread library
2931.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
2941.157Sapb        the pthread library in sync, old threaded applications should
2951.157Sapb        continue to work with an old or new kernel.  Note that named(8)
2961.157Sapb	is the only threaded application in the base system.
2971.157Sapb
2981.154She20061214:
2991.154She	Following the move of string_to_flags() and flags_to_string()
3001.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
3011.154She	will need to do a "make cleandir" in
3021.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
3031.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
3041.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
3051.156She		as the installation images in distrib/
3061.154She	in order to excise stale references to the old stat_flags.h header
3071.154She	file in the ls sources -- stat_flags.h has been removed.
3081.154She
3091.152Schristos20061108:
3101.152Schristos	The configure script used in the src/tools/gcc compiler has been
3111.152Schristos	changed to indicate that our libc has ssp support built-in and
3121.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
3131.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
3141.152Schristos
3151.151Srpaulo20061009:
3161.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
3171.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
3181.151Srpaulo
3191.150Sbjh2120060814:
3201.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
3211.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
3221.150Sbjh21	kernel configuration for an example.  X servers from the last
3231.150Sbjh21	few years should cope.
3241.150Sbjh21
3251.149Schristos20060703:
3261.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
3271.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
3281.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
3291.149Schristos
3301.148Sdogcow20060627:
3311.148Sdogcow	socket(2) has changed, and its system call has been versioned.
3321.148Sdogcow	For userlands with the old version of socket(2), make sure that
3331.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
3341.148Sdogcow	errors will result.
3351.148Sdogcow
3361.1SabsHints for a more successful build:
3371.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3381.123Sjmc    Use build.sh, but do not use its "expert mode":
3391.132Sjmmv	This will automatically build the tools in the
3401.123Sjmc	   correct order, and it will keep the tools and the
3411.123Sjmc	   new build products from interfering with the running
3421.123Sjmc	   system.  This will allow you to ignore most of the
3431.123Sjmc	   other advice in this file.
3441.2Smrg    Build a new kernel first:
3451.2Smrg	This makes sure that any new system calls or features
3461.2Smrg	   expected by the new userland will be present.  This
3471.2Smrg	   helps to avoid critical errors when upgrading.
3481.1Sabs    Use object directories:
3491.1Sabs	This helps to keep stale object
3501.1Sabs	   files from polluting the build if a Makefile "forgets"
3511.1Sabs	   about one.  It also makes it easier to clean up after
3521.1Sabs	   a build.  It's also necessary if you want to use the
3531.1Sabs	   same source tree for multiple machines.
3541.123Sjmc	   To use object directories with build.sh:
3551.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
3561.123Sjmc	   To use object directories without using build.sh:
3571.1Sabs	    a) cd /usr/src ; make cleandir
3581.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
3591.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
3601.1Sabs	    d) cd /usr/src ; make build
3611.2Smrg	   Note that running "make obj" in a directory will create
3621.2Smrg	   in obj.$MACHINE directory.
3631.1Sabs    Build to a DESTDIR:
3641.123Sjmc	This helps to keep old installed files (especially libraries)
3651.123Sjmc	   from interfering with the new build.
3661.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
3671.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
3681.123Sjmc	   environment variable before running make build.  It should be
3691.123Sjmc	   set to the pathname of an initially empty directory.
3701.123Sjmc	   Problems: if you do not use build.sh, you might need to
3711.123Sjmc		update critical utilities without using DESTDIR since
3721.123Sjmc		nothing is executed from what is installed in DESTDIR.
3731.123Sjmc		(See critical utils, below.)
3741.1Sabs    Build often:
3751.1Sabs	This keeps critical utilities current enough to not choke
3761.1Sabs	on any other part of the source tree that depends on up to
3771.123Sjmc	date functionality.  If you use build.sh, you should not have
3781.123Sjmc	this problem.
3791.1Sabs 
3801.1SabsWhat to do if things don't work:
3811.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3821.1SabsWhen things don't work there is usually a few things that commonly
3831.1Sabsshould be done.
3841.1Sabs    1)	make includes
3851.1Sabs	This should be done automatically by make build.
3861.1Sabs    2)  cd share/mk && make install
3871.1Sabs	Again, automatically done by make build.
3881.1Sabs
3891.1SabsFailsafe rebuild of a small part of the tree:
3901.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3911.1SabsTo make sure you rebuild something correctly you want to do
3921.1Sabssomething like the following:
3931.1Sabs    1)  Make sure the includes and .mk files are up to date.
3941.1Sabs    2)  Make sure any program used to build the particular
3951.1Sabs	utility is up to date.  (yacc, lex, etc...)
3961.1Sabs    3)  cd ...path/to/util...
3971.1Sabs	make cleandir
3981.1Sabs	rm ...all obj directories...
3991.1Sabs	make cleandir			# yes, again
4001.1Sabs	make obj
4011.1Sabs	make depend && make
4021.1Sabs
4031.1SabsFailsafe rebuild of the entire tree:
4041.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4051.1SabsIf you really want to make sure the source tree is clean and
4061.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
4071.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
4081.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
4091.1Sabs
4101.1Sabs---cut here---
4111.1Sabs#!/bin/sh
4121.1Sabs. /etc/mk.conf
4131.1Sabs
4141.58Slukemif [ -z $NETBSDSRCDIR ] ; then
4151.58Slukem    NETBSDSRCDIR=/usr/src
4161.1Sabsfi
4171.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
4181.1Sabs    echo Unable to find sources
4191.1Sabs    exit 1
4201.1Sabsfi
4211.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
4221.1Sabs
4231.1Sabsif [ -z $BSDOBJDIR ] ; then
4241.1Sabs    BSDOBJDIR=/usr/obj
4251.1Sabsfi
4261.1Sabsif [ -d $BSDOBJDIR ] ; then
4271.1Sabs    rm -rf $BSDOBJDIR
4281.1Sabsfi
4291.1Sabs
4301.58Slukemcd $NETBSDSRCDIR && make cleandir
4311.1Sabs
4321.1Sabs---cut here---
4331.1Sabs
4341.1SabsCritical utilities:
4351.1Sabs^^^^^^^^^^^^^^^^^^^
4361.3Sitojun	usr.bin/compile_et
4371.1Sabs	usr.bin/make
4381.1Sabs	usr.bin/yacc
4391.1Sabs	usr.bin/lex
4401.11Slukem	usr.bin/xlint
4411.142Sdrochner	usr.bin/config
4421.1Sabs
4431.34SsimonbOther problems and possible solutions:
4441.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4451.1SabsSymptom:Complaints involving a Makefile.
4461.17SerhFix:	Rebuild usr.bin/make:
4471.17Serh	cd usr.bin/make && make && make install
4481.111Ssimonb	Or, a failsafe method if that doesn't work:
4491.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
4501.17Serh
4511.1SabsFix:	Make sure .mk files are up to date.
4521.1Sabs	cd share/mk && make install
4531.2Smrg
4541.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
4551.142SdrochnerFix:	Rebuild usr.bin/config
4561.1Sabs
4571.1SabsSymptom:
4581.1SabsFix:	Rebuild usr.bin/yacc
4591.1Sabs
4601.1SabsSymptom:
4611.1SabsFix:	Rebuild usr.bin/lex
4621.1Sabs
4631.1SabsSymptom:
4641.1SabsFix:	rm /usr/lib/libbfd.a
4651.4Sitojun
4661.4SitojunSymptom:Obsolete intermediate files are used during compilation
4671.4SitojunFix:	Try the following sequence of commands in the directory in question.
4681.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
4691.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
4701.4Sitojun	may remain.  The command tries to clean everything up)
4711.5Swiz
4721.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
4731.207Smbalmer	pointer type
4741.5SwizFix:	Rebuild and install usr.bin/menuc
4751.12Sitojun
4761.12SitojunSymptom:mklocale not found during build in share/locale/ctype
4771.12SitojunFix:	Build and install usr.bin/mklocale
4781.13Sdogcow
4791.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
4801.13SdogcowFix:    Rebuild and install lib/libc
4811.13Sdogcow
4821.142SdrochnerSymptom:usr.bin/config fails to build.
4831.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
4841.13Sdogcow
4851.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
4861.19ScgdFix:    Rebuild and install lib/libc
4871.24Sabs
4881.24SabsSymptom:lint does not understand the '-X' option
4891.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
490