UPDATING revision 1.312
11.312Smrg$NetBSD: UPDATING,v 1.312 2020/08/20 03:09:34 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.311Smrg20200811: 231.312Smrg GCC updates may require cleaning the objdir. This may occur 241.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 251.312Smrg GCC 9 upgrade. 261.311Smrg 271.309Schristos20200614: 281.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 291.310Schristos should handle the migration 301.309Schristos 311.308Schristos20200601: 321.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 331.308Schristos created in the build directories and need cleaning. 341.308Schristos 351.307Smrg20200311: 361.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 371.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 381.307Smrg 391.306Schristos20191118: 401.306Schristos More architectures were switched to gcc8: 411.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 421.306Schristos The same comments as in 20191022 apply. 431.306Schristos 441.305Smartin20191112: 451.305Smartin The LLVM update requires a clean rebuild for all architectures using 461.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 471.305Smartin 481.304Smartin20191022: 491.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 501.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 511.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 521.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 531.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 541.304Smartin daily builds and install that before doing the next in-place build. 551.304Smartin 561.303Smrg20191001: 571.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 581.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 591.303Smrg directory, and also clean src/external/gpl3/gcc. 601.303Smrg 611.302Sriastrad20190903: 621.306Schristos Files with names that coincide with existing files' names on 631.302Sriastrad case-insensitive file systems were inadvertently committed, for 641.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 651.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 661.302Sriastrad ran build.sh distribution or ran build.sh release, you must 671.302Sriastrad manually delete the following files in your DESTDIR (which is 681.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 691.302Sriastrad them: 701.302Sriastrad 711.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 721.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 731.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 741.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 751.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 761.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 771.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 781.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 791.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 801.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 811.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 821.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 831.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 841.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 851.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 861.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 871.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 881.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 891.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 901.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 911.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 921.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 931.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 941.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 951.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 961.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 971.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 981.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 991.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 1001.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 1011.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 1021.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 1031.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 1041.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 1051.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 1061.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 1071.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 1081.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 1091.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 1101.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 1111.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 1121.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1131.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1141.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1151.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1161.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1171.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1181.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1191.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1201.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1211.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1221.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1231.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1241.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1251.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1261.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1271.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1281.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1291.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1301.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1311.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1321.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1331.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1341.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1351.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1361.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1371.302Sriastrad 1381.302Sriastrad We will re-import these radeon firmware images another way 1391.302Sriastrad later. 1401.302Sriastrad 1411.301Smartin20190727: 1421.301Smartin The uefi bootloader has gained tftp support and needs a clean 1431.301Smartin build. If you do update builds, manually clean its object 1441.301Smartin directory by something like: 1451.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1461.301Smartin 1471.300Smartin20190723: 1481.300Smartin The jemalloc allocator in libc is now build without extended 1491.300Smartin debugging (for performance reasons). In update builds make sure 1501.300Smartin to rebuild it completly, by removing all affected object files, 1511.300Smartin including compat builds, something like: 1521.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1531.300Smartin 1541.299Smrg20190207: 1551.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1561.299Smrg 1571.298Smartin20180924: 1581.298Smartin A newer OpenSSL version has been imported. If you are doing 1591.298Smartin update builds, make sure to remove all old obj dirs, like: 1601.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 1611.298Smartin 1621.297Sjoerg20180717: 1631.297Sjoerg On aarch64 int64_t and related types have changed from long long 1641.297Sjoerg to long. This requires recompiling all C++ binaries. 1651.297Sjoerg 1661.296Smartin20180713: 1671.296Smartin On amd64 and i386 static binaries are now build position 1681.296Smartin independend. This requires recompilation of all object 1691.296Smartin files used to create the crunched /rescue binary. 1701.296Smartin Clean the rescue directory in your obj directory before 1711.296Smartin doing an update build, otherwise linking will fail. 1721.296Smartin 1731.293Sjakllsch20180414: 1741.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 1751.293Sjakllsch removal of tools/binutils objects directory may be required 1761.293Sjakllsch to fix tools build failure. 1771.293Sjakllsch 1781.292Smrg20180311: 1791.292Smrg bdftopcf was updated and may need cleaning in the 1801.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 1811.292Smrg link errors. 1821.292Smrg 1831.291Smrg20180212: 1841.291Smrg between OpenSSL and GCC updates, many things may fail to build. 1851.291Smrg any failure that looks like GCC or openssl is best handled by 1861.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 1871.291Smrg is recommended if build failures occur. 1881.291Smrg 1891.288Smartin20171225: 1901.288Smartin removal of the vadvise syscall requires manual removal of all 1911.288Smartin associated files from the libc build object directory (including 1921.289Schristos the .depend files) - a command like: 1931.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 1941.289Schristos For architectures that support multiple "compat" binary targets, 1951.289Schristos you'll need to cleanup both the regular libc directory and the 1961.290Smartin compat ones (the above command will do that). 1971.288Smartin 1981.287Skre20171010: 1991.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 2001.287Skre means that its objdir (or *.d and .depend at least) might need 2011.287Skre to be manually removed - or a build done once without -u. 2021.287Skre 2031.286Smrg20170822: 2041.286Smrg a new version of GMP has been imported and probably 2051.286Smrg will break parts of builds related to themselves or GCC, both 2061.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2071.286Smrg and MPC objdirs or build once without -u. 2081.286Smrg 2091.285Smrg20170816: 2101.285Smrg a new version of MPFR and MPC have been imported and probably 2111.285Smrg will break parts of builds related to themselves or GCC, both 2121.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2131.285Smrg and MPC objdirs or build once without -u. 2141.285Smrg 2151.284Smartin20170402: 2161.284Smartin a new version of dhcpcd has been imported, which does not support 2171.284Smartin update builds from the previous version. Remove your 2181.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2191.284Smartin 2201.281Sroy20170211: 2211.281Sroy a new terminfo database has been imported. 2221.281Sroy The structure of it has changed slightly from prior versions and 2231.281Sroy an updated tic tool is required. 2241.281Sroy If you build.sh, don't use -u 2251.281Sroy 2261.280Skre20170207: 2271.278Skre various arch dependent libc/exect.S files were removed 2281.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2291.279Skre if it exists) or do a clean build. 2301.279Skre (This is a bug in the make system, it should be corrected without 2311.279Skre human intervention, but isn't.) 2321.278Skre 2331.277Smartin20170104: 2341.277Smartin xinput build options have changed. 2351.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2361.277Smartin if you build.sh -u 2371.277Smartin 2381.276Smartin20170103: 2391.276Smartin a new version of flex has been imported. 2401.276Smartin Remove the file from obj (external/bsd/flex) 2411.276Smartin if you build.sh -u 2421.276Smartin 2431.275Sspz20161014: 2441.275Sspz a new version of OpenSSL has been imported. 2451.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2461.275Sspz if you build.sh -u 2471.275Sspz 2481.274Smartin20161009: 2491.274Smartin a new version of dhcpcd has been imported with slightly changed 2501.274Smartin build infrastructure. When doing a build.sh -u this requires 2511.274Smartin pruning the external/bsd/dhcpcd objdir. 2521.274Smartin 2531.273Smrg20160914: 2541.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2551.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2561.273Smrg and a clean objdir. 2571.273Smrg 2581.272Sdholland20160527: 2591.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 2601.272Sdholland been enabled. (see the amd64 entry two down for further info) 2611.272Sdholland 2621.270Schristos20160418: 2631.270Schristos libedit needs manual removal of all autogenerated files since 2641.271Schristos some of them are not autogenerated anymore. Remember that there 2651.271Schristos might be two copies of libedit if your platform builds "compat". 2661.270Schristos 2671.268Sriastrad20160410: 2681.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 2691.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 2701.268Sriastrad executables, means all code, including executables and not just 2711.268Sriastrad shared libraries, is position-independent and hence able to be 2721.268Sriastrad relocated by ASLR, address space layout randomization. 2731.268Sriastrad 2741.268Sriastrad The change was made in Makefile variables for compiler and 2751.268Sriastrad linker flags, for which make(1) does not record dependencies, 2761.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 2771.268Sriastrad 2781.268Sriastrad Partial rebuilds with some modified source files will likely 2791.268Sriastrad fail when linking executables, since the linker refuses to mix 2801.268Sriastrad position-independent code with position-dependent code in 2811.268Sriastrad position-independent executables: 2821.268Sriastrad 2831.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 2841.268Sriastrad 2851.267Smrg20160401: 2861.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 2871.269Sdholland Some people have found that cleandir is not sufficient, so if 2881.269Sdholland in doubt delete the entire object directory tree for gcc. 2891.267Smrg 2901.266Saymeric20160306: 2911.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 2921.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 2931.265Saymeric non-NetBSD hosts if linked with stale object files produced 2941.265Saymeric while they included a non-NetBSD regex.h. 2951.265Saymeric In any case, you should "make cleandir" at least these tools 2961.265Saymeric before updating your toolchain. 2971.265Saymeric 2981.264Smartin20160125: 2991.264Smartin Dtrace has been enabled by default on some architectures. 3001.264Smartin When doing an update build, make sure to clean the etc/mtree 3011.264Smartin object directory before starting the build - otherwise the 3021.264Smartin needed directories in destdir will not be created. 3031.264Smartin An easy way to do this is: 3041.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 3051.264Smartin 3061.263Sdholland20150818: 3071.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 3081.263Sdholland again. 3091.263Sdholland 3101.262Schristos20150413: 3111.262Schristos New acpica requires "make cleandir" and reinstalling yacc 3121.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3131.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3141.262Schristos 3151.261Smartin20150404: 3161.261Smartin Lint changes require a full rebuild of the tool, so make 3171.261Smartin sure to build without -u option to build.sh, or manually 3181.261Smartin do a make cleandir in src/tools/lint1 and 3191.261Smartin src/usr.bin/xlint. 3201.261Smartin 3211.260Sskrll20150310: 3221.260Sskrll Improvements to openssl for arm mean that update builds of 3231.260Sskrll the openssl libraries will fail. A make cleandir in 3241.260Sskrll external/bsd/openssl/lib is needed 3251.260Sskrll 3261.258Smartin20141026: 3271.259Smsaitoh A mishap during the import of pppd may cause your corruption 3281.258Smartin in your cvs directory if you happened to do a cvs update 3291.258Smartin during a short period of time. To fix, just remove the 3301.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3311.258Smartin and let cvs restore it on next update. 3321.258Smartin 3331.256Sapb20140721: 3341.256Sapb The src/external/mit/lua/src directory was accidentally created 3351.256Sapb and then deleted in the CVS repository. If you get errors like 3361.256Sapb 3371.256Sapb cvs [update aborted]: cannot open directory 3381.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3391.256Sapb 3401.256Sapb then delete your local copy of that directory tree and try again. 3411.256Sapb 3421.255Sjoerg20140530: 3431.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3441.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3451.255Sjoerg 3461.251Smartin20140131: 3471.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3481.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3491.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3501.251Smartin 3511.250Schristos20131227: 3521.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3531.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3541.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3551.250Schristos statements to avoid being exposed. 3561.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3571.250Schristos to make clean in libc 3581.250Schristos 3591.249Smrg20131129: 3601.249Smrg The GMP sources were updated, and builds will likely fail without 3611.249Smrg cleaning their build trees for both tools and in-tree, like below. 3621.249Smrg 3631.248Smrg20131128: 3641.248Smrg The MPC and MPFR sources were updated, and builds may require their 3651.248Smrg tools and in-tree directories cleaned for successful updates. 3661.248Smrg 3671.246Smartin20130605: 3681.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 3691.247Sspz to IPSEC (and the older IPSEC version removed). 3701.247Sspz 3711.247Sspz20130605: 3721.246Smartin Previous freetype installations eroneously installed private 3731.246Smartin header files. If you are building against a non-empty $DESTDIR, 3741.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 3751.246Smartin 3761.245Smrg20130531: 3771.245Smrg The xdm update may cause build failure due to xdm.man being 3781.245Smrg in the obj tree. Make sure to ensure any like this: 3791.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 3801.245Smrg is fixed by deleting the xdm.man in the obj tree. 3811.245Smrg 3821.244Smrg20130530: 3831.244Smrg Updates of many xsrc packages will leave old .pc files around. 3841.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 3851.244Smrg 3861.242Schristos20130301: 3871.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 3881.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 3891.242Schristos 3901.238Sdholland20120726: 3911.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 3921.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 3931.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 3941.241Swiz some cases may succeed and install broken OpenSSL libraries that 3951.240Sdholland cause third-party software to link incorrectly and/or crash. 3961.238Sdholland 3971.237Swiz20120507: 3981.241Swiz The database schema for makemandb was changed. You will 3991.237Swiz need to update the database using 'makemandb -f' or wait 4001.237Swiz for the next weekly run to fix it. 4011.237Swiz 4021.236Sbsh20120319: 4031.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 4041.236Sbsh size of db_symtab automatically. You need to update dbsym in 4051.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 4061.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 4071.236Sbsh mk.conf. 4081.236Sbsh 4091.235Sjoerg20120216: 4101.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 4111.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 4121.239Sdholland and 20120216, daily and weekly could have created an unreadable 4131.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4141.235Sjoerg the next run of weekly will fix it. 4151.233Sjoerg 4161.232Schristos20111227: 4171.232Schristos If you built between 20111225 and 20111227 you need to remove 4181.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4191.232Schristos bump has been reverted. 4201.232Schristos 4211.231Stls20111125: 4221.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4231.231Stls means it should no longer be explicitly listed in kernel 4241.231Stls configuration files. The line "pseudo-device rnd" should be 4251.231Stls removed from any custom kernel config files users may have. 4261.231Stls 4271.230Stls20111119: 4281.230Stls A problem with the datastructures used by the rndctl(8) 4291.230Stls utility (pointers in datastructures in an array, making 32->64 4301.230Stls bit compatibility very painful) has been fixed in a 4311.230Stls non-backwards-compatible way. If you replace your kernel, 4321.230Stls replace your rndctl executable too. 4331.241Swiz 4341.229Sjym20111001: 4351.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4361.229Sjym changed and their new version is not backward compatible with the old 4371.241Swiz one. So ensure that all consumers of these functions (currently: 4381.229Sjym quota2 code and its tests) are updated together with the new lib. 4391.229Sjym 4401.228Smrg20110817: 4411.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4421.228Smrg DESTDIR for them should be deleted before updating. 4431.228Smrg 4441.227Sriastrad20110806: 4451.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4461.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4471.227Sriastrad 4481.226Smrg20110805: 4491.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4501.226Smrg the tree to be cleaned. Best to delete both objdir and 4511.226Smrg DESTDIR before running this update. So far, only the 4521.226Smrg sparc64, mips and powerpc platforms have changed. 4531.226Smrg 4541.225Smatt20110803: 4551.241Swiz The layout of external/public-domain/xz has changed. To do an 4561.225Smatt update build you will have to remove the contents of the OBJDIR 4571.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4581.225Smatt is now a directory. 4591.225Smatt 4601.223Sjoerg20110410: 4611.241Swiz The configuration of src/tools/gcc has changed. To do an 4621.224Sdholland update build you have to clean both tools/binutils and 4631.224Sdholland tools/gcc by hand. 4641.223Sjoerg 4651.222Splunky20110328: 4661.222Splunky Building the Xorg binary was moved into a subdirectory to fix 4671.241Swiz ordering issues with "make all". It may be necessary to remove 4681.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 4691.222Splunky if your update build fails, as the "Xorg" entry there is now a 4701.222Splunky directory. 4711.222Splunky 4721.220Sjoerg20110121: 4731.221Slukem Assembler files no longer use -traditional-cpp. This can break 4741.220Sjoerg the build of individual parts of the tree. This is handled 4751.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 4761.220Sjoerg and re-run config(1) for any kernel configurations as needed. 4771.218Sjoerg 4781.217Sjruoho20101217: 4791.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 4801.241Swiz by default. It may be necessary to manually update passwd(5) and 4811.217Sjruoho group(5) in order to make the program work with existing setups. 4821.217Sjruoho 4831.216Schristos20101125: 4841.216Schristos The latest changes to setenv(3) dissallow setting environment 4851.241Swiz variables with names that contain '='. Revision 1.18 of env.c 4861.241Swiz assumed that this was allowed. Installing a new libc with an 4871.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 4881.216Schristos break which affects the autoconf tests for dependency finding, 4891.216Schristos so building gcc will end up printing: 4901.216Schristos checking dependency style of gcc... none 4911.216Schristos configure: error: no usable dependency style found 4921.216Schristos Fix it by rebuilding and re-installing env. 4931.138Slukem 4941.215Smrg20101119: 4951.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 4961.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 4971.215Smrg have any build problems with xsrc, or problems with mismatched 4981.215Smrg versions between xorg-server and drivers. 4991.215Smrg 5001.213Sjmmv20100604: 5011.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 5021.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 5031.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 5041.213Sjmmv trees by hand. 5051.213Sjmmv 5061.211Stnozaki20100522: 5071.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 5081.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 5091.212Smrg build problems with xsrc. 5101.212Smrg 5111.212Smrg20100522: 5121.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 5131.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5141.211Stnozaki 5151.210Schristos20100520: 5161.241Swiz The location of the xkb compiled descriptions has changed. Please 5171.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5181.210Schristos 5191.209Snjoly20100222: 5201.209Snjoly The shared objects file extension has been changed from .so to 5211.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5221.209Snjoly libXX.so. All now stale regular .so files can be removed from 5231.209Snjoly your object directories. 5241.209Snjoly 5251.208Sroy20100204: 5261.208Sroy The termcap database has been removed from the sources, 5271.208Sroy but has not been marked obsolete so it is not removed 5281.208Sroy from the system when upgrading. 5291.208Sroy As such, you will need to remove them from your object 5301.208Sroy and destination directories. 5311.208Sroy 5321.203Sdyoung20091101: 5331.205Sdholland After updating, it may be necessary to make the 'cleandir' 5341.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5351.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5361.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5371.203Sdyoung 5381.202Smrg20091001: 5391.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5401.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5411.206Sdholland 5421.206Sdholland20091001: 5431.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5441.202Smrg symlink, failing the build. Delete the link, and the subdir 5451.202Smrg it is in, and retry your build. 5461.202Smrg 5471.201Sdsl20090718: 5481.201Sdsl libc build changed so that strchr() provides the extra entry 5491.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5501.201Sdsl may fail because the archive contains the unwanted index.o. 5511.201Sdsl (Similarly for strrchr() and rindex().) 5521.201Sdsl 5531.198Smrg20090709: 5541.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5551.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5561.198Smrg 5571.197Smrg20090616: 5581.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 5591.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 5601.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 5611.197Smrg subdirectory has been changed into a file, and this needs to 5621.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 5631.197Smrg 5641.195Sperry20090501: 5651.195Sperry Several new functions were added to string.h/libc, and this 5661.195Sperry can cause autoconf problems during the tool build for people 5671.241Swiz who fail to clean out their tools objects properly. If you 5681.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 5691.195Sperry failure during the tool build, clean out all your tools 5701.195Sperry objects and start again. 5711.195Sperry 5721.194Smrg20090325: 5731.194Smrg The i386 port was switched to i486 default toolchain. This requires 5741.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 5751.194Smrg 5761.192Sskrll20090126: 5771.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 5781.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 5791.207Smbalmer to avoid using the old assembly stub. 5801.192Sskrll 5811.191Sjoerg20090202: 5821.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 5831.191Sjoerg detection. It is recommented to rebuild the cache with 5841.191Sjoerg ``pkg_admin rebuild''. 5851.191Sjoerg 5861.184Schristos20090110: 5871.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 5881.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 5891.188Schristos This is needed even in the MODULAR kernel because there is 5901.188Schristos conditionally compiled code in rtsock.c. 5911.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 5921.184Schristos before installing. 5931.184Schristos 3. If you don't use build.sh and you build directly to root, and 5941.241Swiz your build breaks in the middle, don't despair. Make sure headers 5951.184Schristos are installed properly, and start building libraries first libc 5961.184Schristos and libutil, install them and then continue building all the 5971.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 5981.184Schristos the new libraries are installed, you can restart the build. 5991.184Schristos 4. If you compile packages and you notice link time warnings, 6001.189Shubertf rebuild the required packages to update their shared libraries. 6011.189Shubertf Any package you rebuild will require rebuilding all the packages 6021.189Shubertf that depend on it. 6031.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 6041.186Schristos will be upgraded and it will not be backwards compatible. 6051.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 6061.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 6071.241Swiz for utmp. You are better off removing the old files after 6081.190Sapb upgrading. The automated clearing of /var/run during 6091.190Sapb boot, and the automated rotating of files in /var/log by 6101.190Sapb newsyslog(8), may mean that you do not have to remove the 6111.190Sapb files manually. 6121.190Sapb 7. The optional accounting file (/var/account/acct, see 6131.190Sapb accton(8)) has not been versioned, and will need to be 6141.190Sapb removed. The automatic rotation of the accounting file by 6151.190Sapb /etc/daily limits the bad consequences of failure to remove 6161.190Sapb the file. 6171.196Sdholland 8. Application software that writes time_t to binary files on 6181.241Swiz disk will break or need attention. Most notably: if you are 6191.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6201.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6211.185Sjmcneill 6221.183Spgoyette20081219: 6231.183Spgoyette config(1) has been updated, and one of the files it creates - 6241.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6251.183Spgoyette (done automatically by build.sh) and then you need to rerun 6261.183Spgoyette config on all kernel configuration files before rebuilding those 6271.183Spgoyette kernels. 6281.183Spgoyette 6291.181Scube20081205: 6301.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6311.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6321.181Scube set and will appear as extra files for MKX11=no update builds. 6331.178Slukem 6341.179Stsutsui20081122: 6351.182Stsutsui On i386, various kernel options(4) in GENERIC including 6361.180Swiz file systems have been disabled and moved into kernel modules. 6371.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6381.179Stsutsui following files as well as a new GENERIC kernel: 6391.179Stsutsui 6401.179Stsutsui - build and install kernel modules from src/sys/modules 6411.179Stsutsui 6421.179Stsutsui - install the latest bootloader, which will load a module 6431.180Swiz for the file system from which the kernel is loaded automatically 6441.179Stsutsui 6451.180Swiz If you have to load your kernel from a file system which is not of 6461.180Swiz the same type as the root file system, you have to load the necessary 6471.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6481.179Stsutsui 6491.178Slukem20080827: 6501.178Slukem If you built and installed a libc from sources between 6511.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6521.178Slukem which results in false errors reported by lint(1). 6531.178Slukem Since this breaks the libc build itself, manual help is 6541.180Swiz needed -- lint must be disabled temporarily, e.g.: 6551.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6561.178Slukem 6571.177Schristos20080813: 6581.177Schristos MKDEBUG build was broken because the .depend files did not know 6591.241Swiz about .go files. You need to remove all .depend files and rebuild. 6601.177Schristos 6611.200Sdholland20080802: 6621.200Sdholland A regression in binary compatibility for pthread_mutex_t has 6631.241Swiz been fixed. Unfortunately, the price is breaking compatibility 6641.200Sdholland for -current. 6651.200Sdholland 6661.200Sdholland Threaded programs (using libpthread) and C++ programs (using 6671.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 6681.200Sdholland be recompiled. 6691.200Sdholland 6701.200Sdholland One way to find affected pkgsrc packages: 6711.200Sdholland 6721.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 6731.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 6741.200Sdholland 6751.175Ssimonb20080731: 6761.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 6771.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 6781.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 6791.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 6801.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 6811.176Ssimonb also requires the super block to be in the UFS2 format. You 6821.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 6831.175Ssimonb 6841.174Slukem20080721: 6851.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 6861.174Slukem isn't defined. 6871.174Slukem 6881.173Sfreza20080531: 6891.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 6901.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 6911.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 6921.241Swiz won't work correctly. The following sequence of commands: 6931.173Sfreza 6941.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 6951.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 6961.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 6971.173Sfreza 6981.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 6991.173Sfreza 7001.172Slukem20080503: 7011.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 7021.172Slukem 7031.171She20080521: 7041.171She For a while, unprivileged UPDATE builds would fail to 7051.171She succeed at the checkflist stage, complaining that 7061.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 7071.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 7081.171She If you already hit this problem, update the .mk file, 7091.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 7101.171She 7111.174Slukem20080303: 7121.174Slukem Linker warnings are now fatal if $WARNS>0. 7131.174Slukem 7141.170Schristos20080126: 7151.170Schristos The posix_fadvise system call has been changed from an assembly 7161.241Swiz stub, to a c file that calls an assembly stub. You need to 7171.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7181.170Schristos avoid using the old assembly stub. 7191.170Schristos 7201.168Sjoerg20071209: 7211.241Swiz The acpiec(4) driver has been split into two attachments. If you 7221.168Sjoerg get ACPI errors before the attachment, please update your kernel 7231.169Swiz configuration file appropriately or see GENERIC for more details. 7241.168Sjoerg 7251.166Sxtraeme20071115: 7261.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7271.166Sxtraeme argument specified in the kernel configuration file is not valid 7281.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7291.241Swiz rather than the EC address port. Please update your kernel 7301.167Swiz configuration file appropriately or see GENERIC for more details. 7311.166Sxtraeme 7321.165Sjmmv20071028: 7331.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7341.165Sjmmv You need to update any custom kernel configuration file you have 7351.165Sjmmv to remove any references to pccons (which includes removing the 7361.165Sjmmv now useless XSERVER option) and replace them with the correct 7371.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7381.165Sjmmv for more details. 7391.165Sjmmv 7401.164Sgdt20070913: 7411.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7421.164Sgdt enumerate interfaces was fixed. The bug began to cause 7431.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7441.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7451.164Sgdt could not enumerate interfaces. (These are noted because 7461.164Sgdt normal kernel/userspace version matching hygiene is not 7471.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7481.164Sgdt and userland are from after 20070913. 7491.164Sgdt 7501.163Sjoerg20070703: 7511.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7521.199Sdholland calls the target-specific strip program, and the logic to pass 7531.199Sdholland down STRIP from make has been removed. This requires a 7541.199Sdholland re-installation of tools. 7551.163Sjoerg 7561.161Sdsl20070422: 7571.161Sdsl The way OS emulations lookup filenames inside the emulation root 7581.161Sdsl has been changed. Rather than modify the pathname (and copy back 7591.161Sdsl to userspace) namei() and lookup() directly check the emulation 7601.241Swiz root. One side effect is that absolute symlinks inside the emulated 7611.167Swiz root file system will be relative to that file system - unless they 7621.161Sdsl start /../ this is useful when the emulated root is a real install 7631.161Sdsl that has such links. 7641.161Sdsl This might affect symlinks that have been added to reference outside 7651.161Sdsl the emulated root. 7661.161Sdsl 7671.160Sjmcneill20070412: 7681.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 7691.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 7701.160Sjmcneill example. 7711.160Sjmcneill 7721.159Sgdt20070319: 7731.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 7741.159Sgdt on many platforms due to incorrect flags settings. If you 7751.159Sgdt updated and built after about 20070315, do "nbmake-$arch 7761.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 7771.159Sgdt rebuild of object files that might have been built 7781.159Sgdt incorrectly, and ensure that you have at least 7791.159Sgdt src/lib/libc/Makefile 1.130. 7801.159Sgdt 7811.241Swiz20070210: 7821.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 7831.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 7841.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 7851.158Sdbj will allow dependencies on those files to get get rebuilt 7861.158Sdbj 7871.157Sapb20070209: 7881.157Sapb The threading model was changed when the newlock2 branch 7891.157Sapb was merged to NetBSD-current. If you boot with a new 7901.157Sapb kernel (version 4.99.10), then you also need a new pthread 7911.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 7921.157Sapb an old kernel, then you need the old pthread library 7931.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 7941.157Sapb the pthread library in sync, old threaded applications should 7951.157Sapb continue to work with an old or new kernel. Note that named(8) 7961.157Sapb is the only threaded application in the base system. 7971.157Sapb 7981.154She20061214: 7991.154She Following the move of string_to_flags() and flags_to_string() 8001.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 8011.154She will need to do a "make cleandir" in 8021.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 8031.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 8041.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 8051.156She as the installation images in distrib/ 8061.154She in order to excise stale references to the old stat_flags.h header 8071.154She file in the ls sources -- stat_flags.h has been removed. 8081.154She 8091.152Schristos20061108: 8101.152Schristos The configure script used in the src/tools/gcc compiler has been 8111.152Schristos changed to indicate that our libc has ssp support built-in and 8121.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8131.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8141.152Schristos 8151.151Srpaulo20061009: 8161.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8171.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8181.151Srpaulo 8191.150Sbjh2120060814: 8201.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8211.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8221.150Sbjh21 kernel configuration for an example. X servers from the last 8231.150Sbjh21 few years should cope. 8241.150Sbjh21 8251.149Schristos20060703: 8261.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8271.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8281.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8291.149Schristos 8301.148Sdogcow20060627: 8311.148Sdogcow socket(2) has changed, and its system call has been versioned. 8321.148Sdogcow For userlands with the old version of socket(2), make sure that 8331.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8341.148Sdogcow errors will result. 8351.148Sdogcow 8361.1SabsHints for a more successful build: 8371.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8381.123Sjmc Use build.sh, but do not use its "expert mode": 8391.132Sjmmv This will automatically build the tools in the 8401.123Sjmc correct order, and it will keep the tools and the 8411.123Sjmc new build products from interfering with the running 8421.123Sjmc system. This will allow you to ignore most of the 8431.123Sjmc other advice in this file. 8441.2Smrg Build a new kernel first: 8451.2Smrg This makes sure that any new system calls or features 8461.2Smrg expected by the new userland will be present. This 8471.2Smrg helps to avoid critical errors when upgrading. 8481.1Sabs Use object directories: 8491.1Sabs This helps to keep stale object 8501.1Sabs files from polluting the build if a Makefile "forgets" 8511.1Sabs about one. It also makes it easier to clean up after 8521.1Sabs a build. It's also necessary if you want to use the 8531.1Sabs same source tree for multiple machines. 8541.123Sjmc To use object directories with build.sh: 8551.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8561.123Sjmc To use object directories without using build.sh: 8571.1Sabs a) cd /usr/src ; make cleandir 8581.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8591.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8601.1Sabs d) cd /usr/src ; make build 8611.2Smrg Note that running "make obj" in a directory will create 8621.2Smrg in obj.$MACHINE directory. 8631.1Sabs Build to a DESTDIR: 8641.123Sjmc This helps to keep old installed files (especially libraries) 8651.123Sjmc from interfering with the new build. 8661.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8671.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8681.123Sjmc environment variable before running make build. It should be 8691.123Sjmc set to the pathname of an initially empty directory. 8701.123Sjmc Problems: if you do not use build.sh, you might need to 8711.123Sjmc update critical utilities without using DESTDIR since 8721.123Sjmc nothing is executed from what is installed in DESTDIR. 8731.123Sjmc (See critical utils, below.) 8741.1Sabs Build often: 8751.1Sabs This keeps critical utilities current enough to not choke 8761.1Sabs on any other part of the source tree that depends on up to 8771.123Sjmc date functionality. If you use build.sh, you should not have 8781.123Sjmc this problem. 8791.241Swiz 8801.1SabsWhat to do if things don't work: 8811.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8821.230StlsWhen things don't work there are usually a few things that commonly 8831.1Sabsshould be done. 8841.1Sabs 1) make includes 8851.1Sabs This should be done automatically by make build. 8861.1Sabs 2) cd share/mk && make install 8871.1Sabs Again, automatically done by make build. 8881.1Sabs 8891.1SabsFailsafe rebuild of a small part of the tree: 8901.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8911.1SabsTo make sure you rebuild something correctly you want to do 8921.1Sabssomething like the following: 8931.1Sabs 1) Make sure the includes and .mk files are up to date. 8941.1Sabs 2) Make sure any program used to build the particular 8951.1Sabs utility is up to date. (yacc, lex, etc...) 8961.1Sabs 3) cd ...path/to/util... 8971.1Sabs make cleandir 8981.1Sabs rm ...all obj directories... 8991.1Sabs make cleandir # yes, again 9001.1Sabs make obj 9011.1Sabs make depend && make 9021.1Sabs 9031.1SabsFailsafe rebuild of the entire tree: 9041.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9051.1SabsIf you really want to make sure the source tree is clean and 9061.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 9071.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 9081.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 9091.1Sabs 9101.1Sabs---cut here--- 9111.1Sabs#!/bin/sh 9121.1Sabs. /etc/mk.conf 9131.1Sabs 9141.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9151.58Slukem NETBSDSRCDIR=/usr/src 9161.1Sabsfi 9171.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9181.1Sabs echo Unable to find sources 9191.1Sabs exit 1 9201.1Sabsfi 9211.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9221.1Sabs 9231.1Sabsif [ -z $BSDOBJDIR ] ; then 9241.1Sabs BSDOBJDIR=/usr/obj 9251.1Sabsfi 9261.1Sabsif [ -d $BSDOBJDIR ] ; then 9271.1Sabs rm -rf $BSDOBJDIR 9281.1Sabsfi 9291.1Sabs 9301.58Slukemcd $NETBSDSRCDIR && make cleandir 9311.1Sabs 9321.1Sabs---cut here--- 9331.1Sabs 9341.1SabsCritical utilities: 9351.1Sabs^^^^^^^^^^^^^^^^^^^ 9361.3Sitojun usr.bin/compile_et 9371.1Sabs usr.bin/make 9381.1Sabs usr.bin/yacc 9391.1Sabs usr.bin/lex 9401.11Slukem usr.bin/xlint 9411.142Sdrochner usr.bin/config 9421.1Sabs 9431.34SsimonbOther problems and possible solutions: 9441.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9451.1SabsSymptom:Complaints involving a Makefile. 9461.17SerhFix: Rebuild usr.bin/make: 9471.17Serh cd usr.bin/make && make && make install 9481.111Ssimonb Or, a failsafe method if that doesn't work: 9491.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9501.17Serh 9511.1SabsFix: Make sure .mk files are up to date. 9521.1Sabs cd share/mk && make install 9531.2Smrg 9541.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9551.142SdrochnerFix: Rebuild usr.bin/config 9561.1Sabs 9571.1SabsSymptom: 9581.1SabsFix: Rebuild usr.bin/yacc 9591.1Sabs 9601.1SabsSymptom: 9611.1SabsFix: Rebuild usr.bin/lex 9621.1Sabs 9631.1SabsSymptom: 9641.1SabsFix: rm /usr/lib/libbfd.a 9651.4Sitojun 9661.4SitojunSymptom:Obsolete intermediate files are used during compilation 9671.4SitojunFix: Try the following sequence of commands in the directory in question. 9681.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9691.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9701.4Sitojun may remain. The command tries to clean everything up) 9711.5Swiz 9721.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 9731.207Smbalmer pointer type 9741.5SwizFix: Rebuild and install usr.bin/menuc 9751.12Sitojun 9761.12SitojunSymptom:mklocale not found during build in share/locale/ctype 9771.12SitojunFix: Build and install usr.bin/mklocale 9781.13Sdogcow 9791.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 9801.13SdogcowFix: Rebuild and install lib/libc 9811.13Sdogcow 9821.142SdrochnerSymptom:usr.bin/config fails to build. 9831.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 9841.13Sdogcow 9851.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 9861.19ScgdFix: Rebuild and install lib/libc 9871.24Sabs 9881.24SabsSymptom:lint does not understand the '-X' option 9891.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 9901.223Sjoerg 9911.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 9921.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 9931.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 9941.257Sapb 9951.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 9961.257Sapb No such file or directory. 9971.257SapbCause: If a directory is created by mistake, then it is sometimes 9981.257Sapb deleted from the CVS repository using administrative commands 9991.257Sapb that bypass the normal cvs access controls. If your cvs working tree 10001.257Sapb contains references to a directory that has been deleted on the 10011.257Sapb server in this way, then "cvs update" reports this error. 10021.257SapbFix: Recursively delete the affected directory from your working tree 10031.257Sapb and try the update again. 1004