UPDATING revision 1.239
11.239Sdholland$NetBSD: UPDATING,v 1.239 2012/09/15 18:03:42 dholland Exp $
21.1Sabs
31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent
41.123Sjmcchanges that might cause problems in the build process, and a guide for
51.123Sjmcwhat to do if something doesn't work.
61.1Sabs
71.123SjmcFor a more detailed description of the recommended way to build NetBSD
81.123Sjmcusing build.sh, see the BUILDING file.
91.123Sjmc
101.123SjmcNote that much of the advice in this UPDATING file was written before
111.123Sjmcbuild.sh existed.  Nevertheless, the advice here may be useful for
121.123Sjmcworking around specific problems with build.sh.
131.123Sjmc
141.123SjmcSee also: BUILDING, build.sh, Makefile.
151.1Sabs
161.1SabsRecent changes:
171.1Sabs^^^^^^^^^^^^^^^
181.230Stls
191.238Sdholland20120726:
201.238Sdholland	The update of openssl requires cleaning both the openssl build
211.238Sdholland	directory and DESTDIR; update builds done without taking these
221.238Sdholland	steps may fail, or if not, have been observed to cause
231.238Sdholland	third-party software to link incorrectly.
241.238Sdholland
251.237Swiz20120507:
261.237Swiz	The database schema for makemandb was changed. You will
271.237Swiz	need to update the database using 'makemandb -f' or wait
281.237Swiz	for the next weekly run to fix it.
291.237Swiz
301.236Sbsh20120319:
311.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
321.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
331.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
341.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
351.236Sbsh	mk.conf.
361.236Sbsh
371.235Sjoerg20120216:
381.234Sspz	Default for MKCATPAGES changed to NO. Update builds will fail
391.235Sjoerg	unless DESTDIR is cleaned manually. If you built between 20120207
401.239Sdholland	and 20120216, daily and weekly could have created an unreadable
411.235Sjoerg	/var/db/man.db index for apropos. Running makemandb -f or
421.235Sjoerg	the next run of weekly will fix it.
431.233Sjoerg
441.232Schristos20111227:
451.232Schristos	If you built between 20111225 and 20111227 you need to remove
461.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
471.232Schristos	bump has been reverted.
481.232Schristos
491.231Stls20111125:
501.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
511.231Stls	means it should no longer be explicitly listed in kernel
521.231Stls	configuration files.  The line "pseudo-device rnd" should be
531.231Stls	removed from any custom kernel config files users may have.
541.231Stls
551.230Stls20111119:
561.230Stls	A problem with the datastructures used by the rndctl(8)
571.230Stls	utility (pointers in datastructures in an array, making 32->64
581.230Stls	bit compatibility very painful) has been fixed in a
591.230Stls	non-backwards-compatible way.  If you replace your kernel,
601.230Stls	replace your rndctl executable too.
611.230Stls	
621.229Sjym20111001:
631.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
641.229Sjym	changed and their new version is not backward compatible with the old
651.229Sjym	one. So ensure that all consumers of these functions (currently:
661.229Sjym	quota2 code and its tests) are updated together with the new lib.
671.229Sjym
681.228Smrg20110817:
691.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
701.228Smrg	DESTDIR for them should be deleted before updating.
711.228Smrg
721.227Sriastrad20110806:
731.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
741.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
751.227Sriastrad
761.226Smrg20110805:
771.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
781.226Smrg	the tree to be cleaned.  Best to delete both objdir and
791.226Smrg	DESTDIR before running this update.  So far, only the
801.226Smrg	sparc64, mips and powerpc platforms have changed.
811.226Smrg
821.225Smatt20110803:
831.225Smatt	The layout of external/public-domain/xz has changed. To do an
841.225Smatt	update build you will have to remove the contents of the OBJDIR
851.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
861.225Smatt	is now a directory.
871.225Smatt
881.223Sjoerg20110410:
891.224Sdholland	The configuration of src/tools/gcc has changed. To do an
901.224Sdholland	update build you have to clean both tools/binutils and
911.224Sdholland	tools/gcc by hand.
921.223Sjoerg
931.222Splunky20110328:
941.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
951.222Splunky	ordering issues with "make all". It may be necessary to remove
961.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
971.222Splunky	if your update build fails, as the "Xorg" entry there is now a
981.222Splunky	directory.
991.222Splunky
1001.220Sjoerg20110121:
1011.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
1021.220Sjoerg	the build of individual parts of the tree.  This is handled
1031.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
1041.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
1051.218Sjoerg
1061.217Sjruoho20101217:
1071.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
1081.217Sjruoho	by default. It may be necessary to manually update passwd(5) and
1091.217Sjruoho	group(5) in order to make the program work with existing setups.
1101.217Sjruoho
1111.216Schristos20101125:
1121.216Schristos	The latest changes to setenv(3) dissallow setting environment
1131.216Schristos	variables with names that contain '='. Revision 1.18 of env.c
1141.216Schristos	assumed that this was allowed. Installing a new libc with an
1151.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
1161.216Schristos	break which affects the autoconf tests for dependency finding,
1171.216Schristos	so building gcc will end up printing:
1181.216Schristos	    checking dependency style of gcc... none
1191.216Schristos	    configure: error: no usable dependency style found
1201.216Schristos	Fix it by rebuilding and re-installing env.
1211.138Slukem
1221.215Smrg20101119:
1231.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
1241.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
1251.215Smrg	have any build problems with xsrc, or problems with mismatched
1261.215Smrg	versions between xorg-server and drivers.
1271.215Smrg
1281.213Sjmmv20100604:
1291.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
1301.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
1311.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
1321.213Sjmmv	trees by hand.
1331.213Sjmmv
1341.211Stnozaki20100522:
1351.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
1361.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
1371.212Smrg	build problems with xsrc.
1381.212Smrg
1391.212Smrg20100522:
1401.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
1411.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
1421.211Stnozaki
1431.210Schristos20100520:
1441.210Schristos	The location of the xkb compiled descriptions has changed. Please
1451.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
1461.210Schristos
1471.209Snjoly20100222:
1481.209Snjoly	The shared objects file extension has been changed from .so to
1491.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
1501.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
1511.209Snjoly	your object directories.
1521.209Snjoly
1531.208Sroy20100204:
1541.208Sroy	The termcap database has been removed from the sources,
1551.208Sroy	but has not been marked obsolete so it is not removed
1561.208Sroy	from the system when upgrading.
1571.208Sroy	As such, you will need to remove them from your object
1581.208Sroy	and destination directories.
1591.208Sroy
1601.203Sdyoung20091101:
1611.205Sdholland        After updating, it may be necessary to make the 'cleandir'
1621.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
1631.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
1641.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
1651.203Sdyoung
1661.202Smrg20091001:
1671.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
1681.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
1691.206Sdholland
1701.206Sdholland20091001:
1711.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
1721.202Smrg	symlink, failing the build.  Delete the link, and the subdir
1731.202Smrg	it is in, and retry your build.
1741.202Smrg
1751.201Sdsl20090718:
1761.201Sdsl	libc build changed so that strchr() provides the extra entry
1771.201Sdsl	point for index(). Update build of libc.a (and libc_pic.a)
1781.201Sdsl	may fail because the archive contains the unwanted index.o.
1791.201Sdsl	(Similarly for strrchr() and rindex().)
1801.201Sdsl
1811.198Smrg20090709:
1821.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
1831.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
1841.198Smrg
1851.197Smrg20090616:
1861.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
1871.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
1881.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
1891.197Smrg	subdirectory has been changed into a file, and this needs to
1901.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
1911.197Smrg
1921.195Sperry20090501:
1931.195Sperry	Several new functions were added to string.h/libc, and this
1941.195Sperry	can cause autoconf problems during the tool build for people
1951.195Sperry	who fail to clean out their tools objects properly. If you
1961.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
1971.195Sperry	failure during the tool build, clean out all your tools
1981.195Sperry	objects and start again.
1991.195Sperry
2001.194Smrg20090325:
2011.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
2021.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
2031.194Smrg
2041.192Sskrll20090126:
2051.207Smbalmer	The __posix_fadvise50 system call changed assembly stub type. You
2061.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
2071.207Smbalmer	to avoid using the old assembly stub.
2081.192Sskrll
2091.191Sjoerg20090202:
2101.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
2111.191Sjoerg	detection.  It is recommented to rebuild the cache with
2121.191Sjoerg	``pkg_admin rebuild''.
2131.191Sjoerg
2141.184Schristos20090110:
2151.184Schristos	time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
2161.184Schristos	1. Make sure your kernel has COMPAT_50 in it. Build and install.
2171.188Schristos	   This is needed even in the MODULAR kernel because there is
2181.188Schristos	   conditionally compiled code in rtsock.c.
2191.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
2201.184Schristos	   before installing.
2211.184Schristos	3. If you don't use build.sh and you build directly to root, and
2221.187Sdholland	   your build breaks in the middle, don't despair. Make sure headers
2231.184Schristos	   are installed properly, and start building libraries first libc
2241.184Schristos	   and libutil, install them and then continue building all the
2251.184Schristos	   libraries in src/lib and src/gnu/lib and install them. Once
2261.184Schristos	   the new libraries are installed, you can restart the build.
2271.184Schristos	4. If you compile packages and you notice link time warnings,
2281.189Shubertf	   rebuild the required packages to update their shared libraries.
2291.189Shubertf	   Any package you rebuild will require rebuilding all the packages
2301.189Shubertf	   that depend on it.
2311.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
2321.186Schristos	   will be upgraded and it will not be backwards compatible.
2331.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
2341.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
2351.190Sapb	   for utmp. You are better off removing the old files after
2361.190Sapb	   upgrading.  The automated clearing of /var/run during
2371.190Sapb	   boot, and the automated rotating of files in /var/log by
2381.190Sapb	   newsyslog(8), may mean that you do not have to remove the
2391.190Sapb	   files manually.
2401.190Sapb	7. The optional accounting file (/var/account/acct, see
2411.190Sapb	   accton(8)) has not been versioned, and will need to be
2421.190Sapb	   removed.  The automatic rotation of the accounting file by
2431.190Sapb	   /etc/daily limits the bad consequences of failure to remove
2441.190Sapb	   the file.
2451.196Sdholland	8. Application software that writes time_t to binary files on
2461.196Sdholland	   disk will break or need attention. Most notably: if you are
2471.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
2481.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
2491.185Sjmcneill
2501.183Spgoyette20081219:
2511.183Spgoyette	config(1) has been updated, and one of the files it creates -
2521.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
2531.183Spgoyette	(done automatically by build.sh) and then you need to rerun
2541.183Spgoyette	config on all kernel configuration files before rebuilding those
2551.183Spgoyette	kernels.
2561.183Spgoyette
2571.181Scube20081205:
2581.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
2591.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
2601.181Scube	set and will appear as extra files for MKX11=no update builds.
2611.178Slukem
2621.179Stsutsui20081122:
2631.182Stsutsui	On i386, various kernel options(4) in GENERIC including
2641.180Swiz	file systems have been disabled and moved into kernel modules.
2651.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
2661.179Stsutsui	following files as well as a new GENERIC kernel:
2671.179Stsutsui
2681.179Stsutsui	- build and install kernel modules from src/sys/modules
2691.179Stsutsui
2701.179Stsutsui	- install the latest bootloader, which will load a module
2711.180Swiz	  for the file system from which the kernel is loaded automatically
2721.179Stsutsui
2731.180Swiz	If you have to load your kernel from a file system which is not of
2741.180Swiz	the same type as the root file system, you have to load the necessary
2751.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
2761.179Stsutsui
2771.178Slukem20080827:
2781.178Slukem	If you built and installed a libc from sources between
2791.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
2801.178Slukem	which results in false errors reported by lint(1).
2811.178Slukem	Since this breaks the libc build itself, manual help is
2821.180Swiz	needed -- lint must be disabled temporarily, e.g.:
2831.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
2841.178Slukem
2851.177Schristos20080813:
2861.177Schristos	MKDEBUG build was broken because the .depend files did not know
2871.177Schristos	about .go files. You need to remove all .depend files and rebuild.
2881.177Schristos
2891.200Sdholland20080802:
2901.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
2911.200Sdholland	been fixed. Unfortunately, the price is breaking compatibility
2921.200Sdholland	for -current.
2931.200Sdholland
2941.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
2951.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
2961.200Sdholland	be recompiled.
2971.200Sdholland
2981.200Sdholland	One way to find affected pkgsrc packages:
2991.200Sdholland
3001.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
3011.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
3021.200Sdholland
3031.175Ssimonb20080731:
3041.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
3051.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
3061.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
3071.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
3081.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
3091.176Ssimonb	also requires the super block to be in the UFS2 format.  You
3101.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
3111.175Ssimonb
3121.174Slukem20080721:
3131.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
3141.174Slukem	isn't defined.
3151.174Slukem
3161.173Sfreza20080531:
3171.173Sfreza	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 
3181.173Sfreza	from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
3191.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
3201.173Sfreza	won't work correctly. The following sequence of commands:
3211.173Sfreza
3221.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
3231.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
3241.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
3251.173Sfreza
3261.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
3271.173Sfreza
3281.172Slukem20080503:
3291.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
3301.172Slukem
3311.171She20080521:
3321.171She	For a while, unprivileged UPDATE builds would fail to
3331.171She	succeed at the checkflist stage, complaining that
3341.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
3351.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
3361.171She	If you already hit this problem, update the .mk file,
3371.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
3381.171She
3391.174Slukem20080303:
3401.174Slukem	Linker warnings are now fatal if $WARNS>0.
3411.174Slukem
3421.170Schristos20080126:
3431.170Schristos	The posix_fadvise system call has been changed from an assembly
3441.170Schristos	stub, to a c file that calls an assembly stub. You need to
3451.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
3461.170Schristos	avoid using the old assembly stub.
3471.170Schristos
3481.168Sjoerg20071209:
3491.168Sjoerg	The acpiec(4) driver has been split into two attachments. If you
3501.168Sjoerg	get ACPI errors before the attachment, please update your kernel
3511.169Swiz	configuration file appropriately or see GENERIC for more details.
3521.168Sjoerg
3531.166Sxtraeme20071115:
3541.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
3551.166Sxtraeme	argument specified in the kernel configuration file is not valid
3561.166Sxtraeme	anymore. The itesio(4) driver now uses the Super I/O address port
3571.166Sxtraeme	rather than the EC address port. Please update your kernel
3581.167Swiz	configuration file appropriately or see GENERIC for more details.
3591.166Sxtraeme
3601.165Sjmmv20071028:
3611.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
3621.165Sjmmv	You need to update any custom kernel configuration file you have
3631.165Sjmmv	to remove any references to pccons (which includes removing the
3641.165Sjmmv	now useless XSERVER option) and replace them with the correct
3651.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
3661.165Sjmmv	for more details.
3671.165Sjmmv
3681.164Sgdt20070913:
3691.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
3701.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
3711.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
3721.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
3731.164Sgdt	could not enumerate interfaces.  (These are noted because
3741.164Sgdt	normal kernel/userspace version matching hygiene is not
3751.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
3761.164Sgdt	and userland are from after 20070913.
3771.164Sgdt
3781.163Sjoerg20070703:
3791.199Sdholland	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
3801.199Sdholland	calls the target-specific strip program, and the logic to pass
3811.199Sdholland	down STRIP from make has been removed.  This requires a
3821.199Sdholland	re-installation of tools.
3831.163Sjoerg
3841.161Sdsl20070422:
3851.161Sdsl	The way OS emulations lookup filenames inside the emulation root
3861.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
3871.161Sdsl	to userspace) namei() and lookup() directly check the emulation
3881.161Sdsl	root. One side effect is that absolute symlinks inside the emulated
3891.167Swiz	root file system will be relative to that file system - unless they
3901.161Sdsl	start /../ this is useful when the emulated root is a real install
3911.161Sdsl	that has such links.
3921.161Sdsl	This might affect symlinks that have been added to reference outside
3931.161Sdsl	the emulated root.
3941.161Sdsl
3951.160Sjmcneill20070412:
3961.160Sjmcneill	The pckbc driver on sgimips IP32 has been removed. Use macekbc
3971.160Sjmcneill	instead. See the GENERIC32_IP3x kernel configuration for an
3981.160Sjmcneill	example.
3991.160Sjmcneill
4001.159Sgdt20070319:
4011.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
4021.159Sgdt        on many platforms due to incorrect flags settings.  If you
4031.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
4041.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
4051.159Sgdt	rebuild of object files that might have been built
4061.159Sgdt	incorrectly, and ensure that you have at least
4071.159Sgdt	src/lib/libc/Makefile 1.130.
4081.159Sgdt
4091.158Sdbj20070210: 
4101.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
4111.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
4121.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
4131.158Sdbj        will allow dependencies on those files to get get rebuilt
4141.158Sdbj
4151.157Sapb20070209:
4161.157Sapb        The threading model was changed when the newlock2 branch
4171.157Sapb        was merged to NetBSD-current.  If you boot with a new
4181.157Sapb        kernel (version 4.99.10), then you also need a new pthread
4191.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
4201.157Sapb        an old kernel, then you need the old pthread library
4211.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
4221.157Sapb        the pthread library in sync, old threaded applications should
4231.157Sapb        continue to work with an old or new kernel.  Note that named(8)
4241.157Sapb	is the only threaded application in the base system.
4251.157Sapb
4261.154She20061214:
4271.154She	Following the move of string_to_flags() and flags_to_string()
4281.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
4291.154She	will need to do a "make cleandir" in
4301.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
4311.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
4321.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
4331.156She		as the installation images in distrib/
4341.154She	in order to excise stale references to the old stat_flags.h header
4351.154She	file in the ls sources -- stat_flags.h has been removed.
4361.154She
4371.152Schristos20061108:
4381.152Schristos	The configure script used in the src/tools/gcc compiler has been
4391.152Schristos	changed to indicate that our libc has ssp support built-in and
4401.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
4411.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
4421.152Schristos
4431.151Srpaulo20061009:
4441.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
4451.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
4461.151Srpaulo
4471.150Sbjh2120060814:
4481.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
4491.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
4501.150Sbjh21	kernel configuration for an example.  X servers from the last
4511.150Sbjh21	few years should cope.
4521.150Sbjh21
4531.149Schristos20060703:
4541.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
4551.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
4561.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
4571.149Schristos
4581.148Sdogcow20060627:
4591.148Sdogcow	socket(2) has changed, and its system call has been versioned.
4601.148Sdogcow	For userlands with the old version of socket(2), make sure that
4611.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
4621.148Sdogcow	errors will result.
4631.148Sdogcow
4641.1SabsHints for a more successful build:
4651.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4661.123Sjmc    Use build.sh, but do not use its "expert mode":
4671.132Sjmmv	This will automatically build the tools in the
4681.123Sjmc	   correct order, and it will keep the tools and the
4691.123Sjmc	   new build products from interfering with the running
4701.123Sjmc	   system.  This will allow you to ignore most of the
4711.123Sjmc	   other advice in this file.
4721.2Smrg    Build a new kernel first:
4731.2Smrg	This makes sure that any new system calls or features
4741.2Smrg	   expected by the new userland will be present.  This
4751.2Smrg	   helps to avoid critical errors when upgrading.
4761.1Sabs    Use object directories:
4771.1Sabs	This helps to keep stale object
4781.1Sabs	   files from polluting the build if a Makefile "forgets"
4791.1Sabs	   about one.  It also makes it easier to clean up after
4801.1Sabs	   a build.  It's also necessary if you want to use the
4811.1Sabs	   same source tree for multiple machines.
4821.123Sjmc	   To use object directories with build.sh:
4831.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
4841.123Sjmc	   To use object directories without using build.sh:
4851.1Sabs	    a) cd /usr/src ; make cleandir
4861.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
4871.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
4881.1Sabs	    d) cd /usr/src ; make build
4891.2Smrg	   Note that running "make obj" in a directory will create
4901.2Smrg	   in obj.$MACHINE directory.
4911.1Sabs    Build to a DESTDIR:
4921.123Sjmc	This helps to keep old installed files (especially libraries)
4931.123Sjmc	   from interfering with the new build.
4941.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
4951.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
4961.123Sjmc	   environment variable before running make build.  It should be
4971.123Sjmc	   set to the pathname of an initially empty directory.
4981.123Sjmc	   Problems: if you do not use build.sh, you might need to
4991.123Sjmc		update critical utilities without using DESTDIR since
5001.123Sjmc		nothing is executed from what is installed in DESTDIR.
5011.123Sjmc		(See critical utils, below.)
5021.1Sabs    Build often:
5031.1Sabs	This keeps critical utilities current enough to not choke
5041.1Sabs	on any other part of the source tree that depends on up to
5051.123Sjmc	date functionality.  If you use build.sh, you should not have
5061.123Sjmc	this problem.
5071.1Sabs 
5081.1SabsWhat to do if things don't work:
5091.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5101.230StlsWhen things don't work there are usually a few things that commonly
5111.1Sabsshould be done.
5121.1Sabs    1)	make includes
5131.1Sabs	This should be done automatically by make build.
5141.1Sabs    2)  cd share/mk && make install
5151.1Sabs	Again, automatically done by make build.
5161.1Sabs
5171.1SabsFailsafe rebuild of a small part of the tree:
5181.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5191.1SabsTo make sure you rebuild something correctly you want to do
5201.1Sabssomething like the following:
5211.1Sabs    1)  Make sure the includes and .mk files are up to date.
5221.1Sabs    2)  Make sure any program used to build the particular
5231.1Sabs	utility is up to date.  (yacc, lex, etc...)
5241.1Sabs    3)  cd ...path/to/util...
5251.1Sabs	make cleandir
5261.1Sabs	rm ...all obj directories...
5271.1Sabs	make cleandir			# yes, again
5281.1Sabs	make obj
5291.1Sabs	make depend && make
5301.1Sabs
5311.1SabsFailsafe rebuild of the entire tree:
5321.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5331.1SabsIf you really want to make sure the source tree is clean and
5341.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
5351.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
5361.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
5371.1Sabs
5381.1Sabs---cut here---
5391.1Sabs#!/bin/sh
5401.1Sabs. /etc/mk.conf
5411.1Sabs
5421.58Slukemif [ -z $NETBSDSRCDIR ] ; then
5431.58Slukem    NETBSDSRCDIR=/usr/src
5441.1Sabsfi
5451.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
5461.1Sabs    echo Unable to find sources
5471.1Sabs    exit 1
5481.1Sabsfi
5491.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
5501.1Sabs
5511.1Sabsif [ -z $BSDOBJDIR ] ; then
5521.1Sabs    BSDOBJDIR=/usr/obj
5531.1Sabsfi
5541.1Sabsif [ -d $BSDOBJDIR ] ; then
5551.1Sabs    rm -rf $BSDOBJDIR
5561.1Sabsfi
5571.1Sabs
5581.58Slukemcd $NETBSDSRCDIR && make cleandir
5591.1Sabs
5601.1Sabs---cut here---
5611.1Sabs
5621.1SabsCritical utilities:
5631.1Sabs^^^^^^^^^^^^^^^^^^^
5641.3Sitojun	usr.bin/compile_et
5651.1Sabs	usr.bin/make
5661.1Sabs	usr.bin/yacc
5671.1Sabs	usr.bin/lex
5681.11Slukem	usr.bin/xlint
5691.142Sdrochner	usr.bin/config
5701.1Sabs
5711.34SsimonbOther problems and possible solutions:
5721.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5731.1SabsSymptom:Complaints involving a Makefile.
5741.17SerhFix:	Rebuild usr.bin/make:
5751.17Serh	cd usr.bin/make && make && make install
5761.111Ssimonb	Or, a failsafe method if that doesn't work:
5771.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
5781.17Serh
5791.1SabsFix:	Make sure .mk files are up to date.
5801.1Sabs	cd share/mk && make install
5811.2Smrg
5821.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
5831.142SdrochnerFix:	Rebuild usr.bin/config
5841.1Sabs
5851.1SabsSymptom:
5861.1SabsFix:	Rebuild usr.bin/yacc
5871.1Sabs
5881.1SabsSymptom:
5891.1SabsFix:	Rebuild usr.bin/lex
5901.1Sabs
5911.1SabsSymptom:
5921.1SabsFix:	rm /usr/lib/libbfd.a
5931.4Sitojun
5941.4SitojunSymptom:Obsolete intermediate files are used during compilation
5951.4SitojunFix:	Try the following sequence of commands in the directory in question.
5961.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
5971.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
5981.4Sitojun	may remain.  The command tries to clean everything up)
5991.5Swiz
6001.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
6011.207Smbalmer	pointer type
6021.5SwizFix:	Rebuild and install usr.bin/menuc
6031.12Sitojun
6041.12SitojunSymptom:mklocale not found during build in share/locale/ctype
6051.12SitojunFix:	Build and install usr.bin/mklocale
6061.13Sdogcow
6071.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
6081.13SdogcowFix:    Rebuild and install lib/libc
6091.13Sdogcow
6101.142SdrochnerSymptom:usr.bin/config fails to build.
6111.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
6121.13Sdogcow
6131.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
6141.19ScgdFix:    Rebuild and install lib/libc
6151.24Sabs
6161.24SabsSymptom:lint does not understand the '-X' option
6171.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
6181.223Sjoerg
6191.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
6201.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
6211.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
622