UPDATING revision 1.301
11.301Smartin$NetBSD: UPDATING,v 1.301 2019/07/27 07:55:18 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.301Smartin20190727: 231.301Smartin The uefi bootloader has gained tftp support and needs a clean 241.301Smartin build. If you do update builds, manually clean its object 251.301Smartin directory by something like: 261.301Smartin cd sys/arch/i386/stand/efiboot && make clean 271.301Smartin 281.300Smartin20190723: 291.300Smartin The jemalloc allocator in libc is now build without extended 301.300Smartin debugging (for performance reasons). In update builds make sure 311.300Smartin to rebuild it completly, by removing all affected object files, 321.300Smartin including compat builds, something like: 331.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 341.300Smartin 351.299Smrg20190207: 361.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 371.299Smrg 381.298Smartin20180924: 391.298Smartin A newer OpenSSL version has been imported. If you are doing 401.298Smartin update builds, make sure to remove all old obj dirs, like: 411.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 421.298Smartin 431.297Sjoerg20180717: 441.297Sjoerg On aarch64 int64_t and related types have changed from long long 451.297Sjoerg to long. This requires recompiling all C++ binaries. 461.297Sjoerg 471.296Smartin20180713: 481.296Smartin On amd64 and i386 static binaries are now build position 491.296Smartin independend. This requires recompilation of all object 501.296Smartin files used to create the crunched /rescue binary. 511.296Smartin Clean the rescue directory in your obj directory before 521.296Smartin doing an update build, otherwise linking will fail. 531.296Smartin 541.293Sjakllsch20180414: 551.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 561.293Sjakllsch removal of tools/binutils objects directory may be required 571.293Sjakllsch to fix tools build failure. 581.293Sjakllsch 591.292Smrg20180311: 601.292Smrg bdftopcf was updated and may need cleaning in the 611.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 621.292Smrg link errors. 631.292Smrg 641.291Smrg20180212: 651.291Smrg between OpenSSL and GCC updates, many things may fail to build. 661.291Smrg any failure that looks like GCC or openssl is best handled by 671.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 681.291Smrg is recommended if build failures occur. 691.291Smrg 701.288Smartin20171225: 711.288Smartin removal of the vadvise syscall requires manual removal of all 721.288Smartin associated files from the libc build object directory (including 731.289Schristos the .depend files) - a command like: 741.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 751.289Schristos For architectures that support multiple "compat" binary targets, 761.289Schristos you'll need to cleanup both the regular libc directory and the 771.290Smartin compat ones (the above command will do that). 781.288Smartin 791.287Skre20171010: 801.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 811.287Skre means that its objdir (or *.d and .depend at least) might need 821.287Skre to be manually removed - or a build done once without -u. 831.287Skre 841.286Smrg20170822: 851.286Smrg a new version of GMP has been imported and probably 861.286Smrg will break parts of builds related to themselves or GCC, both 871.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 881.286Smrg and MPC objdirs or build once without -u. 891.286Smrg 901.285Smrg20170816: 911.285Smrg a new version of MPFR and MPC have been imported and probably 921.285Smrg will break parts of builds related to themselves or GCC, both 931.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 941.285Smrg and MPC objdirs or build once without -u. 951.285Smrg 961.284Smartin20170402: 971.284Smartin a new version of dhcpcd has been imported, which does not support 981.284Smartin update builds from the previous version. Remove your 991.284Smartin external/bsd/dhcpcd object dir or build once without -u. 1001.284Smartin 1011.281Sroy20170211: 1021.281Sroy a new terminfo database has been imported. 1031.281Sroy The structure of it has changed slightly from prior versions and 1041.281Sroy an updated tic tool is required. 1051.281Sroy If you build.sh, don't use -u 1061.281Sroy 1071.280Skre20170207: 1081.278Skre various arch dependent libc/exect.S files were removed 1091.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 1101.279Skre if it exists) or do a clean build. 1111.279Skre (This is a bug in the make system, it should be corrected without 1121.279Skre human intervention, but isn't.) 1131.278Skre 1141.277Smartin20170104: 1151.277Smartin xinput build options have changed. 1161.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 1171.277Smartin if you build.sh -u 1181.277Smartin 1191.276Smartin20170103: 1201.276Smartin a new version of flex has been imported. 1211.276Smartin Remove the file from obj (external/bsd/flex) 1221.276Smartin if you build.sh -u 1231.276Smartin 1241.275Sspz20161014: 1251.275Sspz a new version of OpenSSL has been imported. 1261.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 1271.275Sspz if you build.sh -u 1281.275Sspz 1291.274Smartin20161009: 1301.274Smartin a new version of dhcpcd has been imported with slightly changed 1311.274Smartin build infrastructure. When doing a build.sh -u this requires 1321.274Smartin pruning the external/bsd/dhcpcd objdir. 1331.274Smartin 1341.273Smrg20160914: 1351.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 1361.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 1371.273Smrg and a clean objdir. 1381.273Smrg 1391.272Sdholland20160527: 1401.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 1411.272Sdholland been enabled. (see the amd64 entry two down for further info) 1421.272Sdholland 1431.270Schristos20160418: 1441.270Schristos libedit needs manual removal of all autogenerated files since 1451.271Schristos some of them are not autogenerated anymore. Remember that there 1461.271Schristos might be two copies of libedit if your platform builds "compat". 1471.270Schristos 1481.268Sriastrad20160410: 1491.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 1501.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 1511.268Sriastrad executables, means all code, including executables and not just 1521.268Sriastrad shared libraries, is position-independent and hence able to be 1531.268Sriastrad relocated by ASLR, address space layout randomization. 1541.268Sriastrad 1551.268Sriastrad The change was made in Makefile variables for compiler and 1561.268Sriastrad linker flags, for which make(1) does not record dependencies, 1571.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 1581.268Sriastrad 1591.268Sriastrad Partial rebuilds with some modified source files will likely 1601.268Sriastrad fail when linking executables, since the linker refuses to mix 1611.268Sriastrad position-independent code with position-dependent code in 1621.268Sriastrad position-independent executables: 1631.268Sriastrad 1641.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 1651.268Sriastrad 1661.267Smrg20160401: 1671.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 1681.269Sdholland Some people have found that cleandir is not sufficient, so if 1691.269Sdholland in doubt delete the entire object directory tree for gcc. 1701.267Smrg 1711.266Saymeric20160306: 1721.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 1731.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 1741.265Saymeric non-NetBSD hosts if linked with stale object files produced 1751.265Saymeric while they included a non-NetBSD regex.h. 1761.265Saymeric In any case, you should "make cleandir" at least these tools 1771.265Saymeric before updating your toolchain. 1781.265Saymeric 1791.264Smartin20160125: 1801.264Smartin Dtrace has been enabled by default on some architectures. 1811.264Smartin When doing an update build, make sure to clean the etc/mtree 1821.264Smartin object directory before starting the build - otherwise the 1831.264Smartin needed directories in destdir will not be created. 1841.264Smartin An easy way to do this is: 1851.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 1861.264Smartin 1871.263Sdholland20150818: 1881.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 1891.263Sdholland again. 1901.263Sdholland 1911.262Schristos20150413: 1921.262Schristos New acpica requires "make cleandir" and reinstalling yacc 1931.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 1941.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 1951.262Schristos 1961.261Smartin20150404: 1971.261Smartin Lint changes require a full rebuild of the tool, so make 1981.261Smartin sure to build without -u option to build.sh, or manually 1991.261Smartin do a make cleandir in src/tools/lint1 and 2001.261Smartin src/usr.bin/xlint. 2011.261Smartin 2021.260Sskrll20150310: 2031.260Sskrll Improvements to openssl for arm mean that update builds of 2041.260Sskrll the openssl libraries will fail. A make cleandir in 2051.260Sskrll external/bsd/openssl/lib is needed 2061.260Sskrll 2071.258Smartin20141026: 2081.259Smsaitoh A mishap during the import of pppd may cause your corruption 2091.258Smartin in your cvs directory if you happened to do a cvs update 2101.258Smartin during a short period of time. To fix, just remove the 2111.258Smartin directory src/external/bsd/ppp/dist/pppd completely 2121.258Smartin and let cvs restore it on next update. 2131.258Smartin 2141.256Sapb20140721: 2151.256Sapb The src/external/mit/lua/src directory was accidentally created 2161.256Sapb and then deleted in the CVS repository. If you get errors like 2171.256Sapb 2181.256Sapb cvs [update aborted]: cannot open directory 2191.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 2201.256Sapb 2211.256Sapb then delete your local copy of that directory tree and try again. 2221.256Sapb 2231.255Sjoerg20140530: 2241.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 2251.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 2261.255Sjoerg 2271.251Smartin20140131: 2281.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 2291.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 2301.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 2311.251Smartin 2321.250Schristos20131227: 2331.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 2341.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 2351.250Schristos mode7 in your config file. Make sure you put the necessary restrict 2361.250Schristos statements to avoid being exposed. 2371.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 2381.250Schristos to make clean in libc 2391.250Schristos 2401.249Smrg20131129: 2411.249Smrg The GMP sources were updated, and builds will likely fail without 2421.249Smrg cleaning their build trees for both tools and in-tree, like below. 2431.249Smrg 2441.248Smrg20131128: 2451.248Smrg The MPC and MPFR sources were updated, and builds may require their 2461.248Smrg tools and in-tree directories cleaned for successful updates. 2471.248Smrg 2481.246Smartin20130605: 2491.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 2501.247Sspz to IPSEC (and the older IPSEC version removed). 2511.247Sspz 2521.247Sspz20130605: 2531.246Smartin Previous freetype installations eroneously installed private 2541.246Smartin header files. If you are building against a non-empty $DESTDIR, 2551.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 2561.246Smartin 2571.245Smrg20130531: 2581.245Smrg The xdm update may cause build failure due to xdm.man being 2591.245Smrg in the obj tree. Make sure to ensure any like this: 2601.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 2611.245Smrg is fixed by deleting the xdm.man in the obj tree. 2621.245Smrg 2631.244Smrg20130530: 2641.244Smrg Updates of many xsrc packages will leave old .pc files around. 2651.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 2661.244Smrg 2671.242Schristos20130301: 2681.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 2691.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 2701.242Schristos 2711.238Sdholland20120726: 2721.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 2731.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 2741.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 2751.241Swiz some cases may succeed and install broken OpenSSL libraries that 2761.240Sdholland cause third-party software to link incorrectly and/or crash. 2771.238Sdholland 2781.237Swiz20120507: 2791.241Swiz The database schema for makemandb was changed. You will 2801.237Swiz need to update the database using 'makemandb -f' or wait 2811.237Swiz for the next weekly run to fix it. 2821.237Swiz 2831.236Sbsh20120319: 2841.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 2851.236Sbsh size of db_symtab automatically. You need to update dbsym in 2861.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 2871.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 2881.236Sbsh mk.conf. 2891.236Sbsh 2901.235Sjoerg20120216: 2911.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 2921.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 2931.239Sdholland and 20120216, daily and weekly could have created an unreadable 2941.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 2951.235Sjoerg the next run of weekly will fix it. 2961.233Sjoerg 2971.232Schristos20111227: 2981.232Schristos If you built between 20111225 and 20111227 you need to remove 2991.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 3001.232Schristos bump has been reverted. 3011.232Schristos 3021.231Stls20111125: 3031.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 3041.231Stls means it should no longer be explicitly listed in kernel 3051.231Stls configuration files. The line "pseudo-device rnd" should be 3061.231Stls removed from any custom kernel config files users may have. 3071.231Stls 3081.230Stls20111119: 3091.230Stls A problem with the datastructures used by the rndctl(8) 3101.230Stls utility (pointers in datastructures in an array, making 32->64 3111.230Stls bit compatibility very painful) has been fixed in a 3121.230Stls non-backwards-compatible way. If you replace your kernel, 3131.230Stls replace your rndctl executable too. 3141.241Swiz 3151.229Sjym20111001: 3161.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 3171.229Sjym changed and their new version is not backward compatible with the old 3181.241Swiz one. So ensure that all consumers of these functions (currently: 3191.229Sjym quota2 code and its tests) are updated together with the new lib. 3201.229Sjym 3211.228Smrg20110817: 3221.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 3231.228Smrg DESTDIR for them should be deleted before updating. 3241.228Smrg 3251.227Sriastrad20110806: 3261.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 3271.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 3281.227Sriastrad 3291.226Smrg20110805: 3301.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 3311.226Smrg the tree to be cleaned. Best to delete both objdir and 3321.226Smrg DESTDIR before running this update. So far, only the 3331.226Smrg sparc64, mips and powerpc platforms have changed. 3341.226Smrg 3351.225Smatt20110803: 3361.241Swiz The layout of external/public-domain/xz has changed. To do an 3371.225Smatt update build you will have to remove the contents of the OBJDIR 3381.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 3391.225Smatt is now a directory. 3401.225Smatt 3411.223Sjoerg20110410: 3421.241Swiz The configuration of src/tools/gcc has changed. To do an 3431.224Sdholland update build you have to clean both tools/binutils and 3441.224Sdholland tools/gcc by hand. 3451.223Sjoerg 3461.222Splunky20110328: 3471.222Splunky Building the Xorg binary was moved into a subdirectory to fix 3481.241Swiz ordering issues with "make all". It may be necessary to remove 3491.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 3501.222Splunky if your update build fails, as the "Xorg" entry there is now a 3511.222Splunky directory. 3521.222Splunky 3531.220Sjoerg20110121: 3541.221Slukem Assembler files no longer use -traditional-cpp. This can break 3551.220Sjoerg the build of individual parts of the tree. This is handled 3561.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 3571.220Sjoerg and re-run config(1) for any kernel configurations as needed. 3581.218Sjoerg 3591.217Sjruoho20101217: 3601.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 3611.241Swiz by default. It may be necessary to manually update passwd(5) and 3621.217Sjruoho group(5) in order to make the program work with existing setups. 3631.217Sjruoho 3641.216Schristos20101125: 3651.216Schristos The latest changes to setenv(3) dissallow setting environment 3661.241Swiz variables with names that contain '='. Revision 1.18 of env.c 3671.241Swiz assumed that this was allowed. Installing a new libc with an 3681.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 3691.216Schristos break which affects the autoconf tests for dependency finding, 3701.216Schristos so building gcc will end up printing: 3711.216Schristos checking dependency style of gcc... none 3721.216Schristos configure: error: no usable dependency style found 3731.216Schristos Fix it by rebuilding and re-installing env. 3741.138Slukem 3751.215Smrg20101119: 3761.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 3771.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 3781.215Smrg have any build problems with xsrc, or problems with mismatched 3791.215Smrg versions between xorg-server and drivers. 3801.215Smrg 3811.213Sjmmv20100604: 3821.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 3831.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 3841.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 3851.213Sjmmv trees by hand. 3861.213Sjmmv 3871.211Stnozaki20100522: 3881.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 3891.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 3901.212Smrg build problems with xsrc. 3911.212Smrg 3921.212Smrg20100522: 3931.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 3941.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 3951.211Stnozaki 3961.210Schristos20100520: 3971.241Swiz The location of the xkb compiled descriptions has changed. Please 3981.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 3991.210Schristos 4001.209Snjoly20100222: 4011.209Snjoly The shared objects file extension has been changed from .so to 4021.209Snjoly .pico, in order to avoid conflicts with shared libraries names 4031.209Snjoly libXX.so. All now stale regular .so files can be removed from 4041.209Snjoly your object directories. 4051.209Snjoly 4061.208Sroy20100204: 4071.208Sroy The termcap database has been removed from the sources, 4081.208Sroy but has not been marked obsolete so it is not removed 4091.208Sroy from the system when upgrading. 4101.208Sroy As such, you will need to remove them from your object 4111.208Sroy and destination directories. 4121.208Sroy 4131.203Sdyoung20091101: 4141.205Sdholland After updating, it may be necessary to make the 'cleandir' 4151.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 4161.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 4171.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 4181.203Sdyoung 4191.202Smrg20091001: 4201.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 4211.206Sdholland before building a kernel, or the build fails on cpufunc.S. 4221.206Sdholland 4231.206Sdholland20091001: 4241.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 4251.202Smrg symlink, failing the build. Delete the link, and the subdir 4261.202Smrg it is in, and retry your build. 4271.202Smrg 4281.201Sdsl20090718: 4291.201Sdsl libc build changed so that strchr() provides the extra entry 4301.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 4311.201Sdsl may fail because the archive contains the unwanted index.o. 4321.201Sdsl (Similarly for strrchr() and rindex().) 4331.201Sdsl 4341.198Smrg20090709: 4351.198Smrg Native Xorg was upgraded again. Builds will probably fail again 4361.198Smrg without a clean objdir, at least for src/external/mit/xorg. 4371.198Smrg 4381.197Smrg20090616: 4391.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 4401.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 4411.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 4421.197Smrg subdirectory has been changed into a file, and this needs to 4431.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 4441.197Smrg 4451.195Sperry20090501: 4461.195Sperry Several new functions were added to string.h/libc, and this 4471.195Sperry can cause autoconf problems during the tool build for people 4481.241Swiz who fail to clean out their tools objects properly. If you 4491.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 4501.195Sperry failure during the tool build, clean out all your tools 4511.195Sperry objects and start again. 4521.195Sperry 4531.194Smrg20090325: 4541.194Smrg The i386 port was switched to i486 default toolchain. This requires 4551.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 4561.194Smrg 4571.192Sskrll20090126: 4581.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 4591.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 4601.207Smbalmer to avoid using the old assembly stub. 4611.192Sskrll 4621.191Sjoerg20090202: 4631.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 4641.191Sjoerg detection. It is recommented to rebuild the cache with 4651.191Sjoerg ``pkg_admin rebuild''. 4661.191Sjoerg 4671.184Schristos20090110: 4681.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 4691.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 4701.188Schristos This is needed even in the MODULAR kernel because there is 4711.188Schristos conditionally compiled code in rtsock.c. 4721.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 4731.184Schristos before installing. 4741.184Schristos 3. If you don't use build.sh and you build directly to root, and 4751.241Swiz your build breaks in the middle, don't despair. Make sure headers 4761.184Schristos are installed properly, and start building libraries first libc 4771.184Schristos and libutil, install them and then continue building all the 4781.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 4791.184Schristos the new libraries are installed, you can restart the build. 4801.184Schristos 4. If you compile packages and you notice link time warnings, 4811.189Shubertf rebuild the required packages to update their shared libraries. 4821.189Shubertf Any package you rebuild will require rebuilding all the packages 4831.189Shubertf that depend on it. 4841.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 4851.186Schristos will be upgraded and it will not be backwards compatible. 4861.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 4871.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 4881.241Swiz for utmp. You are better off removing the old files after 4891.190Sapb upgrading. The automated clearing of /var/run during 4901.190Sapb boot, and the automated rotating of files in /var/log by 4911.190Sapb newsyslog(8), may mean that you do not have to remove the 4921.190Sapb files manually. 4931.190Sapb 7. The optional accounting file (/var/account/acct, see 4941.190Sapb accton(8)) has not been versioned, and will need to be 4951.190Sapb removed. The automatic rotation of the accounting file by 4961.190Sapb /etc/daily limits the bad consequences of failure to remove 4971.190Sapb the file. 4981.196Sdholland 8. Application software that writes time_t to binary files on 4991.241Swiz disk will break or need attention. Most notably: if you are 5001.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 5011.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 5021.185Sjmcneill 5031.183Spgoyette20081219: 5041.183Spgoyette config(1) has been updated, and one of the files it creates - 5051.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 5061.183Spgoyette (done automatically by build.sh) and then you need to rerun 5071.183Spgoyette config on all kernel configuration files before rebuilding those 5081.183Spgoyette kernels. 5091.183Spgoyette 5101.181Scube20081205: 5111.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 5121.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 5131.181Scube set and will appear as extra files for MKX11=no update builds. 5141.178Slukem 5151.179Stsutsui20081122: 5161.182Stsutsui On i386, various kernel options(4) in GENERIC including 5171.180Swiz file systems have been disabled and moved into kernel modules. 5181.180Swiz Before trying a new GENERIC kernel, you have to prepare the 5191.179Stsutsui following files as well as a new GENERIC kernel: 5201.179Stsutsui 5211.179Stsutsui - build and install kernel modules from src/sys/modules 5221.179Stsutsui 5231.179Stsutsui - install the latest bootloader, which will load a module 5241.180Swiz for the file system from which the kernel is loaded automatically 5251.179Stsutsui 5261.180Swiz If you have to load your kernel from a file system which is not of 5271.180Swiz the same type as the root file system, you have to load the necessary 5281.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 5291.179Stsutsui 5301.178Slukem20080827: 5311.178Slukem If you built and installed a libc from sources between 5321.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 5331.178Slukem which results in false errors reported by lint(1). 5341.178Slukem Since this breaks the libc build itself, manual help is 5351.180Swiz needed -- lint must be disabled temporarily, e.g.: 5361.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 5371.178Slukem 5381.177Schristos20080813: 5391.177Schristos MKDEBUG build was broken because the .depend files did not know 5401.241Swiz about .go files. You need to remove all .depend files and rebuild. 5411.177Schristos 5421.200Sdholland20080802: 5431.200Sdholland A regression in binary compatibility for pthread_mutex_t has 5441.241Swiz been fixed. Unfortunately, the price is breaking compatibility 5451.200Sdholland for -current. 5461.200Sdholland 5471.200Sdholland Threaded programs (using libpthread) and C++ programs (using 5481.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 5491.200Sdholland be recompiled. 5501.200Sdholland 5511.200Sdholland One way to find affected pkgsrc packages: 5521.200Sdholland 5531.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 5541.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 5551.200Sdholland 5561.175Ssimonb20080731: 5571.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 5581.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 5591.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 5601.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 5611.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 5621.176Ssimonb also requires the super block to be in the UFS2 format. You 5631.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 5641.175Ssimonb 5651.174Slukem20080721: 5661.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 5671.174Slukem isn't defined. 5681.174Slukem 5691.173Sfreza20080531: 5701.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 5711.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 5721.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 5731.241Swiz won't work correctly. The following sequence of commands: 5741.173Sfreza 5751.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 5761.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 5771.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 5781.173Sfreza 5791.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 5801.173Sfreza 5811.172Slukem20080503: 5821.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 5831.172Slukem 5841.171She20080521: 5851.171She For a while, unprivileged UPDATE builds would fail to 5861.171She succeed at the checkflist stage, complaining that 5871.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 5881.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 5891.171She If you already hit this problem, update the .mk file, 5901.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 5911.171She 5921.174Slukem20080303: 5931.174Slukem Linker warnings are now fatal if $WARNS>0. 5941.174Slukem 5951.170Schristos20080126: 5961.170Schristos The posix_fadvise system call has been changed from an assembly 5971.241Swiz stub, to a c file that calls an assembly stub. You need to 5981.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 5991.170Schristos avoid using the old assembly stub. 6001.170Schristos 6011.168Sjoerg20071209: 6021.241Swiz The acpiec(4) driver has been split into two attachments. If you 6031.168Sjoerg get ACPI errors before the attachment, please update your kernel 6041.169Swiz configuration file appropriately or see GENERIC for more details. 6051.168Sjoerg 6061.166Sxtraeme20071115: 6071.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 6081.166Sxtraeme argument specified in the kernel configuration file is not valid 6091.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 6101.241Swiz rather than the EC address port. Please update your kernel 6111.167Swiz configuration file appropriately or see GENERIC for more details. 6121.166Sxtraeme 6131.165Sjmmv20071028: 6141.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 6151.165Sjmmv You need to update any custom kernel configuration file you have 6161.165Sjmmv to remove any references to pccons (which includes removing the 6171.165Sjmmv now useless XSERVER option) and replace them with the correct 6181.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 6191.165Sjmmv for more details. 6201.165Sjmmv 6211.164Sgdt20070913: 6221.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 6231.164Sgdt enumerate interfaces was fixed. The bug began to cause 6241.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 6251.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 6261.164Sgdt could not enumerate interfaces. (These are noted because 6271.164Sgdt normal kernel/userspace version matching hygiene is not 6281.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 6291.164Sgdt and userland are from after 20070913. 6301.164Sgdt 6311.163Sjoerg20070703: 6321.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 6331.199Sdholland calls the target-specific strip program, and the logic to pass 6341.199Sdholland down STRIP from make has been removed. This requires a 6351.199Sdholland re-installation of tools. 6361.163Sjoerg 6371.161Sdsl20070422: 6381.161Sdsl The way OS emulations lookup filenames inside the emulation root 6391.161Sdsl has been changed. Rather than modify the pathname (and copy back 6401.161Sdsl to userspace) namei() and lookup() directly check the emulation 6411.241Swiz root. One side effect is that absolute symlinks inside the emulated 6421.167Swiz root file system will be relative to that file system - unless they 6431.161Sdsl start /../ this is useful when the emulated root is a real install 6441.161Sdsl that has such links. 6451.161Sdsl This might affect symlinks that have been added to reference outside 6461.161Sdsl the emulated root. 6471.161Sdsl 6481.160Sjmcneill20070412: 6491.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 6501.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 6511.160Sjmcneill example. 6521.160Sjmcneill 6531.159Sgdt20070319: 6541.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 6551.159Sgdt on many platforms due to incorrect flags settings. If you 6561.159Sgdt updated and built after about 20070315, do "nbmake-$arch 6571.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 6581.159Sgdt rebuild of object files that might have been built 6591.159Sgdt incorrectly, and ensure that you have at least 6601.159Sgdt src/lib/libc/Makefile 1.130. 6611.159Sgdt 6621.241Swiz20070210: 6631.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 6641.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 6651.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 6661.158Sdbj will allow dependencies on those files to get get rebuilt 6671.158Sdbj 6681.157Sapb20070209: 6691.157Sapb The threading model was changed when the newlock2 branch 6701.157Sapb was merged to NetBSD-current. If you boot with a new 6711.157Sapb kernel (version 4.99.10), then you also need a new pthread 6721.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 6731.157Sapb an old kernel, then you need the old pthread library 6741.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 6751.157Sapb the pthread library in sync, old threaded applications should 6761.157Sapb continue to work with an old or new kernel. Note that named(8) 6771.157Sapb is the only threaded application in the base system. 6781.157Sapb 6791.154She20061214: 6801.154She Following the move of string_to_flags() and flags_to_string() 6811.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 6821.154She will need to do a "make cleandir" in 6831.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 6841.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 6851.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 6861.156She as the installation images in distrib/ 6871.154She in order to excise stale references to the old stat_flags.h header 6881.154She file in the ls sources -- stat_flags.h has been removed. 6891.154She 6901.152Schristos20061108: 6911.152Schristos The configure script used in the src/tools/gcc compiler has been 6921.152Schristos changed to indicate that our libc has ssp support built-in and 6931.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 6941.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 6951.152Schristos 6961.151Srpaulo20061009: 6971.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 6981.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 6991.151Srpaulo 7001.150Sbjh2120060814: 7011.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 7021.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 7031.150Sbjh21 kernel configuration for an example. X servers from the last 7041.150Sbjh21 few years should cope. 7051.150Sbjh21 7061.149Schristos20060703: 7071.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 7081.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 7091.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 7101.149Schristos 7111.148Sdogcow20060627: 7121.148Sdogcow socket(2) has changed, and its system call has been versioned. 7131.148Sdogcow For userlands with the old version of socket(2), make sure that 7141.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 7151.148Sdogcow errors will result. 7161.148Sdogcow 7171.1SabsHints for a more successful build: 7181.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7191.123Sjmc Use build.sh, but do not use its "expert mode": 7201.132Sjmmv This will automatically build the tools in the 7211.123Sjmc correct order, and it will keep the tools and the 7221.123Sjmc new build products from interfering with the running 7231.123Sjmc system. This will allow you to ignore most of the 7241.123Sjmc other advice in this file. 7251.2Smrg Build a new kernel first: 7261.2Smrg This makes sure that any new system calls or features 7271.2Smrg expected by the new userland will be present. This 7281.2Smrg helps to avoid critical errors when upgrading. 7291.1Sabs Use object directories: 7301.1Sabs This helps to keep stale object 7311.1Sabs files from polluting the build if a Makefile "forgets" 7321.1Sabs about one. It also makes it easier to clean up after 7331.1Sabs a build. It's also necessary if you want to use the 7341.1Sabs same source tree for multiple machines. 7351.123Sjmc To use object directories with build.sh: 7361.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 7371.123Sjmc To use object directories without using build.sh: 7381.1Sabs a) cd /usr/src ; make cleandir 7391.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 7401.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 7411.1Sabs d) cd /usr/src ; make build 7421.2Smrg Note that running "make obj" in a directory will create 7431.2Smrg in obj.$MACHINE directory. 7441.1Sabs Build to a DESTDIR: 7451.123Sjmc This helps to keep old installed files (especially libraries) 7461.123Sjmc from interfering with the new build. 7471.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 7481.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 7491.123Sjmc environment variable before running make build. It should be 7501.123Sjmc set to the pathname of an initially empty directory. 7511.123Sjmc Problems: if you do not use build.sh, you might need to 7521.123Sjmc update critical utilities without using DESTDIR since 7531.123Sjmc nothing is executed from what is installed in DESTDIR. 7541.123Sjmc (See critical utils, below.) 7551.1Sabs Build often: 7561.1Sabs This keeps critical utilities current enough to not choke 7571.1Sabs on any other part of the source tree that depends on up to 7581.123Sjmc date functionality. If you use build.sh, you should not have 7591.123Sjmc this problem. 7601.241Swiz 7611.1SabsWhat to do if things don't work: 7621.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7631.230StlsWhen things don't work there are usually a few things that commonly 7641.1Sabsshould be done. 7651.1Sabs 1) make includes 7661.1Sabs This should be done automatically by make build. 7671.1Sabs 2) cd share/mk && make install 7681.1Sabs Again, automatically done by make build. 7691.1Sabs 7701.1SabsFailsafe rebuild of a small part of the tree: 7711.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7721.1SabsTo make sure you rebuild something correctly you want to do 7731.1Sabssomething like the following: 7741.1Sabs 1) Make sure the includes and .mk files are up to date. 7751.1Sabs 2) Make sure any program used to build the particular 7761.1Sabs utility is up to date. (yacc, lex, etc...) 7771.1Sabs 3) cd ...path/to/util... 7781.1Sabs make cleandir 7791.1Sabs rm ...all obj directories... 7801.1Sabs make cleandir # yes, again 7811.1Sabs make obj 7821.1Sabs make depend && make 7831.1Sabs 7841.1SabsFailsafe rebuild of the entire tree: 7851.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7861.1SabsIf you really want to make sure the source tree is clean and 7871.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 7881.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 7891.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 7901.1Sabs 7911.1Sabs---cut here--- 7921.1Sabs#!/bin/sh 7931.1Sabs. /etc/mk.conf 7941.1Sabs 7951.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7961.58Slukem NETBSDSRCDIR=/usr/src 7971.1Sabsfi 7981.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7991.1Sabs echo Unable to find sources 8001.1Sabs exit 1 8011.1Sabsfi 8021.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 8031.1Sabs 8041.1Sabsif [ -z $BSDOBJDIR ] ; then 8051.1Sabs BSDOBJDIR=/usr/obj 8061.1Sabsfi 8071.1Sabsif [ -d $BSDOBJDIR ] ; then 8081.1Sabs rm -rf $BSDOBJDIR 8091.1Sabsfi 8101.1Sabs 8111.58Slukemcd $NETBSDSRCDIR && make cleandir 8121.1Sabs 8131.1Sabs---cut here--- 8141.1Sabs 8151.1SabsCritical utilities: 8161.1Sabs^^^^^^^^^^^^^^^^^^^ 8171.3Sitojun usr.bin/compile_et 8181.1Sabs usr.bin/make 8191.1Sabs usr.bin/yacc 8201.1Sabs usr.bin/lex 8211.11Slukem usr.bin/xlint 8221.142Sdrochner usr.bin/config 8231.1Sabs 8241.34SsimonbOther problems and possible solutions: 8251.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8261.1SabsSymptom:Complaints involving a Makefile. 8271.17SerhFix: Rebuild usr.bin/make: 8281.17Serh cd usr.bin/make && make && make install 8291.111Ssimonb Or, a failsafe method if that doesn't work: 8301.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 8311.17Serh 8321.1SabsFix: Make sure .mk files are up to date. 8331.1Sabs cd share/mk && make install 8341.2Smrg 8351.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 8361.142SdrochnerFix: Rebuild usr.bin/config 8371.1Sabs 8381.1SabsSymptom: 8391.1SabsFix: Rebuild usr.bin/yacc 8401.1Sabs 8411.1SabsSymptom: 8421.1SabsFix: Rebuild usr.bin/lex 8431.1Sabs 8441.1SabsSymptom: 8451.1SabsFix: rm /usr/lib/libbfd.a 8461.4Sitojun 8471.4SitojunSymptom:Obsolete intermediate files are used during compilation 8481.4SitojunFix: Try the following sequence of commands in the directory in question. 8491.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 8501.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 8511.4Sitojun may remain. The command tries to clean everything up) 8521.5Swiz 8531.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 8541.207Smbalmer pointer type 8551.5SwizFix: Rebuild and install usr.bin/menuc 8561.12Sitojun 8571.12SitojunSymptom:mklocale not found during build in share/locale/ctype 8581.12SitojunFix: Build and install usr.bin/mklocale 8591.13Sdogcow 8601.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 8611.13SdogcowFix: Rebuild and install lib/libc 8621.13Sdogcow 8631.142SdrochnerSymptom:usr.bin/config fails to build. 8641.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8651.13Sdogcow 8661.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8671.19ScgdFix: Rebuild and install lib/libc 8681.24Sabs 8691.24SabsSymptom:lint does not understand the '-X' option 8701.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 8711.223Sjoerg 8721.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 8731.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 8741.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 8751.257Sapb 8761.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 8771.257Sapb No such file or directory. 8781.257SapbCause: If a directory is created by mistake, then it is sometimes 8791.257Sapb deleted from the CVS repository using administrative commands 8801.257Sapb that bypass the normal cvs access controls. If your cvs working tree 8811.257Sapb contains references to a directory that has been deleted on the 8821.257Sapb server in this way, then "cvs update" reports this error. 8831.257SapbFix: Recursively delete the affected directory from your working tree 8841.257Sapb and try the update again. 885