UPDATING revision 1.274
11.274Smartin$NetBSD: UPDATING,v 1.274 2016/10/10 13:28:24 martin 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.274Smartin20161009:
231.274Smartin	a new version of dhcpcd has been imported with slightly changed
241.274Smartin	build infrastructure. When doing a build.sh -u this requires
251.274Smartin	pruning the external/bsd/dhcpcd objdir.
261.274Smartin
271.273Smrg20160914:
281.273Smrg	i386, amd64, shark, ofppc and macppc have joined shark and x68k
291.273Smrg	ports in using xorg-server 1.18. This requires a clean destdir
301.273Smrg	and a clean objdir.
311.273Smrg
321.272Sdholland20160527:
331.272Sdholland	i386 needs a full cleandir or objdir deletion because PIE has
341.272Sdholland	been enabled. (see the amd64 entry two down for further info)
351.272Sdholland
361.270Schristos20160418:
371.270Schristos	libedit needs manual removal of all autogenerated files since
381.271Schristos	some of them are not autogenerated anymore. Remember that there
391.271Schristos	might be two copies of libedit if your platform builds "compat".
401.270Schristos
411.268Sriastrad20160410:
421.268Sriastrad	amd64 needs full "make cleandir" or deletion of objdir now that
431.268Sriastrad	PIE has been enabled for amd64.  PIE, or position-independent
441.268Sriastrad	executables, means all code, including executables and not just
451.268Sriastrad	shared libraries, is position-independent and hence able to be
461.268Sriastrad	relocated by ASLR, address space layout randomization.
471.268Sriastrad
481.268Sriastrad	The change was made in Makefile variables for compiler and
491.268Sriastrad	linker flags, for which make(1) does not record dependencies,
501.268Sriastrad	hence it is unable to detect that all .o files need rebuilding.
511.268Sriastrad
521.268Sriastrad	Partial rebuilds with some modified source files will likely
531.268Sriastrad	fail when linking executables, since the linker refuses to mix
541.268Sriastrad	position-independent code with position-dependent code in
551.268Sriastrad	position-independent executables:
561.268Sriastrad
571.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
581.268Sriastrad
591.267Smrg20160401:
601.267Smrg	Ports switching to GCC 5.3 will need a full "make cleandir".
611.269Sdholland	Some people have found that cleandir is not sufficient, so if
621.269Sdholland	in doubt delete the entire object directory tree for gcc.
631.267Smrg
641.266Saymeric20160306:
651.265Saymeric	NetBSD's regexp implementation is now part of libnbcompat.
661.265Saymeric	Nblex, nbm4, nbpax, nbsed use it and they may crash on
671.265Saymeric	non-NetBSD hosts if linked with stale object files produced
681.265Saymeric	while they included a non-NetBSD regex.h.
691.265Saymeric	In any case, you should "make cleandir" at least these tools
701.265Saymeric	before updating your toolchain.
711.265Saymeric
721.264Smartin20160125:
731.264Smartin	Dtrace has been enabled by default on some architectures.
741.264Smartin	When doing an update build, make sure to clean the etc/mtree
751.264Smartin	object directory before starting the build - otherwise the
761.264Smartin	needed directories in destdir will not be created.
771.264Smartin	An easy way to do this is:
781.264Smartin	   cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
791.264Smartin
801.263Sdholland20150818:
811.263Sdholland	New acpica requires "make cleandir" in src/external/bsd/acpica
821.263Sdholland	again.
831.263Sdholland
841.262Schristos20150413:
851.262Schristos	New acpica requires "make cleandir" and reinstalling yacc
861.262Schristos	in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
871.262Schristos	also "make cleandir" in /usr/src/external/bsd/acpica.
881.262Schristos
891.261Smartin20150404:
901.261Smartin	Lint changes require a full rebuild of the tool, so make
911.261Smartin	sure to build without -u option to build.sh, or manually
921.261Smartin	do a make cleandir in src/tools/lint1 and
931.261Smartin	src/usr.bin/xlint.
941.261Smartin
951.260Sskrll20150310:
961.260Sskrll	Improvements to openssl for arm mean that update builds of
971.260Sskrll	the openssl libraries will fail. A make cleandir in
981.260Sskrll	external/bsd/openssl/lib is needed
991.260Sskrll
1001.258Smartin20141026:
1011.259Smsaitoh	A mishap during the import of pppd may cause your corruption
1021.258Smartin	in your cvs directory if you happened to do a cvs update
1031.258Smartin	during a short period of time. To fix, just remove the
1041.258Smartin	directory src/external/bsd/ppp/dist/pppd completely
1051.258Smartin	and let cvs restore it on next update.
1061.258Smartin
1071.256Sapb20140721:
1081.256Sapb	The src/external/mit/lua/src directory was accidentally created
1091.256Sapb	and then deleted in the CVS repository.  If you get errors like
1101.256Sapb
1111.256Sapb	cvs [update aborted]: cannot open directory
1121.256Sapb	/cvsroot/src/external/mit/lua/src: No such file or directory
1131.256Sapb
1141.256Sapb	then delete your local copy of that directory tree and try again.
1151.256Sapb
1161.255Sjoerg20140530:
1171.255Sjoerg	ARM eABI switched to DWARF based exception handling. This requires
1181.255Sjoerg	rebuilding all C++ code. It is strongly advised to do a clean build.
1191.255Sjoerg
1201.251Smartin20140131:
1211.253Sjoerg	The new compiler_rt/libc integration moved a few things. It is strongly
1221.254Sskrll	advised to do a clean build. At least lib/libc, the compat version(s)
1231.253Sjoerg	of libc, libkern, rump and the kernels need to be cleaned.
1241.251Smartin
1251.250Schristos20131227:
1261.250Schristos	1. The new ntpd runs in a restricted mode to prevent amplification
1271.250Schristos	   attacks. If you need ntpdc to work you need to explicitly enable
1281.250Schristos	   mode7 in your config file. Make sure you put the necessary restrict
1291.250Schristos	   statements to avoid being exposed.
1301.250Schristos	2. strncat has moved from lib/libc to common/lib/libc; you might need
1311.250Schristos	   to make clean in libc
1321.250Schristos
1331.249Smrg20131129:
1341.249Smrg	The GMP sources were updated, and builds will likely fail without
1351.249Smrg	cleaning their build trees for both tools and in-tree, like below.
1361.249Smrg
1371.248Smrg20131128:
1381.248Smrg	The MPC and MPFR sources were updated, and builds may require their
1391.248Smrg	tools and in-tree directories cleaned for successful updates.
1401.248Smrg
1411.246Smartin20130605:
1421.247Sspz	The kernel option FAST_IPSEC no longer exists, it's been renamed
1431.247Sspz	to IPSEC (and the older IPSEC version removed).
1441.247Sspz
1451.247Sspz20130605:
1461.246Smartin	Previous freetype installations eroneously installed private
1471.246Smartin	header files. If you are building against a non-empty $DESTDIR,
1481.246Smartin	please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
1491.246Smartin
1501.245Smrg20130531:
1511.245Smrg	The xdm update may cause build failure due to xdm.man being
1521.245Smrg	in the obj tree.  Make sure to ensure any like this:
1531.245Smrg		nbmake: nbmake: don't know how to make xdm.man. Stop
1541.245Smrg	is fixed by deleting the xdm.man in the obj tree.
1551.245Smrg
1561.244Smrg20130530:
1571.244Smrg	Updates of many xsrc packages will leave old .pc files around.
1581.244Smrg	Best to clean out the xsrc objdir entirely before rebuilds.
1591.244Smrg
1601.242Schristos20130301:
1611.242Schristos	The removal of netiso requires manual removal of /usr/include/netiso
1621.243Schristos	prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
1631.242Schristos
1641.238Sdholland20120726:
1651.241Swiz	The update of OpenSSL requires cleaning both the OpenSSL build
1661.241Swiz	directory and DESTDIR.  *Even non-update builds require cleaning
1671.240Sdholland	DESTDIR.* Builds done without taking these steps may fail, or in
1681.241Swiz	some cases may succeed and install broken OpenSSL libraries that
1691.240Sdholland	cause third-party software to link incorrectly and/or crash.
1701.238Sdholland
1711.237Swiz20120507:
1721.241Swiz	The database schema for makemandb was changed.  You will
1731.237Swiz	need to update the database using 'makemandb -f' or wait
1741.237Swiz	for the next weekly run to fix it.
1751.237Swiz
1761.236Sbsh20120319:
1771.236Sbsh	sys/conf/Makefile.kern.inc has been modified to adjust the
1781.236Sbsh	size of db_symtab automatically.  You need to update dbsym in
1791.236Sbsh	your $TOOLDIR to build kernels with options SYMTAB_SPACE.  If
1801.236Sbsh	you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
1811.236Sbsh	mk.conf.
1821.236Sbsh
1831.235Sjoerg20120216:
1841.241Swiz	Default for MKCATPAGES changed to NO.  Update builds will fail
1851.241Swiz	unless DESTDIR is cleaned manually.  If you built between 20120207
1861.239Sdholland	and 20120216, daily and weekly could have created an unreadable
1871.241Swiz	/var/db/man.db index for apropos.  Running makemandb -f or
1881.235Sjoerg	the next run of weekly will fix it.
1891.233Sjoerg
1901.232Schristos20111227:
1911.232Schristos	If you built between 20111225 and 20111227 you need to remove
1921.232Schristos	/usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
1931.232Schristos	bump has been reverted.
1941.232Schristos
1951.231Stls20111125:
1961.231Stls	The "rnd" pseudodevice has been added to sys/conf/std, which
1971.231Stls	means it should no longer be explicitly listed in kernel
1981.231Stls	configuration files.  The line "pseudo-device rnd" should be
1991.231Stls	removed from any custom kernel config files users may have.
2001.231Stls
2011.230Stls20111119:
2021.230Stls	A problem with the datastructures used by the rndctl(8)
2031.230Stls	utility (pointers in datastructures in an array, making 32->64
2041.230Stls	bit compatibility very painful) has been fixed in a
2051.230Stls	non-backwards-compatible way.  If you replace your kernel,
2061.230Stls	replace your rndctl executable too.
2071.241Swiz
2081.229Sjym20111001:
2091.229Sjym	the prop_*_send_syscall() functions from proplib(3) have been
2101.229Sjym	changed and their new version is not backward compatible with the old
2111.241Swiz	one.  So ensure that all consumers of these functions (currently:
2121.229Sjym	quota2 code and its tests) are updated together with the new lib.
2131.229Sjym
2141.228Smrg20110817:
2151.228Smrg	sparc has been changed to use GCC 4.5.3, so any objdir or
2161.228Smrg	DESTDIR for them should be deleted before updating.
2171.228Smrg
2181.227Sriastrad20110806:
2191.227Sriastrad	i386 and amd64 have been changed to use GCC 4.5.3, so any
2201.227Sriastrad	objdir or DESTDIR for them should be deleted before updating.
2211.227Sriastrad
2221.226Smrg20110805:
2231.226Smrg	The update to GCC 4.5.3 requires a non-trivial portion of
2241.226Smrg	the tree to be cleaned.  Best to delete both objdir and
2251.226Smrg	DESTDIR before running this update.  So far, only the
2261.226Smrg	sparc64, mips and powerpc platforms have changed.
2271.226Smrg
2281.225Smatt20110803:
2291.241Swiz	The layout of external/public-domain/xz has changed.  To do an
2301.225Smatt	update build you will have to remove the contents of the OBJDIR
2311.225Smatt	for external/public-domain/xz/bin by hand as the xz entry there
2321.225Smatt	is now a directory.
2331.225Smatt
2341.223Sjoerg20110410:
2351.241Swiz	The configuration of src/tools/gcc has changed.  To do an
2361.224Sdholland	update build you have to clean both tools/binutils and
2371.224Sdholland	tools/gcc by hand.
2381.223Sjoerg
2391.222Splunky20110328:
2401.222Splunky	Building the Xorg binary was moved into a subdirectory to fix
2411.241Swiz	ordering issues with "make all".  It may be necessary to remove
2421.222Splunky	the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
2431.222Splunky	if your update build fails, as the "Xorg" entry there is now a
2441.222Splunky	directory.
2451.222Splunky
2461.220Sjoerg20110121:
2471.221Slukem	Assembler files no longer use -traditional-cpp.  This can break
2481.220Sjoerg	the build of individual parts of the tree.  This is handled
2491.220Sjoerg	correctly by build.sh.  Manual builds have to update /usr/share/mk
2501.220Sjoerg	and re-run config(1) for any kernel configurations as needed.
2511.218Sjoerg
2521.217Sjruoho20101217:
2531.217Sjruoho	The tcpdump(8) program was changed to drop privileges and chroot(2)
2541.241Swiz	by default.  It may be necessary to manually update passwd(5) and
2551.217Sjruoho	group(5) in order to make the program work with existing setups.
2561.217Sjruoho
2571.216Schristos20101125:
2581.216Schristos	The latest changes to setenv(3) dissallow setting environment
2591.241Swiz	variables with names that contain '='.  Revision 1.18 of env.c
2601.241Swiz	assumed that this was allowed.  Installing a new libc with an
2611.216Schristos	old copy of /usr/bin/env causes env x=1 printenv | grep x= to
2621.216Schristos	break which affects the autoconf tests for dependency finding,
2631.216Schristos	so building gcc will end up printing:
2641.216Schristos	    checking dependency style of gcc... none
2651.216Schristos	    configure: error: no usable dependency style found
2661.216Schristos	Fix it by rebuilding and re-installing env.
2671.138Slukem
2681.215Smrg20101119:
2691.215Smrg	Recent Xorg updates in xsrc/external/mit/ may cause various build
2701.215Smrg	or run-time problems.  Delete your entire DESTDIR and OBJDIR if you
2711.215Smrg	have any build problems with xsrc, or problems with mismatched
2721.215Smrg	versions between xorg-server and drivers.
2731.215Smrg
2741.213Sjmmv20100604:
2751.213Sjmmv	The update of ATF to 0.9 causes old tests written in shell to fail
2761.213Sjmmv	unless they are rebuilt.  If you are building with MKUPDATE=yes,
2771.213Sjmmv	you need to clean the src/external/bsd/atf/tests/ and the src/tests/
2781.213Sjmmv	trees by hand.
2791.213Sjmmv
2801.211Stnozaki20100522:
2811.212Smrg	Recent Xorg updates in xsrc/external/mit/ will cause various build
2821.212Smrg	problems.  Delete your entire DESTDIR and OBJDIR if you have any
2831.212Smrg	build problems with xsrc.
2841.212Smrg
2851.212Smrg20100522:
2861.211Stnozaki	private section of <ctype.h> was splitted, and now mklocale(1)
2871.214Sdholland	include ctype_local.h, so you have to make cleandir in tools/mklocale.
2881.211Stnozaki
2891.210Schristos20100520:
2901.241Swiz	The location of the xkb compiled descriptions has changed.  Please
2911.210Schristos	remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
2921.210Schristos
2931.209Snjoly20100222:
2941.209Snjoly	The shared objects file extension has been changed from .so to
2951.209Snjoly	.pico, in order to avoid conflicts with shared libraries names
2961.209Snjoly	libXX.so.  All now stale regular .so files can be removed from
2971.209Snjoly	your object directories.
2981.209Snjoly
2991.208Sroy20100204:
3001.208Sroy	The termcap database has been removed from the sources,
3011.208Sroy	but has not been marked obsolete so it is not removed
3021.208Sroy	from the system when upgrading.
3031.208Sroy	As such, you will need to remove them from your object
3041.208Sroy	and destination directories.
3051.208Sroy
3061.203Sdyoung20091101:
3071.205Sdholland        After updating, it may be necessary to make the 'cleandir'
3081.205Sdholland        target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
3091.205Sdholland        'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
3101.205Sdholland        src/tools/lex/ and src/usr.bin/lex/.
3111.203Sdyoung
3121.202Smrg20091001:
3131.206Sdholland	On amd64 you must rebuild tools (to get the new binutils)
3141.206Sdholland	before building a kernel, or the build fails on cpufunc.S.
3151.206Sdholland
3161.206Sdholland20091001:
3171.202Smrg	An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
3181.202Smrg	symlink, failing the build.  Delete the link, and the subdir
3191.202Smrg	it is in, and retry your build.
3201.202Smrg
3211.201Sdsl20090718:
3221.201Sdsl	libc build changed so that strchr() provides the extra entry
3231.241Swiz	point for index().  Update build of libc.a (and libc_pic.a)
3241.201Sdsl	may fail because the archive contains the unwanted index.o.
3251.201Sdsl	(Similarly for strrchr() and rindex().)
3261.201Sdsl
3271.198Smrg20090709:
3281.198Smrg	Native Xorg was upgraded again.  Builds will probably fail again
3291.198Smrg	without a clean objdir, at least for src/external/mit/xorg.
3301.198Smrg
3311.197Smrg20090616:
3321.197Smrg	Native Xorg was upgraded.  Builds will need a clean objdir for
3331.197Smrg	src/external/mit/xorg.  Upgrading a system from sets will not
3341.197Smrg	work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
3351.197Smrg	subdirectory has been changed into a file, and this needs to
3361.197Smrg	be manually "rm -r"'ed before installing xbase.tgz.
3371.197Smrg
3381.195Sperry20090501:
3391.195Sperry	Several new functions were added to string.h/libc, and this
3401.195Sperry	can cause autoconf problems during the tool build for people
3411.241Swiz	who fail to clean out their tools objects properly.  If you
3421.195Sperry	note messages about stpcpy, stpncpy or strnlen accompanying a
3431.195Sperry	failure during the tool build, clean out all your tools
3441.195Sperry	objects and start again.
3451.195Sperry
3461.194Smrg20090325:
3471.194Smrg	The i386 port was switched to i486 default toolchain.  This requires
3481.194Smrg	cleaning your src/tools directory and $TOOLDIR and rebuilding them.
3491.194Smrg
3501.192Sskrll20090126:
3511.241Swiz	The __posix_fadvise50 system call changed assembly stub type.  You
3521.207Smbalmer	need to 'rm -f __posix_fadvise50.*' in the libc build directory
3531.207Smbalmer	to avoid using the old assembly stub.
3541.192Sskrll
3551.191Sjoerg20090202:
3561.191Sjoerg	pkg_install now depends on the pkgdb cache for automatic conflict
3571.191Sjoerg	detection.  It is recommented to rebuild the cache with
3581.191Sjoerg	``pkg_admin rebuild''.
3591.191Sjoerg
3601.184Schristos20090110:
3611.241Swiz	time_t and dev_t have been bumped to 64 bit quantities.  To upgrade:
3621.241Swiz	1. Make sure your kernel has COMPAT_50 in it.  Build and install.
3631.188Schristos	   This is needed even in the MODULAR kernel because there is
3641.188Schristos	   conditionally compiled code in rtsock.c.
3651.184Schristos	2. make sure build.sh completes and the binaries in a chroot work
3661.184Schristos	   before installing.
3671.184Schristos	3. If you don't use build.sh and you build directly to root, and
3681.241Swiz	   your build breaks in the middle, don't despair.  Make sure headers
3691.184Schristos	   are installed properly, and start building libraries first libc
3701.184Schristos	   and libutil, install them and then continue building all the
3711.241Swiz	   libraries in src/lib and src/gnu/lib and install them.  Once
3721.184Schristos	   the new libraries are installed, you can restart the build.
3731.184Schristos	4. If you compile packages and you notice link time warnings,
3741.189Shubertf	   rebuild the required packages to update their shared libraries.
3751.189Shubertf	   Any package you rebuild will require rebuilding all the packages
3761.189Shubertf	   that depend on it.
3771.186Schristos	5. Next time you run pwd_mkdb with the new binary, the file
3781.186Schristos	   will be upgraded and it will not be backwards compatible.
3791.190Sapb	6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
3801.190Sapb	   lastlogx(5)) have been versioned, and there is a heuristic
3811.241Swiz	   for utmp.  You are better off removing the old files after
3821.190Sapb	   upgrading.  The automated clearing of /var/run during
3831.190Sapb	   boot, and the automated rotating of files in /var/log by
3841.190Sapb	   newsyslog(8), may mean that you do not have to remove the
3851.190Sapb	   files manually.
3861.190Sapb	7. The optional accounting file (/var/account/acct, see
3871.190Sapb	   accton(8)) has not been versioned, and will need to be
3881.190Sapb	   removed.  The automatic rotation of the accounting file by
3891.190Sapb	   /etc/daily limits the bad consequences of failure to remove
3901.190Sapb	   the file.
3911.196Sdholland	8. Application software that writes time_t to binary files on
3921.241Swiz	   disk will break or need attention.  Most notably: if you are
3931.196Sdholland	   using PostgreSQL < 8.4, you need to dump your databases,
3941.196Sdholland	   rebuild PostgreSQL with the new time_t, then restore.
3951.185Sjmcneill
3961.183Spgoyette20081219:
3971.183Spgoyette	config(1) has been updated, and one of the files it creates -
3981.183Spgoyette	swapnetbsd.o - has changed format.  You need to rebuild config
3991.183Spgoyette	(done automatically by build.sh) and then you need to rerun
4001.183Spgoyette	config on all kernel configuration files before rebuilding those
4011.183Spgoyette	kernels.
4021.183Spgoyette
4031.181Scube20081205:
4041.181Scube	If you build with MKX11=no, you should remove /etc/rc.d/xdm and
4051.181Scube	/etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
4061.181Scube	set and will appear as extra files for MKX11=no update builds.
4071.178Slukem
4081.179Stsutsui20081122:
4091.182Stsutsui	On i386, various kernel options(4) in GENERIC including
4101.180Swiz	file systems have been disabled and moved into kernel modules.
4111.180Swiz	Before trying a new GENERIC kernel, you have to prepare the
4121.179Stsutsui	following files as well as a new GENERIC kernel:
4131.179Stsutsui
4141.179Stsutsui	- build and install kernel modules from src/sys/modules
4151.179Stsutsui
4161.179Stsutsui	- install the latest bootloader, which will load a module
4171.180Swiz	  for the file system from which the kernel is loaded automatically
4181.179Stsutsui
4191.180Swiz	If you have to load your kernel from a file system which is not of
4201.180Swiz	the same type as the root file system, you have to load the necessary
4211.180Swiz	file system module manually on the boot prompt or in the boot.cfg file.
4221.179Stsutsui
4231.178Slukem20080827:
4241.178Slukem	If you built and installed a libc from sources between
4251.178Slukem	2008/08/20 and 2008/08/26 you got a broken strtouq(3)
4261.178Slukem	which results in false errors reported by lint(1).
4271.178Slukem	Since this breaks the libc build itself, manual help is
4281.180Swiz	needed -- lint must be disabled temporarily, e.g.:
4291.178Slukem	  $ (cd lib/libc && make MKLINT=no dependall install)
4301.178Slukem
4311.177Schristos20080813:
4321.177Schristos	MKDEBUG build was broken because the .depend files did not know
4331.241Swiz	about .go files.  You need to remove all .depend files and rebuild.
4341.177Schristos
4351.200Sdholland20080802:
4361.200Sdholland	A regression in binary compatibility for pthread_mutex_t has
4371.241Swiz	been fixed.  Unfortunately, the price is breaking compatibility
4381.200Sdholland	for -current.
4391.200Sdholland
4401.200Sdholland	Threaded programs (using libpthread) and C++ programs (using
4411.200Sdholland	libstdc++) compiled after 20070907 and before 20080802 need to
4421.200Sdholland	be recompiled.
4431.200Sdholland
4441.200Sdholland	One way to find affected pkgsrc packages:
4451.200Sdholland
4461.200Sdholland	  $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
4471.200Sdholland	  $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
4481.200Sdholland
4491.175Ssimonb20080731:
4501.175Ssimonb	WAPBL (metadata journaling support) has been added, but at this
4511.175Ssimonb	time isn't backwards compatible with pre-WAPBL aware kernels
4521.175Ssimonb	and userland (fsck_ffs in particular).  Please make sure you
4531.175Ssimonb	don't use a journaled filesystem with an older kernel/userland,
4541.176Ssimonb	especially an uncleanly mounted journaled filesystem.  WAPBL
4551.176Ssimonb	also requires the super block to be in the UFS2 format.  You
4561.176Ssimonb	can use fsck_ffs -c 4 to update the superblock format.
4571.175Ssimonb
4581.174Slukem20080721:
4591.174Slukem	Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
4601.174Slukem	isn't defined.
4611.174Slukem
4621.173Sfreza20080531:
4631.241Swiz	The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
4641.241Swiz	from 125 (conflicted with DRVCTLCOMMAND) to 129.  The drvctl(8)
4651.173Sfreza	utility needs to be rebuilt and reinstalled as older binaries
4661.241Swiz	won't work correctly.  The following sequence of commands:
4671.173Sfreza
4681.173Sfreza	  $ (cd sys/sys/ && nbmake-$arch includes)
4691.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch clean)
4701.173Sfreza	  $ (cd sbin/drvctl/ && nbmake-$arch all)
4711.173Sfreza
4721.173Sfreza	leaves new drvctl utility in sbin/drvctl build directory.
4731.173Sfreza
4741.172Slukem20080503:
4751.172Slukem	The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
4761.172Slukem
4771.171She20080521:
4781.171She	For a while, unprivileged UPDATE builds would fail to
4791.171She	succeed at the checkflist stage, complaining that
4801.171She	${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
4811.171She	problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
4821.171She	If you already hit this problem, update the .mk file,
4831.171She	remove ${DESTDIR}/stand/<arch>, and re-run the build.
4841.171She
4851.174Slukem20080303:
4861.174Slukem	Linker warnings are now fatal if $WARNS>0.
4871.174Slukem
4881.170Schristos20080126:
4891.170Schristos	The posix_fadvise system call has been changed from an assembly
4901.241Swiz	stub, to a c file that calls an assembly stub.  You need to
4911.170Schristos	'rm -f posix_fadvise.* .depend' in the libc build directory to
4921.170Schristos	avoid using the old assembly stub.
4931.170Schristos
4941.168Sjoerg20071209:
4951.241Swiz	The acpiec(4) driver has been split into two attachments.  If you
4961.168Sjoerg	get ACPI errors before the attachment, please update your kernel
4971.169Swiz	configuration file appropriately or see GENERIC for more details.
4981.168Sjoerg
4991.166Sxtraeme20071115:
5001.166Sxtraeme	The it(4) driver has been renamed to itesio(4) and the old port
5011.166Sxtraeme	argument specified in the kernel configuration file is not valid
5021.241Swiz	anymore.  The itesio(4) driver now uses the Super I/O address port
5031.241Swiz	rather than the EC address port.  Please update your kernel
5041.167Swiz	configuration file appropriately or see GENERIC for more details.
5051.166Sxtraeme
5061.165Sjmmv20071028:
5071.165Sjmmv	The pccons(4) driver has been removed from the NetBSD/shark port.
5081.165Sjmmv	You need to update any custom kernel configuration file you have
5091.165Sjmmv	to remove any references to pccons (which includes removing the
5101.165Sjmmv	now useless XSERVER option) and replace them with the correct
5111.165Sjmmv	entries for the wscons driver.  See the GENERIC configuration file
5121.165Sjmmv	for more details.
5131.165Sjmmv
5141.164Sgdt20070913:
5151.164Sgdt	A latent bug in dhclient/dhcpd that caused it to be unable to
5161.164Sgdt	enumerate interfaces was fixed.  The bug began to cause
5171.164Sgdt	problems after 20070911 when the kernel's SIOCGIFCONF
5181.164Sgdt	implementation was repaired.  From 20070529 to 20070911 racoon
5191.164Sgdt	could not enumerate interfaces.  (These are noted because
5201.164Sgdt	normal kernel/userspace version matching hygiene is not
5211.164Sgdt	sufficient to avoid this problem.)  Ensure that both kernel
5221.164Sgdt	and userland are from after 20070913.
5231.164Sgdt
5241.163Sjoerg20070703:
5251.241Swiz	nbinstall has been renamed ${MACHINE_GNU_ARCH}-install.  It
5261.199Sdholland	calls the target-specific strip program, and the logic to pass
5271.199Sdholland	down STRIP from make has been removed.  This requires a
5281.199Sdholland	re-installation of tools.
5291.163Sjoerg
5301.161Sdsl20070422:
5311.161Sdsl	The way OS emulations lookup filenames inside the emulation root
5321.161Sdsl	has been changed.  Rather than modify the pathname (and copy back
5331.161Sdsl	to userspace) namei() and lookup() directly check the emulation
5341.241Swiz	root.  One side effect is that absolute symlinks inside the emulated
5351.167Swiz	root file system will be relative to that file system - unless they
5361.161Sdsl	start /../ this is useful when the emulated root is a real install
5371.161Sdsl	that has such links.
5381.161Sdsl	This might affect symlinks that have been added to reference outside
5391.161Sdsl	the emulated root.
5401.161Sdsl
5411.160Sjmcneill20070412:
5421.241Swiz	The pckbc driver on sgimips IP32 has been removed.  Use macekbc
5431.241Swiz	instead.  See the GENERIC32_IP3x kernel configuration for an
5441.160Sjmcneill	example.
5451.160Sjmcneill
5461.159Sgdt20070319:
5471.159Sgdt        src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
5481.159Sgdt        on many platforms due to incorrect flags settings.  If you
5491.159Sgdt        updated and built after about 20070315, do "nbmake-$arch
5501.159Sgdt	cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
5511.159Sgdt	rebuild of object files that might have been built
5521.159Sgdt	incorrectly, and ensure that you have at least
5531.159Sgdt	src/lib/libc/Makefile 1.130.
5541.159Sgdt
5551.241Swiz20070210:
5561.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
5571.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
5581.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
5591.158Sdbj        will allow dependencies on those files to get get rebuilt
5601.158Sdbj
5611.157Sapb20070209:
5621.157Sapb        The threading model was changed when the newlock2 branch
5631.157Sapb        was merged to NetBSD-current.  If you boot with a new
5641.157Sapb        kernel (version 4.99.10), then you also need a new pthread
5651.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
5661.157Sapb        an old kernel, then you need the old pthread library
5671.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
5681.157Sapb        the pthread library in sync, old threaded applications should
5691.157Sapb        continue to work with an old or new kernel.  Note that named(8)
5701.157Sapb	is the only threaded application in the base system.
5711.157Sapb
5721.154She20061214:
5731.154She	Following the move of string_to_flags() and flags_to_string()
5741.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
5751.154She	will need to do a "make cleandir" in
5761.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
5771.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
5781.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
5791.156She		as the installation images in distrib/
5801.154She	in order to excise stale references to the old stat_flags.h header
5811.154She	file in the ls sources -- stat_flags.h has been removed.
5821.154She
5831.152Schristos20061108:
5841.152Schristos	The configure script used in the src/tools/gcc compiler has been
5851.152Schristos	changed to indicate that our libc has ssp support built-in and
5861.241Swiz	does not depend on -lssp and -lssp-nonshared.  You'll need to
5871.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
5881.152Schristos
5891.151Srpaulo20061009:
5901.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
5911.241Swiz	available.  Use net.inet{,6}.tcp{,6}.congctl.selected instead.
5921.151Srpaulo
5931.150Sbjh2120060814:
5941.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
5951.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
5961.150Sbjh21	kernel configuration for an example.  X servers from the last
5971.150Sbjh21	few years should cope.
5981.150Sbjh21
5991.149Schristos20060703:
6001.241Swiz	MPACPI is no more.  We always configure PCI interrupts using ACPI
6011.241Swiz	if we have an ACPI kernel.  The option MPACPI_SCANPCI has been renamed
6021.241Swiz	to ACPI_SCANPCI.  Thanks to work from fvdl.
6031.149Schristos
6041.148Sdogcow20060627:
6051.148Sdogcow	socket(2) has changed, and its system call has been versioned.
6061.148Sdogcow	For userlands with the old version of socket(2), make sure that
6071.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
6081.148Sdogcow	errors will result.
6091.148Sdogcow
6101.1SabsHints for a more successful build:
6111.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6121.123Sjmc    Use build.sh, but do not use its "expert mode":
6131.132Sjmmv	This will automatically build the tools in the
6141.123Sjmc	   correct order, and it will keep the tools and the
6151.123Sjmc	   new build products from interfering with the running
6161.123Sjmc	   system.  This will allow you to ignore most of the
6171.123Sjmc	   other advice in this file.
6181.2Smrg    Build a new kernel first:
6191.2Smrg	This makes sure that any new system calls or features
6201.2Smrg	   expected by the new userland will be present.  This
6211.2Smrg	   helps to avoid critical errors when upgrading.
6221.1Sabs    Use object directories:
6231.1Sabs	This helps to keep stale object
6241.1Sabs	   files from polluting the build if a Makefile "forgets"
6251.1Sabs	   about one.  It also makes it easier to clean up after
6261.1Sabs	   a build.  It's also necessary if you want to use the
6271.1Sabs	   same source tree for multiple machines.
6281.123Sjmc	   To use object directories with build.sh:
6291.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
6301.123Sjmc	   To use object directories without using build.sh:
6311.1Sabs	    a) cd /usr/src ; make cleandir
6321.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
6331.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
6341.1Sabs	    d) cd /usr/src ; make build
6351.2Smrg	   Note that running "make obj" in a directory will create
6361.2Smrg	   in obj.$MACHINE directory.
6371.1Sabs    Build to a DESTDIR:
6381.123Sjmc	This helps to keep old installed files (especially libraries)
6391.123Sjmc	   from interfering with the new build.
6401.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
6411.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
6421.123Sjmc	   environment variable before running make build.  It should be
6431.123Sjmc	   set to the pathname of an initially empty directory.
6441.123Sjmc	   Problems: if you do not use build.sh, you might need to
6451.123Sjmc		update critical utilities without using DESTDIR since
6461.123Sjmc		nothing is executed from what is installed in DESTDIR.
6471.123Sjmc		(See critical utils, below.)
6481.1Sabs    Build often:
6491.1Sabs	This keeps critical utilities current enough to not choke
6501.1Sabs	on any other part of the source tree that depends on up to
6511.123Sjmc	date functionality.  If you use build.sh, you should not have
6521.123Sjmc	this problem.
6531.241Swiz
6541.1SabsWhat to do if things don't work:
6551.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6561.230StlsWhen things don't work there are usually a few things that commonly
6571.1Sabsshould be done.
6581.1Sabs    1)	make includes
6591.1Sabs	This should be done automatically by make build.
6601.1Sabs    2)  cd share/mk && make install
6611.1Sabs	Again, automatically done by make build.
6621.1Sabs
6631.1SabsFailsafe rebuild of a small part of the tree:
6641.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6651.1SabsTo make sure you rebuild something correctly you want to do
6661.1Sabssomething like the following:
6671.1Sabs    1)  Make sure the includes and .mk files are up to date.
6681.1Sabs    2)  Make sure any program used to build the particular
6691.1Sabs	utility is up to date.  (yacc, lex, etc...)
6701.1Sabs    3)  cd ...path/to/util...
6711.1Sabs	make cleandir
6721.1Sabs	rm ...all obj directories...
6731.1Sabs	make cleandir			# yes, again
6741.1Sabs	make obj
6751.1Sabs	make depend && make
6761.1Sabs
6771.1SabsFailsafe rebuild of the entire tree:
6781.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6791.1SabsIf you really want to make sure the source tree is clean and
6801.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
6811.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
6821.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
6831.1Sabs
6841.1Sabs---cut here---
6851.1Sabs#!/bin/sh
6861.1Sabs. /etc/mk.conf
6871.1Sabs
6881.58Slukemif [ -z $NETBSDSRCDIR ] ; then
6891.58Slukem    NETBSDSRCDIR=/usr/src
6901.1Sabsfi
6911.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
6921.1Sabs    echo Unable to find sources
6931.1Sabs    exit 1
6941.1Sabsfi
6951.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
6961.1Sabs
6971.1Sabsif [ -z $BSDOBJDIR ] ; then
6981.1Sabs    BSDOBJDIR=/usr/obj
6991.1Sabsfi
7001.1Sabsif [ -d $BSDOBJDIR ] ; then
7011.1Sabs    rm -rf $BSDOBJDIR
7021.1Sabsfi
7031.1Sabs
7041.58Slukemcd $NETBSDSRCDIR && make cleandir
7051.1Sabs
7061.1Sabs---cut here---
7071.1Sabs
7081.1SabsCritical utilities:
7091.1Sabs^^^^^^^^^^^^^^^^^^^
7101.3Sitojun	usr.bin/compile_et
7111.1Sabs	usr.bin/make
7121.1Sabs	usr.bin/yacc
7131.1Sabs	usr.bin/lex
7141.11Slukem	usr.bin/xlint
7151.142Sdrochner	usr.bin/config
7161.1Sabs
7171.34SsimonbOther problems and possible solutions:
7181.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7191.1SabsSymptom:Complaints involving a Makefile.
7201.17SerhFix:	Rebuild usr.bin/make:
7211.17Serh	cd usr.bin/make && make && make install
7221.111Ssimonb	Or, a failsafe method if that doesn't work:
7231.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
7241.17Serh
7251.1SabsFix:	Make sure .mk files are up to date.
7261.1Sabs	cd share/mk && make install
7271.2Smrg
7281.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
7291.142SdrochnerFix:	Rebuild usr.bin/config
7301.1Sabs
7311.1SabsSymptom:
7321.1SabsFix:	Rebuild usr.bin/yacc
7331.1Sabs
7341.1SabsSymptom:
7351.1SabsFix:	Rebuild usr.bin/lex
7361.1Sabs
7371.1SabsSymptom:
7381.1SabsFix:	rm /usr/lib/libbfd.a
7391.4Sitojun
7401.4SitojunSymptom:Obsolete intermediate files are used during compilation
7411.4SitojunFix:	Try the following sequence of commands in the directory in question.
7421.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
7431.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
7441.4Sitojun	may remain.  The command tries to clean everything up)
7451.5Swiz
7461.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible
7471.207Smbalmer	pointer type
7481.5SwizFix:	Rebuild and install usr.bin/menuc
7491.12Sitojun
7501.12SitojunSymptom:mklocale not found during build in share/locale/ctype
7511.12SitojunFix:	Build and install usr.bin/mklocale
7521.13Sdogcow
7531.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
7541.13SdogcowFix:    Rebuild and install lib/libc
7551.13Sdogcow
7561.142SdrochnerSymptom:usr.bin/config fails to build.
7571.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
7581.13Sdogcow
7591.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
7601.19ScgdFix:    Rebuild and install lib/libc
7611.24Sabs
7621.24SabsSymptom:lint does not understand the '-X' option
7631.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
7641.223Sjoerg
7651.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable
7661.223Sjoerg	(e.g. CPPFLAGS) has changed since the previous run.
7671.223SjoergFix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
7681.257Sapb
7691.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
7701.257Sapb	No such file or directory.
7711.257SapbCause:	If a directory is created by mistake, then it is sometimes
7721.257Sapb	deleted from the CVS repository using administrative commands
7731.257Sapb	that bypass the normal cvs access controls.  If your cvs working tree
7741.257Sapb	contains references to a directory that has been deleted on the
7751.257Sapb	server in this way, then "cvs update" reports this error.
7761.257SapbFix:	Recursively delete the affected directory from your working tree
7771.257Sapb	and try the update again.
778