UPDATING revision 1.259
11.259Smsaitoh$NetBSD: UPDATING,v 1.259 2014/10/27 11:21:28 msaitoh 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.258Smartin20141026:
231.259Smsaitoh	A mishap during the import of pppd may cause your corruption
241.258Smartin	in your cvs directory if you happened to do a cvs update
251.258Smartin	during a short period of time. To fix, just remove the
261.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
271.258Smartin	and let cvs restore it on next update.
281.258Smartin
291.256Sapb20140721:
301.256Sapb	The src/external/mit/lua/src directory was accidentally created
311.256Sapb	and then deleted in the CVS repository.  If you get errors like
321.256Sapb
331.256Sapb	cvs [update aborted]: cannot open directory
341.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
351.256Sapb
361.256Sapb	then delete your local copy of that directory tree and try again.
371.256Sapb
381.255Sjoerg20140530:
391.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
401.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
411.255Sjoerg
421.251Smartin20140131:
431.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
441.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
451.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
461.251Smartin
471.250Schristos20131227:
481.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
491.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
501.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
511.250Schristos	   statements to avoid being exposed.
521.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
531.250Schristos	   to make clean in libc
541.250Schristos
551.249Smrg20131129:
561.249Smrg	The GMP sources were updated, and builds will likely fail without
571.249Smrg	cleaning their build trees for both tools and in-tree, like below.
581.249Smrg
591.248Smrg20131128:
601.248Smrg	The MPC and MPFR sources were updated, and builds may require their
611.248Smrg	tools and in-tree directories cleaned for successful updates.
621.248Smrg
631.246Smartin20130605:
641.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
651.247Sspz	to IPSEC (and the older IPSEC version removed).
661.247Sspz
671.247Sspz20130605:
681.246Smartin	Previous freetype installations eroneously installed private
691.246Smartin	header files. If you are building against a non-empty $DESTDIR,
701.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
711.246Smartin
721.245Smrg20130531:
731.245Smrg	The xdm update may cause build failure due to xdm.man being
741.245Smrg	in the obj tree.  Make sure to ensure any like this:
751.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
761.245Smrg	is fixed by deleting the xdm.man in the obj tree.
771.245Smrg
781.244Smrg20130530:
791.244Smrg	Updates of many xsrc packages will leave old .pc files around.
801.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
811.244Smrg
821.242Schristos20130301:
831.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
841.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
851.242Schristos
861.238Sdholland20120726:
871.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
881.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
891.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
901.241Swiz	some cases may succeed and install broken OpenSSL libraries that
911.240Sdholland	cause third-party software to link incorrectly and/or crash.
921.238Sdholland
931.237Swiz20120507:
941.241Swiz	The database schema for makemandb was changed.  You will
951.237Swiz	need to update the database using 'makemandb -f' or wait
961.237Swiz	for the next weekly run to fix it.
971.237Swiz
981.236Sbsh20120319:
991.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
1001.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
1011.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
1021.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
1031.236Sbsh	mk.conf.
1041.236Sbsh
1051.235Sjoerg20120216:
1061.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
1071.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
1081.239Sdholland	and 20120216, daily and weekly could have created an unreadable
1091.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
1101.235Sjoerg	the next run of weekly will fix it.
1111.233Sjoerg
1121.232Schristos20111227:
1131.232Schristos	If you built between 20111225 and 20111227 you need to remove
1141.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
1151.232Schristos	bump has been reverted.
1161.232Schristos
1171.231Stls20111125:
1181.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
1191.231Stls	means it should no longer be explicitly listed in kernel
1201.231Stls	configuration files.  The line "pseudo-device rnd" should be
1211.231Stls	removed from any custom kernel config files users may have.
1221.231Stls
1231.230Stls20111119:
1241.230Stls	A problem with the datastructures used by the rndctl(8)
1251.230Stls	utility (pointers in datastructures in an array, making 32->64
1261.230Stls	bit compatibility very painful) has been fixed in a
1271.230Stls	non-backwards-compatible way.  If you replace your kernel,
1281.230Stls	replace your rndctl executable too.
1291.241Swiz
1301.229Sjym20111001:
1311.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
1321.229Sjym	changed and their new version is not backward compatible with the old
1331.241Swiz	one.  So ensure that all consumers of these functions (currently:
1341.229Sjym	quota2 code and its tests) are updated together with the new lib.
1351.229Sjym
1361.228Smrg20110817:
1371.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
1381.228Smrg	DESTDIR for them should be deleted before updating.
1391.228Smrg
1401.227Sriastrad20110806:
1411.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
1421.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
1431.227Sriastrad
1441.226Smrg20110805:
1451.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
1461.226Smrg	the tree to be cleaned.  Best to delete both objdir and
1471.226Smrg	DESTDIR before running this update.  So far, only the
1481.226Smrg	sparc64, mips and powerpc platforms have changed.
1491.226Smrg
1501.225Smatt20110803:
1511.241Swiz	The layout of external/public-domain/xz has changed.  To do an
1521.225Smatt	update build you will have to remove the contents of the OBJDIR
1531.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
1541.225Smatt	is now a directory.
1551.225Smatt
1561.223Sjoerg20110410:
1571.241Swiz	The configuration of src/tools/gcc has changed.  To do an
1581.224Sdholland	update build you have to clean both tools/binutils and
1591.224Sdholland	tools/gcc by hand.
1601.223Sjoerg
1611.222Splunky20110328:
1621.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
1631.241Swiz	ordering issues with "make all".  It may be necessary to remove
1641.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
1651.222Splunky	if your update build fails, as the "Xorg" entry there is now a
1661.222Splunky	directory.
1671.222Splunky
1681.220Sjoerg20110121:
1691.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
1701.220Sjoerg	the build of individual parts of the tree.  This is handled
1711.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
1721.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
1731.218Sjoerg
1741.217Sjruoho20101217:
1751.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
1761.241Swiz	by default.  It may be necessary to manually update passwd(5) and
1771.217Sjruoho	group(5) in order to make the program work with existing setups.
1781.217Sjruoho
1791.216Schristos20101125:
1801.216Schristos	The latest changes to setenv(3) dissallow setting environment
1811.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
1821.241Swiz	assumed that this was allowed.  Installing a new libc with an
1831.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
1841.216Schristos	break which affects the autoconf tests for dependency finding,
1851.216Schristos	so building gcc will end up printing:
1861.216Schristos	    checking dependency style of gcc... none
1871.216Schristos	    configure: error: no usable dependency style found
1881.216Schristos	Fix it by rebuilding and re-installing env.
1891.138Slukem
1901.215Smrg20101119:
1911.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
1921.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
1931.215Smrg	have any build problems with xsrc, or problems with mismatched
1941.215Smrg	versions between xorg-server and drivers.
1951.215Smrg
1961.213Sjmmv20100604:
1971.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
1981.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
1991.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
2001.213Sjmmv	trees by hand.
2011.213Sjmmv
2021.211Stnozaki20100522:
2031.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
2041.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
2051.212Smrg	build problems with xsrc.
2061.212Smrg
2071.212Smrg20100522:
2081.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
2091.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
2101.211Stnozaki
2111.210Schristos20100520:
2121.241Swiz	The location of the xkb compiled descriptions has changed.  Please
2131.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
2141.210Schristos
2151.209Snjoly20100222:
2161.209Snjoly	The shared objects file extension has been changed from .so to
2171.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
2181.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
2191.209Snjoly	your object directories.
2201.209Snjoly
2211.208Sroy20100204:
2221.208Sroy	The termcap database has been removed from the sources,
2231.208Sroy	but has not been marked obsolete so it is not removed
2241.208Sroy	from the system when upgrading.
2251.208Sroy	As such, you will need to remove them from your object
2261.208Sroy	and destination directories.
2271.208Sroy
2281.203Sdyoung20091101:
2291.205Sdholland        After updating, it may be necessary to make the 'cleandir'
2301.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
2311.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
2321.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
2331.203Sdyoung
2341.202Smrg20091001:
2351.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
2361.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
2371.206Sdholland
2381.206Sdholland20091001:
2391.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
2401.202Smrg	symlink, failing the build.  Delete the link, and the subdir
2411.202Smrg	it is in, and retry your build.
2421.202Smrg
2431.201Sdsl20090718:
2441.201Sdsl	libc build changed so that strchr() provides the extra entry
2451.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
2461.201Sdsl	may fail because the archive contains the unwanted index.o.
2471.201Sdsl	(Similarly for strrchr() and rindex().)
2481.201Sdsl
2491.198Smrg20090709:
2501.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
2511.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
2521.198Smrg
2531.197Smrg20090616:
2541.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
2551.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
2561.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
2571.197Smrg	subdirectory has been changed into a file, and this needs to
2581.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
2591.197Smrg
2601.195Sperry20090501:
2611.195Sperry	Several new functions were added to string.h/libc, and this
2621.195Sperry	can cause autoconf problems during the tool build for people
2631.241Swiz	who fail to clean out their tools objects properly.  If you
2641.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
2651.195Sperry	failure during the tool build, clean out all your tools
2661.195Sperry	objects and start again.
2671.195Sperry
2681.194Smrg20090325:
2691.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
2701.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
2711.194Smrg
2721.192Sskrll20090126:
2731.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
2741.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
2751.207Smbalmer	to avoid using the old assembly stub.
2761.192Sskrll
2771.191Sjoerg20090202:
2781.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
2791.191Sjoerg	detection.  It is recommented to rebuild the cache with
2801.191Sjoerg	``pkg_admin rebuild''.
2811.191Sjoerg
2821.184Schristos20090110:
2831.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
2841.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
2851.188Schristos	   This is needed even in the MODULAR kernel because there is
2861.188Schristos	   conditionally compiled code in rtsock.c.
2871.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
2881.184Schristos	   before installing.
2891.184Schristos	3. If you don't use build.sh and you build directly to root, and
2901.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
2911.184Schristos	   are installed properly, and start building libraries first libc
2921.184Schristos	   and libutil, install them and then continue building all the
2931.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
2941.184Schristos	   the new libraries are installed, you can restart the build.
2951.184Schristos	4. If you compile packages and you notice link time warnings,
2961.189Shubertf	   rebuild the required packages to update their shared libraries.
2971.189Shubertf	   Any package you rebuild will require rebuilding all the packages
2981.189Shubertf	   that depend on it.
2991.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
3001.186Schristos	   will be upgraded and it will not be backwards compatible.
3011.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
3021.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
3031.241Swiz	   for utmp.  You are better off removing the old files after
3041.190Sapb	   upgrading.  The automated clearing of /var/run during
3051.190Sapb	   boot, and the automated rotating of files in /var/log by
3061.190Sapb	   newsyslog(8), may mean that you do not have to remove the
3071.190Sapb	   files manually.
3081.190Sapb	7. The optional accounting file (/var/account/acct, see
3091.190Sapb	   accton(8)) has not been versioned, and will need to be
3101.190Sapb	   removed.  The automatic rotation of the accounting file by
3111.190Sapb	   /etc/daily limits the bad consequences of failure to remove
3121.190Sapb	   the file.
3131.196Sdholland	8. Application software that writes time_t to binary files on
3141.241Swiz	   disk will break or need attention.  Most notably: if you are
3151.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
3161.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
3171.185Sjmcneill
3181.183Spgoyette20081219:
3191.183Spgoyette	config(1) has been updated, and one of the files it creates -
3201.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
3211.183Spgoyette	(done automatically by build.sh) and then you need to rerun
3221.183Spgoyette	config on all kernel configuration files before rebuilding those
3231.183Spgoyette	kernels.
3241.183Spgoyette
3251.181Scube20081205:
3261.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
3271.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
3281.181Scube	set and will appear as extra files for MKX11=no update builds.
3291.178Slukem
3301.179Stsutsui20081122:
3311.182Stsutsui	On i386, various kernel options(4) in GENERIC including
3321.180Swiz	file systems have been disabled and moved into kernel modules.
3331.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
3341.179Stsutsui	following files as well as a new GENERIC kernel:
3351.179Stsutsui
3361.179Stsutsui	- build and install kernel modules from src/sys/modules
3371.179Stsutsui
3381.179Stsutsui	- install the latest bootloader, which will load a module
3391.180Swiz	  for the file system from which the kernel is loaded automatically
3401.179Stsutsui
3411.180Swiz	If you have to load your kernel from a file system which is not of
3421.180Swiz	the same type as the root file system, you have to load the necessary
3431.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
3441.179Stsutsui
3451.178Slukem20080827:
3461.178Slukem	If you built and installed a libc from sources between
3471.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
3481.178Slukem	which results in false errors reported by lint(1).
3491.178Slukem	Since this breaks the libc build itself, manual help is
3501.180Swiz	needed -- lint must be disabled temporarily, e.g.:
3511.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
3521.178Slukem
3531.177Schristos20080813:
3541.177Schristos	MKDEBUG build was broken because the .depend files did not know
3551.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
3561.177Schristos
3571.200Sdholland20080802:
3581.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
3591.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
3601.200Sdholland	for -current.
3611.200Sdholland
3621.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
3631.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
3641.200Sdholland	be recompiled.
3651.200Sdholland
3661.200Sdholland	One way to find affected pkgsrc packages:
3671.200Sdholland
3681.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
3691.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
3701.200Sdholland
3711.175Ssimonb20080731:
3721.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
3731.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
3741.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
3751.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
3761.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
3771.176Ssimonb	also requires the super block to be in the UFS2 format.  You
3781.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
3791.175Ssimonb
3801.174Slukem20080721:
3811.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
3821.174Slukem	isn't defined.
3831.174Slukem
3841.173Sfreza20080531:
3851.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
3861.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
3871.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
3881.241Swiz	won't work correctly.  The following sequence of commands:
3891.173Sfreza
3901.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
3911.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
3921.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
3931.173Sfreza
3941.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
3951.173Sfreza
3961.172Slukem20080503:
3971.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
3981.172Slukem
3991.171She20080521:
4001.171She	For a while, unprivileged UPDATE builds would fail to
4011.171She	succeed at the checkflist stage, complaining that
4021.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
4031.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
4041.171She	If you already hit this problem, update the .mk file,
4051.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
4061.171She
4071.174Slukem20080303:
4081.174Slukem	Linker warnings are now fatal if $WARNS>0.
4091.174Slukem
4101.170Schristos20080126:
4111.170Schristos	The posix_fadvise system call has been changed from an assembly
4121.241Swiz	stub, to a c file that calls an assembly stub.  You need to
4131.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
4141.170Schristos	avoid using the old assembly stub.
4151.170Schristos
4161.168Sjoerg20071209:
4171.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
4181.168Sjoerg	get ACPI errors before the attachment, please update your kernel
4191.169Swiz	configuration file appropriately or see GENERIC for more details.
4201.168Sjoerg
4211.166Sxtraeme20071115:
4221.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
4231.166Sxtraeme	argument specified in the kernel configuration file is not valid
4241.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
4251.241Swiz	rather than the EC address port.  Please update your kernel
4261.167Swiz	configuration file appropriately or see GENERIC for more details.
4271.166Sxtraeme
4281.165Sjmmv20071028:
4291.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
4301.165Sjmmv	You need to update any custom kernel configuration file you have
4311.165Sjmmv	to remove any references to pccons (which includes removing the
4321.165Sjmmv	now useless XSERVER option) and replace them with the correct
4331.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
4341.165Sjmmv	for more details.
4351.165Sjmmv
4361.164Sgdt20070913:
4371.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
4381.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
4391.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
4401.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
4411.164Sgdt	could not enumerate interfaces.  (These are noted because
4421.164Sgdt	normal kernel/userspace version matching hygiene is not
4431.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
4441.164Sgdt	and userland are from after 20070913.
4451.164Sgdt
4461.163Sjoerg20070703:
4471.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
4481.199Sdholland	calls the target-specific strip program, and the logic to pass
4491.199Sdholland	down STRIP from make has been removed.  This requires a
4501.199Sdholland	re-installation of tools.
4511.163Sjoerg
4521.161Sdsl20070422:
4531.161Sdsl	The way OS emulations lookup filenames inside the emulation root
4541.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
4551.161Sdsl	to userspace) namei() and lookup() directly check the emulation
4561.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
4571.167Swiz	root file system will be relative to that file system - unless they
4581.161Sdsl	start /../ this is useful when the emulated root is a real install
4591.161Sdsl	that has such links.
4601.161Sdsl	This might affect symlinks that have been added to reference outside
4611.161Sdsl	the emulated root.
4621.161Sdsl
4631.160Sjmcneill20070412:
4641.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
4651.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
4661.160Sjmcneill	example.
4671.160Sjmcneill
4681.159Sgdt20070319:
4691.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
4701.159Sgdt        on many platforms due to incorrect flags settings.  If you
4711.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
4721.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
4731.159Sgdt	rebuild of object files that might have been built
4741.159Sgdt	incorrectly, and ensure that you have at least
4751.159Sgdt	src/lib/libc/Makefile 1.130.
4761.159Sgdt
4771.241Swiz20070210:
4781.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
4791.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
4801.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
4811.158Sdbj        will allow dependencies on those files to get get rebuilt
4821.158Sdbj
4831.157Sapb20070209:
4841.157Sapb        The threading model was changed when the newlock2 branch
4851.157Sapb        was merged to NetBSD-current.  If you boot with a new
4861.157Sapb        kernel (version 4.99.10), then you also need a new pthread
4871.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
4881.157Sapb        an old kernel, then you need the old pthread library
4891.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
4901.157Sapb        the pthread library in sync, old threaded applications should
4911.157Sapb        continue to work with an old or new kernel.  Note that named(8)
4921.157Sapb	is the only threaded application in the base system.
4931.157Sapb
4941.154She20061214:
4951.154She	Following the move of string_to_flags() and flags_to_string()
4961.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
4971.154She	will need to do a "make cleandir" in
4981.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
4991.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
5001.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
5011.156She		as the installation images in distrib/
5021.154She	in order to excise stale references to the old stat_flags.h header
5031.154She	file in the ls sources -- stat_flags.h has been removed.
5041.154She
5051.152Schristos20061108:
5061.152Schristos	The configure script used in the src/tools/gcc compiler has been
5071.152Schristos	changed to indicate that our libc has ssp support built-in and
5081.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
5091.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
5101.152Schristos
5111.151Srpaulo20061009:
5121.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
5131.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
5141.151Srpaulo
5151.150Sbjh2120060814:
5161.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
5171.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
5181.150Sbjh21	kernel configuration for an example.  X servers from the last
5191.150Sbjh21	few years should cope.
5201.150Sbjh21
5211.149Schristos20060703:
5221.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
5231.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
5241.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
5251.149Schristos
5261.148Sdogcow20060627:
5271.148Sdogcow	socket(2) has changed, and its system call has been versioned.
5281.148Sdogcow	For userlands with the old version of socket(2), make sure that
5291.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
5301.148Sdogcow	errors will result.
5311.148Sdogcow
5321.1SabsHints for a more successful build:
5331.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5341.123Sjmc    Use build.sh, but do not use its "expert mode":
5351.132Sjmmv	This will automatically build the tools in the
5361.123Sjmc	   correct order, and it will keep the tools and the
5371.123Sjmc	   new build products from interfering with the running
5381.123Sjmc	   system.  This will allow you to ignore most of the
5391.123Sjmc	   other advice in this file.
5401.2Smrg    Build a new kernel first:
5411.2Smrg	This makes sure that any new system calls or features
5421.2Smrg	   expected by the new userland will be present.  This
5431.2Smrg	   helps to avoid critical errors when upgrading.
5441.1Sabs    Use object directories:
5451.1Sabs	This helps to keep stale object
5461.1Sabs	   files from polluting the build if a Makefile "forgets"
5471.1Sabs	   about one.  It also makes it easier to clean up after
5481.1Sabs	   a build.  It's also necessary if you want to use the
5491.1Sabs	   same source tree for multiple machines.
5501.123Sjmc	   To use object directories with build.sh:
5511.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
5521.123Sjmc	   To use object directories without using build.sh:
5531.1Sabs	    a) cd /usr/src ; make cleandir
5541.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
5551.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
5561.1Sabs	    d) cd /usr/src ; make build
5571.2Smrg	   Note that running "make obj" in a directory will create
5581.2Smrg	   in obj.$MACHINE directory.
5591.1Sabs    Build to a DESTDIR:
5601.123Sjmc	This helps to keep old installed files (especially libraries)
5611.123Sjmc	   from interfering with the new build.
5621.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
5631.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
5641.123Sjmc	   environment variable before running make build.  It should be
5651.123Sjmc	   set to the pathname of an initially empty directory.
5661.123Sjmc	   Problems: if you do not use build.sh, you might need to
5671.123Sjmc		update critical utilities without using DESTDIR since
5681.123Sjmc		nothing is executed from what is installed in DESTDIR.
5691.123Sjmc		(See critical utils, below.)
5701.1Sabs    Build often:
5711.1Sabs	This keeps critical utilities current enough to not choke
5721.1Sabs	on any other part of the source tree that depends on up to
5731.123Sjmc	date functionality.  If you use build.sh, you should not have
5741.123Sjmc	this problem.
5751.241Swiz
5761.1SabsWhat to do if things don't work:
5771.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5781.230StlsWhen things don't work there are usually a few things that commonly
5791.1Sabsshould be done.
5801.1Sabs    1)	make includes
5811.1Sabs	This should be done automatically by make build.
5821.1Sabs    2)  cd share/mk && make install
5831.1Sabs	Again, automatically done by make build.
5841.1Sabs
5851.1SabsFailsafe rebuild of a small part of the tree:
5861.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5871.1SabsTo make sure you rebuild something correctly you want to do
5881.1Sabssomething like the following:
5891.1Sabs    1)  Make sure the includes and .mk files are up to date.
5901.1Sabs    2)  Make sure any program used to build the particular
5911.1Sabs	utility is up to date.  (yacc, lex, etc...)
5921.1Sabs    3)  cd ...path/to/util...
5931.1Sabs	make cleandir
5941.1Sabs	rm ...all obj directories...
5951.1Sabs	make cleandir			# yes, again
5961.1Sabs	make obj
5971.1Sabs	make depend && make
5981.1Sabs
5991.1SabsFailsafe rebuild of the entire tree:
6001.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6011.1SabsIf you really want to make sure the source tree is clean and
6021.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
6031.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
6041.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
6051.1Sabs
6061.1Sabs---cut here---
6071.1Sabs#!/bin/sh
6081.1Sabs. /etc/mk.conf
6091.1Sabs
6101.58Slukemif [ -z $NETBSDSRCDIR ] ; then
6111.58Slukem    NETBSDSRCDIR=/usr/src
6121.1Sabsfi
6131.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
6141.1Sabs    echo Unable to find sources
6151.1Sabs    exit 1
6161.1Sabsfi
6171.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
6181.1Sabs
6191.1Sabsif [ -z $BSDOBJDIR ] ; then
6201.1Sabs    BSDOBJDIR=/usr/obj
6211.1Sabsfi
6221.1Sabsif [ -d $BSDOBJDIR ] ; then
6231.1Sabs    rm -rf $BSDOBJDIR
6241.1Sabsfi
6251.1Sabs
6261.58Slukemcd $NETBSDSRCDIR && make cleandir
6271.1Sabs
6281.1Sabs---cut here---
6291.1Sabs
6301.1SabsCritical utilities:
6311.1Sabs^^^^^^^^^^^^^^^^^^^
6321.3Sitojun	usr.bin/compile_et
6331.1Sabs	usr.bin/make
6341.1Sabs	usr.bin/yacc
6351.1Sabs	usr.bin/lex
6361.11Slukem	usr.bin/xlint
6371.142Sdrochner	usr.bin/config
6381.1Sabs
6391.34SsimonbOther problems and possible solutions:
6401.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6411.1SabsSymptom:Complaints involving a Makefile.
6421.17SerhFix:	Rebuild usr.bin/make:
6431.17Serh	cd usr.bin/make && make && make install
6441.111Ssimonb	Or, a failsafe method if that doesn't work:
6451.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
6461.17Serh
6471.1SabsFix:	Make sure .mk files are up to date.
6481.1Sabs	cd share/mk && make install
6491.2Smrg
6501.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
6511.142SdrochnerFix:	Rebuild usr.bin/config
6521.1Sabs
6531.1SabsSymptom:
6541.1SabsFix:	Rebuild usr.bin/yacc
6551.1Sabs
6561.1SabsSymptom:
6571.1SabsFix:	Rebuild usr.bin/lex
6581.1Sabs
6591.1SabsSymptom:
6601.1SabsFix:	rm /usr/lib/libbfd.a
6611.4Sitojun
6621.4SitojunSymptom:Obsolete intermediate files are used during compilation
6631.4SitojunFix:	Try the following sequence of commands in the directory in question.
6641.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
6651.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
6661.4Sitojun	may remain.  The command tries to clean everything up)
6671.5Swiz
6681.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
6691.207Smbalmer	pointer type
6701.5SwizFix:	Rebuild and install usr.bin/menuc
6711.12Sitojun
6721.12SitojunSymptom:mklocale not found during build in share/locale/ctype
6731.12SitojunFix:	Build and install usr.bin/mklocale
6741.13Sdogcow
6751.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
6761.13SdogcowFix:    Rebuild and install lib/libc
6771.13Sdogcow
6781.142SdrochnerSymptom:usr.bin/config fails to build.
6791.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
6801.13Sdogcow
6811.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
6821.19ScgdFix:    Rebuild and install lib/libc
6831.24Sabs
6841.24SabsSymptom:lint does not understand the '-X' option
6851.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
6861.223Sjoerg
6871.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
6881.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
6891.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
6901.257Sapb
6911.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
6921.257Sapb	No such file or directory.
6931.257SapbCause:	If a directory is created by mistake, then it is sometimes
6941.257Sapb	deleted from the CVS repository using administrative commands
6951.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
6961.257Sapb	contains references to a directory that has been deleted on the
6971.257Sapb	server in this way, then "cvs update" reports this error.
6981.257SapbFix:	Recursively delete the affected directory from your working tree
6991.257Sapb	and try the update again.
700