UPDATING revision 1.287
11.287Skre$NetBSD: UPDATING,v 1.287 2017/10/13 07:04:58 kre 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.287Skre20171010:
231.287Skre	a change to the build structure of external/bsd/acpica/bin/iasl
241.287Skre	means that its objdir (or *.d and .depend at least) might need
251.287Skre	to be manually removed - or a build done once without -u.
261.287Skre
271.286Smrg20170822:
281.286Smrg	a new version of GMP has been imported and probably
291.286Smrg	will break parts of builds related to themselves or GCC, both
301.286Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
311.286Smrg	and MPC objdirs or build once without -u.
321.286Smrg
331.285Smrg20170816:
341.285Smrg	a new version of MPFR and MPC have been imported and probably
351.285Smrg	will break parts of builds related to themselves or GCC, both
361.285Smrg	in the tools and the native section.  Remove all GCC, GMP, MPFR
371.285Smrg	and MPC objdirs or build once without -u.
381.285Smrg
391.284Smartin20170402:
401.284Smartin	a new version of dhcpcd has been imported, which does not support
411.284Smartin	update builds from the previous version. Remove your
421.284Smartin	external/bsd/dhcpcd object dir or build once without -u.
431.284Smartin
441.281Sroy20170211:
451.281Sroy	a new terminfo database has been imported.
461.281Sroy	The structure of it has changed slightly from prior versions and
471.281Sroy	an updated tic tool is required.
481.281Sroy	If you build.sh, don't use -u
491.281Sroy
501.280Skre20170207:
511.278Skre	various arch dependent libc/exect.S files were removed
521.279Skre	Either remove the obj directories (lib/libc and compat/amd64/i386/lib
531.279Skre	if it exists) or do a clean build.
541.279Skre	(This is a bug in the make system, it should be corrected without
551.279Skre	human intervention, but isn't.)
561.278Skre
571.277Smartin20170104:
581.277Smartin	xinput build options have changed.
591.277Smartin	Remove the obj directory (external/mit/xorg/bin/xinput)
601.277Smartin	if you build.sh -u
611.277Smartin
621.276Smartin20170103:
631.276Smartin	a new version of flex has been imported.
641.276Smartin	Remove the file from obj (external/bsd/flex)
651.276Smartin	if you build.sh -u
661.276Smartin
671.275Sspz20161014:
681.275Sspz	a new version of OpenSSL has been imported.
691.275Sspz	Remove the files from obj (crypto/external/bsd/openssl) 
701.275Sspz	if you build.sh -u
711.275Sspz
721.274Smartin20161009:
731.274Smartin	a new version of dhcpcd has been imported with slightly changed
741.274Smartin	build infrastructure. When doing a build.sh -u this requires
751.274Smartin	pruning the external/bsd/dhcpcd objdir.
761.274Smartin
771.273Smrg20160914:
781.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
791.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
801.273Smrg	and a clean objdir.
811.273Smrg
821.272Sdholland20160527:
831.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
841.272Sdholland	been enabled. (see the amd64 entry two down for further info)
851.272Sdholland
861.270Schristos20160418:
871.270Schristos	libedit needs manual removal of all autogenerated files since
881.271Schristos	some of them are not autogenerated anymore. Remember that there
891.271Schristos	might be two copies of libedit if your platform builds "compat".
901.270Schristos
911.268Sriastrad20160410:
921.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
931.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
941.268Sriastrad	executables, means all code, including executables and not just
951.268Sriastrad	shared libraries, is position-independent and hence able to be
961.268Sriastrad	relocated by ASLR, address space layout randomization.
971.268Sriastrad
981.268Sriastrad	The change was made in Makefile variables for compiler and
991.268Sriastrad	linker flags, for which make(1) does not record dependencies,
1001.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
1011.268Sriastrad
1021.268Sriastrad	Partial rebuilds with some modified source files will likely
1031.268Sriastrad	fail when linking executables, since the linker refuses to mix
1041.268Sriastrad	position-independent code with position-dependent code in
1051.268Sriastrad	position-independent executables:
1061.268Sriastrad
1071.268Sriastrad		.../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC
1081.268Sriastrad
1091.267Smrg20160401:
1101.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
1111.269Sdholland	Some people have found that cleandir is not sufficient, so if
1121.269Sdholland	in doubt delete the entire object directory tree for gcc.
1131.267Smrg
1141.266Saymeric20160306:
1151.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
1161.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
1171.265Saymeric	non-NetBSD hosts if linked with stale object files produced
1181.265Saymeric	while they included a non-NetBSD regex.h.
1191.265Saymeric	In any case, you should "make cleandir" at least these tools
1201.265Saymeric	before updating your toolchain.
1211.265Saymeric
1221.264Smartin20160125:
1231.264Smartin	Dtrace has been enabled by default on some architectures.
1241.264Smartin	When doing an update build, make sure to clean the etc/mtree
1251.264Smartin	object directory before starting the build - otherwise the
1261.264Smartin	needed directories in destdir will not be created.
1271.264Smartin	An easy way to do this is:
1281.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
1291.264Smartin
1301.263Sdholland20150818:
1311.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
1321.263Sdholland	again.
1331.263Sdholland
1341.262Schristos20150413:
1351.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
1361.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
1371.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
1381.262Schristos
1391.261Smartin20150404:
1401.261Smartin	Lint changes require a full rebuild of the tool, so make
1411.261Smartin	sure to build without -u option to build.sh, or manually
1421.261Smartin	do a make cleandir in src/tools/lint1 and
1431.261Smartin	src/usr.bin/xlint.
1441.261Smartin
1451.260Sskrll20150310:
1461.260Sskrll	Improvements to openssl for arm mean that update builds of
1471.260Sskrll	the openssl libraries will fail. A make cleandir in
1481.260Sskrll	external/bsd/openssl/lib is needed
1491.260Sskrll
1501.258Smartin20141026:
1511.259Smsaitoh	A mishap during the import of pppd may cause your corruption
1521.258Smartin	in your cvs directory if you happened to do a cvs update
1531.258Smartin	during a short period of time. To fix, just remove the
1541.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
1551.258Smartin	and let cvs restore it on next update.
1561.258Smartin
1571.256Sapb20140721:
1581.256Sapb	The src/external/mit/lua/src directory was accidentally created
1591.256Sapb	and then deleted in the CVS repository.  If you get errors like
1601.256Sapb
1611.256Sapb	cvs [update aborted]: cannot open directory
1621.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
1631.256Sapb
1641.256Sapb	then delete your local copy of that directory tree and try again.
1651.256Sapb
1661.255Sjoerg20140530:
1671.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
1681.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
1691.255Sjoerg
1701.251Smartin20140131:
1711.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
1721.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
1731.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
1741.251Smartin
1751.250Schristos20131227:
1761.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
1771.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
1781.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
1791.250Schristos	   statements to avoid being exposed.
1801.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
1811.250Schristos	   to make clean in libc
1821.250Schristos
1831.249Smrg20131129:
1841.249Smrg	The GMP sources were updated, and builds will likely fail without
1851.249Smrg	cleaning their build trees for both tools and in-tree, like below.
1861.249Smrg
1871.248Smrg20131128:
1881.248Smrg	The MPC and MPFR sources were updated, and builds may require their
1891.248Smrg	tools and in-tree directories cleaned for successful updates.
1901.248Smrg
1911.246Smartin20130605:
1921.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
1931.247Sspz	to IPSEC (and the older IPSEC version removed).
1941.247Sspz
1951.247Sspz20130605:
1961.246Smartin	Previous freetype installations eroneously installed private
1971.246Smartin	header files. If you are building against a non-empty $DESTDIR,
1981.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
1991.246Smartin
2001.245Smrg20130531:
2011.245Smrg	The xdm update may cause build failure due to xdm.man being
2021.245Smrg	in the obj tree.  Make sure to ensure any like this:
2031.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
2041.245Smrg	is fixed by deleting the xdm.man in the obj tree.
2051.245Smrg
2061.244Smrg20130530:
2071.244Smrg	Updates of many xsrc packages will leave old .pc files around.
2081.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
2091.244Smrg
2101.242Schristos20130301:
2111.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
2121.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
2131.242Schristos
2141.238Sdholland20120726:
2151.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
2161.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
2171.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
2181.241Swiz	some cases may succeed and install broken OpenSSL libraries that
2191.240Sdholland	cause third-party software to link incorrectly and/or crash.
2201.238Sdholland
2211.237Swiz20120507:
2221.241Swiz	The database schema for makemandb was changed.  You will
2231.237Swiz	need to update the database using 'makemandb -f' or wait
2241.237Swiz	for the next weekly run to fix it.
2251.237Swiz
2261.236Sbsh20120319:
2271.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
2281.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
2291.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
2301.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
2311.236Sbsh	mk.conf.
2321.236Sbsh
2331.235Sjoerg20120216:
2341.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
2351.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
2361.239Sdholland	and 20120216, daily and weekly could have created an unreadable
2371.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
2381.235Sjoerg	the next run of weekly will fix it.
2391.233Sjoerg
2401.232Schristos20111227:
2411.232Schristos	If you built between 20111225 and 20111227 you need to remove
2421.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
2431.232Schristos	bump has been reverted.
2441.232Schristos
2451.231Stls20111125:
2461.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
2471.231Stls	means it should no longer be explicitly listed in kernel
2481.231Stls	configuration files.  The line "pseudo-device rnd" should be
2491.231Stls	removed from any custom kernel config files users may have.
2501.231Stls
2511.230Stls20111119:
2521.230Stls	A problem with the datastructures used by the rndctl(8)
2531.230Stls	utility (pointers in datastructures in an array, making 32->64
2541.230Stls	bit compatibility very painful) has been fixed in a
2551.230Stls	non-backwards-compatible way.  If you replace your kernel,
2561.230Stls	replace your rndctl executable too.
2571.241Swiz
2581.229Sjym20111001:
2591.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
2601.229Sjym	changed and their new version is not backward compatible with the old
2611.241Swiz	one.  So ensure that all consumers of these functions (currently:
2621.229Sjym	quota2 code and its tests) are updated together with the new lib.
2631.229Sjym
2641.228Smrg20110817:
2651.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
2661.228Smrg	DESTDIR for them should be deleted before updating.
2671.228Smrg
2681.227Sriastrad20110806:
2691.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
2701.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
2711.227Sriastrad
2721.226Smrg20110805:
2731.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
2741.226Smrg	the tree to be cleaned.  Best to delete both objdir and
2751.226Smrg	DESTDIR before running this update.  So far, only the
2761.226Smrg	sparc64, mips and powerpc platforms have changed.
2771.226Smrg
2781.225Smatt20110803:
2791.241Swiz	The layout of external/public-domain/xz has changed.  To do an
2801.225Smatt	update build you will have to remove the contents of the OBJDIR
2811.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
2821.225Smatt	is now a directory.
2831.225Smatt
2841.223Sjoerg20110410:
2851.241Swiz	The configuration of src/tools/gcc has changed.  To do an
2861.224Sdholland	update build you have to clean both tools/binutils and
2871.224Sdholland	tools/gcc by hand.
2881.223Sjoerg
2891.222Splunky20110328:
2901.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
2911.241Swiz	ordering issues with "make all".  It may be necessary to remove
2921.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
2931.222Splunky	if your update build fails, as the "Xorg" entry there is now a
2941.222Splunky	directory.
2951.222Splunky
2961.220Sjoerg20110121:
2971.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
2981.220Sjoerg	the build of individual parts of the tree.  This is handled
2991.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
3001.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
3011.218Sjoerg
3021.217Sjruoho20101217:
3031.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
3041.241Swiz	by default.  It may be necessary to manually update passwd(5) and
3051.217Sjruoho	group(5) in order to make the program work with existing setups.
3061.217Sjruoho
3071.216Schristos20101125:
3081.216Schristos	The latest changes to setenv(3) dissallow setting environment
3091.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
3101.241Swiz	assumed that this was allowed.  Installing a new libc with an
3111.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
3121.216Schristos	break which affects the autoconf tests for dependency finding,
3131.216Schristos	so building gcc will end up printing:
3141.216Schristos	    checking dependency style of gcc... none
3151.216Schristos	    configure: error: no usable dependency style found
3161.216Schristos	Fix it by rebuilding and re-installing env.
3171.138Slukem
3181.215Smrg20101119:
3191.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
3201.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
3211.215Smrg	have any build problems with xsrc, or problems with mismatched
3221.215Smrg	versions between xorg-server and drivers.
3231.215Smrg
3241.213Sjmmv20100604:
3251.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
3261.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
3271.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
3281.213Sjmmv	trees by hand.
3291.213Sjmmv
3301.211Stnozaki20100522:
3311.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
3321.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
3331.212Smrg	build problems with xsrc.
3341.212Smrg
3351.212Smrg20100522:
3361.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
3371.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
3381.211Stnozaki
3391.210Schristos20100520:
3401.241Swiz	The location of the xkb compiled descriptions has changed.  Please
3411.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
3421.210Schristos
3431.209Snjoly20100222:
3441.209Snjoly	The shared objects file extension has been changed from .so to
3451.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
3461.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
3471.209Snjoly	your object directories.
3481.209Snjoly
3491.208Sroy20100204:
3501.208Sroy	The termcap database has been removed from the sources,
3511.208Sroy	but has not been marked obsolete so it is not removed
3521.208Sroy	from the system when upgrading.
3531.208Sroy	As such, you will need to remove them from your object
3541.208Sroy	and destination directories.
3551.208Sroy
3561.203Sdyoung20091101:
3571.205Sdholland        After updating, it may be necessary to make the 'cleandir'
3581.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
3591.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
3601.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
3611.203Sdyoung
3621.202Smrg20091001:
3631.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
3641.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
3651.206Sdholland
3661.206Sdholland20091001:
3671.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
3681.202Smrg	symlink, failing the build.  Delete the link, and the subdir
3691.202Smrg	it is in, and retry your build.
3701.202Smrg
3711.201Sdsl20090718:
3721.201Sdsl	libc build changed so that strchr() provides the extra entry
3731.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
3741.201Sdsl	may fail because the archive contains the unwanted index.o.
3751.201Sdsl	(Similarly for strrchr() and rindex().)
3761.201Sdsl
3771.198Smrg20090709:
3781.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
3791.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
3801.198Smrg
3811.197Smrg20090616:
3821.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
3831.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
3841.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
3851.197Smrg	subdirectory has been changed into a file, and this needs to
3861.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
3871.197Smrg
3881.195Sperry20090501:
3891.195Sperry	Several new functions were added to string.h/libc, and this
3901.195Sperry	can cause autoconf problems during the tool build for people
3911.241Swiz	who fail to clean out their tools objects properly.  If you
3921.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
3931.195Sperry	failure during the tool build, clean out all your tools
3941.195Sperry	objects and start again.
3951.195Sperry
3961.194Smrg20090325:
3971.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
3981.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
3991.194Smrg
4001.192Sskrll20090126:
4011.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
4021.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
4031.207Smbalmer	to avoid using the old assembly stub.
4041.192Sskrll
4051.191Sjoerg20090202:
4061.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
4071.191Sjoerg	detection.  It is recommented to rebuild the cache with
4081.191Sjoerg	``pkg_admin rebuild''.
4091.191Sjoerg
4101.184Schristos20090110:
4111.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
4121.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
4131.188Schristos	   This is needed even in the MODULAR kernel because there is
4141.188Schristos	   conditionally compiled code in rtsock.c.
4151.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
4161.184Schristos	   before installing.
4171.184Schristos	3. If you don't use build.sh and you build directly to root, and
4181.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
4191.184Schristos	   are installed properly, and start building libraries first libc
4201.184Schristos	   and libutil, install them and then continue building all the
4211.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
4221.184Schristos	   the new libraries are installed, you can restart the build.
4231.184Schristos	4. If you compile packages and you notice link time warnings,
4241.189Shubertf	   rebuild the required packages to update their shared libraries.
4251.189Shubertf	   Any package you rebuild will require rebuilding all the packages
4261.189Shubertf	   that depend on it.
4271.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
4281.186Schristos	   will be upgraded and it will not be backwards compatible.
4291.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
4301.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
4311.241Swiz	   for utmp.  You are better off removing the old files after
4321.190Sapb	   upgrading.  The automated clearing of /var/run during
4331.190Sapb	   boot, and the automated rotating of files in /var/log by
4341.190Sapb	   newsyslog(8), may mean that you do not have to remove the
4351.190Sapb	   files manually.
4361.190Sapb	7. The optional accounting file (/var/account/acct, see
4371.190Sapb	   accton(8)) has not been versioned, and will need to be
4381.190Sapb	   removed.  The automatic rotation of the accounting file by
4391.190Sapb	   /etc/daily limits the bad consequences of failure to remove
4401.190Sapb	   the file.
4411.196Sdholland	8. Application software that writes time_t to binary files on
4421.241Swiz	   disk will break or need attention.  Most notably: if you are
4431.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
4441.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
4451.185Sjmcneill
4461.183Spgoyette20081219:
4471.183Spgoyette	config(1) has been updated, and one of the files it creates -
4481.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
4491.183Spgoyette	(done automatically by build.sh) and then you need to rerun
4501.183Spgoyette	config on all kernel configuration files before rebuilding those
4511.183Spgoyette	kernels.
4521.183Spgoyette
4531.181Scube20081205:
4541.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
4551.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
4561.181Scube	set and will appear as extra files for MKX11=no update builds.
4571.178Slukem
4581.179Stsutsui20081122:
4591.182Stsutsui	On i386, various kernel options(4) in GENERIC including
4601.180Swiz	file systems have been disabled and moved into kernel modules.
4611.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
4621.179Stsutsui	following files as well as a new GENERIC kernel:
4631.179Stsutsui
4641.179Stsutsui	- build and install kernel modules from src/sys/modules
4651.179Stsutsui
4661.179Stsutsui	- install the latest bootloader, which will load a module
4671.180Swiz	  for the file system from which the kernel is loaded automatically
4681.179Stsutsui
4691.180Swiz	If you have to load your kernel from a file system which is not of
4701.180Swiz	the same type as the root file system, you have to load the necessary
4711.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
4721.179Stsutsui
4731.178Slukem20080827:
4741.178Slukem	If you built and installed a libc from sources between
4751.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
4761.178Slukem	which results in false errors reported by lint(1).
4771.178Slukem	Since this breaks the libc build itself, manual help is
4781.180Swiz	needed -- lint must be disabled temporarily, e.g.:
4791.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
4801.178Slukem
4811.177Schristos20080813:
4821.177Schristos	MKDEBUG build was broken because the .depend files did not know
4831.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
4841.177Schristos
4851.200Sdholland20080802:
4861.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
4871.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
4881.200Sdholland	for -current.
4891.200Sdholland
4901.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
4911.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
4921.200Sdholland	be recompiled.
4931.200Sdholland
4941.200Sdholland	One way to find affected pkgsrc packages:
4951.200Sdholland
4961.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
4971.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
4981.200Sdholland
4991.175Ssimonb20080731:
5001.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
5011.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
5021.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
5031.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
5041.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
5051.176Ssimonb	also requires the super block to be in the UFS2 format.  You
5061.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
5071.175Ssimonb
5081.174Slukem20080721:
5091.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
5101.174Slukem	isn't defined.
5111.174Slukem
5121.173Sfreza20080531:
5131.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
5141.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
5151.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
5161.241Swiz	won't work correctly.  The following sequence of commands:
5171.173Sfreza
5181.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
5191.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
5201.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
5211.173Sfreza
5221.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
5231.173Sfreza
5241.172Slukem20080503:
5251.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
5261.172Slukem
5271.171She20080521:
5281.171She	For a while, unprivileged UPDATE builds would fail to
5291.171She	succeed at the checkflist stage, complaining that
5301.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
5311.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
5321.171She	If you already hit this problem, update the .mk file,
5331.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
5341.171She
5351.174Slukem20080303:
5361.174Slukem	Linker warnings are now fatal if $WARNS>0.
5371.174Slukem
5381.170Schristos20080126:
5391.170Schristos	The posix_fadvise system call has been changed from an assembly
5401.241Swiz	stub, to a c file that calls an assembly stub.  You need to
5411.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
5421.170Schristos	avoid using the old assembly stub.
5431.170Schristos
5441.168Sjoerg20071209:
5451.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
5461.168Sjoerg	get ACPI errors before the attachment, please update your kernel
5471.169Swiz	configuration file appropriately or see GENERIC for more details.
5481.168Sjoerg
5491.166Sxtraeme20071115:
5501.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
5511.166Sxtraeme	argument specified in the kernel configuration file is not valid
5521.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
5531.241Swiz	rather than the EC address port.  Please update your kernel
5541.167Swiz	configuration file appropriately or see GENERIC for more details.
5551.166Sxtraeme
5561.165Sjmmv20071028:
5571.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
5581.165Sjmmv	You need to update any custom kernel configuration file you have
5591.165Sjmmv	to remove any references to pccons (which includes removing the
5601.165Sjmmv	now useless XSERVER option) and replace them with the correct
5611.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
5621.165Sjmmv	for more details.
5631.165Sjmmv
5641.164Sgdt20070913:
5651.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
5661.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
5671.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
5681.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
5691.164Sgdt	could not enumerate interfaces.  (These are noted because
5701.164Sgdt	normal kernel/userspace version matching hygiene is not
5711.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
5721.164Sgdt	and userland are from after 20070913.
5731.164Sgdt
5741.163Sjoerg20070703:
5751.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
5761.199Sdholland	calls the target-specific strip program, and the logic to pass
5771.199Sdholland	down STRIP from make has been removed.  This requires a
5781.199Sdholland	re-installation of tools.
5791.163Sjoerg
5801.161Sdsl20070422:
5811.161Sdsl	The way OS emulations lookup filenames inside the emulation root
5821.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
5831.161Sdsl	to userspace) namei() and lookup() directly check the emulation
5841.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
5851.167Swiz	root file system will be relative to that file system - unless they
5861.161Sdsl	start /../ this is useful when the emulated root is a real install
5871.161Sdsl	that has such links.
5881.161Sdsl	This might affect symlinks that have been added to reference outside
5891.161Sdsl	the emulated root.
5901.161Sdsl
5911.160Sjmcneill20070412:
5921.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
5931.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
5941.160Sjmcneill	example.
5951.160Sjmcneill
5961.159Sgdt20070319:
5971.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
5981.159Sgdt        on many platforms due to incorrect flags settings.  If you
5991.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
6001.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
6011.159Sgdt	rebuild of object files that might have been built
6021.159Sgdt	incorrectly, and ensure that you have at least
6031.159Sgdt	src/lib/libc/Makefile 1.130.
6041.159Sgdt
6051.241Swiz20070210:
6061.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
6071.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
6081.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
6091.158Sdbj        will allow dependencies on those files to get get rebuilt
6101.158Sdbj
6111.157Sapb20070209:
6121.157Sapb        The threading model was changed when the newlock2 branch
6131.157Sapb        was merged to NetBSD-current.  If you boot with a new
6141.157Sapb        kernel (version 4.99.10), then you also need a new pthread
6151.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
6161.157Sapb        an old kernel, then you need the old pthread library
6171.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
6181.157Sapb        the pthread library in sync, old threaded applications should
6191.157Sapb        continue to work with an old or new kernel.  Note that named(8)
6201.157Sapb	is the only threaded application in the base system.
6211.157Sapb
6221.154She20061214:
6231.154She	Following the move of string_to_flags() and flags_to_string()
6241.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
6251.154She	will need to do a "make cleandir" in
6261.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
6271.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
6281.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
6291.156She		as the installation images in distrib/
6301.154She	in order to excise stale references to the old stat_flags.h header
6311.154She	file in the ls sources -- stat_flags.h has been removed.
6321.154She
6331.152Schristos20061108:
6341.152Schristos	The configure script used in the src/tools/gcc compiler has been
6351.152Schristos	changed to indicate that our libc has ssp support built-in and
6361.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
6371.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
6381.152Schristos
6391.151Srpaulo20061009:
6401.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
6411.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
6421.151Srpaulo
6431.150Sbjh2120060814:
6441.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
6451.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
6461.150Sbjh21	kernel configuration for an example.  X servers from the last
6471.150Sbjh21	few years should cope.
6481.150Sbjh21
6491.149Schristos20060703:
6501.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
6511.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
6521.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
6531.149Schristos
6541.148Sdogcow20060627:
6551.148Sdogcow	socket(2) has changed, and its system call has been versioned.
6561.148Sdogcow	For userlands with the old version of socket(2), make sure that
6571.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
6581.148Sdogcow	errors will result.
6591.148Sdogcow
6601.1SabsHints for a more successful build:
6611.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6621.123Sjmc    Use build.sh, but do not use its "expert mode":
6631.132Sjmmv	This will automatically build the tools in the
6641.123Sjmc	   correct order, and it will keep the tools and the
6651.123Sjmc	   new build products from interfering with the running
6661.123Sjmc	   system.  This will allow you to ignore most of the
6671.123Sjmc	   other advice in this file.
6681.2Smrg    Build a new kernel first:
6691.2Smrg	This makes sure that any new system calls or features
6701.2Smrg	   expected by the new userland will be present.  This
6711.2Smrg	   helps to avoid critical errors when upgrading.
6721.1Sabs    Use object directories:
6731.1Sabs	This helps to keep stale object
6741.1Sabs	   files from polluting the build if a Makefile "forgets"
6751.1Sabs	   about one.  It also makes it easier to clean up after
6761.1Sabs	   a build.  It's also necessary if you want to use the
6771.1Sabs	   same source tree for multiple machines.
6781.123Sjmc	   To use object directories with build.sh:
6791.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
6801.123Sjmc	   To use object directories without using build.sh:
6811.1Sabs	    a) cd /usr/src ; make cleandir
6821.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
6831.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
6841.1Sabs	    d) cd /usr/src ; make build
6851.2Smrg	   Note that running "make obj" in a directory will create
6861.2Smrg	   in obj.$MACHINE directory.
6871.1Sabs    Build to a DESTDIR:
6881.123Sjmc	This helps to keep old installed files (especially libraries)
6891.123Sjmc	   from interfering with the new build.
6901.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
6911.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
6921.123Sjmc	   environment variable before running make build.  It should be
6931.123Sjmc	   set to the pathname of an initially empty directory.
6941.123Sjmc	   Problems: if you do not use build.sh, you might need to
6951.123Sjmc		update critical utilities without using DESTDIR since
6961.123Sjmc		nothing is executed from what is installed in DESTDIR.
6971.123Sjmc		(See critical utils, below.)
6981.1Sabs    Build often:
6991.1Sabs	This keeps critical utilities current enough to not choke
7001.1Sabs	on any other part of the source tree that depends on up to
7011.123Sjmc	date functionality.  If you use build.sh, you should not have
7021.123Sjmc	this problem.
7031.241Swiz
7041.1SabsWhat to do if things don't work:
7051.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7061.230StlsWhen things don't work there are usually a few things that commonly
7071.1Sabsshould be done.
7081.1Sabs    1)	make includes
7091.1Sabs	This should be done automatically by make build.
7101.1Sabs    2)  cd share/mk && make install
7111.1Sabs	Again, automatically done by make build.
7121.1Sabs
7131.1SabsFailsafe rebuild of a small part of the tree:
7141.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7151.1SabsTo make sure you rebuild something correctly you want to do
7161.1Sabssomething like the following:
7171.1Sabs    1)  Make sure the includes and .mk files are up to date.
7181.1Sabs    2)  Make sure any program used to build the particular
7191.1Sabs	utility is up to date.  (yacc, lex, etc...)
7201.1Sabs    3)  cd ...path/to/util...
7211.1Sabs	make cleandir
7221.1Sabs	rm ...all obj directories...
7231.1Sabs	make cleandir			# yes, again
7241.1Sabs	make obj
7251.1Sabs	make depend && make
7261.1Sabs
7271.1SabsFailsafe rebuild of the entire tree:
7281.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7291.1SabsIf you really want to make sure the source tree is clean and
7301.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
7311.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
7321.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
7331.1Sabs
7341.1Sabs---cut here---
7351.1Sabs#!/bin/sh
7361.1Sabs. /etc/mk.conf
7371.1Sabs
7381.58Slukemif [ -z $NETBSDSRCDIR ] ; then
7391.58Slukem    NETBSDSRCDIR=/usr/src
7401.1Sabsfi
7411.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
7421.1Sabs    echo Unable to find sources
7431.1Sabs    exit 1
7441.1Sabsfi
7451.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
7461.1Sabs
7471.1Sabsif [ -z $BSDOBJDIR ] ; then
7481.1Sabs    BSDOBJDIR=/usr/obj
7491.1Sabsfi
7501.1Sabsif [ -d $BSDOBJDIR ] ; then
7511.1Sabs    rm -rf $BSDOBJDIR
7521.1Sabsfi
7531.1Sabs
7541.58Slukemcd $NETBSDSRCDIR && make cleandir
7551.1Sabs
7561.1Sabs---cut here---
7571.1Sabs
7581.1SabsCritical utilities:
7591.1Sabs^^^^^^^^^^^^^^^^^^^
7601.3Sitojun	usr.bin/compile_et
7611.1Sabs	usr.bin/make
7621.1Sabs	usr.bin/yacc
7631.1Sabs	usr.bin/lex
7641.11Slukem	usr.bin/xlint
7651.142Sdrochner	usr.bin/config
7661.1Sabs
7671.34SsimonbOther problems and possible solutions:
7681.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7691.1SabsSymptom:Complaints involving a Makefile.
7701.17SerhFix:	Rebuild usr.bin/make:
7711.17Serh	cd usr.bin/make && make && make install
7721.111Ssimonb	Or, a failsafe method if that doesn't work:
7731.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
7741.17Serh
7751.1SabsFix:	Make sure .mk files are up to date.
7761.1Sabs	cd share/mk && make install
7771.2Smrg
7781.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
7791.142SdrochnerFix:	Rebuild usr.bin/config
7801.1Sabs
7811.1SabsSymptom:
7821.1SabsFix:	Rebuild usr.bin/yacc
7831.1Sabs
7841.1SabsSymptom:
7851.1SabsFix:	Rebuild usr.bin/lex
7861.1Sabs
7871.1SabsSymptom:
7881.1SabsFix:	rm /usr/lib/libbfd.a
7891.4Sitojun
7901.4SitojunSymptom:Obsolete intermediate files are used during compilation
7911.4SitojunFix:	Try the following sequence of commands in the directory in question.
7921.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
7931.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
7941.4Sitojun	may remain.  The command tries to clean everything up)
7951.5Swiz
7961.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
7971.207Smbalmer	pointer type
7981.5SwizFix:	Rebuild and install usr.bin/menuc
7991.12Sitojun
8001.12SitojunSymptom:mklocale not found during build in share/locale/ctype
8011.12SitojunFix:	Build and install usr.bin/mklocale
8021.13Sdogcow
8031.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
8041.13SdogcowFix:    Rebuild and install lib/libc
8051.13Sdogcow
8061.142SdrochnerSymptom:usr.bin/config fails to build.
8071.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
8081.13Sdogcow
8091.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
8101.19ScgdFix:    Rebuild and install lib/libc
8111.24Sabs
8121.24SabsSymptom:lint does not understand the '-X' option
8131.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
8141.223Sjoerg
8151.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
8161.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
8171.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
8181.257Sapb
8191.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
8201.257Sapb	No such file or directory.
8211.257SapbCause:	If a directory is created by mistake, then it is sometimes
8221.257Sapb	deleted from the CVS repository using administrative commands
8231.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
8241.257Sapb	contains references to a directory that has been deleted on the
8251.257Sapb	server in this way, then "cvs update" reports this error.
8261.257SapbFix:	Recursively delete the affected directory from your working tree
8271.257Sapb	and try the update again.
828