UPDATING revision 1.257
11.257Sapb$NetBSD: UPDATING,v 1.257 2014/07/23 08:52:32 apb 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.257SapbSections are marked with "^^^^^".  After the section on "Recent changes"
151.257Sapbare several sections containing more general information.
161.257Sapb
171.123SjmcSee also: BUILDING, build.sh, Makefile.
181.1Sabs
191.1SabsRecent changes:
201.1Sabs^^^^^^^^^^^^^^^
211.230Stls
221.256Sapb20140721:
231.256Sapb	The src/external/mit/lua/src directory was accidentally created
241.256Sapb	and then deleted in the CVS repository.  If you get errors like
251.256Sapb
261.256Sapb	cvs [update aborted]: cannot open directory
271.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
281.256Sapb
291.256Sapb	then delete your local copy of that directory tree and try again.
301.256Sapb
311.255Sjoerg20140530:
321.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
331.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
341.255Sjoerg
351.251Smartin20140131:
361.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
371.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
381.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
391.251Smartin
401.250Schristos20131227:
411.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
421.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
431.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
441.250Schristos	   statements to avoid being exposed.
451.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
461.250Schristos	   to make clean in libc
471.250Schristos
481.249Smrg20131129:
491.249Smrg	The GMP sources were updated, and builds will likely fail without
501.249Smrg	cleaning their build trees for both tools and in-tree, like below.
511.249Smrg
521.248Smrg20131128:
531.248Smrg	The MPC and MPFR sources were updated, and builds may require their
541.248Smrg	tools and in-tree directories cleaned for successful updates.
551.248Smrg
561.246Smartin20130605:
571.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
581.247Sspz	to IPSEC (and the older IPSEC version removed).
591.247Sspz
601.247Sspz20130605:
611.246Smartin	Previous freetype installations eroneously installed private
621.246Smartin	header files. If you are building against a non-empty $DESTDIR,
631.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
641.246Smartin
651.245Smrg20130531:
661.245Smrg	The xdm update may cause build failure due to xdm.man being
671.245Smrg	in the obj tree.  Make sure to ensure any like this:
681.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
691.245Smrg	is fixed by deleting the xdm.man in the obj tree.
701.245Smrg
711.244Smrg20130530:
721.244Smrg	Updates of many xsrc packages will leave old .pc files around.
731.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
741.244Smrg
751.242Schristos20130301:
761.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
771.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
781.242Schristos
791.238Sdholland20120726:
801.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
811.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
821.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
831.241Swiz	some cases may succeed and install broken OpenSSL libraries that
841.240Sdholland	cause third-party software to link incorrectly and/or crash.
851.238Sdholland
861.237Swiz20120507:
871.241Swiz	The database schema for makemandb was changed.  You will
881.237Swiz	need to update the database using 'makemandb -f' or wait
891.237Swiz	for the next weekly run to fix it.
901.237Swiz
911.236Sbsh20120319:
921.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
931.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
941.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
951.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
961.236Sbsh	mk.conf.
971.236Sbsh
981.235Sjoerg20120216:
991.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
1001.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
1011.239Sdholland	and 20120216, daily and weekly could have created an unreadable
1021.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
1031.235Sjoerg	the next run of weekly will fix it.
1041.233Sjoerg
1051.232Schristos20111227:
1061.232Schristos	If you built between 20111225 and 20111227 you need to remove
1071.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
1081.232Schristos	bump has been reverted.
1091.232Schristos
1101.231Stls20111125:
1111.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
1121.231Stls	means it should no longer be explicitly listed in kernel
1131.231Stls	configuration files.  The line "pseudo-device rnd" should be
1141.231Stls	removed from any custom kernel config files users may have.
1151.231Stls
1161.230Stls20111119:
1171.230Stls	A problem with the datastructures used by the rndctl(8)
1181.230Stls	utility (pointers in datastructures in an array, making 32->64
1191.230Stls	bit compatibility very painful) has been fixed in a
1201.230Stls	non-backwards-compatible way.  If you replace your kernel,
1211.230Stls	replace your rndctl executable too.
1221.241Swiz
1231.229Sjym20111001:
1241.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
1251.229Sjym	changed and their new version is not backward compatible with the old
1261.241Swiz	one.  So ensure that all consumers of these functions (currently:
1271.229Sjym	quota2 code and its tests) are updated together with the new lib.
1281.229Sjym
1291.228Smrg20110817:
1301.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
1311.228Smrg	DESTDIR for them should be deleted before updating.
1321.228Smrg
1331.227Sriastrad20110806:
1341.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
1351.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
1361.227Sriastrad
1371.226Smrg20110805:
1381.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
1391.226Smrg	the tree to be cleaned.  Best to delete both objdir and
1401.226Smrg	DESTDIR before running this update.  So far, only the
1411.226Smrg	sparc64, mips and powerpc platforms have changed.
1421.226Smrg
1431.225Smatt20110803:
1441.241Swiz	The layout of external/public-domain/xz has changed.  To do an
1451.225Smatt	update build you will have to remove the contents of the OBJDIR
1461.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
1471.225Smatt	is now a directory.
1481.225Smatt
1491.223Sjoerg20110410:
1501.241Swiz	The configuration of src/tools/gcc has changed.  To do an
1511.224Sdholland	update build you have to clean both tools/binutils and
1521.224Sdholland	tools/gcc by hand.
1531.223Sjoerg
1541.222Splunky20110328:
1551.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
1561.241Swiz	ordering issues with "make all".  It may be necessary to remove
1571.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
1581.222Splunky	if your update build fails, as the "Xorg" entry there is now a
1591.222Splunky	directory.
1601.222Splunky
1611.220Sjoerg20110121:
1621.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
1631.220Sjoerg	the build of individual parts of the tree.  This is handled
1641.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
1651.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
1661.218Sjoerg
1671.217Sjruoho20101217:
1681.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
1691.241Swiz	by default.  It may be necessary to manually update passwd(5) and
1701.217Sjruoho	group(5) in order to make the program work with existing setups.
1711.217Sjruoho
1721.216Schristos20101125:
1731.216Schristos	The latest changes to setenv(3) dissallow setting environment
1741.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
1751.241Swiz	assumed that this was allowed.  Installing a new libc with an
1761.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
1771.216Schristos	break which affects the autoconf tests for dependency finding,
1781.216Schristos	so building gcc will end up printing:
1791.216Schristos	    checking dependency style of gcc... none
1801.216Schristos	    configure: error: no usable dependency style found
1811.216Schristos	Fix it by rebuilding and re-installing env.
1821.138Slukem
1831.215Smrg20101119:
1841.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
1851.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
1861.215Smrg	have any build problems with xsrc, or problems with mismatched
1871.215Smrg	versions between xorg-server and drivers.
1881.215Smrg
1891.213Sjmmv20100604:
1901.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
1911.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
1921.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
1931.213Sjmmv	trees by hand.
1941.213Sjmmv
1951.211Stnozaki20100522:
1961.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
1971.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
1981.212Smrg	build problems with xsrc.
1991.212Smrg
2001.212Smrg20100522:
2011.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
2021.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
2031.211Stnozaki
2041.210Schristos20100520:
2051.241Swiz	The location of the xkb compiled descriptions has changed.  Please
2061.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
2071.210Schristos
2081.209Snjoly20100222:
2091.209Snjoly	The shared objects file extension has been changed from .so to
2101.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
2111.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
2121.209Snjoly	your object directories.
2131.209Snjoly
2141.208Sroy20100204:
2151.208Sroy	The termcap database has been removed from the sources,
2161.208Sroy	but has not been marked obsolete so it is not removed
2171.208Sroy	from the system when upgrading.
2181.208Sroy	As such, you will need to remove them from your object
2191.208Sroy	and destination directories.
2201.208Sroy
2211.203Sdyoung20091101:
2221.205Sdholland        After updating, it may be necessary to make the 'cleandir'
2231.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
2241.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
2251.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
2261.203Sdyoung
2271.202Smrg20091001:
2281.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
2291.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
2301.206Sdholland
2311.206Sdholland20091001:
2321.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
2331.202Smrg	symlink, failing the build.  Delete the link, and the subdir
2341.202Smrg	it is in, and retry your build.
2351.202Smrg
2361.201Sdsl20090718:
2371.201Sdsl	libc build changed so that strchr() provides the extra entry
2381.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
2391.201Sdsl	may fail because the archive contains the unwanted index.o.
2401.201Sdsl	(Similarly for strrchr() and rindex().)
2411.201Sdsl
2421.198Smrg20090709:
2431.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
2441.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
2451.198Smrg
2461.197Smrg20090616:
2471.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
2481.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
2491.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
2501.197Smrg	subdirectory has been changed into a file, and this needs to
2511.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
2521.197Smrg
2531.195Sperry20090501:
2541.195Sperry	Several new functions were added to string.h/libc, and this
2551.195Sperry	can cause autoconf problems during the tool build for people
2561.241Swiz	who fail to clean out their tools objects properly.  If you
2571.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
2581.195Sperry	failure during the tool build, clean out all your tools
2591.195Sperry	objects and start again.
2601.195Sperry
2611.194Smrg20090325:
2621.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
2631.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
2641.194Smrg
2651.192Sskrll20090126:
2661.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
2671.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
2681.207Smbalmer	to avoid using the old assembly stub.
2691.192Sskrll
2701.191Sjoerg20090202:
2711.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
2721.191Sjoerg	detection.  It is recommented to rebuild the cache with
2731.191Sjoerg	``pkg_admin rebuild''.
2741.191Sjoerg
2751.184Schristos20090110:
2761.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
2771.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
2781.188Schristos	   This is needed even in the MODULAR kernel because there is
2791.188Schristos	   conditionally compiled code in rtsock.c.
2801.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
2811.184Schristos	   before installing.
2821.184Schristos	3. If you don't use build.sh and you build directly to root, and
2831.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
2841.184Schristos	   are installed properly, and start building libraries first libc
2851.184Schristos	   and libutil, install them and then continue building all the
2861.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
2871.184Schristos	   the new libraries are installed, you can restart the build.
2881.184Schristos	4. If you compile packages and you notice link time warnings,
2891.189Shubertf	   rebuild the required packages to update their shared libraries.
2901.189Shubertf	   Any package you rebuild will require rebuilding all the packages
2911.189Shubertf	   that depend on it.
2921.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
2931.186Schristos	   will be upgraded and it will not be backwards compatible.
2941.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
2951.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
2961.241Swiz	   for utmp.  You are better off removing the old files after
2971.190Sapb	   upgrading.  The automated clearing of /var/run during
2981.190Sapb	   boot, and the automated rotating of files in /var/log by
2991.190Sapb	   newsyslog(8), may mean that you do not have to remove the
3001.190Sapb	   files manually.
3011.190Sapb	7. The optional accounting file (/var/account/acct, see
3021.190Sapb	   accton(8)) has not been versioned, and will need to be
3031.190Sapb	   removed.  The automatic rotation of the accounting file by
3041.190Sapb	   /etc/daily limits the bad consequences of failure to remove
3051.190Sapb	   the file.
3061.196Sdholland	8. Application software that writes time_t to binary files on
3071.241Swiz	   disk will break or need attention.  Most notably: if you are
3081.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
3091.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
3101.185Sjmcneill
3111.183Spgoyette20081219:
3121.183Spgoyette	config(1) has been updated, and one of the files it creates -
3131.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
3141.183Spgoyette	(done automatically by build.sh) and then you need to rerun
3151.183Spgoyette	config on all kernel configuration files before rebuilding those
3161.183Spgoyette	kernels.
3171.183Spgoyette
3181.181Scube20081205:
3191.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
3201.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
3211.181Scube	set and will appear as extra files for MKX11=no update builds.
3221.178Slukem
3231.179Stsutsui20081122:
3241.182Stsutsui	On i386, various kernel options(4) in GENERIC including
3251.180Swiz	file systems have been disabled and moved into kernel modules.
3261.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
3271.179Stsutsui	following files as well as a new GENERIC kernel:
3281.179Stsutsui
3291.179Stsutsui	- build and install kernel modules from src/sys/modules
3301.179Stsutsui
3311.179Stsutsui	- install the latest bootloader, which will load a module
3321.180Swiz	  for the file system from which the kernel is loaded automatically
3331.179Stsutsui
3341.180Swiz	If you have to load your kernel from a file system which is not of
3351.180Swiz	the same type as the root file system, you have to load the necessary
3361.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
3371.179Stsutsui
3381.178Slukem20080827:
3391.178Slukem	If you built and installed a libc from sources between
3401.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
3411.178Slukem	which results in false errors reported by lint(1).
3421.178Slukem	Since this breaks the libc build itself, manual help is
3431.180Swiz	needed -- lint must be disabled temporarily, e.g.:
3441.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
3451.178Slukem
3461.177Schristos20080813:
3471.177Schristos	MKDEBUG build was broken because the .depend files did not know
3481.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
3491.177Schristos
3501.200Sdholland20080802:
3511.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
3521.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
3531.200Sdholland	for -current.
3541.200Sdholland
3551.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
3561.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
3571.200Sdholland	be recompiled.
3581.200Sdholland
3591.200Sdholland	One way to find affected pkgsrc packages:
3601.200Sdholland
3611.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
3621.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
3631.200Sdholland
3641.175Ssimonb20080731:
3651.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
3661.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
3671.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
3681.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
3691.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
3701.176Ssimonb	also requires the super block to be in the UFS2 format.  You
3711.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
3721.175Ssimonb
3731.174Slukem20080721:
3741.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
3751.174Slukem	isn't defined.
3761.174Slukem
3771.173Sfreza20080531:
3781.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
3791.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
3801.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
3811.241Swiz	won't work correctly.  The following sequence of commands:
3821.173Sfreza
3831.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
3841.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
3851.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
3861.173Sfreza
3871.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
3881.173Sfreza
3891.172Slukem20080503:
3901.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
3911.172Slukem
3921.171She20080521:
3931.171She	For a while, unprivileged UPDATE builds would fail to
3941.171She	succeed at the checkflist stage, complaining that
3951.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
3961.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
3971.171She	If you already hit this problem, update the .mk file,
3981.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
3991.171She
4001.174Slukem20080303:
4011.174Slukem	Linker warnings are now fatal if $WARNS>0.
4021.174Slukem
4031.170Schristos20080126:
4041.170Schristos	The posix_fadvise system call has been changed from an assembly
4051.241Swiz	stub, to a c file that calls an assembly stub.  You need to
4061.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
4071.170Schristos	avoid using the old assembly stub.
4081.170Schristos
4091.168Sjoerg20071209:
4101.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
4111.168Sjoerg	get ACPI errors before the attachment, please update your kernel
4121.169Swiz	configuration file appropriately or see GENERIC for more details.
4131.168Sjoerg
4141.166Sxtraeme20071115:
4151.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
4161.166Sxtraeme	argument specified in the kernel configuration file is not valid
4171.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
4181.241Swiz	rather than the EC address port.  Please update your kernel
4191.167Swiz	configuration file appropriately or see GENERIC for more details.
4201.166Sxtraeme
4211.165Sjmmv20071028:
4221.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
4231.165Sjmmv	You need to update any custom kernel configuration file you have
4241.165Sjmmv	to remove any references to pccons (which includes removing the
4251.165Sjmmv	now useless XSERVER option) and replace them with the correct
4261.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
4271.165Sjmmv	for more details.
4281.165Sjmmv
4291.164Sgdt20070913:
4301.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
4311.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
4321.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
4331.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
4341.164Sgdt	could not enumerate interfaces.  (These are noted because
4351.164Sgdt	normal kernel/userspace version matching hygiene is not
4361.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
4371.164Sgdt	and userland are from after 20070913.
4381.164Sgdt
4391.163Sjoerg20070703:
4401.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
4411.199Sdholland	calls the target-specific strip program, and the logic to pass
4421.199Sdholland	down STRIP from make has been removed.  This requires a
4431.199Sdholland	re-installation of tools.
4441.163Sjoerg
4451.161Sdsl20070422:
4461.161Sdsl	The way OS emulations lookup filenames inside the emulation root
4471.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
4481.161Sdsl	to userspace) namei() and lookup() directly check the emulation
4491.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
4501.167Swiz	root file system will be relative to that file system - unless they
4511.161Sdsl	start /../ this is useful when the emulated root is a real install
4521.161Sdsl	that has such links.
4531.161Sdsl	This might affect symlinks that have been added to reference outside
4541.161Sdsl	the emulated root.
4551.161Sdsl
4561.160Sjmcneill20070412:
4571.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
4581.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
4591.160Sjmcneill	example.
4601.160Sjmcneill
4611.159Sgdt20070319:
4621.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
4631.159Sgdt        on many platforms due to incorrect flags settings.  If you
4641.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
4651.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
4661.159Sgdt	rebuild of object files that might have been built
4671.159Sgdt	incorrectly, and ensure that you have at least
4681.159Sgdt	src/lib/libc/Makefile 1.130.
4691.159Sgdt
4701.241Swiz20070210:
4711.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
4721.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
4731.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
4741.158Sdbj        will allow dependencies on those files to get get rebuilt
4751.158Sdbj
4761.157Sapb20070209:
4771.157Sapb        The threading model was changed when the newlock2 branch
4781.157Sapb        was merged to NetBSD-current.  If you boot with a new
4791.157Sapb        kernel (version 4.99.10), then you also need a new pthread
4801.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
4811.157Sapb        an old kernel, then you need the old pthread library
4821.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
4831.157Sapb        the pthread library in sync, old threaded applications should
4841.157Sapb        continue to work with an old or new kernel.  Note that named(8)
4851.157Sapb	is the only threaded application in the base system.
4861.157Sapb
4871.154She20061214:
4881.154She	Following the move of string_to_flags() and flags_to_string()
4891.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
4901.154She	will need to do a "make cleandir" in
4911.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
4921.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
4931.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
4941.156She		as the installation images in distrib/
4951.154She	in order to excise stale references to the old stat_flags.h header
4961.154She	file in the ls sources -- stat_flags.h has been removed.
4971.154She
4981.152Schristos20061108:
4991.152Schristos	The configure script used in the src/tools/gcc compiler has been
5001.152Schristos	changed to indicate that our libc has ssp support built-in and
5011.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
5021.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
5031.152Schristos
5041.151Srpaulo20061009:
5051.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
5061.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
5071.151Srpaulo
5081.150Sbjh2120060814:
5091.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
5101.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
5111.150Sbjh21	kernel configuration for an example.  X servers from the last
5121.150Sbjh21	few years should cope.
5131.150Sbjh21
5141.149Schristos20060703:
5151.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
5161.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
5171.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
5181.149Schristos
5191.148Sdogcow20060627:
5201.148Sdogcow	socket(2) has changed, and its system call has been versioned.
5211.148Sdogcow	For userlands with the old version of socket(2), make sure that
5221.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
5231.148Sdogcow	errors will result.
5241.148Sdogcow
5251.1SabsHints for a more successful build:
5261.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5271.123Sjmc    Use build.sh, but do not use its "expert mode":
5281.132Sjmmv	This will automatically build the tools in the
5291.123Sjmc	   correct order, and it will keep the tools and the
5301.123Sjmc	   new build products from interfering with the running
5311.123Sjmc	   system.  This will allow you to ignore most of the
5321.123Sjmc	   other advice in this file.
5331.2Smrg    Build a new kernel first:
5341.2Smrg	This makes sure that any new system calls or features
5351.2Smrg	   expected by the new userland will be present.  This
5361.2Smrg	   helps to avoid critical errors when upgrading.
5371.1Sabs    Use object directories:
5381.1Sabs	This helps to keep stale object
5391.1Sabs	   files from polluting the build if a Makefile "forgets"
5401.1Sabs	   about one.  It also makes it easier to clean up after
5411.1Sabs	   a build.  It's also necessary if you want to use the
5421.1Sabs	   same source tree for multiple machines.
5431.123Sjmc	   To use object directories with build.sh:
5441.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
5451.123Sjmc	   To use object directories without using build.sh:
5461.1Sabs	    a) cd /usr/src ; make cleandir
5471.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
5481.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
5491.1Sabs	    d) cd /usr/src ; make build
5501.2Smrg	   Note that running "make obj" in a directory will create
5511.2Smrg	   in obj.$MACHINE directory.
5521.1Sabs    Build to a DESTDIR:
5531.123Sjmc	This helps to keep old installed files (especially libraries)
5541.123Sjmc	   from interfering with the new build.
5551.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
5561.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
5571.123Sjmc	   environment variable before running make build.  It should be
5581.123Sjmc	   set to the pathname of an initially empty directory.
5591.123Sjmc	   Problems: if you do not use build.sh, you might need to
5601.123Sjmc		update critical utilities without using DESTDIR since
5611.123Sjmc		nothing is executed from what is installed in DESTDIR.
5621.123Sjmc		(See critical utils, below.)
5631.1Sabs    Build often:
5641.1Sabs	This keeps critical utilities current enough to not choke
5651.1Sabs	on any other part of the source tree that depends on up to
5661.123Sjmc	date functionality.  If you use build.sh, you should not have
5671.123Sjmc	this problem.
5681.241Swiz
5691.1SabsWhat to do if things don't work:
5701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5711.230StlsWhen things don't work there are usually a few things that commonly
5721.1Sabsshould be done.
5731.1Sabs    1)	make includes
5741.1Sabs	This should be done automatically by make build.
5751.1Sabs    2)  cd share/mk && make install
5761.1Sabs	Again, automatically done by make build.
5771.1Sabs
5781.1SabsFailsafe rebuild of a small part of the tree:
5791.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5801.1SabsTo make sure you rebuild something correctly you want to do
5811.1Sabssomething like the following:
5821.1Sabs    1)  Make sure the includes and .mk files are up to date.
5831.1Sabs    2)  Make sure any program used to build the particular
5841.1Sabs	utility is up to date.  (yacc, lex, etc...)
5851.1Sabs    3)  cd ...path/to/util...
5861.1Sabs	make cleandir
5871.1Sabs	rm ...all obj directories...
5881.1Sabs	make cleandir			# yes, again
5891.1Sabs	make obj
5901.1Sabs	make depend && make
5911.1Sabs
5921.1SabsFailsafe rebuild of the entire tree:
5931.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5941.1SabsIf you really want to make sure the source tree is clean and
5951.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
5961.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
5971.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
5981.1Sabs
5991.1Sabs---cut here---
6001.1Sabs#!/bin/sh
6011.1Sabs. /etc/mk.conf
6021.1Sabs
6031.58Slukemif [ -z $NETBSDSRCDIR ] ; then
6041.58Slukem    NETBSDSRCDIR=/usr/src
6051.1Sabsfi
6061.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
6071.1Sabs    echo Unable to find sources
6081.1Sabs    exit 1
6091.1Sabsfi
6101.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
6111.1Sabs
6121.1Sabsif [ -z $BSDOBJDIR ] ; then
6131.1Sabs    BSDOBJDIR=/usr/obj
6141.1Sabsfi
6151.1Sabsif [ -d $BSDOBJDIR ] ; then
6161.1Sabs    rm -rf $BSDOBJDIR
6171.1Sabsfi
6181.1Sabs
6191.58Slukemcd $NETBSDSRCDIR && make cleandir
6201.1Sabs
6211.1Sabs---cut here---
6221.1Sabs
6231.1SabsCritical utilities:
6241.1Sabs^^^^^^^^^^^^^^^^^^^
6251.3Sitojun	usr.bin/compile_et
6261.1Sabs	usr.bin/make
6271.1Sabs	usr.bin/yacc
6281.1Sabs	usr.bin/lex
6291.11Slukem	usr.bin/xlint
6301.142Sdrochner	usr.bin/config
6311.1Sabs
6321.34SsimonbOther problems and possible solutions:
6331.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6341.1SabsSymptom:Complaints involving a Makefile.
6351.17SerhFix:	Rebuild usr.bin/make:
6361.17Serh	cd usr.bin/make && make && make install
6371.111Ssimonb	Or, a failsafe method if that doesn't work:
6381.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
6391.17Serh
6401.1SabsFix:	Make sure .mk files are up to date.
6411.1Sabs	cd share/mk && make install
6421.2Smrg
6431.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
6441.142SdrochnerFix:	Rebuild usr.bin/config
6451.1Sabs
6461.1SabsSymptom:
6471.1SabsFix:	Rebuild usr.bin/yacc
6481.1Sabs
6491.1SabsSymptom:
6501.1SabsFix:	Rebuild usr.bin/lex
6511.1Sabs
6521.1SabsSymptom:
6531.1SabsFix:	rm /usr/lib/libbfd.a
6541.4Sitojun
6551.4SitojunSymptom:Obsolete intermediate files are used during compilation
6561.4SitojunFix:	Try the following sequence of commands in the directory in question.
6571.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
6581.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
6591.4Sitojun	may remain.  The command tries to clean everything up)
6601.5Swiz
6611.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
6621.207Smbalmer	pointer type
6631.5SwizFix:	Rebuild and install usr.bin/menuc
6641.12Sitojun
6651.12SitojunSymptom:mklocale not found during build in share/locale/ctype
6661.12SitojunFix:	Build and install usr.bin/mklocale
6671.13Sdogcow
6681.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
6691.13SdogcowFix:    Rebuild and install lib/libc
6701.13Sdogcow
6711.142SdrochnerSymptom:usr.bin/config fails to build.
6721.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
6731.13Sdogcow
6741.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
6751.19ScgdFix:    Rebuild and install lib/libc
6761.24Sabs
6771.24SabsSymptom:lint does not understand the '-X' option
6781.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
6791.223Sjoerg
6801.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
6811.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
6821.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
6831.257Sapb
6841.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
6851.257Sapb	No such file or directory.
6861.257SapbCause:	If a directory is created by mistake, then it is sometimes
6871.257Sapb	deleted from the CVS repository using administrative commands
6881.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
6891.257Sapb	contains references to a directory that has been deleted on the
6901.257Sapb	server in this way, then "cvs update" reports this error.
6911.257SapbFix:	Recursively delete the affected directory from your working tree
6921.257Sapb	and try the update again.
693