UPDATING revision 1.260
11.260Sskrll$NetBSD: UPDATING,v 1.260 2015/03/11 08:50:32 skrll 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.260Sskrll20150310:
231.260Sskrll	Improvements to openssl for arm mean that update builds of
241.260Sskrll	the openssl libraries will fail. A make cleandir in
251.260Sskrll	external/bsd/openssl/lib is needed
261.260Sskrll
271.258Smartin20141026:
281.259Smsaitoh	A mishap during the import of pppd may cause your corruption
291.258Smartin	in your cvs directory if you happened to do a cvs update
301.258Smartin	during a short period of time. To fix, just remove the
311.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
321.258Smartin	and let cvs restore it on next update.
331.258Smartin
341.256Sapb20140721:
351.256Sapb	The src/external/mit/lua/src directory was accidentally created
361.256Sapb	and then deleted in the CVS repository.  If you get errors like
371.256Sapb
381.256Sapb	cvs [update aborted]: cannot open directory
391.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
401.256Sapb
411.256Sapb	then delete your local copy of that directory tree and try again.
421.256Sapb
431.255Sjoerg20140530:
441.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
451.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
461.255Sjoerg
471.251Smartin20140131:
481.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
491.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
501.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
511.251Smartin
521.250Schristos20131227:
531.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
541.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
551.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
561.250Schristos	   statements to avoid being exposed.
571.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
581.250Schristos	   to make clean in libc
591.250Schristos
601.249Smrg20131129:
611.249Smrg	The GMP sources were updated, and builds will likely fail without
621.249Smrg	cleaning their build trees for both tools and in-tree, like below.
631.249Smrg
641.248Smrg20131128:
651.248Smrg	The MPC and MPFR sources were updated, and builds may require their
661.248Smrg	tools and in-tree directories cleaned for successful updates.
671.248Smrg
681.246Smartin20130605:
691.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
701.247Sspz	to IPSEC (and the older IPSEC version removed).
711.247Sspz
721.247Sspz20130605:
731.246Smartin	Previous freetype installations eroneously installed private
741.246Smartin	header files. If you are building against a non-empty $DESTDIR,
751.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
761.246Smartin
771.245Smrg20130531:
781.245Smrg	The xdm update may cause build failure due to xdm.man being
791.245Smrg	in the obj tree.  Make sure to ensure any like this:
801.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
811.245Smrg	is fixed by deleting the xdm.man in the obj tree.
821.245Smrg
831.244Smrg20130530:
841.244Smrg	Updates of many xsrc packages will leave old .pc files around.
851.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
861.244Smrg
871.242Schristos20130301:
881.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
891.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
901.242Schristos
911.238Sdholland20120726:
921.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
931.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
941.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
951.241Swiz	some cases may succeed and install broken OpenSSL libraries that
961.240Sdholland	cause third-party software to link incorrectly and/or crash.
971.238Sdholland
981.237Swiz20120507:
991.241Swiz	The database schema for makemandb was changed.  You will
1001.237Swiz	need to update the database using 'makemandb -f' or wait
1011.237Swiz	for the next weekly run to fix it.
1021.237Swiz
1031.236Sbsh20120319:
1041.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
1051.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
1061.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
1071.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
1081.236Sbsh	mk.conf.
1091.236Sbsh
1101.235Sjoerg20120216:
1111.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
1121.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
1131.239Sdholland	and 20120216, daily and weekly could have created an unreadable
1141.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
1151.235Sjoerg	the next run of weekly will fix it.
1161.233Sjoerg
1171.232Schristos20111227:
1181.232Schristos	If you built between 20111225 and 20111227 you need to remove
1191.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
1201.232Schristos	bump has been reverted.
1211.232Schristos
1221.231Stls20111125:
1231.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
1241.231Stls	means it should no longer be explicitly listed in kernel
1251.231Stls	configuration files.  The line "pseudo-device rnd" should be
1261.231Stls	removed from any custom kernel config files users may have.
1271.231Stls
1281.230Stls20111119:
1291.230Stls	A problem with the datastructures used by the rndctl(8)
1301.230Stls	utility (pointers in datastructures in an array, making 32->64
1311.230Stls	bit compatibility very painful) has been fixed in a
1321.230Stls	non-backwards-compatible way.  If you replace your kernel,
1331.230Stls	replace your rndctl executable too.
1341.241Swiz
1351.229Sjym20111001:
1361.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
1371.229Sjym	changed and their new version is not backward compatible with the old
1381.241Swiz	one.  So ensure that all consumers of these functions (currently:
1391.229Sjym	quota2 code and its tests) are updated together with the new lib.
1401.229Sjym
1411.228Smrg20110817:
1421.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
1431.228Smrg	DESTDIR for them should be deleted before updating.
1441.228Smrg
1451.227Sriastrad20110806:
1461.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
1471.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
1481.227Sriastrad
1491.226Smrg20110805:
1501.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
1511.226Smrg	the tree to be cleaned.  Best to delete both objdir and
1521.226Smrg	DESTDIR before running this update.  So far, only the
1531.226Smrg	sparc64, mips and powerpc platforms have changed.
1541.226Smrg
1551.225Smatt20110803:
1561.241Swiz	The layout of external/public-domain/xz has changed.  To do an
1571.225Smatt	update build you will have to remove the contents of the OBJDIR
1581.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
1591.225Smatt	is now a directory.
1601.225Smatt
1611.223Sjoerg20110410:
1621.241Swiz	The configuration of src/tools/gcc has changed.  To do an
1631.224Sdholland	update build you have to clean both tools/binutils and
1641.224Sdholland	tools/gcc by hand.
1651.223Sjoerg
1661.222Splunky20110328:
1671.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
1681.241Swiz	ordering issues with "make all".  It may be necessary to remove
1691.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
1701.222Splunky	if your update build fails, as the "Xorg" entry there is now a
1711.222Splunky	directory.
1721.222Splunky
1731.220Sjoerg20110121:
1741.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
1751.220Sjoerg	the build of individual parts of the tree.  This is handled
1761.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
1771.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
1781.218Sjoerg
1791.217Sjruoho20101217:
1801.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
1811.241Swiz	by default.  It may be necessary to manually update passwd(5) and
1821.217Sjruoho	group(5) in order to make the program work with existing setups.
1831.217Sjruoho
1841.216Schristos20101125:
1851.216Schristos	The latest changes to setenv(3) dissallow setting environment
1861.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
1871.241Swiz	assumed that this was allowed.  Installing a new libc with an
1881.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
1891.216Schristos	break which affects the autoconf tests for dependency finding,
1901.216Schristos	so building gcc will end up printing:
1911.216Schristos	    checking dependency style of gcc... none
1921.216Schristos	    configure: error: no usable dependency style found
1931.216Schristos	Fix it by rebuilding and re-installing env.
1941.138Slukem
1951.215Smrg20101119:
1961.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
1971.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
1981.215Smrg	have any build problems with xsrc, or problems with mismatched
1991.215Smrg	versions between xorg-server and drivers.
2001.215Smrg
2011.213Sjmmv20100604:
2021.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
2031.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
2041.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
2051.213Sjmmv	trees by hand.
2061.213Sjmmv
2071.211Stnozaki20100522:
2081.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
2091.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
2101.212Smrg	build problems with xsrc.
2111.212Smrg
2121.212Smrg20100522:
2131.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
2141.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
2151.211Stnozaki
2161.210Schristos20100520:
2171.241Swiz	The location of the xkb compiled descriptions has changed.  Please
2181.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
2191.210Schristos
2201.209Snjoly20100222:
2211.209Snjoly	The shared objects file extension has been changed from .so to
2221.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
2231.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
2241.209Snjoly	your object directories.
2251.209Snjoly
2261.208Sroy20100204:
2271.208Sroy	The termcap database has been removed from the sources,
2281.208Sroy	but has not been marked obsolete so it is not removed
2291.208Sroy	from the system when upgrading.
2301.208Sroy	As such, you will need to remove them from your object
2311.208Sroy	and destination directories.
2321.208Sroy
2331.203Sdyoung20091101:
2341.205Sdholland        After updating, it may be necessary to make the 'cleandir'
2351.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
2361.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
2371.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
2381.203Sdyoung
2391.202Smrg20091001:
2401.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
2411.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
2421.206Sdholland
2431.206Sdholland20091001:
2441.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
2451.202Smrg	symlink, failing the build.  Delete the link, and the subdir
2461.202Smrg	it is in, and retry your build.
2471.202Smrg
2481.201Sdsl20090718:
2491.201Sdsl	libc build changed so that strchr() provides the extra entry
2501.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
2511.201Sdsl	may fail because the archive contains the unwanted index.o.
2521.201Sdsl	(Similarly for strrchr() and rindex().)
2531.201Sdsl
2541.198Smrg20090709:
2551.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
2561.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
2571.198Smrg
2581.197Smrg20090616:
2591.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
2601.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
2611.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
2621.197Smrg	subdirectory has been changed into a file, and this needs to
2631.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
2641.197Smrg
2651.195Sperry20090501:
2661.195Sperry	Several new functions were added to string.h/libc, and this
2671.195Sperry	can cause autoconf problems during the tool build for people
2681.241Swiz	who fail to clean out their tools objects properly.  If you
2691.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
2701.195Sperry	failure during the tool build, clean out all your tools
2711.195Sperry	objects and start again.
2721.195Sperry
2731.194Smrg20090325:
2741.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
2751.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
2761.194Smrg
2771.192Sskrll20090126:
2781.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
2791.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
2801.207Smbalmer	to avoid using the old assembly stub.
2811.192Sskrll
2821.191Sjoerg20090202:
2831.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
2841.191Sjoerg	detection.  It is recommented to rebuild the cache with
2851.191Sjoerg	``pkg_admin rebuild''.
2861.191Sjoerg
2871.184Schristos20090110:
2881.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
2891.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
2901.188Schristos	   This is needed even in the MODULAR kernel because there is
2911.188Schristos	   conditionally compiled code in rtsock.c.
2921.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
2931.184Schristos	   before installing.
2941.184Schristos	3. If you don't use build.sh and you build directly to root, and
2951.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
2961.184Schristos	   are installed properly, and start building libraries first libc
2971.184Schristos	   and libutil, install them and then continue building all the
2981.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
2991.184Schristos	   the new libraries are installed, you can restart the build.
3001.184Schristos	4. If you compile packages and you notice link time warnings,
3011.189Shubertf	   rebuild the required packages to update their shared libraries.
3021.189Shubertf	   Any package you rebuild will require rebuilding all the packages
3031.189Shubertf	   that depend on it.
3041.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
3051.186Schristos	   will be upgraded and it will not be backwards compatible.
3061.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
3071.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
3081.241Swiz	   for utmp.  You are better off removing the old files after
3091.190Sapb	   upgrading.  The automated clearing of /var/run during
3101.190Sapb	   boot, and the automated rotating of files in /var/log by
3111.190Sapb	   newsyslog(8), may mean that you do not have to remove the
3121.190Sapb	   files manually.
3131.190Sapb	7. The optional accounting file (/var/account/acct, see
3141.190Sapb	   accton(8)) has not been versioned, and will need to be
3151.190Sapb	   removed.  The automatic rotation of the accounting file by
3161.190Sapb	   /etc/daily limits the bad consequences of failure to remove
3171.190Sapb	   the file.
3181.196Sdholland	8. Application software that writes time_t to binary files on
3191.241Swiz	   disk will break or need attention.  Most notably: if you are
3201.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
3211.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
3221.185Sjmcneill
3231.183Spgoyette20081219:
3241.183Spgoyette	config(1) has been updated, and one of the files it creates -
3251.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
3261.183Spgoyette	(done automatically by build.sh) and then you need to rerun
3271.183Spgoyette	config on all kernel configuration files before rebuilding those
3281.183Spgoyette	kernels.
3291.183Spgoyette
3301.181Scube20081205:
3311.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
3321.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
3331.181Scube	set and will appear as extra files for MKX11=no update builds.
3341.178Slukem
3351.179Stsutsui20081122:
3361.182Stsutsui	On i386, various kernel options(4) in GENERIC including
3371.180Swiz	file systems have been disabled and moved into kernel modules.
3381.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
3391.179Stsutsui	following files as well as a new GENERIC kernel:
3401.179Stsutsui
3411.179Stsutsui	- build and install kernel modules from src/sys/modules
3421.179Stsutsui
3431.179Stsutsui	- install the latest bootloader, which will load a module
3441.180Swiz	  for the file system from which the kernel is loaded automatically
3451.179Stsutsui
3461.180Swiz	If you have to load your kernel from a file system which is not of
3471.180Swiz	the same type as the root file system, you have to load the necessary
3481.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
3491.179Stsutsui
3501.178Slukem20080827:
3511.178Slukem	If you built and installed a libc from sources between
3521.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
3531.178Slukem	which results in false errors reported by lint(1).
3541.178Slukem	Since this breaks the libc build itself, manual help is
3551.180Swiz	needed -- lint must be disabled temporarily, e.g.:
3561.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
3571.178Slukem
3581.177Schristos20080813:
3591.177Schristos	MKDEBUG build was broken because the .depend files did not know
3601.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
3611.177Schristos
3621.200Sdholland20080802:
3631.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
3641.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
3651.200Sdholland	for -current.
3661.200Sdholland
3671.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
3681.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
3691.200Sdholland	be recompiled.
3701.200Sdholland
3711.200Sdholland	One way to find affected pkgsrc packages:
3721.200Sdholland
3731.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
3741.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
3751.200Sdholland
3761.175Ssimonb20080731:
3771.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
3781.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
3791.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
3801.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
3811.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
3821.176Ssimonb	also requires the super block to be in the UFS2 format.  You
3831.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
3841.175Ssimonb
3851.174Slukem20080721:
3861.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
3871.174Slukem	isn't defined.
3881.174Slukem
3891.173Sfreza20080531:
3901.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
3911.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
3921.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
3931.241Swiz	won't work correctly.  The following sequence of commands:
3941.173Sfreza
3951.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
3961.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
3971.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
3981.173Sfreza
3991.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
4001.173Sfreza
4011.172Slukem20080503:
4021.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
4031.172Slukem
4041.171She20080521:
4051.171She	For a while, unprivileged UPDATE builds would fail to
4061.171She	succeed at the checkflist stage, complaining that
4071.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
4081.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
4091.171She	If you already hit this problem, update the .mk file,
4101.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
4111.171She
4121.174Slukem20080303:
4131.174Slukem	Linker warnings are now fatal if $WARNS>0.
4141.174Slukem
4151.170Schristos20080126:
4161.170Schristos	The posix_fadvise system call has been changed from an assembly
4171.241Swiz	stub, to a c file that calls an assembly stub.  You need to
4181.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
4191.170Schristos	avoid using the old assembly stub.
4201.170Schristos
4211.168Sjoerg20071209:
4221.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
4231.168Sjoerg	get ACPI errors before the attachment, please update your kernel
4241.169Swiz	configuration file appropriately or see GENERIC for more details.
4251.168Sjoerg
4261.166Sxtraeme20071115:
4271.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
4281.166Sxtraeme	argument specified in the kernel configuration file is not valid
4291.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
4301.241Swiz	rather than the EC address port.  Please update your kernel
4311.167Swiz	configuration file appropriately or see GENERIC for more details.
4321.166Sxtraeme
4331.165Sjmmv20071028:
4341.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
4351.165Sjmmv	You need to update any custom kernel configuration file you have
4361.165Sjmmv	to remove any references to pccons (which includes removing the
4371.165Sjmmv	now useless XSERVER option) and replace them with the correct
4381.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
4391.165Sjmmv	for more details.
4401.165Sjmmv
4411.164Sgdt20070913:
4421.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
4431.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
4441.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
4451.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
4461.164Sgdt	could not enumerate interfaces.  (These are noted because
4471.164Sgdt	normal kernel/userspace version matching hygiene is not
4481.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
4491.164Sgdt	and userland are from after 20070913.
4501.164Sgdt
4511.163Sjoerg20070703:
4521.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
4531.199Sdholland	calls the target-specific strip program, and the logic to pass
4541.199Sdholland	down STRIP from make has been removed.  This requires a
4551.199Sdholland	re-installation of tools.
4561.163Sjoerg
4571.161Sdsl20070422:
4581.161Sdsl	The way OS emulations lookup filenames inside the emulation root
4591.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
4601.161Sdsl	to userspace) namei() and lookup() directly check the emulation
4611.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
4621.167Swiz	root file system will be relative to that file system - unless they
4631.161Sdsl	start /../ this is useful when the emulated root is a real install
4641.161Sdsl	that has such links.
4651.161Sdsl	This might affect symlinks that have been added to reference outside
4661.161Sdsl	the emulated root.
4671.161Sdsl
4681.160Sjmcneill20070412:
4691.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
4701.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
4711.160Sjmcneill	example.
4721.160Sjmcneill
4731.159Sgdt20070319:
4741.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
4751.159Sgdt        on many platforms due to incorrect flags settings.  If you
4761.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
4771.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
4781.159Sgdt	rebuild of object files that might have been built
4791.159Sgdt	incorrectly, and ensure that you have at least
4801.159Sgdt	src/lib/libc/Makefile 1.130.
4811.159Sgdt
4821.241Swiz20070210:
4831.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
4841.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
4851.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
4861.158Sdbj        will allow dependencies on those files to get get rebuilt
4871.158Sdbj
4881.157Sapb20070209:
4891.157Sapb        The threading model was changed when the newlock2 branch
4901.157Sapb        was merged to NetBSD-current.  If you boot with a new
4911.157Sapb        kernel (version 4.99.10), then you also need a new pthread
4921.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
4931.157Sapb        an old kernel, then you need the old pthread library
4941.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
4951.157Sapb        the pthread library in sync, old threaded applications should
4961.157Sapb        continue to work with an old or new kernel.  Note that named(8)
4971.157Sapb	is the only threaded application in the base system.
4981.157Sapb
4991.154She20061214:
5001.154She	Following the move of string_to_flags() and flags_to_string()
5011.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
5021.154She	will need to do a "make cleandir" in
5031.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
5041.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
5051.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
5061.156She		as the installation images in distrib/
5071.154She	in order to excise stale references to the old stat_flags.h header
5081.154She	file in the ls sources -- stat_flags.h has been removed.
5091.154She
5101.152Schristos20061108:
5111.152Schristos	The configure script used in the src/tools/gcc compiler has been
5121.152Schristos	changed to indicate that our libc has ssp support built-in and
5131.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
5141.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
5151.152Schristos
5161.151Srpaulo20061009:
5171.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
5181.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
5191.151Srpaulo
5201.150Sbjh2120060814:
5211.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
5221.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
5231.150Sbjh21	kernel configuration for an example.  X servers from the last
5241.150Sbjh21	few years should cope.
5251.150Sbjh21
5261.149Schristos20060703:
5271.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
5281.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
5291.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
5301.149Schristos
5311.148Sdogcow20060627:
5321.148Sdogcow	socket(2) has changed, and its system call has been versioned.
5331.148Sdogcow	For userlands with the old version of socket(2), make sure that
5341.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
5351.148Sdogcow	errors will result.
5361.148Sdogcow
5371.1SabsHints for a more successful build:
5381.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5391.123Sjmc    Use build.sh, but do not use its "expert mode":
5401.132Sjmmv	This will automatically build the tools in the
5411.123Sjmc	   correct order, and it will keep the tools and the
5421.123Sjmc	   new build products from interfering with the running
5431.123Sjmc	   system.  This will allow you to ignore most of the
5441.123Sjmc	   other advice in this file.
5451.2Smrg    Build a new kernel first:
5461.2Smrg	This makes sure that any new system calls or features
5471.2Smrg	   expected by the new userland will be present.  This
5481.2Smrg	   helps to avoid critical errors when upgrading.
5491.1Sabs    Use object directories:
5501.1Sabs	This helps to keep stale object
5511.1Sabs	   files from polluting the build if a Makefile "forgets"
5521.1Sabs	   about one.  It also makes it easier to clean up after
5531.1Sabs	   a build.  It's also necessary if you want to use the
5541.1Sabs	   same source tree for multiple machines.
5551.123Sjmc	   To use object directories with build.sh:
5561.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
5571.123Sjmc	   To use object directories without using build.sh:
5581.1Sabs	    a) cd /usr/src ; make cleandir
5591.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
5601.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
5611.1Sabs	    d) cd /usr/src ; make build
5621.2Smrg	   Note that running "make obj" in a directory will create
5631.2Smrg	   in obj.$MACHINE directory.
5641.1Sabs    Build to a DESTDIR:
5651.123Sjmc	This helps to keep old installed files (especially libraries)
5661.123Sjmc	   from interfering with the new build.
5671.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
5681.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
5691.123Sjmc	   environment variable before running make build.  It should be
5701.123Sjmc	   set to the pathname of an initially empty directory.
5711.123Sjmc	   Problems: if you do not use build.sh, you might need to
5721.123Sjmc		update critical utilities without using DESTDIR since
5731.123Sjmc		nothing is executed from what is installed in DESTDIR.
5741.123Sjmc		(See critical utils, below.)
5751.1Sabs    Build often:
5761.1Sabs	This keeps critical utilities current enough to not choke
5771.1Sabs	on any other part of the source tree that depends on up to
5781.123Sjmc	date functionality.  If you use build.sh, you should not have
5791.123Sjmc	this problem.
5801.241Swiz
5811.1SabsWhat to do if things don't work:
5821.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5831.230StlsWhen things don't work there are usually a few things that commonly
5841.1Sabsshould be done.
5851.1Sabs    1)	make includes
5861.1Sabs	This should be done automatically by make build.
5871.1Sabs    2)  cd share/mk && make install
5881.1Sabs	Again, automatically done by make build.
5891.1Sabs
5901.1SabsFailsafe rebuild of a small part of the tree:
5911.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5921.1SabsTo make sure you rebuild something correctly you want to do
5931.1Sabssomething like the following:
5941.1Sabs    1)  Make sure the includes and .mk files are up to date.
5951.1Sabs    2)  Make sure any program used to build the particular
5961.1Sabs	utility is up to date.  (yacc, lex, etc...)
5971.1Sabs    3)  cd ...path/to/util...
5981.1Sabs	make cleandir
5991.1Sabs	rm ...all obj directories...
6001.1Sabs	make cleandir			# yes, again
6011.1Sabs	make obj
6021.1Sabs	make depend && make
6031.1Sabs
6041.1SabsFailsafe rebuild of the entire tree:
6051.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6061.1SabsIf you really want to make sure the source tree is clean and
6071.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
6081.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
6091.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
6101.1Sabs
6111.1Sabs---cut here---
6121.1Sabs#!/bin/sh
6131.1Sabs. /etc/mk.conf
6141.1Sabs
6151.58Slukemif [ -z $NETBSDSRCDIR ] ; then
6161.58Slukem    NETBSDSRCDIR=/usr/src
6171.1Sabsfi
6181.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
6191.1Sabs    echo Unable to find sources
6201.1Sabs    exit 1
6211.1Sabsfi
6221.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
6231.1Sabs
6241.1Sabsif [ -z $BSDOBJDIR ] ; then
6251.1Sabs    BSDOBJDIR=/usr/obj
6261.1Sabsfi
6271.1Sabsif [ -d $BSDOBJDIR ] ; then
6281.1Sabs    rm -rf $BSDOBJDIR
6291.1Sabsfi
6301.1Sabs
6311.58Slukemcd $NETBSDSRCDIR && make cleandir
6321.1Sabs
6331.1Sabs---cut here---
6341.1Sabs
6351.1SabsCritical utilities:
6361.1Sabs^^^^^^^^^^^^^^^^^^^
6371.3Sitojun	usr.bin/compile_et
6381.1Sabs	usr.bin/make
6391.1Sabs	usr.bin/yacc
6401.1Sabs	usr.bin/lex
6411.11Slukem	usr.bin/xlint
6421.142Sdrochner	usr.bin/config
6431.1Sabs
6441.34SsimonbOther problems and possible solutions:
6451.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6461.1SabsSymptom:Complaints involving a Makefile.
6471.17SerhFix:	Rebuild usr.bin/make:
6481.17Serh	cd usr.bin/make && make && make install
6491.111Ssimonb	Or, a failsafe method if that doesn't work:
6501.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
6511.17Serh
6521.1SabsFix:	Make sure .mk files are up to date.
6531.1Sabs	cd share/mk && make install
6541.2Smrg
6551.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
6561.142SdrochnerFix:	Rebuild usr.bin/config
6571.1Sabs
6581.1SabsSymptom:
6591.1SabsFix:	Rebuild usr.bin/yacc
6601.1Sabs
6611.1SabsSymptom:
6621.1SabsFix:	Rebuild usr.bin/lex
6631.1Sabs
6641.1SabsSymptom:
6651.1SabsFix:	rm /usr/lib/libbfd.a
6661.4Sitojun
6671.4SitojunSymptom:Obsolete intermediate files are used during compilation
6681.4SitojunFix:	Try the following sequence of commands in the directory in question.
6691.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
6701.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
6711.4Sitojun	may remain.  The command tries to clean everything up)
6721.5Swiz
6731.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
6741.207Smbalmer	pointer type
6751.5SwizFix:	Rebuild and install usr.bin/menuc
6761.12Sitojun
6771.12SitojunSymptom:mklocale not found during build in share/locale/ctype
6781.12SitojunFix:	Build and install usr.bin/mklocale
6791.13Sdogcow
6801.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
6811.13SdogcowFix:    Rebuild and install lib/libc
6821.13Sdogcow
6831.142SdrochnerSymptom:usr.bin/config fails to build.
6841.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
6851.13Sdogcow
6861.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
6871.19ScgdFix:    Rebuild and install lib/libc
6881.24Sabs
6891.24SabsSymptom:lint does not understand the '-X' option
6901.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
6911.223Sjoerg
6921.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
6931.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
6941.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
6951.257Sapb
6961.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
6971.257Sapb	No such file or directory.
6981.257SapbCause:	If a directory is created by mistake, then it is sometimes
6991.257Sapb	deleted from the CVS repository using administrative commands
7001.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
7011.257Sapb	contains references to a directory that has been deleted on the
7021.257Sapb	server in this way, then "cvs update" reports this error.
7031.257SapbFix:	Recursively delete the affected directory from your working tree
7041.257Sapb	and try the update again.
705