UPDATING revision 1.269
11.269Sdholland$NetBSD: UPDATING,v 1.269 2016/04/16 19:47:45 dholland 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.268Sriastrad20160410: 231.268Sriastrad 241.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 251.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 261.268Sriastrad executables, means all code, including executables and not just 271.268Sriastrad shared libraries, is position-independent and hence able to be 281.268Sriastrad relocated by ASLR, address space layout randomization. 291.268Sriastrad 301.268Sriastrad The change was made in Makefile variables for compiler and 311.268Sriastrad linker flags, for which make(1) does not record dependencies, 321.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 331.268Sriastrad 341.268Sriastrad Partial rebuilds with some modified source files will likely 351.268Sriastrad fail when linking executables, since the linker refuses to mix 361.268Sriastrad position-independent code with position-dependent code in 371.268Sriastrad position-independent executables: 381.268Sriastrad 391.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 401.268Sriastrad 411.267Smrg20160401: 421.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 431.269Sdholland Some people have found that cleandir is not sufficient, so if 441.269Sdholland in doubt delete the entire object directory tree for gcc. 451.267Smrg 461.266Saymeric20160306: 471.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 481.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 491.265Saymeric non-NetBSD hosts if linked with stale object files produced 501.265Saymeric while they included a non-NetBSD regex.h. 511.265Saymeric In any case, you should "make cleandir" at least these tools 521.265Saymeric before updating your toolchain. 531.265Saymeric 541.264Smartin20160125: 551.264Smartin Dtrace has been enabled by default on some architectures. 561.264Smartin When doing an update build, make sure to clean the etc/mtree 571.264Smartin object directory before starting the build - otherwise the 581.264Smartin needed directories in destdir will not be created. 591.264Smartin An easy way to do this is: 601.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 611.264Smartin 621.263Sdholland20150818: 631.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 641.263Sdholland again. 651.263Sdholland 661.262Schristos20150413: 671.262Schristos New acpica requires "make cleandir" and reinstalling yacc 681.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 691.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 701.262Schristos 711.261Smartin20150404: 721.261Smartin Lint changes require a full rebuild of the tool, so make 731.261Smartin sure to build without -u option to build.sh, or manually 741.261Smartin do a make cleandir in src/tools/lint1 and 751.261Smartin src/usr.bin/xlint. 761.261Smartin 771.260Sskrll20150310: 781.260Sskrll Improvements to openssl for arm mean that update builds of 791.260Sskrll the openssl libraries will fail. A make cleandir in 801.260Sskrll external/bsd/openssl/lib is needed 811.260Sskrll 821.258Smartin20141026: 831.259Smsaitoh A mishap during the import of pppd may cause your corruption 841.258Smartin in your cvs directory if you happened to do a cvs update 851.258Smartin during a short period of time. To fix, just remove the 861.258Smartin directory src/external/bsd/ppp/dist/pppd completely 871.258Smartin and let cvs restore it on next update. 881.258Smartin 891.256Sapb20140721: 901.256Sapb The src/external/mit/lua/src directory was accidentally created 911.256Sapb and then deleted in the CVS repository. If you get errors like 921.256Sapb 931.256Sapb cvs [update aborted]: cannot open directory 941.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 951.256Sapb 961.256Sapb then delete your local copy of that directory tree and try again. 971.256Sapb 981.255Sjoerg20140530: 991.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 1001.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 1011.255Sjoerg 1021.251Smartin20140131: 1031.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 1041.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 1051.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 1061.251Smartin 1071.250Schristos20131227: 1081.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 1091.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 1101.250Schristos mode7 in your config file. Make sure you put the necessary restrict 1111.250Schristos statements to avoid being exposed. 1121.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 1131.250Schristos to make clean in libc 1141.250Schristos 1151.249Smrg20131129: 1161.249Smrg The GMP sources were updated, and builds will likely fail without 1171.249Smrg cleaning their build trees for both tools and in-tree, like below. 1181.249Smrg 1191.248Smrg20131128: 1201.248Smrg The MPC and MPFR sources were updated, and builds may require their 1211.248Smrg tools and in-tree directories cleaned for successful updates. 1221.248Smrg 1231.246Smartin20130605: 1241.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 1251.247Sspz to IPSEC (and the older IPSEC version removed). 1261.247Sspz 1271.247Sspz20130605: 1281.246Smartin Previous freetype installations eroneously installed private 1291.246Smartin header files. If you are building against a non-empty $DESTDIR, 1301.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 1311.246Smartin 1321.245Smrg20130531: 1331.245Smrg The xdm update may cause build failure due to xdm.man being 1341.245Smrg in the obj tree. Make sure to ensure any like this: 1351.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 1361.245Smrg is fixed by deleting the xdm.man in the obj tree. 1371.245Smrg 1381.244Smrg20130530: 1391.244Smrg Updates of many xsrc packages will leave old .pc files around. 1401.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 1411.244Smrg 1421.242Schristos20130301: 1431.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 1441.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 1451.242Schristos 1461.238Sdholland20120726: 1471.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 1481.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 1491.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 1501.241Swiz some cases may succeed and install broken OpenSSL libraries that 1511.240Sdholland cause third-party software to link incorrectly and/or crash. 1521.238Sdholland 1531.237Swiz20120507: 1541.241Swiz The database schema for makemandb was changed. You will 1551.237Swiz need to update the database using 'makemandb -f' or wait 1561.237Swiz for the next weekly run to fix it. 1571.237Swiz 1581.236Sbsh20120319: 1591.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 1601.236Sbsh size of db_symtab automatically. You need to update dbsym in 1611.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 1621.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 1631.236Sbsh mk.conf. 1641.236Sbsh 1651.235Sjoerg20120216: 1661.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 1671.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 1681.239Sdholland and 20120216, daily and weekly could have created an unreadable 1691.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 1701.235Sjoerg the next run of weekly will fix it. 1711.233Sjoerg 1721.232Schristos20111227: 1731.232Schristos If you built between 20111225 and 20111227 you need to remove 1741.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 1751.232Schristos bump has been reverted. 1761.232Schristos 1771.231Stls20111125: 1781.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 1791.231Stls means it should no longer be explicitly listed in kernel 1801.231Stls configuration files. The line "pseudo-device rnd" should be 1811.231Stls removed from any custom kernel config files users may have. 1821.231Stls 1831.230Stls20111119: 1841.230Stls A problem with the datastructures used by the rndctl(8) 1851.230Stls utility (pointers in datastructures in an array, making 32->64 1861.230Stls bit compatibility very painful) has been fixed in a 1871.230Stls non-backwards-compatible way. If you replace your kernel, 1881.230Stls replace your rndctl executable too. 1891.241Swiz 1901.229Sjym20111001: 1911.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 1921.229Sjym changed and their new version is not backward compatible with the old 1931.241Swiz one. So ensure that all consumers of these functions (currently: 1941.229Sjym quota2 code and its tests) are updated together with the new lib. 1951.229Sjym 1961.228Smrg20110817: 1971.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 1981.228Smrg DESTDIR for them should be deleted before updating. 1991.228Smrg 2001.227Sriastrad20110806: 2011.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 2021.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 2031.227Sriastrad 2041.226Smrg20110805: 2051.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 2061.226Smrg the tree to be cleaned. Best to delete both objdir and 2071.226Smrg DESTDIR before running this update. So far, only the 2081.226Smrg sparc64, mips and powerpc platforms have changed. 2091.226Smrg 2101.225Smatt20110803: 2111.241Swiz The layout of external/public-domain/xz has changed. To do an 2121.225Smatt update build you will have to remove the contents of the OBJDIR 2131.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 2141.225Smatt is now a directory. 2151.225Smatt 2161.223Sjoerg20110410: 2171.241Swiz The configuration of src/tools/gcc has changed. To do an 2181.224Sdholland update build you have to clean both tools/binutils and 2191.224Sdholland tools/gcc by hand. 2201.223Sjoerg 2211.222Splunky20110328: 2221.222Splunky Building the Xorg binary was moved into a subdirectory to fix 2231.241Swiz ordering issues with "make all". It may be necessary to remove 2241.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 2251.222Splunky if your update build fails, as the "Xorg" entry there is now a 2261.222Splunky directory. 2271.222Splunky 2281.220Sjoerg20110121: 2291.221Slukem Assembler files no longer use -traditional-cpp. This can break 2301.220Sjoerg the build of individual parts of the tree. This is handled 2311.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 2321.220Sjoerg and re-run config(1) for any kernel configurations as needed. 2331.218Sjoerg 2341.217Sjruoho20101217: 2351.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 2361.241Swiz by default. It may be necessary to manually update passwd(5) and 2371.217Sjruoho group(5) in order to make the program work with existing setups. 2381.217Sjruoho 2391.216Schristos20101125: 2401.216Schristos The latest changes to setenv(3) dissallow setting environment 2411.241Swiz variables with names that contain '='. Revision 1.18 of env.c 2421.241Swiz assumed that this was allowed. Installing a new libc with an 2431.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 2441.216Schristos break which affects the autoconf tests for dependency finding, 2451.216Schristos so building gcc will end up printing: 2461.216Schristos checking dependency style of gcc... none 2471.216Schristos configure: error: no usable dependency style found 2481.216Schristos Fix it by rebuilding and re-installing env. 2491.138Slukem 2501.215Smrg20101119: 2511.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 2521.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 2531.215Smrg have any build problems with xsrc, or problems with mismatched 2541.215Smrg versions between xorg-server and drivers. 2551.215Smrg 2561.213Sjmmv20100604: 2571.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 2581.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 2591.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 2601.213Sjmmv trees by hand. 2611.213Sjmmv 2621.211Stnozaki20100522: 2631.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 2641.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 2651.212Smrg build problems with xsrc. 2661.212Smrg 2671.212Smrg20100522: 2681.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 2691.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 2701.211Stnozaki 2711.210Schristos20100520: 2721.241Swiz The location of the xkb compiled descriptions has changed. Please 2731.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 2741.210Schristos 2751.209Snjoly20100222: 2761.209Snjoly The shared objects file extension has been changed from .so to 2771.209Snjoly .pico, in order to avoid conflicts with shared libraries names 2781.209Snjoly libXX.so. All now stale regular .so files can be removed from 2791.209Snjoly your object directories. 2801.209Snjoly 2811.208Sroy20100204: 2821.208Sroy The termcap database has been removed from the sources, 2831.208Sroy but has not been marked obsolete so it is not removed 2841.208Sroy from the system when upgrading. 2851.208Sroy As such, you will need to remove them from your object 2861.208Sroy and destination directories. 2871.208Sroy 2881.203Sdyoung20091101: 2891.205Sdholland After updating, it may be necessary to make the 'cleandir' 2901.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 2911.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 2921.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 2931.203Sdyoung 2941.202Smrg20091001: 2951.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 2961.206Sdholland before building a kernel, or the build fails on cpufunc.S. 2971.206Sdholland 2981.206Sdholland20091001: 2991.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 3001.202Smrg symlink, failing the build. Delete the link, and the subdir 3011.202Smrg it is in, and retry your build. 3021.202Smrg 3031.201Sdsl20090718: 3041.201Sdsl libc build changed so that strchr() provides the extra entry 3051.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 3061.201Sdsl may fail because the archive contains the unwanted index.o. 3071.201Sdsl (Similarly for strrchr() and rindex().) 3081.201Sdsl 3091.198Smrg20090709: 3101.198Smrg Native Xorg was upgraded again. Builds will probably fail again 3111.198Smrg without a clean objdir, at least for src/external/mit/xorg. 3121.198Smrg 3131.197Smrg20090616: 3141.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 3151.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 3161.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 3171.197Smrg subdirectory has been changed into a file, and this needs to 3181.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 3191.197Smrg 3201.195Sperry20090501: 3211.195Sperry Several new functions were added to string.h/libc, and this 3221.195Sperry can cause autoconf problems during the tool build for people 3231.241Swiz who fail to clean out their tools objects properly. If you 3241.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 3251.195Sperry failure during the tool build, clean out all your tools 3261.195Sperry objects and start again. 3271.195Sperry 3281.194Smrg20090325: 3291.194Smrg The i386 port was switched to i486 default toolchain. This requires 3301.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 3311.194Smrg 3321.192Sskrll20090126: 3331.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 3341.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 3351.207Smbalmer to avoid using the old assembly stub. 3361.192Sskrll 3371.191Sjoerg20090202: 3381.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 3391.191Sjoerg detection. It is recommented to rebuild the cache with 3401.191Sjoerg ``pkg_admin rebuild''. 3411.191Sjoerg 3421.184Schristos20090110: 3431.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 3441.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 3451.188Schristos This is needed even in the MODULAR kernel because there is 3461.188Schristos conditionally compiled code in rtsock.c. 3471.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 3481.184Schristos before installing. 3491.184Schristos 3. If you don't use build.sh and you build directly to root, and 3501.241Swiz your build breaks in the middle, don't despair. Make sure headers 3511.184Schristos are installed properly, and start building libraries first libc 3521.184Schristos and libutil, install them and then continue building all the 3531.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 3541.184Schristos the new libraries are installed, you can restart the build. 3551.184Schristos 4. If you compile packages and you notice link time warnings, 3561.189Shubertf rebuild the required packages to update their shared libraries. 3571.189Shubertf Any package you rebuild will require rebuilding all the packages 3581.189Shubertf that depend on it. 3591.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 3601.186Schristos will be upgraded and it will not be backwards compatible. 3611.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 3621.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 3631.241Swiz for utmp. You are better off removing the old files after 3641.190Sapb upgrading. The automated clearing of /var/run during 3651.190Sapb boot, and the automated rotating of files in /var/log by 3661.190Sapb newsyslog(8), may mean that you do not have to remove the 3671.190Sapb files manually. 3681.190Sapb 7. The optional accounting file (/var/account/acct, see 3691.190Sapb accton(8)) has not been versioned, and will need to be 3701.190Sapb removed. The automatic rotation of the accounting file by 3711.190Sapb /etc/daily limits the bad consequences of failure to remove 3721.190Sapb the file. 3731.196Sdholland 8. Application software that writes time_t to binary files on 3741.241Swiz disk will break or need attention. Most notably: if you are 3751.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 3761.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 3771.185Sjmcneill 3781.183Spgoyette20081219: 3791.183Spgoyette config(1) has been updated, and one of the files it creates - 3801.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 3811.183Spgoyette (done automatically by build.sh) and then you need to rerun 3821.183Spgoyette config on all kernel configuration files before rebuilding those 3831.183Spgoyette kernels. 3841.183Spgoyette 3851.181Scube20081205: 3861.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 3871.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 3881.181Scube set and will appear as extra files for MKX11=no update builds. 3891.178Slukem 3901.179Stsutsui20081122: 3911.182Stsutsui On i386, various kernel options(4) in GENERIC including 3921.180Swiz file systems have been disabled and moved into kernel modules. 3931.180Swiz Before trying a new GENERIC kernel, you have to prepare the 3941.179Stsutsui following files as well as a new GENERIC kernel: 3951.179Stsutsui 3961.179Stsutsui - build and install kernel modules from src/sys/modules 3971.179Stsutsui 3981.179Stsutsui - install the latest bootloader, which will load a module 3991.180Swiz for the file system from which the kernel is loaded automatically 4001.179Stsutsui 4011.180Swiz If you have to load your kernel from a file system which is not of 4021.180Swiz the same type as the root file system, you have to load the necessary 4031.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 4041.179Stsutsui 4051.178Slukem20080827: 4061.178Slukem If you built and installed a libc from sources between 4071.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 4081.178Slukem which results in false errors reported by lint(1). 4091.178Slukem Since this breaks the libc build itself, manual help is 4101.180Swiz needed -- lint must be disabled temporarily, e.g.: 4111.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 4121.178Slukem 4131.177Schristos20080813: 4141.177Schristos MKDEBUG build was broken because the .depend files did not know 4151.241Swiz about .go files. You need to remove all .depend files and rebuild. 4161.177Schristos 4171.200Sdholland20080802: 4181.200Sdholland A regression in binary compatibility for pthread_mutex_t has 4191.241Swiz been fixed. Unfortunately, the price is breaking compatibility 4201.200Sdholland for -current. 4211.200Sdholland 4221.200Sdholland Threaded programs (using libpthread) and C++ programs (using 4231.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 4241.200Sdholland be recompiled. 4251.200Sdholland 4261.200Sdholland One way to find affected pkgsrc packages: 4271.200Sdholland 4281.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 4291.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 4301.200Sdholland 4311.175Ssimonb20080731: 4321.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 4331.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 4341.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 4351.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 4361.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 4371.176Ssimonb also requires the super block to be in the UFS2 format. You 4381.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 4391.175Ssimonb 4401.174Slukem20080721: 4411.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 4421.174Slukem isn't defined. 4431.174Slukem 4441.173Sfreza20080531: 4451.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 4461.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 4471.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 4481.241Swiz won't work correctly. The following sequence of commands: 4491.173Sfreza 4501.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 4511.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 4521.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 4531.173Sfreza 4541.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 4551.173Sfreza 4561.172Slukem20080503: 4571.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 4581.172Slukem 4591.171She20080521: 4601.171She For a while, unprivileged UPDATE builds would fail to 4611.171She succeed at the checkflist stage, complaining that 4621.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 4631.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 4641.171She If you already hit this problem, update the .mk file, 4651.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 4661.171She 4671.174Slukem20080303: 4681.174Slukem Linker warnings are now fatal if $WARNS>0. 4691.174Slukem 4701.170Schristos20080126: 4711.170Schristos The posix_fadvise system call has been changed from an assembly 4721.241Swiz stub, to a c file that calls an assembly stub. You need to 4731.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 4741.170Schristos avoid using the old assembly stub. 4751.170Schristos 4761.168Sjoerg20071209: 4771.241Swiz The acpiec(4) driver has been split into two attachments. If you 4781.168Sjoerg get ACPI errors before the attachment, please update your kernel 4791.169Swiz configuration file appropriately or see GENERIC for more details. 4801.168Sjoerg 4811.166Sxtraeme20071115: 4821.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 4831.166Sxtraeme argument specified in the kernel configuration file is not valid 4841.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 4851.241Swiz rather than the EC address port. Please update your kernel 4861.167Swiz configuration file appropriately or see GENERIC for more details. 4871.166Sxtraeme 4881.165Sjmmv20071028: 4891.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 4901.165Sjmmv You need to update any custom kernel configuration file you have 4911.165Sjmmv to remove any references to pccons (which includes removing the 4921.165Sjmmv now useless XSERVER option) and replace them with the correct 4931.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 4941.165Sjmmv for more details. 4951.165Sjmmv 4961.164Sgdt20070913: 4971.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 4981.164Sgdt enumerate interfaces was fixed. The bug began to cause 4991.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 5001.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 5011.164Sgdt could not enumerate interfaces. (These are noted because 5021.164Sgdt normal kernel/userspace version matching hygiene is not 5031.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 5041.164Sgdt and userland are from after 20070913. 5051.164Sgdt 5061.163Sjoerg20070703: 5071.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 5081.199Sdholland calls the target-specific strip program, and the logic to pass 5091.199Sdholland down STRIP from make has been removed. This requires a 5101.199Sdholland re-installation of tools. 5111.163Sjoerg 5121.161Sdsl20070422: 5131.161Sdsl The way OS emulations lookup filenames inside the emulation root 5141.161Sdsl has been changed. Rather than modify the pathname (and copy back 5151.161Sdsl to userspace) namei() and lookup() directly check the emulation 5161.241Swiz root. One side effect is that absolute symlinks inside the emulated 5171.167Swiz root file system will be relative to that file system - unless they 5181.161Sdsl start /../ this is useful when the emulated root is a real install 5191.161Sdsl that has such links. 5201.161Sdsl This might affect symlinks that have been added to reference outside 5211.161Sdsl the emulated root. 5221.161Sdsl 5231.160Sjmcneill20070412: 5241.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 5251.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 5261.160Sjmcneill example. 5271.160Sjmcneill 5281.159Sgdt20070319: 5291.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 5301.159Sgdt on many platforms due to incorrect flags settings. If you 5311.159Sgdt updated and built after about 20070315, do "nbmake-$arch 5321.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 5331.159Sgdt rebuild of object files that might have been built 5341.159Sgdt incorrectly, and ensure that you have at least 5351.159Sgdt src/lib/libc/Makefile 1.130. 5361.159Sgdt 5371.241Swiz20070210: 5381.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 5391.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 5401.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 5411.158Sdbj will allow dependencies on those files to get get rebuilt 5421.158Sdbj 5431.157Sapb20070209: 5441.157Sapb The threading model was changed when the newlock2 branch 5451.157Sapb was merged to NetBSD-current. If you boot with a new 5461.157Sapb kernel (version 4.99.10), then you also need a new pthread 5471.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 5481.157Sapb an old kernel, then you need the old pthread library 5491.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 5501.157Sapb the pthread library in sync, old threaded applications should 5511.157Sapb continue to work with an old or new kernel. Note that named(8) 5521.157Sapb is the only threaded application in the base system. 5531.157Sapb 5541.154She20061214: 5551.154She Following the move of string_to_flags() and flags_to_string() 5561.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 5571.154She will need to do a "make cleandir" in 5581.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 5591.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 5601.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 5611.156She as the installation images in distrib/ 5621.154She in order to excise stale references to the old stat_flags.h header 5631.154She file in the ls sources -- stat_flags.h has been removed. 5641.154She 5651.152Schristos20061108: 5661.152Schristos The configure script used in the src/tools/gcc compiler has been 5671.152Schristos changed to indicate that our libc has ssp support built-in and 5681.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 5691.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 5701.152Schristos 5711.151Srpaulo20061009: 5721.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 5731.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 5741.151Srpaulo 5751.150Sbjh2120060814: 5761.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 5771.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 5781.150Sbjh21 kernel configuration for an example. X servers from the last 5791.150Sbjh21 few years should cope. 5801.150Sbjh21 5811.149Schristos20060703: 5821.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 5831.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 5841.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 5851.149Schristos 5861.148Sdogcow20060627: 5871.148Sdogcow socket(2) has changed, and its system call has been versioned. 5881.148Sdogcow For userlands with the old version of socket(2), make sure that 5891.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 5901.148Sdogcow errors will result. 5911.148Sdogcow 5921.1SabsHints for a more successful build: 5931.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5941.123Sjmc Use build.sh, but do not use its "expert mode": 5951.132Sjmmv This will automatically build the tools in the 5961.123Sjmc correct order, and it will keep the tools and the 5971.123Sjmc new build products from interfering with the running 5981.123Sjmc system. This will allow you to ignore most of the 5991.123Sjmc other advice in this file. 6001.2Smrg Build a new kernel first: 6011.2Smrg This makes sure that any new system calls or features 6021.2Smrg expected by the new userland will be present. This 6031.2Smrg helps to avoid critical errors when upgrading. 6041.1Sabs Use object directories: 6051.1Sabs This helps to keep stale object 6061.1Sabs files from polluting the build if a Makefile "forgets" 6071.1Sabs about one. It also makes it easier to clean up after 6081.1Sabs a build. It's also necessary if you want to use the 6091.1Sabs same source tree for multiple machines. 6101.123Sjmc To use object directories with build.sh: 6111.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 6121.123Sjmc To use object directories without using build.sh: 6131.1Sabs a) cd /usr/src ; make cleandir 6141.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 6151.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 6161.1Sabs d) cd /usr/src ; make build 6171.2Smrg Note that running "make obj" in a directory will create 6181.2Smrg in obj.$MACHINE directory. 6191.1Sabs Build to a DESTDIR: 6201.123Sjmc This helps to keep old installed files (especially libraries) 6211.123Sjmc from interfering with the new build. 6221.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 6231.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 6241.123Sjmc environment variable before running make build. It should be 6251.123Sjmc set to the pathname of an initially empty directory. 6261.123Sjmc Problems: if you do not use build.sh, you might need to 6271.123Sjmc update critical utilities without using DESTDIR since 6281.123Sjmc nothing is executed from what is installed in DESTDIR. 6291.123Sjmc (See critical utils, below.) 6301.1Sabs Build often: 6311.1Sabs This keeps critical utilities current enough to not choke 6321.1Sabs on any other part of the source tree that depends on up to 6331.123Sjmc date functionality. If you use build.sh, you should not have 6341.123Sjmc this problem. 6351.241Swiz 6361.1SabsWhat to do if things don't work: 6371.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6381.230StlsWhen things don't work there are usually a few things that commonly 6391.1Sabsshould be done. 6401.1Sabs 1) make includes 6411.1Sabs This should be done automatically by make build. 6421.1Sabs 2) cd share/mk && make install 6431.1Sabs Again, automatically done by make build. 6441.1Sabs 6451.1SabsFailsafe rebuild of a small part of the tree: 6461.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6471.1SabsTo make sure you rebuild something correctly you want to do 6481.1Sabssomething like the following: 6491.1Sabs 1) Make sure the includes and .mk files are up to date. 6501.1Sabs 2) Make sure any program used to build the particular 6511.1Sabs utility is up to date. (yacc, lex, etc...) 6521.1Sabs 3) cd ...path/to/util... 6531.1Sabs make cleandir 6541.1Sabs rm ...all obj directories... 6551.1Sabs make cleandir # yes, again 6561.1Sabs make obj 6571.1Sabs make depend && make 6581.1Sabs 6591.1SabsFailsafe rebuild of the entire tree: 6601.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6611.1SabsIf you really want to make sure the source tree is clean and 6621.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 6631.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 6641.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 6651.1Sabs 6661.1Sabs---cut here--- 6671.1Sabs#!/bin/sh 6681.1Sabs. /etc/mk.conf 6691.1Sabs 6701.58Slukemif [ -z $NETBSDSRCDIR ] ; then 6711.58Slukem NETBSDSRCDIR=/usr/src 6721.1Sabsfi 6731.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 6741.1Sabs echo Unable to find sources 6751.1Sabs exit 1 6761.1Sabsfi 6771.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 6781.1Sabs 6791.1Sabsif [ -z $BSDOBJDIR ] ; then 6801.1Sabs BSDOBJDIR=/usr/obj 6811.1Sabsfi 6821.1Sabsif [ -d $BSDOBJDIR ] ; then 6831.1Sabs rm -rf $BSDOBJDIR 6841.1Sabsfi 6851.1Sabs 6861.58Slukemcd $NETBSDSRCDIR && make cleandir 6871.1Sabs 6881.1Sabs---cut here--- 6891.1Sabs 6901.1SabsCritical utilities: 6911.1Sabs^^^^^^^^^^^^^^^^^^^ 6921.3Sitojun usr.bin/compile_et 6931.1Sabs usr.bin/make 6941.1Sabs usr.bin/yacc 6951.1Sabs usr.bin/lex 6961.11Slukem usr.bin/xlint 6971.142Sdrochner usr.bin/config 6981.1Sabs 6991.34SsimonbOther problems and possible solutions: 7001.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7011.1SabsSymptom:Complaints involving a Makefile. 7021.17SerhFix: Rebuild usr.bin/make: 7031.17Serh cd usr.bin/make && make && make install 7041.111Ssimonb Or, a failsafe method if that doesn't work: 7051.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 7061.17Serh 7071.1SabsFix: Make sure .mk files are up to date. 7081.1Sabs cd share/mk && make install 7091.2Smrg 7101.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 7111.142SdrochnerFix: Rebuild usr.bin/config 7121.1Sabs 7131.1SabsSymptom: 7141.1SabsFix: Rebuild usr.bin/yacc 7151.1Sabs 7161.1SabsSymptom: 7171.1SabsFix: Rebuild usr.bin/lex 7181.1Sabs 7191.1SabsSymptom: 7201.1SabsFix: rm /usr/lib/libbfd.a 7211.4Sitojun 7221.4SitojunSymptom:Obsolete intermediate files are used during compilation 7231.4SitojunFix: Try the following sequence of commands in the directory in question. 7241.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 7251.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 7261.4Sitojun may remain. The command tries to clean everything up) 7271.5Swiz 7281.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 7291.207Smbalmer pointer type 7301.5SwizFix: Rebuild and install usr.bin/menuc 7311.12Sitojun 7321.12SitojunSymptom:mklocale not found during build in share/locale/ctype 7331.12SitojunFix: Build and install usr.bin/mklocale 7341.13Sdogcow 7351.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 7361.13SdogcowFix: Rebuild and install lib/libc 7371.13Sdogcow 7381.142SdrochnerSymptom:usr.bin/config fails to build. 7391.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 7401.13Sdogcow 7411.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 7421.19ScgdFix: Rebuild and install lib/libc 7431.24Sabs 7441.24SabsSymptom:lint does not understand the '-X' option 7451.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 7461.223Sjoerg 7471.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 7481.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 7491.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 7501.257Sapb 7511.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 7521.257Sapb No such file or directory. 7531.257SapbCause: If a directory is created by mistake, then it is sometimes 7541.257Sapb deleted from the CVS repository using administrative commands 7551.257Sapb that bypass the normal cvs access controls. If your cvs working tree 7561.257Sapb contains references to a directory that has been deleted on the 7571.257Sapb server in this way, then "cvs update" reports this error. 7581.257SapbFix: Recursively delete the affected directory from your working tree 7591.257Sapb and try the update again. 760