UPDATING revision 1.314
11.314Smrg$NetBSD: UPDATING,v 1.314 2020/09/12 08:31:39 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.314Smrg20200912: 231.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 241.314Smrg for several more, as will binutils 2.34. Clean as required. 251.314Smrg 261.313Smrg20200907: 271.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 281.313Smrg probably requires cleaning the tools/binutils. 291.313Smrg 301.311Smrg20200811: 311.312Smrg GCC updates may require cleaning the objdir. This may occur 321.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 331.312Smrg GCC 9 upgrade. 341.311Smrg 351.309Schristos20200614: 361.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 371.310Schristos should handle the migration 381.309Schristos 391.308Schristos20200601: 401.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 411.308Schristos created in the build directories and need cleaning. 421.308Schristos 431.307Smrg20200311: 441.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 451.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 461.307Smrg 471.306Schristos20191118: 481.306Schristos More architectures were switched to gcc8: 491.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 501.306Schristos The same comments as in 20191022 apply. 511.306Schristos 521.305Smartin20191112: 531.305Smartin The LLVM update requires a clean rebuild for all architectures using 541.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 551.305Smartin 561.304Smartin20191022: 571.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 581.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 591.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 601.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 611.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 621.304Smartin daily builds and install that before doing the next in-place build. 631.304Smartin 641.303Smrg20191001: 651.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 661.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 671.303Smrg directory, and also clean src/external/gpl3/gcc. 681.303Smrg 691.302Sriastrad20190903: 701.306Schristos Files with names that coincide with existing files' names on 711.302Sriastrad case-insensitive file systems were inadvertently committed, for 721.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 731.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 741.302Sriastrad ran build.sh distribution or ran build.sh release, you must 751.302Sriastrad manually delete the following files in your DESTDIR (which is 761.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 771.302Sriastrad them: 781.302Sriastrad 791.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 801.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 811.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 821.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 831.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 841.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 851.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 861.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 871.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 881.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 891.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 901.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 911.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 921.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 931.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 941.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 951.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 961.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 971.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 981.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 991.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 1001.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 1011.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 1021.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 1031.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 1041.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 1051.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 1061.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 1071.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 1081.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 1091.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 1101.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 1111.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 1121.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 1131.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 1141.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 1151.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 1161.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 1171.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 1181.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 1191.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 1201.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1211.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1221.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1231.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1241.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1251.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1261.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1271.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1281.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1291.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1301.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1311.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1321.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1331.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1341.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1351.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1361.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1371.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1381.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1391.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1401.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1411.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1421.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1431.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1441.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1451.302Sriastrad 1461.302Sriastrad We will re-import these radeon firmware images another way 1471.302Sriastrad later. 1481.302Sriastrad 1491.301Smartin20190727: 1501.301Smartin The uefi bootloader has gained tftp support and needs a clean 1511.301Smartin build. If you do update builds, manually clean its object 1521.301Smartin directory by something like: 1531.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1541.301Smartin 1551.300Smartin20190723: 1561.300Smartin The jemalloc allocator in libc is now build without extended 1571.300Smartin debugging (for performance reasons). In update builds make sure 1581.300Smartin to rebuild it completly, by removing all affected object files, 1591.300Smartin including compat builds, something like: 1601.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1611.300Smartin 1621.299Smrg20190207: 1631.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1641.299Smrg 1651.298Smartin20180924: 1661.298Smartin A newer OpenSSL version has been imported. If you are doing 1671.298Smartin update builds, make sure to remove all old obj dirs, like: 1681.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 1691.298Smartin 1701.297Sjoerg20180717: 1711.297Sjoerg On aarch64 int64_t and related types have changed from long long 1721.297Sjoerg to long. This requires recompiling all C++ binaries. 1731.297Sjoerg 1741.296Smartin20180713: 1751.296Smartin On amd64 and i386 static binaries are now build position 1761.296Smartin independend. This requires recompilation of all object 1771.296Smartin files used to create the crunched /rescue binary. 1781.296Smartin Clean the rescue directory in your obj directory before 1791.296Smartin doing an update build, otherwise linking will fail. 1801.296Smartin 1811.293Sjakllsch20180414: 1821.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 1831.293Sjakllsch removal of tools/binutils objects directory may be required 1841.293Sjakllsch to fix tools build failure. 1851.293Sjakllsch 1861.292Smrg20180311: 1871.292Smrg bdftopcf was updated and may need cleaning in the 1881.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 1891.292Smrg link errors. 1901.292Smrg 1911.291Smrg20180212: 1921.291Smrg between OpenSSL and GCC updates, many things may fail to build. 1931.291Smrg any failure that looks like GCC or openssl is best handled by 1941.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 1951.291Smrg is recommended if build failures occur. 1961.291Smrg 1971.288Smartin20171225: 1981.288Smartin removal of the vadvise syscall requires manual removal of all 1991.288Smartin associated files from the libc build object directory (including 2001.289Schristos the .depend files) - a command like: 2011.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 2021.289Schristos For architectures that support multiple "compat" binary targets, 2031.289Schristos you'll need to cleanup both the regular libc directory and the 2041.290Smartin compat ones (the above command will do that). 2051.288Smartin 2061.287Skre20171010: 2071.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 2081.287Skre means that its objdir (or *.d and .depend at least) might need 2091.287Skre to be manually removed - or a build done once without -u. 2101.287Skre 2111.286Smrg20170822: 2121.286Smrg a new version of GMP has been imported and probably 2131.286Smrg will break parts of builds related to themselves or GCC, both 2141.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2151.286Smrg and MPC objdirs or build once without -u. 2161.286Smrg 2171.285Smrg20170816: 2181.285Smrg a new version of MPFR and MPC have been imported and probably 2191.285Smrg will break parts of builds related to themselves or GCC, both 2201.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2211.285Smrg and MPC objdirs or build once without -u. 2221.285Smrg 2231.284Smartin20170402: 2241.284Smartin a new version of dhcpcd has been imported, which does not support 2251.284Smartin update builds from the previous version. Remove your 2261.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2271.284Smartin 2281.281Sroy20170211: 2291.281Sroy a new terminfo database has been imported. 2301.281Sroy The structure of it has changed slightly from prior versions and 2311.281Sroy an updated tic tool is required. 2321.281Sroy If you build.sh, don't use -u 2331.281Sroy 2341.280Skre20170207: 2351.278Skre various arch dependent libc/exect.S files were removed 2361.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2371.279Skre if it exists) or do a clean build. 2381.279Skre (This is a bug in the make system, it should be corrected without 2391.279Skre human intervention, but isn't.) 2401.278Skre 2411.277Smartin20170104: 2421.277Smartin xinput build options have changed. 2431.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2441.277Smartin if you build.sh -u 2451.277Smartin 2461.276Smartin20170103: 2471.276Smartin a new version of flex has been imported. 2481.276Smartin Remove the file from obj (external/bsd/flex) 2491.276Smartin if you build.sh -u 2501.276Smartin 2511.275Sspz20161014: 2521.275Sspz a new version of OpenSSL has been imported. 2531.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2541.275Sspz if you build.sh -u 2551.275Sspz 2561.274Smartin20161009: 2571.274Smartin a new version of dhcpcd has been imported with slightly changed 2581.274Smartin build infrastructure. When doing a build.sh -u this requires 2591.274Smartin pruning the external/bsd/dhcpcd objdir. 2601.274Smartin 2611.273Smrg20160914: 2621.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2631.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2641.273Smrg and a clean objdir. 2651.273Smrg 2661.272Sdholland20160527: 2671.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 2681.272Sdholland been enabled. (see the amd64 entry two down for further info) 2691.272Sdholland 2701.270Schristos20160418: 2711.270Schristos libedit needs manual removal of all autogenerated files since 2721.271Schristos some of them are not autogenerated anymore. Remember that there 2731.271Schristos might be two copies of libedit if your platform builds "compat". 2741.270Schristos 2751.268Sriastrad20160410: 2761.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 2771.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 2781.268Sriastrad executables, means all code, including executables and not just 2791.268Sriastrad shared libraries, is position-independent and hence able to be 2801.268Sriastrad relocated by ASLR, address space layout randomization. 2811.268Sriastrad 2821.268Sriastrad The change was made in Makefile variables for compiler and 2831.268Sriastrad linker flags, for which make(1) does not record dependencies, 2841.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 2851.268Sriastrad 2861.268Sriastrad Partial rebuilds with some modified source files will likely 2871.268Sriastrad fail when linking executables, since the linker refuses to mix 2881.268Sriastrad position-independent code with position-dependent code in 2891.268Sriastrad position-independent executables: 2901.268Sriastrad 2911.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 2921.268Sriastrad 2931.267Smrg20160401: 2941.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 2951.269Sdholland Some people have found that cleandir is not sufficient, so if 2961.269Sdholland in doubt delete the entire object directory tree for gcc. 2971.267Smrg 2981.266Saymeric20160306: 2991.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 3001.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 3011.265Saymeric non-NetBSD hosts if linked with stale object files produced 3021.265Saymeric while they included a non-NetBSD regex.h. 3031.265Saymeric In any case, you should "make cleandir" at least these tools 3041.265Saymeric before updating your toolchain. 3051.265Saymeric 3061.264Smartin20160125: 3071.264Smartin Dtrace has been enabled by default on some architectures. 3081.264Smartin When doing an update build, make sure to clean the etc/mtree 3091.264Smartin object directory before starting the build - otherwise the 3101.264Smartin needed directories in destdir will not be created. 3111.264Smartin An easy way to do this is: 3121.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 3131.264Smartin 3141.263Sdholland20150818: 3151.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 3161.263Sdholland again. 3171.263Sdholland 3181.262Schristos20150413: 3191.262Schristos New acpica requires "make cleandir" and reinstalling yacc 3201.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3211.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3221.262Schristos 3231.261Smartin20150404: 3241.261Smartin Lint changes require a full rebuild of the tool, so make 3251.261Smartin sure to build without -u option to build.sh, or manually 3261.261Smartin do a make cleandir in src/tools/lint1 and 3271.261Smartin src/usr.bin/xlint. 3281.261Smartin 3291.260Sskrll20150310: 3301.260Sskrll Improvements to openssl for arm mean that update builds of 3311.260Sskrll the openssl libraries will fail. A make cleandir in 3321.260Sskrll external/bsd/openssl/lib is needed 3331.260Sskrll 3341.258Smartin20141026: 3351.259Smsaitoh A mishap during the import of pppd may cause your corruption 3361.258Smartin in your cvs directory if you happened to do a cvs update 3371.258Smartin during a short period of time. To fix, just remove the 3381.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3391.258Smartin and let cvs restore it on next update. 3401.258Smartin 3411.256Sapb20140721: 3421.256Sapb The src/external/mit/lua/src directory was accidentally created 3431.256Sapb and then deleted in the CVS repository. If you get errors like 3441.256Sapb 3451.256Sapb cvs [update aborted]: cannot open directory 3461.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3471.256Sapb 3481.256Sapb then delete your local copy of that directory tree and try again. 3491.256Sapb 3501.255Sjoerg20140530: 3511.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3521.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3531.255Sjoerg 3541.251Smartin20140131: 3551.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3561.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3571.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3581.251Smartin 3591.250Schristos20131227: 3601.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3611.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3621.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3631.250Schristos statements to avoid being exposed. 3641.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3651.250Schristos to make clean in libc 3661.250Schristos 3671.249Smrg20131129: 3681.249Smrg The GMP sources were updated, and builds will likely fail without 3691.249Smrg cleaning their build trees for both tools and in-tree, like below. 3701.249Smrg 3711.248Smrg20131128: 3721.248Smrg The MPC and MPFR sources were updated, and builds may require their 3731.248Smrg tools and in-tree directories cleaned for successful updates. 3741.248Smrg 3751.246Smartin20130605: 3761.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 3771.247Sspz to IPSEC (and the older IPSEC version removed). 3781.247Sspz 3791.247Sspz20130605: 3801.246Smartin Previous freetype installations eroneously installed private 3811.246Smartin header files. If you are building against a non-empty $DESTDIR, 3821.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 3831.246Smartin 3841.245Smrg20130531: 3851.245Smrg The xdm update may cause build failure due to xdm.man being 3861.245Smrg in the obj tree. Make sure to ensure any like this: 3871.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 3881.245Smrg is fixed by deleting the xdm.man in the obj tree. 3891.245Smrg 3901.244Smrg20130530: 3911.244Smrg Updates of many xsrc packages will leave old .pc files around. 3921.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 3931.244Smrg 3941.242Schristos20130301: 3951.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 3961.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 3971.242Schristos 3981.238Sdholland20120726: 3991.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 4001.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 4011.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 4021.241Swiz some cases may succeed and install broken OpenSSL libraries that 4031.240Sdholland cause third-party software to link incorrectly and/or crash. 4041.238Sdholland 4051.237Swiz20120507: 4061.241Swiz The database schema for makemandb was changed. You will 4071.237Swiz need to update the database using 'makemandb -f' or wait 4081.237Swiz for the next weekly run to fix it. 4091.237Swiz 4101.236Sbsh20120319: 4111.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 4121.236Sbsh size of db_symtab automatically. You need to update dbsym in 4131.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 4141.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 4151.236Sbsh mk.conf. 4161.236Sbsh 4171.235Sjoerg20120216: 4181.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 4191.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 4201.239Sdholland and 20120216, daily and weekly could have created an unreadable 4211.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4221.235Sjoerg the next run of weekly will fix it. 4231.233Sjoerg 4241.232Schristos20111227: 4251.232Schristos If you built between 20111225 and 20111227 you need to remove 4261.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4271.232Schristos bump has been reverted. 4281.232Schristos 4291.231Stls20111125: 4301.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4311.231Stls means it should no longer be explicitly listed in kernel 4321.231Stls configuration files. The line "pseudo-device rnd" should be 4331.231Stls removed from any custom kernel config files users may have. 4341.231Stls 4351.230Stls20111119: 4361.230Stls A problem with the datastructures used by the rndctl(8) 4371.230Stls utility (pointers in datastructures in an array, making 32->64 4381.230Stls bit compatibility very painful) has been fixed in a 4391.230Stls non-backwards-compatible way. If you replace your kernel, 4401.230Stls replace your rndctl executable too. 4411.241Swiz 4421.229Sjym20111001: 4431.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4441.229Sjym changed and their new version is not backward compatible with the old 4451.241Swiz one. So ensure that all consumers of these functions (currently: 4461.229Sjym quota2 code and its tests) are updated together with the new lib. 4471.229Sjym 4481.228Smrg20110817: 4491.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4501.228Smrg DESTDIR for them should be deleted before updating. 4511.228Smrg 4521.227Sriastrad20110806: 4531.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4541.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4551.227Sriastrad 4561.226Smrg20110805: 4571.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4581.226Smrg the tree to be cleaned. Best to delete both objdir and 4591.226Smrg DESTDIR before running this update. So far, only the 4601.226Smrg sparc64, mips and powerpc platforms have changed. 4611.226Smrg 4621.225Smatt20110803: 4631.241Swiz The layout of external/public-domain/xz has changed. To do an 4641.225Smatt update build you will have to remove the contents of the OBJDIR 4651.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4661.225Smatt is now a directory. 4671.225Smatt 4681.223Sjoerg20110410: 4691.241Swiz The configuration of src/tools/gcc has changed. To do an 4701.224Sdholland update build you have to clean both tools/binutils and 4711.224Sdholland tools/gcc by hand. 4721.223Sjoerg 4731.222Splunky20110328: 4741.222Splunky Building the Xorg binary was moved into a subdirectory to fix 4751.241Swiz ordering issues with "make all". It may be necessary to remove 4761.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 4771.222Splunky if your update build fails, as the "Xorg" entry there is now a 4781.222Splunky directory. 4791.222Splunky 4801.220Sjoerg20110121: 4811.221Slukem Assembler files no longer use -traditional-cpp. This can break 4821.220Sjoerg the build of individual parts of the tree. This is handled 4831.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 4841.220Sjoerg and re-run config(1) for any kernel configurations as needed. 4851.218Sjoerg 4861.217Sjruoho20101217: 4871.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 4881.241Swiz by default. It may be necessary to manually update passwd(5) and 4891.217Sjruoho group(5) in order to make the program work with existing setups. 4901.217Sjruoho 4911.216Schristos20101125: 4921.216Schristos The latest changes to setenv(3) dissallow setting environment 4931.241Swiz variables with names that contain '='. Revision 1.18 of env.c 4941.241Swiz assumed that this was allowed. Installing a new libc with an 4951.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 4961.216Schristos break which affects the autoconf tests for dependency finding, 4971.216Schristos so building gcc will end up printing: 4981.216Schristos checking dependency style of gcc... none 4991.216Schristos configure: error: no usable dependency style found 5001.216Schristos Fix it by rebuilding and re-installing env. 5011.138Slukem 5021.215Smrg20101119: 5031.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 5041.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 5051.215Smrg have any build problems with xsrc, or problems with mismatched 5061.215Smrg versions between xorg-server and drivers. 5071.215Smrg 5081.213Sjmmv20100604: 5091.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 5101.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 5111.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 5121.213Sjmmv trees by hand. 5131.213Sjmmv 5141.211Stnozaki20100522: 5151.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 5161.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 5171.212Smrg build problems with xsrc. 5181.212Smrg 5191.212Smrg20100522: 5201.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 5211.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5221.211Stnozaki 5231.210Schristos20100520: 5241.241Swiz The location of the xkb compiled descriptions has changed. Please 5251.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5261.210Schristos 5271.209Snjoly20100222: 5281.209Snjoly The shared objects file extension has been changed from .so to 5291.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5301.209Snjoly libXX.so. All now stale regular .so files can be removed from 5311.209Snjoly your object directories. 5321.209Snjoly 5331.208Sroy20100204: 5341.208Sroy The termcap database has been removed from the sources, 5351.208Sroy but has not been marked obsolete so it is not removed 5361.208Sroy from the system when upgrading. 5371.208Sroy As such, you will need to remove them from your object 5381.208Sroy and destination directories. 5391.208Sroy 5401.203Sdyoung20091101: 5411.205Sdholland After updating, it may be necessary to make the 'cleandir' 5421.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5431.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5441.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5451.203Sdyoung 5461.202Smrg20091001: 5471.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5481.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5491.206Sdholland 5501.206Sdholland20091001: 5511.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5521.202Smrg symlink, failing the build. Delete the link, and the subdir 5531.202Smrg it is in, and retry your build. 5541.202Smrg 5551.201Sdsl20090718: 5561.201Sdsl libc build changed so that strchr() provides the extra entry 5571.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5581.201Sdsl may fail because the archive contains the unwanted index.o. 5591.201Sdsl (Similarly for strrchr() and rindex().) 5601.201Sdsl 5611.198Smrg20090709: 5621.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5631.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5641.198Smrg 5651.197Smrg20090616: 5661.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 5671.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 5681.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 5691.197Smrg subdirectory has been changed into a file, and this needs to 5701.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 5711.197Smrg 5721.195Sperry20090501: 5731.195Sperry Several new functions were added to string.h/libc, and this 5741.195Sperry can cause autoconf problems during the tool build for people 5751.241Swiz who fail to clean out their tools objects properly. If you 5761.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 5771.195Sperry failure during the tool build, clean out all your tools 5781.195Sperry objects and start again. 5791.195Sperry 5801.194Smrg20090325: 5811.194Smrg The i386 port was switched to i486 default toolchain. This requires 5821.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 5831.194Smrg 5841.192Sskrll20090126: 5851.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 5861.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 5871.207Smbalmer to avoid using the old assembly stub. 5881.192Sskrll 5891.191Sjoerg20090202: 5901.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 5911.191Sjoerg detection. It is recommented to rebuild the cache with 5921.191Sjoerg ``pkg_admin rebuild''. 5931.191Sjoerg 5941.184Schristos20090110: 5951.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 5961.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 5971.188Schristos This is needed even in the MODULAR kernel because there is 5981.188Schristos conditionally compiled code in rtsock.c. 5991.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 6001.184Schristos before installing. 6011.184Schristos 3. If you don't use build.sh and you build directly to root, and 6021.241Swiz your build breaks in the middle, don't despair. Make sure headers 6031.184Schristos are installed properly, and start building libraries first libc 6041.184Schristos and libutil, install them and then continue building all the 6051.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 6061.184Schristos the new libraries are installed, you can restart the build. 6071.184Schristos 4. If you compile packages and you notice link time warnings, 6081.189Shubertf rebuild the required packages to update their shared libraries. 6091.189Shubertf Any package you rebuild will require rebuilding all the packages 6101.189Shubertf that depend on it. 6111.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 6121.186Schristos will be upgraded and it will not be backwards compatible. 6131.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 6141.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 6151.241Swiz for utmp. You are better off removing the old files after 6161.190Sapb upgrading. The automated clearing of /var/run during 6171.190Sapb boot, and the automated rotating of files in /var/log by 6181.190Sapb newsyslog(8), may mean that you do not have to remove the 6191.190Sapb files manually. 6201.190Sapb 7. The optional accounting file (/var/account/acct, see 6211.190Sapb accton(8)) has not been versioned, and will need to be 6221.190Sapb removed. The automatic rotation of the accounting file by 6231.190Sapb /etc/daily limits the bad consequences of failure to remove 6241.190Sapb the file. 6251.196Sdholland 8. Application software that writes time_t to binary files on 6261.241Swiz disk will break or need attention. Most notably: if you are 6271.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6281.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6291.185Sjmcneill 6301.183Spgoyette20081219: 6311.183Spgoyette config(1) has been updated, and one of the files it creates - 6321.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6331.183Spgoyette (done automatically by build.sh) and then you need to rerun 6341.183Spgoyette config on all kernel configuration files before rebuilding those 6351.183Spgoyette kernels. 6361.183Spgoyette 6371.181Scube20081205: 6381.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6391.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6401.181Scube set and will appear as extra files for MKX11=no update builds. 6411.178Slukem 6421.179Stsutsui20081122: 6431.182Stsutsui On i386, various kernel options(4) in GENERIC including 6441.180Swiz file systems have been disabled and moved into kernel modules. 6451.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6461.179Stsutsui following files as well as a new GENERIC kernel: 6471.179Stsutsui 6481.179Stsutsui - build and install kernel modules from src/sys/modules 6491.179Stsutsui 6501.179Stsutsui - install the latest bootloader, which will load a module 6511.180Swiz for the file system from which the kernel is loaded automatically 6521.179Stsutsui 6531.180Swiz If you have to load your kernel from a file system which is not of 6541.180Swiz the same type as the root file system, you have to load the necessary 6551.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6561.179Stsutsui 6571.178Slukem20080827: 6581.178Slukem If you built and installed a libc from sources between 6591.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6601.178Slukem which results in false errors reported by lint(1). 6611.178Slukem Since this breaks the libc build itself, manual help is 6621.180Swiz needed -- lint must be disabled temporarily, e.g.: 6631.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6641.178Slukem 6651.177Schristos20080813: 6661.177Schristos MKDEBUG build was broken because the .depend files did not know 6671.241Swiz about .go files. You need to remove all .depend files and rebuild. 6681.177Schristos 6691.200Sdholland20080802: 6701.200Sdholland A regression in binary compatibility for pthread_mutex_t has 6711.241Swiz been fixed. Unfortunately, the price is breaking compatibility 6721.200Sdholland for -current. 6731.200Sdholland 6741.200Sdholland Threaded programs (using libpthread) and C++ programs (using 6751.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 6761.200Sdholland be recompiled. 6771.200Sdholland 6781.200Sdholland One way to find affected pkgsrc packages: 6791.200Sdholland 6801.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 6811.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 6821.200Sdholland 6831.175Ssimonb20080731: 6841.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 6851.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 6861.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 6871.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 6881.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 6891.176Ssimonb also requires the super block to be in the UFS2 format. You 6901.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 6911.175Ssimonb 6921.174Slukem20080721: 6931.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 6941.174Slukem isn't defined. 6951.174Slukem 6961.173Sfreza20080531: 6971.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 6981.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 6991.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 7001.241Swiz won't work correctly. The following sequence of commands: 7011.173Sfreza 7021.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 7031.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 7041.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 7051.173Sfreza 7061.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 7071.173Sfreza 7081.172Slukem20080503: 7091.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 7101.172Slukem 7111.171She20080521: 7121.171She For a while, unprivileged UPDATE builds would fail to 7131.171She succeed at the checkflist stage, complaining that 7141.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 7151.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 7161.171She If you already hit this problem, update the .mk file, 7171.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 7181.171She 7191.174Slukem20080303: 7201.174Slukem Linker warnings are now fatal if $WARNS>0. 7211.174Slukem 7221.170Schristos20080126: 7231.170Schristos The posix_fadvise system call has been changed from an assembly 7241.241Swiz stub, to a c file that calls an assembly stub. You need to 7251.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7261.170Schristos avoid using the old assembly stub. 7271.170Schristos 7281.168Sjoerg20071209: 7291.241Swiz The acpiec(4) driver has been split into two attachments. If you 7301.168Sjoerg get ACPI errors before the attachment, please update your kernel 7311.169Swiz configuration file appropriately or see GENERIC for more details. 7321.168Sjoerg 7331.166Sxtraeme20071115: 7341.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7351.166Sxtraeme argument specified in the kernel configuration file is not valid 7361.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7371.241Swiz rather than the EC address port. Please update your kernel 7381.167Swiz configuration file appropriately or see GENERIC for more details. 7391.166Sxtraeme 7401.165Sjmmv20071028: 7411.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7421.165Sjmmv You need to update any custom kernel configuration file you have 7431.165Sjmmv to remove any references to pccons (which includes removing the 7441.165Sjmmv now useless XSERVER option) and replace them with the correct 7451.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7461.165Sjmmv for more details. 7471.165Sjmmv 7481.164Sgdt20070913: 7491.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7501.164Sgdt enumerate interfaces was fixed. The bug began to cause 7511.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7521.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7531.164Sgdt could not enumerate interfaces. (These are noted because 7541.164Sgdt normal kernel/userspace version matching hygiene is not 7551.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7561.164Sgdt and userland are from after 20070913. 7571.164Sgdt 7581.163Sjoerg20070703: 7591.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7601.199Sdholland calls the target-specific strip program, and the logic to pass 7611.199Sdholland down STRIP from make has been removed. This requires a 7621.199Sdholland re-installation of tools. 7631.163Sjoerg 7641.161Sdsl20070422: 7651.161Sdsl The way OS emulations lookup filenames inside the emulation root 7661.161Sdsl has been changed. Rather than modify the pathname (and copy back 7671.161Sdsl to userspace) namei() and lookup() directly check the emulation 7681.241Swiz root. One side effect is that absolute symlinks inside the emulated 7691.167Swiz root file system will be relative to that file system - unless they 7701.161Sdsl start /../ this is useful when the emulated root is a real install 7711.161Sdsl that has such links. 7721.161Sdsl This might affect symlinks that have been added to reference outside 7731.161Sdsl the emulated root. 7741.161Sdsl 7751.160Sjmcneill20070412: 7761.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 7771.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 7781.160Sjmcneill example. 7791.160Sjmcneill 7801.159Sgdt20070319: 7811.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 7821.159Sgdt on many platforms due to incorrect flags settings. If you 7831.159Sgdt updated and built after about 20070315, do "nbmake-$arch 7841.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 7851.159Sgdt rebuild of object files that might have been built 7861.159Sgdt incorrectly, and ensure that you have at least 7871.159Sgdt src/lib/libc/Makefile 1.130. 7881.159Sgdt 7891.241Swiz20070210: 7901.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 7911.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 7921.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 7931.158Sdbj will allow dependencies on those files to get get rebuilt 7941.158Sdbj 7951.157Sapb20070209: 7961.157Sapb The threading model was changed when the newlock2 branch 7971.157Sapb was merged to NetBSD-current. If you boot with a new 7981.157Sapb kernel (version 4.99.10), then you also need a new pthread 7991.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 8001.157Sapb an old kernel, then you need the old pthread library 8011.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 8021.157Sapb the pthread library in sync, old threaded applications should 8031.157Sapb continue to work with an old or new kernel. Note that named(8) 8041.157Sapb is the only threaded application in the base system. 8051.157Sapb 8061.154She20061214: 8071.154She Following the move of string_to_flags() and flags_to_string() 8081.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 8091.154She will need to do a "make cleandir" in 8101.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 8111.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 8121.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 8131.156She as the installation images in distrib/ 8141.154She in order to excise stale references to the old stat_flags.h header 8151.154She file in the ls sources -- stat_flags.h has been removed. 8161.154She 8171.152Schristos20061108: 8181.152Schristos The configure script used in the src/tools/gcc compiler has been 8191.152Schristos changed to indicate that our libc has ssp support built-in and 8201.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8211.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8221.152Schristos 8231.151Srpaulo20061009: 8241.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8251.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8261.151Srpaulo 8271.150Sbjh2120060814: 8281.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8291.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8301.150Sbjh21 kernel configuration for an example. X servers from the last 8311.150Sbjh21 few years should cope. 8321.150Sbjh21 8331.149Schristos20060703: 8341.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8351.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8361.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8371.149Schristos 8381.148Sdogcow20060627: 8391.148Sdogcow socket(2) has changed, and its system call has been versioned. 8401.148Sdogcow For userlands with the old version of socket(2), make sure that 8411.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8421.148Sdogcow errors will result. 8431.148Sdogcow 8441.1SabsHints for a more successful build: 8451.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8461.123Sjmc Use build.sh, but do not use its "expert mode": 8471.132Sjmmv This will automatically build the tools in the 8481.123Sjmc correct order, and it will keep the tools and the 8491.123Sjmc new build products from interfering with the running 8501.123Sjmc system. This will allow you to ignore most of the 8511.123Sjmc other advice in this file. 8521.2Smrg Build a new kernel first: 8531.2Smrg This makes sure that any new system calls or features 8541.2Smrg expected by the new userland will be present. This 8551.2Smrg helps to avoid critical errors when upgrading. 8561.1Sabs Use object directories: 8571.1Sabs This helps to keep stale object 8581.1Sabs files from polluting the build if a Makefile "forgets" 8591.1Sabs about one. It also makes it easier to clean up after 8601.1Sabs a build. It's also necessary if you want to use the 8611.1Sabs same source tree for multiple machines. 8621.123Sjmc To use object directories with build.sh: 8631.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8641.123Sjmc To use object directories without using build.sh: 8651.1Sabs a) cd /usr/src ; make cleandir 8661.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8671.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8681.1Sabs d) cd /usr/src ; make build 8691.2Smrg Note that running "make obj" in a directory will create 8701.2Smrg in obj.$MACHINE directory. 8711.1Sabs Build to a DESTDIR: 8721.123Sjmc This helps to keep old installed files (especially libraries) 8731.123Sjmc from interfering with the new build. 8741.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8751.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8761.123Sjmc environment variable before running make build. It should be 8771.123Sjmc set to the pathname of an initially empty directory. 8781.123Sjmc Problems: if you do not use build.sh, you might need to 8791.123Sjmc update critical utilities without using DESTDIR since 8801.123Sjmc nothing is executed from what is installed in DESTDIR. 8811.123Sjmc (See critical utils, below.) 8821.1Sabs Build often: 8831.1Sabs This keeps critical utilities current enough to not choke 8841.1Sabs on any other part of the source tree that depends on up to 8851.123Sjmc date functionality. If you use build.sh, you should not have 8861.123Sjmc this problem. 8871.241Swiz 8881.1SabsWhat to do if things don't work: 8891.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8901.230StlsWhen things don't work there are usually a few things that commonly 8911.1Sabsshould be done. 8921.1Sabs 1) make includes 8931.1Sabs This should be done automatically by make build. 8941.1Sabs 2) cd share/mk && make install 8951.1Sabs Again, automatically done by make build. 8961.1Sabs 8971.1SabsFailsafe rebuild of a small part of the tree: 8981.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8991.1SabsTo make sure you rebuild something correctly you want to do 9001.1Sabssomething like the following: 9011.1Sabs 1) Make sure the includes and .mk files are up to date. 9021.1Sabs 2) Make sure any program used to build the particular 9031.1Sabs utility is up to date. (yacc, lex, etc...) 9041.1Sabs 3) cd ...path/to/util... 9051.1Sabs make cleandir 9061.1Sabs rm ...all obj directories... 9071.1Sabs make cleandir # yes, again 9081.1Sabs make obj 9091.1Sabs make depend && make 9101.1Sabs 9111.1SabsFailsafe rebuild of the entire tree: 9121.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9131.1SabsIf you really want to make sure the source tree is clean and 9141.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 9151.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 9161.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 9171.1Sabs 9181.1Sabs---cut here--- 9191.1Sabs#!/bin/sh 9201.1Sabs. /etc/mk.conf 9211.1Sabs 9221.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9231.58Slukem NETBSDSRCDIR=/usr/src 9241.1Sabsfi 9251.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9261.1Sabs echo Unable to find sources 9271.1Sabs exit 1 9281.1Sabsfi 9291.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9301.1Sabs 9311.1Sabsif [ -z $BSDOBJDIR ] ; then 9321.1Sabs BSDOBJDIR=/usr/obj 9331.1Sabsfi 9341.1Sabsif [ -d $BSDOBJDIR ] ; then 9351.1Sabs rm -rf $BSDOBJDIR 9361.1Sabsfi 9371.1Sabs 9381.58Slukemcd $NETBSDSRCDIR && make cleandir 9391.1Sabs 9401.1Sabs---cut here--- 9411.1Sabs 9421.1SabsCritical utilities: 9431.1Sabs^^^^^^^^^^^^^^^^^^^ 9441.3Sitojun usr.bin/compile_et 9451.1Sabs usr.bin/make 9461.1Sabs usr.bin/yacc 9471.1Sabs usr.bin/lex 9481.11Slukem usr.bin/xlint 9491.142Sdrochner usr.bin/config 9501.1Sabs 9511.34SsimonbOther problems and possible solutions: 9521.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9531.1SabsSymptom:Complaints involving a Makefile. 9541.17SerhFix: Rebuild usr.bin/make: 9551.17Serh cd usr.bin/make && make && make install 9561.111Ssimonb Or, a failsafe method if that doesn't work: 9571.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9581.17Serh 9591.1SabsFix: Make sure .mk files are up to date. 9601.1Sabs cd share/mk && make install 9611.2Smrg 9621.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9631.142SdrochnerFix: Rebuild usr.bin/config 9641.1Sabs 9651.1SabsSymptom: 9661.1SabsFix: Rebuild usr.bin/yacc 9671.1Sabs 9681.1SabsSymptom: 9691.1SabsFix: Rebuild usr.bin/lex 9701.1Sabs 9711.1SabsSymptom: 9721.1SabsFix: rm /usr/lib/libbfd.a 9731.4Sitojun 9741.4SitojunSymptom:Obsolete intermediate files are used during compilation 9751.4SitojunFix: Try the following sequence of commands in the directory in question. 9761.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9771.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9781.4Sitojun may remain. The command tries to clean everything up) 9791.5Swiz 9801.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 9811.207Smbalmer pointer type 9821.5SwizFix: Rebuild and install usr.bin/menuc 9831.12Sitojun 9841.12SitojunSymptom:mklocale not found during build in share/locale/ctype 9851.12SitojunFix: Build and install usr.bin/mklocale 9861.13Sdogcow 9871.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 9881.13SdogcowFix: Rebuild and install lib/libc 9891.13Sdogcow 9901.142SdrochnerSymptom:usr.bin/config fails to build. 9911.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 9921.13Sdogcow 9931.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 9941.19ScgdFix: Rebuild and install lib/libc 9951.24Sabs 9961.24SabsSymptom:lint does not understand the '-X' option 9971.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 9981.223Sjoerg 9991.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 10001.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 10011.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 10021.257Sapb 10031.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 10041.257Sapb No such file or directory. 10051.257SapbCause: If a directory is created by mistake, then it is sometimes 10061.257Sapb deleted from the CVS repository using administrative commands 10071.257Sapb that bypass the normal cvs access controls. If your cvs working tree 10081.257Sapb contains references to a directory that has been deleted on the 10091.257Sapb server in this way, then "cvs update" reports this error. 10101.257SapbFix: Recursively delete the affected directory from your working tree 10111.257Sapb and try the update again. 1012