UPDATING revision 1.319
11.319Smrg$NetBSD: UPDATING,v 1.319 2021/07/11 21:58:52 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.319Smrg20210711: 231.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 241.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 251.319Smrg 261.318Smrg20210417: 271.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 281.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 291.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 301.318Smrg 311.317Srillig20201230: 321.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 331.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 341.317Srillig 351.316Smrg20201016: 361.316Smrg MIPS kernel modules have been disabled until they work. This will 371.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 381.316Smrg 391.315Smrg20200925: 401.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 411.315Smrg in both the tools and external dirs. 421.315Smrg 431.314Smrg20200912: 441.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 451.314Smrg for several more, as will binutils 2.34. Clean as required. 461.314Smrg 471.313Smrg20200907: 481.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 491.313Smrg probably requires cleaning the tools/binutils. 501.313Smrg 511.311Smrg20200811: 521.312Smrg GCC updates may require cleaning the objdir. This may occur 531.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 541.312Smrg GCC 9 upgrade. 551.311Smrg 561.309Schristos20200614: 571.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 581.310Schristos should handle the migration 591.309Schristos 601.308Schristos20200601: 611.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 621.308Schristos created in the build directories and need cleaning. 631.308Schristos 641.307Smrg20200311: 651.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 661.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 671.307Smrg 681.306Schristos20191118: 691.306Schristos More architectures were switched to gcc8: 701.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 711.306Schristos The same comments as in 20191022 apply. 721.306Schristos 731.305Smartin20191112: 741.305Smartin The LLVM update requires a clean rebuild for all architectures using 751.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 761.305Smartin 771.304Smartin20191022: 781.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 791.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 801.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 811.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 821.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 831.304Smartin daily builds and install that before doing the next in-place build. 841.304Smartin 851.303Smrg20191001: 861.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 871.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 881.303Smrg directory, and also clean src/external/gpl3/gcc. 891.303Smrg 901.302Sriastrad20190903: 911.306Schristos Files with names that coincide with existing files' names on 921.302Sriastrad case-insensitive file systems were inadvertently committed, for 931.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 941.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 951.302Sriastrad ran build.sh distribution or ran build.sh release, you must 961.302Sriastrad manually delete the following files in your DESTDIR (which is 971.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 981.302Sriastrad them: 991.302Sriastrad 1001.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 1011.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 1021.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 1031.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 1041.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 1051.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 1061.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 1071.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 1081.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 1091.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 1101.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 1111.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 1121.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 1131.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 1141.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 1151.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 1161.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 1171.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 1181.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 1191.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 1201.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 1211.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 1221.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 1231.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 1241.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 1251.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 1261.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 1271.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 1281.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 1291.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 1301.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 1311.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 1321.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 1331.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 1341.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 1351.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 1361.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 1371.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 1381.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 1391.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 1401.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 1411.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1421.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1431.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1441.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1451.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1461.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1471.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1481.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1491.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1501.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1511.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1521.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1531.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1541.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1551.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1561.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1571.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1581.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1591.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1601.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1611.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1621.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1631.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1641.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1651.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1661.302Sriastrad 1671.302Sriastrad We will re-import these radeon firmware images another way 1681.302Sriastrad later. 1691.302Sriastrad 1701.301Smartin20190727: 1711.301Smartin The uefi bootloader has gained tftp support and needs a clean 1721.301Smartin build. If you do update builds, manually clean its object 1731.301Smartin directory by something like: 1741.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1751.301Smartin 1761.300Smartin20190723: 1771.300Smartin The jemalloc allocator in libc is now build without extended 1781.300Smartin debugging (for performance reasons). In update builds make sure 1791.300Smartin to rebuild it completly, by removing all affected object files, 1801.300Smartin including compat builds, something like: 1811.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1821.300Smartin 1831.299Smrg20190207: 1841.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1851.299Smrg 1861.298Smartin20180924: 1871.298Smartin A newer OpenSSL version has been imported. If you are doing 1881.298Smartin update builds, make sure to remove all old obj dirs, like: 1891.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 1901.298Smartin 1911.297Sjoerg20180717: 1921.297Sjoerg On aarch64 int64_t and related types have changed from long long 1931.297Sjoerg to long. This requires recompiling all C++ binaries. 1941.297Sjoerg 1951.296Smartin20180713: 1961.296Smartin On amd64 and i386 static binaries are now build position 1971.296Smartin independend. This requires recompilation of all object 1981.296Smartin files used to create the crunched /rescue binary. 1991.296Smartin Clean the rescue directory in your obj directory before 2001.296Smartin doing an update build, otherwise linking will fail. 2011.296Smartin 2021.293Sjakllsch20180414: 2031.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 2041.293Sjakllsch removal of tools/binutils objects directory may be required 2051.293Sjakllsch to fix tools build failure. 2061.293Sjakllsch 2071.292Smrg20180311: 2081.292Smrg bdftopcf was updated and may need cleaning in the 2091.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 2101.292Smrg link errors. 2111.292Smrg 2121.291Smrg20180212: 2131.291Smrg between OpenSSL and GCC updates, many things may fail to build. 2141.291Smrg any failure that looks like GCC or openssl is best handled by 2151.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 2161.291Smrg is recommended if build failures occur. 2171.291Smrg 2181.288Smartin20171225: 2191.288Smartin removal of the vadvise syscall requires manual removal of all 2201.288Smartin associated files from the libc build object directory (including 2211.289Schristos the .depend files) - a command like: 2221.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 2231.289Schristos For architectures that support multiple "compat" binary targets, 2241.289Schristos you'll need to cleanup both the regular libc directory and the 2251.290Smartin compat ones (the above command will do that). 2261.288Smartin 2271.287Skre20171010: 2281.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 2291.287Skre means that its objdir (or *.d and .depend at least) might need 2301.287Skre to be manually removed - or a build done once without -u. 2311.287Skre 2321.286Smrg20170822: 2331.286Smrg a new version of GMP has been imported and probably 2341.286Smrg will break parts of builds related to themselves or GCC, both 2351.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2361.286Smrg and MPC objdirs or build once without -u. 2371.286Smrg 2381.285Smrg20170816: 2391.285Smrg a new version of MPFR and MPC have been imported and probably 2401.285Smrg will break parts of builds related to themselves or GCC, both 2411.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2421.285Smrg and MPC objdirs or build once without -u. 2431.285Smrg 2441.284Smartin20170402: 2451.284Smartin a new version of dhcpcd has been imported, which does not support 2461.284Smartin update builds from the previous version. Remove your 2471.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2481.284Smartin 2491.281Sroy20170211: 2501.281Sroy a new terminfo database has been imported. 2511.281Sroy The structure of it has changed slightly from prior versions and 2521.281Sroy an updated tic tool is required. 2531.281Sroy If you build.sh, don't use -u 2541.281Sroy 2551.280Skre20170207: 2561.278Skre various arch dependent libc/exect.S files were removed 2571.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2581.279Skre if it exists) or do a clean build. 2591.279Skre (This is a bug in the make system, it should be corrected without 2601.279Skre human intervention, but isn't.) 2611.278Skre 2621.277Smartin20170104: 2631.277Smartin xinput build options have changed. 2641.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2651.277Smartin if you build.sh -u 2661.277Smartin 2671.276Smartin20170103: 2681.276Smartin a new version of flex has been imported. 2691.276Smartin Remove the file from obj (external/bsd/flex) 2701.276Smartin if you build.sh -u 2711.276Smartin 2721.275Sspz20161014: 2731.275Sspz a new version of OpenSSL has been imported. 2741.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2751.275Sspz if you build.sh -u 2761.275Sspz 2771.274Smartin20161009: 2781.274Smartin a new version of dhcpcd has been imported with slightly changed 2791.274Smartin build infrastructure. When doing a build.sh -u this requires 2801.274Smartin pruning the external/bsd/dhcpcd objdir. 2811.274Smartin 2821.273Smrg20160914: 2831.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2841.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2851.273Smrg and a clean objdir. 2861.273Smrg 2871.272Sdholland20160527: 2881.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 2891.272Sdholland been enabled. (see the amd64 entry two down for further info) 2901.272Sdholland 2911.270Schristos20160418: 2921.270Schristos libedit needs manual removal of all autogenerated files since 2931.271Schristos some of them are not autogenerated anymore. Remember that there 2941.271Schristos might be two copies of libedit if your platform builds "compat". 2951.270Schristos 2961.268Sriastrad20160410: 2971.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 2981.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 2991.268Sriastrad executables, means all code, including executables and not just 3001.268Sriastrad shared libraries, is position-independent and hence able to be 3011.268Sriastrad relocated by ASLR, address space layout randomization. 3021.268Sriastrad 3031.268Sriastrad The change was made in Makefile variables for compiler and 3041.268Sriastrad linker flags, for which make(1) does not record dependencies, 3051.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 3061.268Sriastrad 3071.268Sriastrad Partial rebuilds with some modified source files will likely 3081.268Sriastrad fail when linking executables, since the linker refuses to mix 3091.268Sriastrad position-independent code with position-dependent code in 3101.268Sriastrad position-independent executables: 3111.268Sriastrad 3121.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 3131.268Sriastrad 3141.267Smrg20160401: 3151.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 3161.269Sdholland Some people have found that cleandir is not sufficient, so if 3171.269Sdholland in doubt delete the entire object directory tree for gcc. 3181.267Smrg 3191.266Saymeric20160306: 3201.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 3211.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 3221.265Saymeric non-NetBSD hosts if linked with stale object files produced 3231.265Saymeric while they included a non-NetBSD regex.h. 3241.265Saymeric In any case, you should "make cleandir" at least these tools 3251.265Saymeric before updating your toolchain. 3261.265Saymeric 3271.264Smartin20160125: 3281.264Smartin Dtrace has been enabled by default on some architectures. 3291.264Smartin When doing an update build, make sure to clean the etc/mtree 3301.264Smartin object directory before starting the build - otherwise the 3311.264Smartin needed directories in destdir will not be created. 3321.264Smartin An easy way to do this is: 3331.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 3341.264Smartin 3351.263Sdholland20150818: 3361.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 3371.263Sdholland again. 3381.263Sdholland 3391.262Schristos20150413: 3401.262Schristos New acpica requires "make cleandir" and reinstalling yacc 3411.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3421.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3431.262Schristos 3441.261Smartin20150404: 3451.261Smartin Lint changes require a full rebuild of the tool, so make 3461.261Smartin sure to build without -u option to build.sh, or manually 3471.261Smartin do a make cleandir in src/tools/lint1 and 3481.261Smartin src/usr.bin/xlint. 3491.261Smartin 3501.260Sskrll20150310: 3511.260Sskrll Improvements to openssl for arm mean that update builds of 3521.260Sskrll the openssl libraries will fail. A make cleandir in 3531.260Sskrll external/bsd/openssl/lib is needed 3541.260Sskrll 3551.258Smartin20141026: 3561.259Smsaitoh A mishap during the import of pppd may cause your corruption 3571.258Smartin in your cvs directory if you happened to do a cvs update 3581.258Smartin during a short period of time. To fix, just remove the 3591.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3601.258Smartin and let cvs restore it on next update. 3611.258Smartin 3621.256Sapb20140721: 3631.256Sapb The src/external/mit/lua/src directory was accidentally created 3641.256Sapb and then deleted in the CVS repository. If you get errors like 3651.256Sapb 3661.256Sapb cvs [update aborted]: cannot open directory 3671.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3681.256Sapb 3691.256Sapb then delete your local copy of that directory tree and try again. 3701.256Sapb 3711.255Sjoerg20140530: 3721.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3731.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3741.255Sjoerg 3751.251Smartin20140131: 3761.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3771.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3781.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3791.251Smartin 3801.250Schristos20131227: 3811.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3821.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3831.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3841.250Schristos statements to avoid being exposed. 3851.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3861.250Schristos to make clean in libc 3871.250Schristos 3881.249Smrg20131129: 3891.249Smrg The GMP sources were updated, and builds will likely fail without 3901.249Smrg cleaning their build trees for both tools and in-tree, like below. 3911.249Smrg 3921.248Smrg20131128: 3931.248Smrg The MPC and MPFR sources were updated, and builds may require their 3941.248Smrg tools and in-tree directories cleaned for successful updates. 3951.248Smrg 3961.246Smartin20130605: 3971.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 3981.247Sspz to IPSEC (and the older IPSEC version removed). 3991.247Sspz 4001.247Sspz20130605: 4011.246Smartin Previous freetype installations eroneously installed private 4021.246Smartin header files. If you are building against a non-empty $DESTDIR, 4031.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 4041.246Smartin 4051.245Smrg20130531: 4061.245Smrg The xdm update may cause build failure due to xdm.man being 4071.245Smrg in the obj tree. Make sure to ensure any like this: 4081.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 4091.245Smrg is fixed by deleting the xdm.man in the obj tree. 4101.245Smrg 4111.244Smrg20130530: 4121.244Smrg Updates of many xsrc packages will leave old .pc files around. 4131.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 4141.244Smrg 4151.242Schristos20130301: 4161.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 4171.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 4181.242Schristos 4191.238Sdholland20120726: 4201.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 4211.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 4221.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 4231.241Swiz some cases may succeed and install broken OpenSSL libraries that 4241.240Sdholland cause third-party software to link incorrectly and/or crash. 4251.238Sdholland 4261.237Swiz20120507: 4271.241Swiz The database schema for makemandb was changed. You will 4281.237Swiz need to update the database using 'makemandb -f' or wait 4291.237Swiz for the next weekly run to fix it. 4301.237Swiz 4311.236Sbsh20120319: 4321.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 4331.236Sbsh size of db_symtab automatically. You need to update dbsym in 4341.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 4351.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 4361.236Sbsh mk.conf. 4371.236Sbsh 4381.235Sjoerg20120216: 4391.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 4401.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 4411.239Sdholland and 20120216, daily and weekly could have created an unreadable 4421.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4431.235Sjoerg the next run of weekly will fix it. 4441.233Sjoerg 4451.232Schristos20111227: 4461.232Schristos If you built between 20111225 and 20111227 you need to remove 4471.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4481.232Schristos bump has been reverted. 4491.232Schristos 4501.231Stls20111125: 4511.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4521.231Stls means it should no longer be explicitly listed in kernel 4531.231Stls configuration files. The line "pseudo-device rnd" should be 4541.231Stls removed from any custom kernel config files users may have. 4551.231Stls 4561.230Stls20111119: 4571.230Stls A problem with the datastructures used by the rndctl(8) 4581.230Stls utility (pointers in datastructures in an array, making 32->64 4591.230Stls bit compatibility very painful) has been fixed in a 4601.230Stls non-backwards-compatible way. If you replace your kernel, 4611.230Stls replace your rndctl executable too. 4621.241Swiz 4631.229Sjym20111001: 4641.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4651.229Sjym changed and their new version is not backward compatible with the old 4661.241Swiz one. So ensure that all consumers of these functions (currently: 4671.229Sjym quota2 code and its tests) are updated together with the new lib. 4681.229Sjym 4691.228Smrg20110817: 4701.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4711.228Smrg DESTDIR for them should be deleted before updating. 4721.228Smrg 4731.227Sriastrad20110806: 4741.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4751.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4761.227Sriastrad 4771.226Smrg20110805: 4781.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4791.226Smrg the tree to be cleaned. Best to delete both objdir and 4801.226Smrg DESTDIR before running this update. So far, only the 4811.226Smrg sparc64, mips and powerpc platforms have changed. 4821.226Smrg 4831.225Smatt20110803: 4841.241Swiz The layout of external/public-domain/xz has changed. To do an 4851.225Smatt update build you will have to remove the contents of the OBJDIR 4861.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4871.225Smatt is now a directory. 4881.225Smatt 4891.223Sjoerg20110410: 4901.241Swiz The configuration of src/tools/gcc has changed. To do an 4911.224Sdholland update build you have to clean both tools/binutils and 4921.224Sdholland tools/gcc by hand. 4931.223Sjoerg 4941.222Splunky20110328: 4951.222Splunky Building the Xorg binary was moved into a subdirectory to fix 4961.241Swiz ordering issues with "make all". It may be necessary to remove 4971.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 4981.222Splunky if your update build fails, as the "Xorg" entry there is now a 4991.222Splunky directory. 5001.222Splunky 5011.220Sjoerg20110121: 5021.221Slukem Assembler files no longer use -traditional-cpp. This can break 5031.220Sjoerg the build of individual parts of the tree. This is handled 5041.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 5051.220Sjoerg and re-run config(1) for any kernel configurations as needed. 5061.218Sjoerg 5071.217Sjruoho20101217: 5081.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 5091.241Swiz by default. It may be necessary to manually update passwd(5) and 5101.217Sjruoho group(5) in order to make the program work with existing setups. 5111.217Sjruoho 5121.216Schristos20101125: 5131.216Schristos The latest changes to setenv(3) dissallow setting environment 5141.241Swiz variables with names that contain '='. Revision 1.18 of env.c 5151.241Swiz assumed that this was allowed. Installing a new libc with an 5161.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 5171.216Schristos break which affects the autoconf tests for dependency finding, 5181.216Schristos so building gcc will end up printing: 5191.216Schristos checking dependency style of gcc... none 5201.216Schristos configure: error: no usable dependency style found 5211.216Schristos Fix it by rebuilding and re-installing env. 5221.138Slukem 5231.215Smrg20101119: 5241.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 5251.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 5261.215Smrg have any build problems with xsrc, or problems with mismatched 5271.215Smrg versions between xorg-server and drivers. 5281.215Smrg 5291.213Sjmmv20100604: 5301.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 5311.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 5321.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 5331.213Sjmmv trees by hand. 5341.213Sjmmv 5351.211Stnozaki20100522: 5361.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 5371.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 5381.212Smrg build problems with xsrc. 5391.212Smrg 5401.212Smrg20100522: 5411.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 5421.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5431.211Stnozaki 5441.210Schristos20100520: 5451.241Swiz The location of the xkb compiled descriptions has changed. Please 5461.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5471.210Schristos 5481.209Snjoly20100222: 5491.209Snjoly The shared objects file extension has been changed from .so to 5501.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5511.209Snjoly libXX.so. All now stale regular .so files can be removed from 5521.209Snjoly your object directories. 5531.209Snjoly 5541.208Sroy20100204: 5551.208Sroy The termcap database has been removed from the sources, 5561.208Sroy but has not been marked obsolete so it is not removed 5571.208Sroy from the system when upgrading. 5581.208Sroy As such, you will need to remove them from your object 5591.208Sroy and destination directories. 5601.208Sroy 5611.203Sdyoung20091101: 5621.205Sdholland After updating, it may be necessary to make the 'cleandir' 5631.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5641.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5651.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5661.203Sdyoung 5671.202Smrg20091001: 5681.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5691.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5701.206Sdholland 5711.206Sdholland20091001: 5721.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5731.202Smrg symlink, failing the build. Delete the link, and the subdir 5741.202Smrg it is in, and retry your build. 5751.202Smrg 5761.201Sdsl20090718: 5771.201Sdsl libc build changed so that strchr() provides the extra entry 5781.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5791.201Sdsl may fail because the archive contains the unwanted index.o. 5801.201Sdsl (Similarly for strrchr() and rindex().) 5811.201Sdsl 5821.198Smrg20090709: 5831.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5841.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5851.198Smrg 5861.197Smrg20090616: 5871.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 5881.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 5891.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 5901.197Smrg subdirectory has been changed into a file, and this needs to 5911.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 5921.197Smrg 5931.195Sperry20090501: 5941.195Sperry Several new functions were added to string.h/libc, and this 5951.195Sperry can cause autoconf problems during the tool build for people 5961.241Swiz who fail to clean out their tools objects properly. If you 5971.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 5981.195Sperry failure during the tool build, clean out all your tools 5991.195Sperry objects and start again. 6001.195Sperry 6011.194Smrg20090325: 6021.194Smrg The i386 port was switched to i486 default toolchain. This requires 6031.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 6041.194Smrg 6051.192Sskrll20090126: 6061.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 6071.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 6081.207Smbalmer to avoid using the old assembly stub. 6091.192Sskrll 6101.191Sjoerg20090202: 6111.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 6121.191Sjoerg detection. It is recommented to rebuild the cache with 6131.191Sjoerg ``pkg_admin rebuild''. 6141.191Sjoerg 6151.184Schristos20090110: 6161.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 6171.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 6181.188Schristos This is needed even in the MODULAR kernel because there is 6191.188Schristos conditionally compiled code in rtsock.c. 6201.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 6211.184Schristos before installing. 6221.184Schristos 3. If you don't use build.sh and you build directly to root, and 6231.241Swiz your build breaks in the middle, don't despair. Make sure headers 6241.184Schristos are installed properly, and start building libraries first libc 6251.184Schristos and libutil, install them and then continue building all the 6261.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 6271.184Schristos the new libraries are installed, you can restart the build. 6281.184Schristos 4. If you compile packages and you notice link time warnings, 6291.189Shubertf rebuild the required packages to update their shared libraries. 6301.189Shubertf Any package you rebuild will require rebuilding all the packages 6311.189Shubertf that depend on it. 6321.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 6331.186Schristos will be upgraded and it will not be backwards compatible. 6341.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 6351.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 6361.241Swiz for utmp. You are better off removing the old files after 6371.190Sapb upgrading. The automated clearing of /var/run during 6381.190Sapb boot, and the automated rotating of files in /var/log by 6391.190Sapb newsyslog(8), may mean that you do not have to remove the 6401.190Sapb files manually. 6411.190Sapb 7. The optional accounting file (/var/account/acct, see 6421.190Sapb accton(8)) has not been versioned, and will need to be 6431.190Sapb removed. The automatic rotation of the accounting file by 6441.190Sapb /etc/daily limits the bad consequences of failure to remove 6451.190Sapb the file. 6461.196Sdholland 8. Application software that writes time_t to binary files on 6471.241Swiz disk will break or need attention. Most notably: if you are 6481.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6491.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6501.185Sjmcneill 6511.183Spgoyette20081219: 6521.183Spgoyette config(1) has been updated, and one of the files it creates - 6531.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6541.183Spgoyette (done automatically by build.sh) and then you need to rerun 6551.183Spgoyette config on all kernel configuration files before rebuilding those 6561.183Spgoyette kernels. 6571.183Spgoyette 6581.181Scube20081205: 6591.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6601.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6611.181Scube set and will appear as extra files for MKX11=no update builds. 6621.178Slukem 6631.179Stsutsui20081122: 6641.182Stsutsui On i386, various kernel options(4) in GENERIC including 6651.180Swiz file systems have been disabled and moved into kernel modules. 6661.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6671.179Stsutsui following files as well as a new GENERIC kernel: 6681.179Stsutsui 6691.179Stsutsui - build and install kernel modules from src/sys/modules 6701.179Stsutsui 6711.179Stsutsui - install the latest bootloader, which will load a module 6721.180Swiz for the file system from which the kernel is loaded automatically 6731.179Stsutsui 6741.180Swiz If you have to load your kernel from a file system which is not of 6751.180Swiz the same type as the root file system, you have to load the necessary 6761.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6771.179Stsutsui 6781.178Slukem20080827: 6791.178Slukem If you built and installed a libc from sources between 6801.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6811.178Slukem which results in false errors reported by lint(1). 6821.178Slukem Since this breaks the libc build itself, manual help is 6831.180Swiz needed -- lint must be disabled temporarily, e.g.: 6841.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6851.178Slukem 6861.177Schristos20080813: 6871.177Schristos MKDEBUG build was broken because the .depend files did not know 6881.241Swiz about .go files. You need to remove all .depend files and rebuild. 6891.177Schristos 6901.200Sdholland20080802: 6911.200Sdholland A regression in binary compatibility for pthread_mutex_t has 6921.241Swiz been fixed. Unfortunately, the price is breaking compatibility 6931.200Sdholland for -current. 6941.200Sdholland 6951.200Sdholland Threaded programs (using libpthread) and C++ programs (using 6961.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 6971.200Sdholland be recompiled. 6981.200Sdholland 6991.200Sdholland One way to find affected pkgsrc packages: 7001.200Sdholland 7011.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 7021.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 7031.200Sdholland 7041.175Ssimonb20080731: 7051.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 7061.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 7071.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 7081.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 7091.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 7101.176Ssimonb also requires the super block to be in the UFS2 format. You 7111.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 7121.175Ssimonb 7131.174Slukem20080721: 7141.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 7151.174Slukem isn't defined. 7161.174Slukem 7171.173Sfreza20080531: 7181.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 7191.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 7201.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 7211.241Swiz won't work correctly. The following sequence of commands: 7221.173Sfreza 7231.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 7241.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 7251.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 7261.173Sfreza 7271.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 7281.173Sfreza 7291.172Slukem20080503: 7301.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 7311.172Slukem 7321.171She20080521: 7331.171She For a while, unprivileged UPDATE builds would fail to 7341.171She succeed at the checkflist stage, complaining that 7351.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 7361.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 7371.171She If you already hit this problem, update the .mk file, 7381.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 7391.171She 7401.174Slukem20080303: 7411.174Slukem Linker warnings are now fatal if $WARNS>0. 7421.174Slukem 7431.170Schristos20080126: 7441.170Schristos The posix_fadvise system call has been changed from an assembly 7451.241Swiz stub, to a c file that calls an assembly stub. You need to 7461.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7471.170Schristos avoid using the old assembly stub. 7481.170Schristos 7491.168Sjoerg20071209: 7501.241Swiz The acpiec(4) driver has been split into two attachments. If you 7511.168Sjoerg get ACPI errors before the attachment, please update your kernel 7521.169Swiz configuration file appropriately or see GENERIC for more details. 7531.168Sjoerg 7541.166Sxtraeme20071115: 7551.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7561.166Sxtraeme argument specified in the kernel configuration file is not valid 7571.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7581.241Swiz rather than the EC address port. Please update your kernel 7591.167Swiz configuration file appropriately or see GENERIC for more details. 7601.166Sxtraeme 7611.165Sjmmv20071028: 7621.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7631.165Sjmmv You need to update any custom kernel configuration file you have 7641.165Sjmmv to remove any references to pccons (which includes removing the 7651.165Sjmmv now useless XSERVER option) and replace them with the correct 7661.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7671.165Sjmmv for more details. 7681.165Sjmmv 7691.164Sgdt20070913: 7701.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7711.164Sgdt enumerate interfaces was fixed. The bug began to cause 7721.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7731.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7741.164Sgdt could not enumerate interfaces. (These are noted because 7751.164Sgdt normal kernel/userspace version matching hygiene is not 7761.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7771.164Sgdt and userland are from after 20070913. 7781.164Sgdt 7791.163Sjoerg20070703: 7801.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7811.199Sdholland calls the target-specific strip program, and the logic to pass 7821.199Sdholland down STRIP from make has been removed. This requires a 7831.199Sdholland re-installation of tools. 7841.163Sjoerg 7851.161Sdsl20070422: 7861.161Sdsl The way OS emulations lookup filenames inside the emulation root 7871.161Sdsl has been changed. Rather than modify the pathname (and copy back 7881.161Sdsl to userspace) namei() and lookup() directly check the emulation 7891.241Swiz root. One side effect is that absolute symlinks inside the emulated 7901.167Swiz root file system will be relative to that file system - unless they 7911.161Sdsl start /../ this is useful when the emulated root is a real install 7921.161Sdsl that has such links. 7931.161Sdsl This might affect symlinks that have been added to reference outside 7941.161Sdsl the emulated root. 7951.161Sdsl 7961.160Sjmcneill20070412: 7971.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 7981.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 7991.160Sjmcneill example. 8001.160Sjmcneill 8011.159Sgdt20070319: 8021.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 8031.159Sgdt on many platforms due to incorrect flags settings. If you 8041.159Sgdt updated and built after about 20070315, do "nbmake-$arch 8051.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 8061.159Sgdt rebuild of object files that might have been built 8071.159Sgdt incorrectly, and ensure that you have at least 8081.159Sgdt src/lib/libc/Makefile 1.130. 8091.159Sgdt 8101.241Swiz20070210: 8111.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 8121.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 8131.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 8141.158Sdbj will allow dependencies on those files to get get rebuilt 8151.158Sdbj 8161.157Sapb20070209: 8171.157Sapb The threading model was changed when the newlock2 branch 8181.157Sapb was merged to NetBSD-current. If you boot with a new 8191.157Sapb kernel (version 4.99.10), then you also need a new pthread 8201.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 8211.157Sapb an old kernel, then you need the old pthread library 8221.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 8231.157Sapb the pthread library in sync, old threaded applications should 8241.157Sapb continue to work with an old or new kernel. Note that named(8) 8251.157Sapb is the only threaded application in the base system. 8261.157Sapb 8271.154She20061214: 8281.154She Following the move of string_to_flags() and flags_to_string() 8291.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 8301.154She will need to do a "make cleandir" in 8311.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 8321.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 8331.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 8341.156She as the installation images in distrib/ 8351.154She in order to excise stale references to the old stat_flags.h header 8361.154She file in the ls sources -- stat_flags.h has been removed. 8371.154She 8381.152Schristos20061108: 8391.152Schristos The configure script used in the src/tools/gcc compiler has been 8401.152Schristos changed to indicate that our libc has ssp support built-in and 8411.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8421.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8431.152Schristos 8441.151Srpaulo20061009: 8451.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8461.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8471.151Srpaulo 8481.150Sbjh2120060814: 8491.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8501.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8511.150Sbjh21 kernel configuration for an example. X servers from the last 8521.150Sbjh21 few years should cope. 8531.150Sbjh21 8541.149Schristos20060703: 8551.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8561.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8571.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8581.149Schristos 8591.148Sdogcow20060627: 8601.148Sdogcow socket(2) has changed, and its system call has been versioned. 8611.148Sdogcow For userlands with the old version of socket(2), make sure that 8621.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8631.148Sdogcow errors will result. 8641.148Sdogcow 8651.1SabsHints for a more successful build: 8661.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8671.123Sjmc Use build.sh, but do not use its "expert mode": 8681.132Sjmmv This will automatically build the tools in the 8691.123Sjmc correct order, and it will keep the tools and the 8701.123Sjmc new build products from interfering with the running 8711.123Sjmc system. This will allow you to ignore most of the 8721.123Sjmc other advice in this file. 8731.2Smrg Build a new kernel first: 8741.2Smrg This makes sure that any new system calls or features 8751.2Smrg expected by the new userland will be present. This 8761.2Smrg helps to avoid critical errors when upgrading. 8771.1Sabs Use object directories: 8781.1Sabs This helps to keep stale object 8791.1Sabs files from polluting the build if a Makefile "forgets" 8801.1Sabs about one. It also makes it easier to clean up after 8811.1Sabs a build. It's also necessary if you want to use the 8821.1Sabs same source tree for multiple machines. 8831.123Sjmc To use object directories with build.sh: 8841.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8851.123Sjmc To use object directories without using build.sh: 8861.1Sabs a) cd /usr/src ; make cleandir 8871.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8881.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8891.1Sabs d) cd /usr/src ; make build 8901.2Smrg Note that running "make obj" in a directory will create 8911.2Smrg in obj.$MACHINE directory. 8921.1Sabs Build to a DESTDIR: 8931.123Sjmc This helps to keep old installed files (especially libraries) 8941.123Sjmc from interfering with the new build. 8951.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8961.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8971.123Sjmc environment variable before running make build. It should be 8981.123Sjmc set to the pathname of an initially empty directory. 8991.123Sjmc Problems: if you do not use build.sh, you might need to 9001.123Sjmc update critical utilities without using DESTDIR since 9011.123Sjmc nothing is executed from what is installed in DESTDIR. 9021.123Sjmc (See critical utils, below.) 9031.1Sabs Build often: 9041.1Sabs This keeps critical utilities current enough to not choke 9051.1Sabs on any other part of the source tree that depends on up to 9061.123Sjmc date functionality. If you use build.sh, you should not have 9071.123Sjmc this problem. 9081.241Swiz 9091.1SabsWhat to do if things don't work: 9101.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9111.230StlsWhen things don't work there are usually a few things that commonly 9121.1Sabsshould be done. 9131.1Sabs 1) make includes 9141.1Sabs This should be done automatically by make build. 9151.1Sabs 2) cd share/mk && make install 9161.1Sabs Again, automatically done by make build. 9171.1Sabs 9181.1SabsFailsafe rebuild of a small part of the tree: 9191.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9201.1SabsTo make sure you rebuild something correctly you want to do 9211.1Sabssomething like the following: 9221.1Sabs 1) Make sure the includes and .mk files are up to date. 9231.1Sabs 2) Make sure any program used to build the particular 9241.1Sabs utility is up to date. (yacc, lex, etc...) 9251.1Sabs 3) cd ...path/to/util... 9261.1Sabs make cleandir 9271.1Sabs rm ...all obj directories... 9281.1Sabs make cleandir # yes, again 9291.1Sabs make obj 9301.1Sabs make depend && make 9311.1Sabs 9321.1SabsFailsafe rebuild of the entire tree: 9331.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9341.1SabsIf you really want to make sure the source tree is clean and 9351.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 9361.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 9371.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 9381.1Sabs 9391.1Sabs---cut here--- 9401.1Sabs#!/bin/sh 9411.1Sabs. /etc/mk.conf 9421.1Sabs 9431.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9441.58Slukem NETBSDSRCDIR=/usr/src 9451.1Sabsfi 9461.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9471.1Sabs echo Unable to find sources 9481.1Sabs exit 1 9491.1Sabsfi 9501.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9511.1Sabs 9521.1Sabsif [ -z $BSDOBJDIR ] ; then 9531.1Sabs BSDOBJDIR=/usr/obj 9541.1Sabsfi 9551.1Sabsif [ -d $BSDOBJDIR ] ; then 9561.1Sabs rm -rf $BSDOBJDIR 9571.1Sabsfi 9581.1Sabs 9591.58Slukemcd $NETBSDSRCDIR && make cleandir 9601.1Sabs 9611.1Sabs---cut here--- 9621.1Sabs 9631.1SabsCritical utilities: 9641.1Sabs^^^^^^^^^^^^^^^^^^^ 9651.3Sitojun usr.bin/compile_et 9661.1Sabs usr.bin/make 9671.1Sabs usr.bin/yacc 9681.1Sabs usr.bin/lex 9691.11Slukem usr.bin/xlint 9701.142Sdrochner usr.bin/config 9711.1Sabs 9721.34SsimonbOther problems and possible solutions: 9731.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9741.1SabsSymptom:Complaints involving a Makefile. 9751.17SerhFix: Rebuild usr.bin/make: 9761.17Serh cd usr.bin/make && make && make install 9771.111Ssimonb Or, a failsafe method if that doesn't work: 9781.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9791.17Serh 9801.1SabsFix: Make sure .mk files are up to date. 9811.1Sabs cd share/mk && make install 9821.2Smrg 9831.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9841.142SdrochnerFix: Rebuild usr.bin/config 9851.1Sabs 9861.1SabsSymptom: 9871.1SabsFix: Rebuild usr.bin/yacc 9881.1Sabs 9891.1SabsSymptom: 9901.1SabsFix: Rebuild usr.bin/lex 9911.1Sabs 9921.1SabsSymptom: 9931.1SabsFix: rm /usr/lib/libbfd.a 9941.4Sitojun 9951.4SitojunSymptom:Obsolete intermediate files are used during compilation 9961.4SitojunFix: Try the following sequence of commands in the directory in question. 9971.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9981.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9991.4Sitojun may remain. The command tries to clean everything up) 10001.5Swiz 10011.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 10021.207Smbalmer pointer type 10031.5SwizFix: Rebuild and install usr.bin/menuc 10041.12Sitojun 10051.12SitojunSymptom:mklocale not found during build in share/locale/ctype 10061.12SitojunFix: Build and install usr.bin/mklocale 10071.13Sdogcow 10081.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 10091.13SdogcowFix: Rebuild and install lib/libc 10101.13Sdogcow 10111.142SdrochnerSymptom:usr.bin/config fails to build. 10121.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 10131.13Sdogcow 10141.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 10151.19ScgdFix: Rebuild and install lib/libc 10161.24Sabs 10171.24SabsSymptom:lint does not understand the '-X' option 10181.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 10191.223Sjoerg 10201.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 10211.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 10221.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 10231.257Sapb 10241.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 10251.257Sapb No such file or directory. 10261.257SapbCause: If a directory is created by mistake, then it is sometimes 10271.257Sapb deleted from the CVS repository using administrative commands 10281.257Sapb that bypass the normal cvs access controls. If your cvs working tree 10291.257Sapb contains references to a directory that has been deleted on the 10301.257Sapb server in this way, then "cvs update" reports this error. 10311.257SapbFix: Recursively delete the affected directory from your working tree 10321.257Sapb and try the update again. 1033