UPDATING revision 1.286
11.286Smrg$NetBSD: UPDATING,v 1.286 2017/08/22 10:04:44 mrg 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.286Smrg20170822: 231.286Smrg a new version of GMP has been imported and probably 241.286Smrg will break parts of builds related to themselves or GCC, both 251.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 261.286Smrg and MPC objdirs or build once without -u. 271.286Smrg 281.285Smrg20170816: 291.285Smrg a new version of MPFR and MPC have been imported and probably 301.285Smrg will break parts of builds related to themselves or GCC, both 311.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 321.285Smrg and MPC objdirs or build once without -u. 331.285Smrg 341.284Smartin20170402: 351.284Smartin a new version of dhcpcd has been imported, which does not support 361.284Smartin update builds from the previous version. Remove your 371.284Smartin external/bsd/dhcpcd object dir or build once without -u. 381.284Smartin 391.281Sroy20170211: 401.281Sroy a new terminfo database has been imported. 411.281Sroy The structure of it has changed slightly from prior versions and 421.281Sroy an updated tic tool is required. 431.281Sroy If you build.sh, don't use -u 441.281Sroy 451.280Skre20170207: 461.278Skre various arch dependent libc/exect.S files were removed 471.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 481.279Skre if it exists) or do a clean build. 491.279Skre (This is a bug in the make system, it should be corrected without 501.279Skre human intervention, but isn't.) 511.278Skre 521.277Smartin20170104: 531.277Smartin xinput build options have changed. 541.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 551.277Smartin if you build.sh -u 561.277Smartin 571.276Smartin20170103: 581.276Smartin a new version of flex has been imported. 591.276Smartin Remove the file from obj (external/bsd/flex) 601.276Smartin if you build.sh -u 611.276Smartin 621.275Sspz20161014: 631.275Sspz a new version of OpenSSL has been imported. 641.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 651.275Sspz if you build.sh -u 661.275Sspz 671.274Smartin20161009: 681.274Smartin a new version of dhcpcd has been imported with slightly changed 691.274Smartin build infrastructure. When doing a build.sh -u this requires 701.274Smartin pruning the external/bsd/dhcpcd objdir. 711.274Smartin 721.273Smrg20160914: 731.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 741.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 751.273Smrg and a clean objdir. 761.273Smrg 771.272Sdholland20160527: 781.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 791.272Sdholland been enabled. (see the amd64 entry two down for further info) 801.272Sdholland 811.270Schristos20160418: 821.270Schristos libedit needs manual removal of all autogenerated files since 831.271Schristos some of them are not autogenerated anymore. Remember that there 841.271Schristos might be two copies of libedit if your platform builds "compat". 851.270Schristos 861.268Sriastrad20160410: 871.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 881.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 891.268Sriastrad executables, means all code, including executables and not just 901.268Sriastrad shared libraries, is position-independent and hence able to be 911.268Sriastrad relocated by ASLR, address space layout randomization. 921.268Sriastrad 931.268Sriastrad The change was made in Makefile variables for compiler and 941.268Sriastrad linker flags, for which make(1) does not record dependencies, 951.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 961.268Sriastrad 971.268Sriastrad Partial rebuilds with some modified source files will likely 981.268Sriastrad fail when linking executables, since the linker refuses to mix 991.268Sriastrad position-independent code with position-dependent code in 1001.268Sriastrad position-independent executables: 1011.268Sriastrad 1021.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 1031.268Sriastrad 1041.267Smrg20160401: 1051.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 1061.269Sdholland Some people have found that cleandir is not sufficient, so if 1071.269Sdholland in doubt delete the entire object directory tree for gcc. 1081.267Smrg 1091.266Saymeric20160306: 1101.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 1111.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 1121.265Saymeric non-NetBSD hosts if linked with stale object files produced 1131.265Saymeric while they included a non-NetBSD regex.h. 1141.265Saymeric In any case, you should "make cleandir" at least these tools 1151.265Saymeric before updating your toolchain. 1161.265Saymeric 1171.264Smartin20160125: 1181.264Smartin Dtrace has been enabled by default on some architectures. 1191.264Smartin When doing an update build, make sure to clean the etc/mtree 1201.264Smartin object directory before starting the build - otherwise the 1211.264Smartin needed directories in destdir will not be created. 1221.264Smartin An easy way to do this is: 1231.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 1241.264Smartin 1251.263Sdholland20150818: 1261.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 1271.263Sdholland again. 1281.263Sdholland 1291.262Schristos20150413: 1301.262Schristos New acpica requires "make cleandir" and reinstalling yacc 1311.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 1321.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 1331.262Schristos 1341.261Smartin20150404: 1351.261Smartin Lint changes require a full rebuild of the tool, so make 1361.261Smartin sure to build without -u option to build.sh, or manually 1371.261Smartin do a make cleandir in src/tools/lint1 and 1381.261Smartin src/usr.bin/xlint. 1391.261Smartin 1401.260Sskrll20150310: 1411.260Sskrll Improvements to openssl for arm mean that update builds of 1421.260Sskrll the openssl libraries will fail. A make cleandir in 1431.260Sskrll external/bsd/openssl/lib is needed 1441.260Sskrll 1451.258Smartin20141026: 1461.259Smsaitoh A mishap during the import of pppd may cause your corruption 1471.258Smartin in your cvs directory if you happened to do a cvs update 1481.258Smartin during a short period of time. To fix, just remove the 1491.258Smartin directory src/external/bsd/ppp/dist/pppd completely 1501.258Smartin and let cvs restore it on next update. 1511.258Smartin 1521.256Sapb20140721: 1531.256Sapb The src/external/mit/lua/src directory was accidentally created 1541.256Sapb and then deleted in the CVS repository. If you get errors like 1551.256Sapb 1561.256Sapb cvs [update aborted]: cannot open directory 1571.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 1581.256Sapb 1591.256Sapb then delete your local copy of that directory tree and try again. 1601.256Sapb 1611.255Sjoerg20140530: 1621.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 1631.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 1641.255Sjoerg 1651.251Smartin20140131: 1661.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 1671.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 1681.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 1691.251Smartin 1701.250Schristos20131227: 1711.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 1721.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 1731.250Schristos mode7 in your config file. Make sure you put the necessary restrict 1741.250Schristos statements to avoid being exposed. 1751.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 1761.250Schristos to make clean in libc 1771.250Schristos 1781.249Smrg20131129: 1791.249Smrg The GMP sources were updated, and builds will likely fail without 1801.249Smrg cleaning their build trees for both tools and in-tree, like below. 1811.249Smrg 1821.248Smrg20131128: 1831.248Smrg The MPC and MPFR sources were updated, and builds may require their 1841.248Smrg tools and in-tree directories cleaned for successful updates. 1851.248Smrg 1861.246Smartin20130605: 1871.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 1881.247Sspz to IPSEC (and the older IPSEC version removed). 1891.247Sspz 1901.247Sspz20130605: 1911.246Smartin Previous freetype installations eroneously installed private 1921.246Smartin header files. If you are building against a non-empty $DESTDIR, 1931.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 1941.246Smartin 1951.245Smrg20130531: 1961.245Smrg The xdm update may cause build failure due to xdm.man being 1971.245Smrg in the obj tree. Make sure to ensure any like this: 1981.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 1991.245Smrg is fixed by deleting the xdm.man in the obj tree. 2001.245Smrg 2011.244Smrg20130530: 2021.244Smrg Updates of many xsrc packages will leave old .pc files around. 2031.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 2041.244Smrg 2051.242Schristos20130301: 2061.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 2071.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 2081.242Schristos 2091.238Sdholland20120726: 2101.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 2111.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 2121.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 2131.241Swiz some cases may succeed and install broken OpenSSL libraries that 2141.240Sdholland cause third-party software to link incorrectly and/or crash. 2151.238Sdholland 2161.237Swiz20120507: 2171.241Swiz The database schema for makemandb was changed. You will 2181.237Swiz need to update the database using 'makemandb -f' or wait 2191.237Swiz for the next weekly run to fix it. 2201.237Swiz 2211.236Sbsh20120319: 2221.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 2231.236Sbsh size of db_symtab automatically. You need to update dbsym in 2241.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 2251.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 2261.236Sbsh mk.conf. 2271.236Sbsh 2281.235Sjoerg20120216: 2291.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 2301.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 2311.239Sdholland and 20120216, daily and weekly could have created an unreadable 2321.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 2331.235Sjoerg the next run of weekly will fix it. 2341.233Sjoerg 2351.232Schristos20111227: 2361.232Schristos If you built between 20111225 and 20111227 you need to remove 2371.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 2381.232Schristos bump has been reverted. 2391.232Schristos 2401.231Stls20111125: 2411.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 2421.231Stls means it should no longer be explicitly listed in kernel 2431.231Stls configuration files. The line "pseudo-device rnd" should be 2441.231Stls removed from any custom kernel config files users may have. 2451.231Stls 2461.230Stls20111119: 2471.230Stls A problem with the datastructures used by the rndctl(8) 2481.230Stls utility (pointers in datastructures in an array, making 32->64 2491.230Stls bit compatibility very painful) has been fixed in a 2501.230Stls non-backwards-compatible way. If you replace your kernel, 2511.230Stls replace your rndctl executable too. 2521.241Swiz 2531.229Sjym20111001: 2541.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 2551.229Sjym changed and their new version is not backward compatible with the old 2561.241Swiz one. So ensure that all consumers of these functions (currently: 2571.229Sjym quota2 code and its tests) are updated together with the new lib. 2581.229Sjym 2591.228Smrg20110817: 2601.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 2611.228Smrg DESTDIR for them should be deleted before updating. 2621.228Smrg 2631.227Sriastrad20110806: 2641.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 2651.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 2661.227Sriastrad 2671.226Smrg20110805: 2681.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 2691.226Smrg the tree to be cleaned. Best to delete both objdir and 2701.226Smrg DESTDIR before running this update. So far, only the 2711.226Smrg sparc64, mips and powerpc platforms have changed. 2721.226Smrg 2731.225Smatt20110803: 2741.241Swiz The layout of external/public-domain/xz has changed. To do an 2751.225Smatt update build you will have to remove the contents of the OBJDIR 2761.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 2771.225Smatt is now a directory. 2781.225Smatt 2791.223Sjoerg20110410: 2801.241Swiz The configuration of src/tools/gcc has changed. To do an 2811.224Sdholland update build you have to clean both tools/binutils and 2821.224Sdholland tools/gcc by hand. 2831.223Sjoerg 2841.222Splunky20110328: 2851.222Splunky Building the Xorg binary was moved into a subdirectory to fix 2861.241Swiz ordering issues with "make all". It may be necessary to remove 2871.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 2881.222Splunky if your update build fails, as the "Xorg" entry there is now a 2891.222Splunky directory. 2901.222Splunky 2911.220Sjoerg20110121: 2921.221Slukem Assembler files no longer use -traditional-cpp. This can break 2931.220Sjoerg the build of individual parts of the tree. This is handled 2941.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 2951.220Sjoerg and re-run config(1) for any kernel configurations as needed. 2961.218Sjoerg 2971.217Sjruoho20101217: 2981.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 2991.241Swiz by default. It may be necessary to manually update passwd(5) and 3001.217Sjruoho group(5) in order to make the program work with existing setups. 3011.217Sjruoho 3021.216Schristos20101125: 3031.216Schristos The latest changes to setenv(3) dissallow setting environment 3041.241Swiz variables with names that contain '='. Revision 1.18 of env.c 3051.241Swiz assumed that this was allowed. Installing a new libc with an 3061.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 3071.216Schristos break which affects the autoconf tests for dependency finding, 3081.216Schristos so building gcc will end up printing: 3091.216Schristos checking dependency style of gcc... none 3101.216Schristos configure: error: no usable dependency style found 3111.216Schristos Fix it by rebuilding and re-installing env. 3121.138Slukem 3131.215Smrg20101119: 3141.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 3151.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 3161.215Smrg have any build problems with xsrc, or problems with mismatched 3171.215Smrg versions between xorg-server and drivers. 3181.215Smrg 3191.213Sjmmv20100604: 3201.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 3211.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 3221.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 3231.213Sjmmv trees by hand. 3241.213Sjmmv 3251.211Stnozaki20100522: 3261.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 3271.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 3281.212Smrg build problems with xsrc. 3291.212Smrg 3301.212Smrg20100522: 3311.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 3321.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 3331.211Stnozaki 3341.210Schristos20100520: 3351.241Swiz The location of the xkb compiled descriptions has changed. Please 3361.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 3371.210Schristos 3381.209Snjoly20100222: 3391.209Snjoly The shared objects file extension has been changed from .so to 3401.209Snjoly .pico, in order to avoid conflicts with shared libraries names 3411.209Snjoly libXX.so. All now stale regular .so files can be removed from 3421.209Snjoly your object directories. 3431.209Snjoly 3441.208Sroy20100204: 3451.208Sroy The termcap database has been removed from the sources, 3461.208Sroy but has not been marked obsolete so it is not removed 3471.208Sroy from the system when upgrading. 3481.208Sroy As such, you will need to remove them from your object 3491.208Sroy and destination directories. 3501.208Sroy 3511.203Sdyoung20091101: 3521.205Sdholland After updating, it may be necessary to make the 'cleandir' 3531.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 3541.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 3551.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 3561.203Sdyoung 3571.202Smrg20091001: 3581.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 3591.206Sdholland before building a kernel, or the build fails on cpufunc.S. 3601.206Sdholland 3611.206Sdholland20091001: 3621.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 3631.202Smrg symlink, failing the build. Delete the link, and the subdir 3641.202Smrg it is in, and retry your build. 3651.202Smrg 3661.201Sdsl20090718: 3671.201Sdsl libc build changed so that strchr() provides the extra entry 3681.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 3691.201Sdsl may fail because the archive contains the unwanted index.o. 3701.201Sdsl (Similarly for strrchr() and rindex().) 3711.201Sdsl 3721.198Smrg20090709: 3731.198Smrg Native Xorg was upgraded again. Builds will probably fail again 3741.198Smrg without a clean objdir, at least for src/external/mit/xorg. 3751.198Smrg 3761.197Smrg20090616: 3771.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 3781.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 3791.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 3801.197Smrg subdirectory has been changed into a file, and this needs to 3811.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 3821.197Smrg 3831.195Sperry20090501: 3841.195Sperry Several new functions were added to string.h/libc, and this 3851.195Sperry can cause autoconf problems during the tool build for people 3861.241Swiz who fail to clean out their tools objects properly. If you 3871.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 3881.195Sperry failure during the tool build, clean out all your tools 3891.195Sperry objects and start again. 3901.195Sperry 3911.194Smrg20090325: 3921.194Smrg The i386 port was switched to i486 default toolchain. This requires 3931.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 3941.194Smrg 3951.192Sskrll20090126: 3961.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 3971.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 3981.207Smbalmer to avoid using the old assembly stub. 3991.192Sskrll 4001.191Sjoerg20090202: 4011.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 4021.191Sjoerg detection. It is recommented to rebuild the cache with 4031.191Sjoerg ``pkg_admin rebuild''. 4041.191Sjoerg 4051.184Schristos20090110: 4061.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 4071.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 4081.188Schristos This is needed even in the MODULAR kernel because there is 4091.188Schristos conditionally compiled code in rtsock.c. 4101.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 4111.184Schristos before installing. 4121.184Schristos 3. If you don't use build.sh and you build directly to root, and 4131.241Swiz your build breaks in the middle, don't despair. Make sure headers 4141.184Schristos are installed properly, and start building libraries first libc 4151.184Schristos and libutil, install them and then continue building all the 4161.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 4171.184Schristos the new libraries are installed, you can restart the build. 4181.184Schristos 4. If you compile packages and you notice link time warnings, 4191.189Shubertf rebuild the required packages to update their shared libraries. 4201.189Shubertf Any package you rebuild will require rebuilding all the packages 4211.189Shubertf that depend on it. 4221.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 4231.186Schristos will be upgraded and it will not be backwards compatible. 4241.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 4251.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 4261.241Swiz for utmp. You are better off removing the old files after 4271.190Sapb upgrading. The automated clearing of /var/run during 4281.190Sapb boot, and the automated rotating of files in /var/log by 4291.190Sapb newsyslog(8), may mean that you do not have to remove the 4301.190Sapb files manually. 4311.190Sapb 7. The optional accounting file (/var/account/acct, see 4321.190Sapb accton(8)) has not been versioned, and will need to be 4331.190Sapb removed. The automatic rotation of the accounting file by 4341.190Sapb /etc/daily limits the bad consequences of failure to remove 4351.190Sapb the file. 4361.196Sdholland 8. Application software that writes time_t to binary files on 4371.241Swiz disk will break or need attention. Most notably: if you are 4381.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 4391.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 4401.185Sjmcneill 4411.183Spgoyette20081219: 4421.183Spgoyette config(1) has been updated, and one of the files it creates - 4431.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 4441.183Spgoyette (done automatically by build.sh) and then you need to rerun 4451.183Spgoyette config on all kernel configuration files before rebuilding those 4461.183Spgoyette kernels. 4471.183Spgoyette 4481.181Scube20081205: 4491.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 4501.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 4511.181Scube set and will appear as extra files for MKX11=no update builds. 4521.178Slukem 4531.179Stsutsui20081122: 4541.182Stsutsui On i386, various kernel options(4) in GENERIC including 4551.180Swiz file systems have been disabled and moved into kernel modules. 4561.180Swiz Before trying a new GENERIC kernel, you have to prepare the 4571.179Stsutsui following files as well as a new GENERIC kernel: 4581.179Stsutsui 4591.179Stsutsui - build and install kernel modules from src/sys/modules 4601.179Stsutsui 4611.179Stsutsui - install the latest bootloader, which will load a module 4621.180Swiz for the file system from which the kernel is loaded automatically 4631.179Stsutsui 4641.180Swiz If you have to load your kernel from a file system which is not of 4651.180Swiz the same type as the root file system, you have to load the necessary 4661.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 4671.179Stsutsui 4681.178Slukem20080827: 4691.178Slukem If you built and installed a libc from sources between 4701.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 4711.178Slukem which results in false errors reported by lint(1). 4721.178Slukem Since this breaks the libc build itself, manual help is 4731.180Swiz needed -- lint must be disabled temporarily, e.g.: 4741.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 4751.178Slukem 4761.177Schristos20080813: 4771.177Schristos MKDEBUG build was broken because the .depend files did not know 4781.241Swiz about .go files. You need to remove all .depend files and rebuild. 4791.177Schristos 4801.200Sdholland20080802: 4811.200Sdholland A regression in binary compatibility for pthread_mutex_t has 4821.241Swiz been fixed. Unfortunately, the price is breaking compatibility 4831.200Sdholland for -current. 4841.200Sdholland 4851.200Sdholland Threaded programs (using libpthread) and C++ programs (using 4861.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 4871.200Sdholland be recompiled. 4881.200Sdholland 4891.200Sdholland One way to find affected pkgsrc packages: 4901.200Sdholland 4911.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 4921.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 4931.200Sdholland 4941.175Ssimonb20080731: 4951.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 4961.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 4971.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 4981.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 4991.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 5001.176Ssimonb also requires the super block to be in the UFS2 format. You 5011.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 5021.175Ssimonb 5031.174Slukem20080721: 5041.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 5051.174Slukem isn't defined. 5061.174Slukem 5071.173Sfreza20080531: 5081.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 5091.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 5101.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 5111.241Swiz won't work correctly. The following sequence of commands: 5121.173Sfreza 5131.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 5141.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 5151.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 5161.173Sfreza 5171.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 5181.173Sfreza 5191.172Slukem20080503: 5201.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 5211.172Slukem 5221.171She20080521: 5231.171She For a while, unprivileged UPDATE builds would fail to 5241.171She succeed at the checkflist stage, complaining that 5251.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 5261.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 5271.171She If you already hit this problem, update the .mk file, 5281.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 5291.171She 5301.174Slukem20080303: 5311.174Slukem Linker warnings are now fatal if $WARNS>0. 5321.174Slukem 5331.170Schristos20080126: 5341.170Schristos The posix_fadvise system call has been changed from an assembly 5351.241Swiz stub, to a c file that calls an assembly stub. You need to 5361.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 5371.170Schristos avoid using the old assembly stub. 5381.170Schristos 5391.168Sjoerg20071209: 5401.241Swiz The acpiec(4) driver has been split into two attachments. If you 5411.168Sjoerg get ACPI errors before the attachment, please update your kernel 5421.169Swiz configuration file appropriately or see GENERIC for more details. 5431.168Sjoerg 5441.166Sxtraeme20071115: 5451.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 5461.166Sxtraeme argument specified in the kernel configuration file is not valid 5471.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 5481.241Swiz rather than the EC address port. Please update your kernel 5491.167Swiz configuration file appropriately or see GENERIC for more details. 5501.166Sxtraeme 5511.165Sjmmv20071028: 5521.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 5531.165Sjmmv You need to update any custom kernel configuration file you have 5541.165Sjmmv to remove any references to pccons (which includes removing the 5551.165Sjmmv now useless XSERVER option) and replace them with the correct 5561.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 5571.165Sjmmv for more details. 5581.165Sjmmv 5591.164Sgdt20070913: 5601.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 5611.164Sgdt enumerate interfaces was fixed. The bug began to cause 5621.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 5631.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 5641.164Sgdt could not enumerate interfaces. (These are noted because 5651.164Sgdt normal kernel/userspace version matching hygiene is not 5661.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 5671.164Sgdt and userland are from after 20070913. 5681.164Sgdt 5691.163Sjoerg20070703: 5701.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 5711.199Sdholland calls the target-specific strip program, and the logic to pass 5721.199Sdholland down STRIP from make has been removed. This requires a 5731.199Sdholland re-installation of tools. 5741.163Sjoerg 5751.161Sdsl20070422: 5761.161Sdsl The way OS emulations lookup filenames inside the emulation root 5771.161Sdsl has been changed. Rather than modify the pathname (and copy back 5781.161Sdsl to userspace) namei() and lookup() directly check the emulation 5791.241Swiz root. One side effect is that absolute symlinks inside the emulated 5801.167Swiz root file system will be relative to that file system - unless they 5811.161Sdsl start /../ this is useful when the emulated root is a real install 5821.161Sdsl that has such links. 5831.161Sdsl This might affect symlinks that have been added to reference outside 5841.161Sdsl the emulated root. 5851.161Sdsl 5861.160Sjmcneill20070412: 5871.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 5881.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 5891.160Sjmcneill example. 5901.160Sjmcneill 5911.159Sgdt20070319: 5921.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 5931.159Sgdt on many platforms due to incorrect flags settings. If you 5941.159Sgdt updated and built after about 20070315, do "nbmake-$arch 5951.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 5961.159Sgdt rebuild of object files that might have been built 5971.159Sgdt incorrectly, and ensure that you have at least 5981.159Sgdt src/lib/libc/Makefile 1.130. 5991.159Sgdt 6001.241Swiz20070210: 6011.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 6021.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 6031.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 6041.158Sdbj will allow dependencies on those files to get get rebuilt 6051.158Sdbj 6061.157Sapb20070209: 6071.157Sapb The threading model was changed when the newlock2 branch 6081.157Sapb was merged to NetBSD-current. If you boot with a new 6091.157Sapb kernel (version 4.99.10), then you also need a new pthread 6101.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 6111.157Sapb an old kernel, then you need the old pthread library 6121.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 6131.157Sapb the pthread library in sync, old threaded applications should 6141.157Sapb continue to work with an old or new kernel. Note that named(8) 6151.157Sapb is the only threaded application in the base system. 6161.157Sapb 6171.154She20061214: 6181.154She Following the move of string_to_flags() and flags_to_string() 6191.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 6201.154She will need to do a "make cleandir" in 6211.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 6221.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 6231.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 6241.156She as the installation images in distrib/ 6251.154She in order to excise stale references to the old stat_flags.h header 6261.154She file in the ls sources -- stat_flags.h has been removed. 6271.154She 6281.152Schristos20061108: 6291.152Schristos The configure script used in the src/tools/gcc compiler has been 6301.152Schristos changed to indicate that our libc has ssp support built-in and 6311.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 6321.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 6331.152Schristos 6341.151Srpaulo20061009: 6351.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 6361.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 6371.151Srpaulo 6381.150Sbjh2120060814: 6391.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 6401.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 6411.150Sbjh21 kernel configuration for an example. X servers from the last 6421.150Sbjh21 few years should cope. 6431.150Sbjh21 6441.149Schristos20060703: 6451.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 6461.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 6471.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 6481.149Schristos 6491.148Sdogcow20060627: 6501.148Sdogcow socket(2) has changed, and its system call has been versioned. 6511.148Sdogcow For userlands with the old version of socket(2), make sure that 6521.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 6531.148Sdogcow errors will result. 6541.148Sdogcow 6551.1SabsHints for a more successful build: 6561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6571.123Sjmc Use build.sh, but do not use its "expert mode": 6581.132Sjmmv This will automatically build the tools in the 6591.123Sjmc correct order, and it will keep the tools and the 6601.123Sjmc new build products from interfering with the running 6611.123Sjmc system. This will allow you to ignore most of the 6621.123Sjmc other advice in this file. 6631.2Smrg Build a new kernel first: 6641.2Smrg This makes sure that any new system calls or features 6651.2Smrg expected by the new userland will be present. This 6661.2Smrg helps to avoid critical errors when upgrading. 6671.1Sabs Use object directories: 6681.1Sabs This helps to keep stale object 6691.1Sabs files from polluting the build if a Makefile "forgets" 6701.1Sabs about one. It also makes it easier to clean up after 6711.1Sabs a build. It's also necessary if you want to use the 6721.1Sabs same source tree for multiple machines. 6731.123Sjmc To use object directories with build.sh: 6741.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 6751.123Sjmc To use object directories without using build.sh: 6761.1Sabs a) cd /usr/src ; make cleandir 6771.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 6781.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 6791.1Sabs d) cd /usr/src ; make build 6801.2Smrg Note that running "make obj" in a directory will create 6811.2Smrg in obj.$MACHINE directory. 6821.1Sabs Build to a DESTDIR: 6831.123Sjmc This helps to keep old installed files (especially libraries) 6841.123Sjmc from interfering with the new build. 6851.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 6861.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 6871.123Sjmc environment variable before running make build. It should be 6881.123Sjmc set to the pathname of an initially empty directory. 6891.123Sjmc Problems: if you do not use build.sh, you might need to 6901.123Sjmc update critical utilities without using DESTDIR since 6911.123Sjmc nothing is executed from what is installed in DESTDIR. 6921.123Sjmc (See critical utils, below.) 6931.1Sabs Build often: 6941.1Sabs This keeps critical utilities current enough to not choke 6951.1Sabs on any other part of the source tree that depends on up to 6961.123Sjmc date functionality. If you use build.sh, you should not have 6971.123Sjmc this problem. 6981.241Swiz 6991.1SabsWhat to do if things don't work: 7001.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7011.230StlsWhen things don't work there are usually a few things that commonly 7021.1Sabsshould be done. 7031.1Sabs 1) make includes 7041.1Sabs This should be done automatically by make build. 7051.1Sabs 2) cd share/mk && make install 7061.1Sabs Again, automatically done by make build. 7071.1Sabs 7081.1SabsFailsafe rebuild of a small part of the tree: 7091.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7101.1SabsTo make sure you rebuild something correctly you want to do 7111.1Sabssomething like the following: 7121.1Sabs 1) Make sure the includes and .mk files are up to date. 7131.1Sabs 2) Make sure any program used to build the particular 7141.1Sabs utility is up to date. (yacc, lex, etc...) 7151.1Sabs 3) cd ...path/to/util... 7161.1Sabs make cleandir 7171.1Sabs rm ...all obj directories... 7181.1Sabs make cleandir # yes, again 7191.1Sabs make obj 7201.1Sabs make depend && make 7211.1Sabs 7221.1SabsFailsafe rebuild of the entire tree: 7231.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7241.1SabsIf you really want to make sure the source tree is clean and 7251.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 7261.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 7271.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 7281.1Sabs 7291.1Sabs---cut here--- 7301.1Sabs#!/bin/sh 7311.1Sabs. /etc/mk.conf 7321.1Sabs 7331.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7341.58Slukem NETBSDSRCDIR=/usr/src 7351.1Sabsfi 7361.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7371.1Sabs echo Unable to find sources 7381.1Sabs exit 1 7391.1Sabsfi 7401.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 7411.1Sabs 7421.1Sabsif [ -z $BSDOBJDIR ] ; then 7431.1Sabs BSDOBJDIR=/usr/obj 7441.1Sabsfi 7451.1Sabsif [ -d $BSDOBJDIR ] ; then 7461.1Sabs rm -rf $BSDOBJDIR 7471.1Sabsfi 7481.1Sabs 7491.58Slukemcd $NETBSDSRCDIR && make cleandir 7501.1Sabs 7511.1Sabs---cut here--- 7521.1Sabs 7531.1SabsCritical utilities: 7541.1Sabs^^^^^^^^^^^^^^^^^^^ 7551.3Sitojun usr.bin/compile_et 7561.1Sabs usr.bin/make 7571.1Sabs usr.bin/yacc 7581.1Sabs usr.bin/lex 7591.11Slukem usr.bin/xlint 7601.142Sdrochner usr.bin/config 7611.1Sabs 7621.34SsimonbOther problems and possible solutions: 7631.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7641.1SabsSymptom:Complaints involving a Makefile. 7651.17SerhFix: Rebuild usr.bin/make: 7661.17Serh cd usr.bin/make && make && make install 7671.111Ssimonb Or, a failsafe method if that doesn't work: 7681.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 7691.17Serh 7701.1SabsFix: Make sure .mk files are up to date. 7711.1Sabs cd share/mk && make install 7721.2Smrg 7731.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 7741.142SdrochnerFix: Rebuild usr.bin/config 7751.1Sabs 7761.1SabsSymptom: 7771.1SabsFix: Rebuild usr.bin/yacc 7781.1Sabs 7791.1SabsSymptom: 7801.1SabsFix: Rebuild usr.bin/lex 7811.1Sabs 7821.1SabsSymptom: 7831.1SabsFix: rm /usr/lib/libbfd.a 7841.4Sitojun 7851.4SitojunSymptom:Obsolete intermediate files are used during compilation 7861.4SitojunFix: Try the following sequence of commands in the directory in question. 7871.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 7881.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 7891.4Sitojun may remain. The command tries to clean everything up) 7901.5Swiz 7911.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 7921.207Smbalmer pointer type 7931.5SwizFix: Rebuild and install usr.bin/menuc 7941.12Sitojun 7951.12SitojunSymptom:mklocale not found during build in share/locale/ctype 7961.12SitojunFix: Build and install usr.bin/mklocale 7971.13Sdogcow 7981.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 7991.13SdogcowFix: Rebuild and install lib/libc 8001.13Sdogcow 8011.142SdrochnerSymptom:usr.bin/config fails to build. 8021.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8031.13Sdogcow 8041.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8051.19ScgdFix: Rebuild and install lib/libc 8061.24Sabs 8071.24SabsSymptom:lint does not understand the '-X' option 8081.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 8091.223Sjoerg 8101.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 8111.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 8121.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 8131.257Sapb 8141.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 8151.257Sapb No such file or directory. 8161.257SapbCause: If a directory is created by mistake, then it is sometimes 8171.257Sapb deleted from the CVS repository using administrative commands 8181.257Sapb that bypass the normal cvs access controls. If your cvs working tree 8191.257Sapb contains references to a directory that has been deleted on the 8201.257Sapb server in this way, then "cvs update" reports this error. 8211.257SapbFix: Recursively delete the affected directory from your working tree 8221.257Sapb and try the update again. 823