UPDATING revision 1.305
11.305Smartin$NetBSD: UPDATING,v 1.305 2019/11/13 09:59:02 martin Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.257SapbSections are marked with "^^^^^". After the section on "Recent changes" 151.257Sapbare several sections containing more general information. 161.257Sapb 171.123SjmcSee also: BUILDING, build.sh, Makefile. 181.1Sabs 191.1SabsRecent changes: 201.1Sabs^^^^^^^^^^^^^^^ 211.230Stls 221.305Smartin20191112: 231.305Smartin The LLVM update requires a clean rebuild for all architectures using 241.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 251.305Smartin 261.304Smartin20191022: 271.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 281.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 291.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 301.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 311.304Smartin once and install sets, or download compt.{tar.xz,tgz} from the 321.304Smartin daily builds and install that before doing the next in-place build. 331.304Smartin 341.303Smrg20191001: 351.303Smrg 361.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 371.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 381.303Smrg directory, and also clean src/external/gpl3/gcc. 391.303Smrg 401.302Sriastrad20190903: 411.302Sriastrad 421.302Sriastrad File with names that coincide with existing files' names on 431.302Sriastrad case-insensitive file systems were inadvertently committed, for 441.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 451.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 461.302Sriastrad ran build.sh distribution or ran build.sh release, you must 471.302Sriastrad manually delete the following files in your DESTDIR (which is 481.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 491.302Sriastrad them: 501.302Sriastrad 511.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 521.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 531.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 541.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 551.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 561.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 571.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 581.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 591.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 601.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 611.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 621.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 631.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 641.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 651.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 661.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 671.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 681.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 691.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 701.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 711.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 721.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 731.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 741.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 751.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 761.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 771.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 781.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 791.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 801.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 811.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 821.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 831.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 841.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 851.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 861.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 871.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 881.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 891.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 901.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 911.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 921.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 931.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 941.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 951.302Sriastrad /libdata/firmware/radeon/oland_me.bin 961.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 971.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 981.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 991.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1001.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1011.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1021.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1031.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1041.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1051.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1061.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1071.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1081.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1091.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1101.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1111.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1121.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1131.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1141.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1151.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1161.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1171.302Sriastrad 1181.302Sriastrad We will re-import these radeon firmware images another way 1191.302Sriastrad later. 1201.302Sriastrad 1211.301Smartin20190727: 1221.301Smartin The uefi bootloader has gained tftp support and needs a clean 1231.301Smartin build. If you do update builds, manually clean its object 1241.301Smartin directory by something like: 1251.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1261.301Smartin 1271.300Smartin20190723: 1281.300Smartin The jemalloc allocator in libc is now build without extended 1291.300Smartin debugging (for performance reasons). In update builds make sure 1301.300Smartin to rebuild it completly, by removing all affected object files, 1311.300Smartin including compat builds, something like: 1321.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1331.300Smartin 1341.299Smrg20190207: 1351.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1361.299Smrg 1371.298Smartin20180924: 1381.298Smartin A newer OpenSSL version has been imported. If you are doing 1391.298Smartin update builds, make sure to remove all old obj dirs, like: 1401.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 1411.298Smartin 1421.297Sjoerg20180717: 1431.297Sjoerg On aarch64 int64_t and related types have changed from long long 1441.297Sjoerg to long. This requires recompiling all C++ binaries. 1451.297Sjoerg 1461.296Smartin20180713: 1471.296Smartin On amd64 and i386 static binaries are now build position 1481.296Smartin independend. This requires recompilation of all object 1491.296Smartin files used to create the crunched /rescue binary. 1501.296Smartin Clean the rescue directory in your obj directory before 1511.296Smartin doing an update build, otherwise linking will fail. 1521.296Smartin 1531.293Sjakllsch20180414: 1541.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 1551.293Sjakllsch removal of tools/binutils objects directory may be required 1561.293Sjakllsch to fix tools build failure. 1571.293Sjakllsch 1581.292Smrg20180311: 1591.292Smrg bdftopcf was updated and may need cleaning in the 1601.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 1611.292Smrg link errors. 1621.292Smrg 1631.291Smrg20180212: 1641.291Smrg between OpenSSL and GCC updates, many things may fail to build. 1651.291Smrg any failure that looks like GCC or openssl is best handled by 1661.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 1671.291Smrg is recommended if build failures occur. 1681.291Smrg 1691.288Smartin20171225: 1701.288Smartin removal of the vadvise syscall requires manual removal of all 1711.288Smartin associated files from the libc build object directory (including 1721.289Schristos the .depend files) - a command like: 1731.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 1741.289Schristos For architectures that support multiple "compat" binary targets, 1751.289Schristos you'll need to cleanup both the regular libc directory and the 1761.290Smartin compat ones (the above command will do that). 1771.288Smartin 1781.287Skre20171010: 1791.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 1801.287Skre means that its objdir (or *.d and .depend at least) might need 1811.287Skre to be manually removed - or a build done once without -u. 1821.287Skre 1831.286Smrg20170822: 1841.286Smrg a new version of GMP has been imported and probably 1851.286Smrg will break parts of builds related to themselves or GCC, both 1861.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 1871.286Smrg and MPC objdirs or build once without -u. 1881.286Smrg 1891.285Smrg20170816: 1901.285Smrg a new version of MPFR and MPC have been imported and probably 1911.285Smrg will break parts of builds related to themselves or GCC, both 1921.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 1931.285Smrg and MPC objdirs or build once without -u. 1941.285Smrg 1951.284Smartin20170402: 1961.284Smartin a new version of dhcpcd has been imported, which does not support 1971.284Smartin update builds from the previous version. Remove your 1981.284Smartin external/bsd/dhcpcd object dir or build once without -u. 1991.284Smartin 2001.281Sroy20170211: 2011.281Sroy a new terminfo database has been imported. 2021.281Sroy The structure of it has changed slightly from prior versions and 2031.281Sroy an updated tic tool is required. 2041.281Sroy If you build.sh, don't use -u 2051.281Sroy 2061.280Skre20170207: 2071.278Skre various arch dependent libc/exect.S files were removed 2081.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2091.279Skre if it exists) or do a clean build. 2101.279Skre (This is a bug in the make system, it should be corrected without 2111.279Skre human intervention, but isn't.) 2121.278Skre 2131.277Smartin20170104: 2141.277Smartin xinput build options have changed. 2151.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2161.277Smartin if you build.sh -u 2171.277Smartin 2181.276Smartin20170103: 2191.276Smartin a new version of flex has been imported. 2201.276Smartin Remove the file from obj (external/bsd/flex) 2211.276Smartin if you build.sh -u 2221.276Smartin 2231.275Sspz20161014: 2241.275Sspz a new version of OpenSSL has been imported. 2251.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2261.275Sspz if you build.sh -u 2271.275Sspz 2281.274Smartin20161009: 2291.274Smartin a new version of dhcpcd has been imported with slightly changed 2301.274Smartin build infrastructure. When doing a build.sh -u this requires 2311.274Smartin pruning the external/bsd/dhcpcd objdir. 2321.274Smartin 2331.273Smrg20160914: 2341.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2351.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2361.273Smrg and a clean objdir. 2371.273Smrg 2381.272Sdholland20160527: 2391.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 2401.272Sdholland been enabled. (see the amd64 entry two down for further info) 2411.272Sdholland 2421.270Schristos20160418: 2431.270Schristos libedit needs manual removal of all autogenerated files since 2441.271Schristos some of them are not autogenerated anymore. Remember that there 2451.271Schristos might be two copies of libedit if your platform builds "compat". 2461.270Schristos 2471.268Sriastrad20160410: 2481.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 2491.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 2501.268Sriastrad executables, means all code, including executables and not just 2511.268Sriastrad shared libraries, is position-independent and hence able to be 2521.268Sriastrad relocated by ASLR, address space layout randomization. 2531.268Sriastrad 2541.268Sriastrad The change was made in Makefile variables for compiler and 2551.268Sriastrad linker flags, for which make(1) does not record dependencies, 2561.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 2571.268Sriastrad 2581.268Sriastrad Partial rebuilds with some modified source files will likely 2591.268Sriastrad fail when linking executables, since the linker refuses to mix 2601.268Sriastrad position-independent code with position-dependent code in 2611.268Sriastrad position-independent executables: 2621.268Sriastrad 2631.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 2641.268Sriastrad 2651.267Smrg20160401: 2661.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 2671.269Sdholland Some people have found that cleandir is not sufficient, so if 2681.269Sdholland in doubt delete the entire object directory tree for gcc. 2691.267Smrg 2701.266Saymeric20160306: 2711.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 2721.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 2731.265Saymeric non-NetBSD hosts if linked with stale object files produced 2741.265Saymeric while they included a non-NetBSD regex.h. 2751.265Saymeric In any case, you should "make cleandir" at least these tools 2761.265Saymeric before updating your toolchain. 2771.265Saymeric 2781.264Smartin20160125: 2791.264Smartin Dtrace has been enabled by default on some architectures. 2801.264Smartin When doing an update build, make sure to clean the etc/mtree 2811.264Smartin object directory before starting the build - otherwise the 2821.264Smartin needed directories in destdir will not be created. 2831.264Smartin An easy way to do this is: 2841.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 2851.264Smartin 2861.263Sdholland20150818: 2871.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 2881.263Sdholland again. 2891.263Sdholland 2901.262Schristos20150413: 2911.262Schristos New acpica requires "make cleandir" and reinstalling yacc 2921.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 2931.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 2941.262Schristos 2951.261Smartin20150404: 2961.261Smartin Lint changes require a full rebuild of the tool, so make 2971.261Smartin sure to build without -u option to build.sh, or manually 2981.261Smartin do a make cleandir in src/tools/lint1 and 2991.261Smartin src/usr.bin/xlint. 3001.261Smartin 3011.260Sskrll20150310: 3021.260Sskrll Improvements to openssl for arm mean that update builds of 3031.260Sskrll the openssl libraries will fail. A make cleandir in 3041.260Sskrll external/bsd/openssl/lib is needed 3051.260Sskrll 3061.258Smartin20141026: 3071.259Smsaitoh A mishap during the import of pppd may cause your corruption 3081.258Smartin in your cvs directory if you happened to do a cvs update 3091.258Smartin during a short period of time. To fix, just remove the 3101.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3111.258Smartin and let cvs restore it on next update. 3121.258Smartin 3131.256Sapb20140721: 3141.256Sapb The src/external/mit/lua/src directory was accidentally created 3151.256Sapb and then deleted in the CVS repository. If you get errors like 3161.256Sapb 3171.256Sapb cvs [update aborted]: cannot open directory 3181.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3191.256Sapb 3201.256Sapb then delete your local copy of that directory tree and try again. 3211.256Sapb 3221.255Sjoerg20140530: 3231.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3241.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3251.255Sjoerg 3261.251Smartin20140131: 3271.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3281.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3291.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3301.251Smartin 3311.250Schristos20131227: 3321.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3331.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3341.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3351.250Schristos statements to avoid being exposed. 3361.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3371.250Schristos to make clean in libc 3381.250Schristos 3391.249Smrg20131129: 3401.249Smrg The GMP sources were updated, and builds will likely fail without 3411.249Smrg cleaning their build trees for both tools and in-tree, like below. 3421.249Smrg 3431.248Smrg20131128: 3441.248Smrg The MPC and MPFR sources were updated, and builds may require their 3451.248Smrg tools and in-tree directories cleaned for successful updates. 3461.248Smrg 3471.246Smartin20130605: 3481.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 3491.247Sspz to IPSEC (and the older IPSEC version removed). 3501.247Sspz 3511.247Sspz20130605: 3521.246Smartin Previous freetype installations eroneously installed private 3531.246Smartin header files. If you are building against a non-empty $DESTDIR, 3541.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 3551.246Smartin 3561.245Smrg20130531: 3571.245Smrg The xdm update may cause build failure due to xdm.man being 3581.245Smrg in the obj tree. Make sure to ensure any like this: 3591.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 3601.245Smrg is fixed by deleting the xdm.man in the obj tree. 3611.245Smrg 3621.244Smrg20130530: 3631.244Smrg Updates of many xsrc packages will leave old .pc files around. 3641.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 3651.244Smrg 3661.242Schristos20130301: 3671.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 3681.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 3691.242Schristos 3701.238Sdholland20120726: 3711.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 3721.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 3731.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 3741.241Swiz some cases may succeed and install broken OpenSSL libraries that 3751.240Sdholland cause third-party software to link incorrectly and/or crash. 3761.238Sdholland 3771.237Swiz20120507: 3781.241Swiz The database schema for makemandb was changed. You will 3791.237Swiz need to update the database using 'makemandb -f' or wait 3801.237Swiz for the next weekly run to fix it. 3811.237Swiz 3821.236Sbsh20120319: 3831.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 3841.236Sbsh size of db_symtab automatically. You need to update dbsym in 3851.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 3861.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 3871.236Sbsh mk.conf. 3881.236Sbsh 3891.235Sjoerg20120216: 3901.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 3911.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 3921.239Sdholland and 20120216, daily and weekly could have created an unreadable 3931.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 3941.235Sjoerg the next run of weekly will fix it. 3951.233Sjoerg 3961.232Schristos20111227: 3971.232Schristos If you built between 20111225 and 20111227 you need to remove 3981.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 3991.232Schristos bump has been reverted. 4001.232Schristos 4011.231Stls20111125: 4021.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4031.231Stls means it should no longer be explicitly listed in kernel 4041.231Stls configuration files. The line "pseudo-device rnd" should be 4051.231Stls removed from any custom kernel config files users may have. 4061.231Stls 4071.230Stls20111119: 4081.230Stls A problem with the datastructures used by the rndctl(8) 4091.230Stls utility (pointers in datastructures in an array, making 32->64 4101.230Stls bit compatibility very painful) has been fixed in a 4111.230Stls non-backwards-compatible way. If you replace your kernel, 4121.230Stls replace your rndctl executable too. 4131.241Swiz 4141.229Sjym20111001: 4151.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4161.229Sjym changed and their new version is not backward compatible with the old 4171.241Swiz one. So ensure that all consumers of these functions (currently: 4181.229Sjym quota2 code and its tests) are updated together with the new lib. 4191.229Sjym 4201.228Smrg20110817: 4211.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4221.228Smrg DESTDIR for them should be deleted before updating. 4231.228Smrg 4241.227Sriastrad20110806: 4251.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4261.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4271.227Sriastrad 4281.226Smrg20110805: 4291.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4301.226Smrg the tree to be cleaned. Best to delete both objdir and 4311.226Smrg DESTDIR before running this update. So far, only the 4321.226Smrg sparc64, mips and powerpc platforms have changed. 4331.226Smrg 4341.225Smatt20110803: 4351.241Swiz The layout of external/public-domain/xz has changed. To do an 4361.225Smatt update build you will have to remove the contents of the OBJDIR 4371.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4381.225Smatt is now a directory. 4391.225Smatt 4401.223Sjoerg20110410: 4411.241Swiz The configuration of src/tools/gcc has changed. To do an 4421.224Sdholland update build you have to clean both tools/binutils and 4431.224Sdholland tools/gcc by hand. 4441.223Sjoerg 4451.222Splunky20110328: 4461.222Splunky Building the Xorg binary was moved into a subdirectory to fix 4471.241Swiz ordering issues with "make all". It may be necessary to remove 4481.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 4491.222Splunky if your update build fails, as the "Xorg" entry there is now a 4501.222Splunky directory. 4511.222Splunky 4521.220Sjoerg20110121: 4531.221Slukem Assembler files no longer use -traditional-cpp. This can break 4541.220Sjoerg the build of individual parts of the tree. This is handled 4551.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 4561.220Sjoerg and re-run config(1) for any kernel configurations as needed. 4571.218Sjoerg 4581.217Sjruoho20101217: 4591.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 4601.241Swiz by default. It may be necessary to manually update passwd(5) and 4611.217Sjruoho group(5) in order to make the program work with existing setups. 4621.217Sjruoho 4631.216Schristos20101125: 4641.216Schristos The latest changes to setenv(3) dissallow setting environment 4651.241Swiz variables with names that contain '='. Revision 1.18 of env.c 4661.241Swiz assumed that this was allowed. Installing a new libc with an 4671.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 4681.216Schristos break which affects the autoconf tests for dependency finding, 4691.216Schristos so building gcc will end up printing: 4701.216Schristos checking dependency style of gcc... none 4711.216Schristos configure: error: no usable dependency style found 4721.216Schristos Fix it by rebuilding and re-installing env. 4731.138Slukem 4741.215Smrg20101119: 4751.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 4761.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 4771.215Smrg have any build problems with xsrc, or problems with mismatched 4781.215Smrg versions between xorg-server and drivers. 4791.215Smrg 4801.213Sjmmv20100604: 4811.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 4821.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 4831.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 4841.213Sjmmv trees by hand. 4851.213Sjmmv 4861.211Stnozaki20100522: 4871.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 4881.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 4891.212Smrg build problems with xsrc. 4901.212Smrg 4911.212Smrg20100522: 4921.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 4931.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 4941.211Stnozaki 4951.210Schristos20100520: 4961.241Swiz The location of the xkb compiled descriptions has changed. Please 4971.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 4981.210Schristos 4991.209Snjoly20100222: 5001.209Snjoly The shared objects file extension has been changed from .so to 5011.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5021.209Snjoly libXX.so. All now stale regular .so files can be removed from 5031.209Snjoly your object directories. 5041.209Snjoly 5051.208Sroy20100204: 5061.208Sroy The termcap database has been removed from the sources, 5071.208Sroy but has not been marked obsolete so it is not removed 5081.208Sroy from the system when upgrading. 5091.208Sroy As such, you will need to remove them from your object 5101.208Sroy and destination directories. 5111.208Sroy 5121.203Sdyoung20091101: 5131.205Sdholland After updating, it may be necessary to make the 'cleandir' 5141.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5151.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5161.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5171.203Sdyoung 5181.202Smrg20091001: 5191.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5201.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5211.206Sdholland 5221.206Sdholland20091001: 5231.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5241.202Smrg symlink, failing the build. Delete the link, and the subdir 5251.202Smrg it is in, and retry your build. 5261.202Smrg 5271.201Sdsl20090718: 5281.201Sdsl libc build changed so that strchr() provides the extra entry 5291.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5301.201Sdsl may fail because the archive contains the unwanted index.o. 5311.201Sdsl (Similarly for strrchr() and rindex().) 5321.201Sdsl 5331.198Smrg20090709: 5341.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5351.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5361.198Smrg 5371.197Smrg20090616: 5381.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 5391.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 5401.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 5411.197Smrg subdirectory has been changed into a file, and this needs to 5421.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 5431.197Smrg 5441.195Sperry20090501: 5451.195Sperry Several new functions were added to string.h/libc, and this 5461.195Sperry can cause autoconf problems during the tool build for people 5471.241Swiz who fail to clean out their tools objects properly. If you 5481.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 5491.195Sperry failure during the tool build, clean out all your tools 5501.195Sperry objects and start again. 5511.195Sperry 5521.194Smrg20090325: 5531.194Smrg The i386 port was switched to i486 default toolchain. This requires 5541.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 5551.194Smrg 5561.192Sskrll20090126: 5571.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 5581.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 5591.207Smbalmer to avoid using the old assembly stub. 5601.192Sskrll 5611.191Sjoerg20090202: 5621.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 5631.191Sjoerg detection. It is recommented to rebuild the cache with 5641.191Sjoerg ``pkg_admin rebuild''. 5651.191Sjoerg 5661.184Schristos20090110: 5671.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 5681.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 5691.188Schristos This is needed even in the MODULAR kernel because there is 5701.188Schristos conditionally compiled code in rtsock.c. 5711.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 5721.184Schristos before installing. 5731.184Schristos 3. If you don't use build.sh and you build directly to root, and 5741.241Swiz your build breaks in the middle, don't despair. Make sure headers 5751.184Schristos are installed properly, and start building libraries first libc 5761.184Schristos and libutil, install them and then continue building all the 5771.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 5781.184Schristos the new libraries are installed, you can restart the build. 5791.184Schristos 4. If you compile packages and you notice link time warnings, 5801.189Shubertf rebuild the required packages to update their shared libraries. 5811.189Shubertf Any package you rebuild will require rebuilding all the packages 5821.189Shubertf that depend on it. 5831.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 5841.186Schristos will be upgraded and it will not be backwards compatible. 5851.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 5861.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 5871.241Swiz for utmp. You are better off removing the old files after 5881.190Sapb upgrading. The automated clearing of /var/run during 5891.190Sapb boot, and the automated rotating of files in /var/log by 5901.190Sapb newsyslog(8), may mean that you do not have to remove the 5911.190Sapb files manually. 5921.190Sapb 7. The optional accounting file (/var/account/acct, see 5931.190Sapb accton(8)) has not been versioned, and will need to be 5941.190Sapb removed. The automatic rotation of the accounting file by 5951.190Sapb /etc/daily limits the bad consequences of failure to remove 5961.190Sapb the file. 5971.196Sdholland 8. Application software that writes time_t to binary files on 5981.241Swiz disk will break or need attention. Most notably: if you are 5991.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6001.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6011.185Sjmcneill 6021.183Spgoyette20081219: 6031.183Spgoyette config(1) has been updated, and one of the files it creates - 6041.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6051.183Spgoyette (done automatically by build.sh) and then you need to rerun 6061.183Spgoyette config on all kernel configuration files before rebuilding those 6071.183Spgoyette kernels. 6081.183Spgoyette 6091.181Scube20081205: 6101.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6111.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6121.181Scube set and will appear as extra files for MKX11=no update builds. 6131.178Slukem 6141.179Stsutsui20081122: 6151.182Stsutsui On i386, various kernel options(4) in GENERIC including 6161.180Swiz file systems have been disabled and moved into kernel modules. 6171.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6181.179Stsutsui following files as well as a new GENERIC kernel: 6191.179Stsutsui 6201.179Stsutsui - build and install kernel modules from src/sys/modules 6211.179Stsutsui 6221.179Stsutsui - install the latest bootloader, which will load a module 6231.180Swiz for the file system from which the kernel is loaded automatically 6241.179Stsutsui 6251.180Swiz If you have to load your kernel from a file system which is not of 6261.180Swiz the same type as the root file system, you have to load the necessary 6271.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6281.179Stsutsui 6291.178Slukem20080827: 6301.178Slukem If you built and installed a libc from sources between 6311.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6321.178Slukem which results in false errors reported by lint(1). 6331.178Slukem Since this breaks the libc build itself, manual help is 6341.180Swiz needed -- lint must be disabled temporarily, e.g.: 6351.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6361.178Slukem 6371.177Schristos20080813: 6381.177Schristos MKDEBUG build was broken because the .depend files did not know 6391.241Swiz about .go files. You need to remove all .depend files and rebuild. 6401.177Schristos 6411.200Sdholland20080802: 6421.200Sdholland A regression in binary compatibility for pthread_mutex_t has 6431.241Swiz been fixed. Unfortunately, the price is breaking compatibility 6441.200Sdholland for -current. 6451.200Sdholland 6461.200Sdholland Threaded programs (using libpthread) and C++ programs (using 6471.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 6481.200Sdholland be recompiled. 6491.200Sdholland 6501.200Sdholland One way to find affected pkgsrc packages: 6511.200Sdholland 6521.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 6531.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 6541.200Sdholland 6551.175Ssimonb20080731: 6561.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 6571.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 6581.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 6591.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 6601.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 6611.176Ssimonb also requires the super block to be in the UFS2 format. You 6621.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 6631.175Ssimonb 6641.174Slukem20080721: 6651.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 6661.174Slukem isn't defined. 6671.174Slukem 6681.173Sfreza20080531: 6691.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 6701.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 6711.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 6721.241Swiz won't work correctly. The following sequence of commands: 6731.173Sfreza 6741.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 6751.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 6761.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 6771.173Sfreza 6781.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 6791.173Sfreza 6801.172Slukem20080503: 6811.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 6821.172Slukem 6831.171She20080521: 6841.171She For a while, unprivileged UPDATE builds would fail to 6851.171She succeed at the checkflist stage, complaining that 6861.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 6871.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 6881.171She If you already hit this problem, update the .mk file, 6891.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 6901.171She 6911.174Slukem20080303: 6921.174Slukem Linker warnings are now fatal if $WARNS>0. 6931.174Slukem 6941.170Schristos20080126: 6951.170Schristos The posix_fadvise system call has been changed from an assembly 6961.241Swiz stub, to a c file that calls an assembly stub. You need to 6971.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 6981.170Schristos avoid using the old assembly stub. 6991.170Schristos 7001.168Sjoerg20071209: 7011.241Swiz The acpiec(4) driver has been split into two attachments. If you 7021.168Sjoerg get ACPI errors before the attachment, please update your kernel 7031.169Swiz configuration file appropriately or see GENERIC for more details. 7041.168Sjoerg 7051.166Sxtraeme20071115: 7061.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7071.166Sxtraeme argument specified in the kernel configuration file is not valid 7081.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7091.241Swiz rather than the EC address port. Please update your kernel 7101.167Swiz configuration file appropriately or see GENERIC for more details. 7111.166Sxtraeme 7121.165Sjmmv20071028: 7131.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7141.165Sjmmv You need to update any custom kernel configuration file you have 7151.165Sjmmv to remove any references to pccons (which includes removing the 7161.165Sjmmv now useless XSERVER option) and replace them with the correct 7171.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7181.165Sjmmv for more details. 7191.165Sjmmv 7201.164Sgdt20070913: 7211.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7221.164Sgdt enumerate interfaces was fixed. The bug began to cause 7231.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7241.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7251.164Sgdt could not enumerate interfaces. (These are noted because 7261.164Sgdt normal kernel/userspace version matching hygiene is not 7271.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7281.164Sgdt and userland are from after 20070913. 7291.164Sgdt 7301.163Sjoerg20070703: 7311.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7321.199Sdholland calls the target-specific strip program, and the logic to pass 7331.199Sdholland down STRIP from make has been removed. This requires a 7341.199Sdholland re-installation of tools. 7351.163Sjoerg 7361.161Sdsl20070422: 7371.161Sdsl The way OS emulations lookup filenames inside the emulation root 7381.161Sdsl has been changed. Rather than modify the pathname (and copy back 7391.161Sdsl to userspace) namei() and lookup() directly check the emulation 7401.241Swiz root. One side effect is that absolute symlinks inside the emulated 7411.167Swiz root file system will be relative to that file system - unless they 7421.161Sdsl start /../ this is useful when the emulated root is a real install 7431.161Sdsl that has such links. 7441.161Sdsl This might affect symlinks that have been added to reference outside 7451.161Sdsl the emulated root. 7461.161Sdsl 7471.160Sjmcneill20070412: 7481.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 7491.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 7501.160Sjmcneill example. 7511.160Sjmcneill 7521.159Sgdt20070319: 7531.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 7541.159Sgdt on many platforms due to incorrect flags settings. If you 7551.159Sgdt updated and built after about 20070315, do "nbmake-$arch 7561.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 7571.159Sgdt rebuild of object files that might have been built 7581.159Sgdt incorrectly, and ensure that you have at least 7591.159Sgdt src/lib/libc/Makefile 1.130. 7601.159Sgdt 7611.241Swiz20070210: 7621.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 7631.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 7641.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 7651.158Sdbj will allow dependencies on those files to get get rebuilt 7661.158Sdbj 7671.157Sapb20070209: 7681.157Sapb The threading model was changed when the newlock2 branch 7691.157Sapb was merged to NetBSD-current. If you boot with a new 7701.157Sapb kernel (version 4.99.10), then you also need a new pthread 7711.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 7721.157Sapb an old kernel, then you need the old pthread library 7731.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 7741.157Sapb the pthread library in sync, old threaded applications should 7751.157Sapb continue to work with an old or new kernel. Note that named(8) 7761.157Sapb is the only threaded application in the base system. 7771.157Sapb 7781.154She20061214: 7791.154She Following the move of string_to_flags() and flags_to_string() 7801.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 7811.154She will need to do a "make cleandir" in 7821.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 7831.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 7841.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 7851.156She as the installation images in distrib/ 7861.154She in order to excise stale references to the old stat_flags.h header 7871.154She file in the ls sources -- stat_flags.h has been removed. 7881.154She 7891.152Schristos20061108: 7901.152Schristos The configure script used in the src/tools/gcc compiler has been 7911.152Schristos changed to indicate that our libc has ssp support built-in and 7921.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 7931.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 7941.152Schristos 7951.151Srpaulo20061009: 7961.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 7971.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 7981.151Srpaulo 7991.150Sbjh2120060814: 8001.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8011.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8021.150Sbjh21 kernel configuration for an example. X servers from the last 8031.150Sbjh21 few years should cope. 8041.150Sbjh21 8051.149Schristos20060703: 8061.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8071.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8081.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8091.149Schristos 8101.148Sdogcow20060627: 8111.148Sdogcow socket(2) has changed, and its system call has been versioned. 8121.148Sdogcow For userlands with the old version of socket(2), make sure that 8131.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8141.148Sdogcow errors will result. 8151.148Sdogcow 8161.1SabsHints for a more successful build: 8171.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8181.123Sjmc Use build.sh, but do not use its "expert mode": 8191.132Sjmmv This will automatically build the tools in the 8201.123Sjmc correct order, and it will keep the tools and the 8211.123Sjmc new build products from interfering with the running 8221.123Sjmc system. This will allow you to ignore most of the 8231.123Sjmc other advice in this file. 8241.2Smrg Build a new kernel first: 8251.2Smrg This makes sure that any new system calls or features 8261.2Smrg expected by the new userland will be present. This 8271.2Smrg helps to avoid critical errors when upgrading. 8281.1Sabs Use object directories: 8291.1Sabs This helps to keep stale object 8301.1Sabs files from polluting the build if a Makefile "forgets" 8311.1Sabs about one. It also makes it easier to clean up after 8321.1Sabs a build. It's also necessary if you want to use the 8331.1Sabs same source tree for multiple machines. 8341.123Sjmc To use object directories with build.sh: 8351.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8361.123Sjmc To use object directories without using build.sh: 8371.1Sabs a) cd /usr/src ; make cleandir 8381.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8391.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8401.1Sabs d) cd /usr/src ; make build 8411.2Smrg Note that running "make obj" in a directory will create 8421.2Smrg in obj.$MACHINE directory. 8431.1Sabs Build to a DESTDIR: 8441.123Sjmc This helps to keep old installed files (especially libraries) 8451.123Sjmc from interfering with the new build. 8461.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8471.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8481.123Sjmc environment variable before running make build. It should be 8491.123Sjmc set to the pathname of an initially empty directory. 8501.123Sjmc Problems: if you do not use build.sh, you might need to 8511.123Sjmc update critical utilities without using DESTDIR since 8521.123Sjmc nothing is executed from what is installed in DESTDIR. 8531.123Sjmc (See critical utils, below.) 8541.1Sabs Build often: 8551.1Sabs This keeps critical utilities current enough to not choke 8561.1Sabs on any other part of the source tree that depends on up to 8571.123Sjmc date functionality. If you use build.sh, you should not have 8581.123Sjmc this problem. 8591.241Swiz 8601.1SabsWhat to do if things don't work: 8611.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8621.230StlsWhen things don't work there are usually a few things that commonly 8631.1Sabsshould be done. 8641.1Sabs 1) make includes 8651.1Sabs This should be done automatically by make build. 8661.1Sabs 2) cd share/mk && make install 8671.1Sabs Again, automatically done by make build. 8681.1Sabs 8691.1SabsFailsafe rebuild of a small part of the tree: 8701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8711.1SabsTo make sure you rebuild something correctly you want to do 8721.1Sabssomething like the following: 8731.1Sabs 1) Make sure the includes and .mk files are up to date. 8741.1Sabs 2) Make sure any program used to build the particular 8751.1Sabs utility is up to date. (yacc, lex, etc...) 8761.1Sabs 3) cd ...path/to/util... 8771.1Sabs make cleandir 8781.1Sabs rm ...all obj directories... 8791.1Sabs make cleandir # yes, again 8801.1Sabs make obj 8811.1Sabs make depend && make 8821.1Sabs 8831.1SabsFailsafe rebuild of the entire tree: 8841.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8851.1SabsIf you really want to make sure the source tree is clean and 8861.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 8871.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 8881.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 8891.1Sabs 8901.1Sabs---cut here--- 8911.1Sabs#!/bin/sh 8921.1Sabs. /etc/mk.conf 8931.1Sabs 8941.58Slukemif [ -z $NETBSDSRCDIR ] ; then 8951.58Slukem NETBSDSRCDIR=/usr/src 8961.1Sabsfi 8971.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 8981.1Sabs echo Unable to find sources 8991.1Sabs exit 1 9001.1Sabsfi 9011.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9021.1Sabs 9031.1Sabsif [ -z $BSDOBJDIR ] ; then 9041.1Sabs BSDOBJDIR=/usr/obj 9051.1Sabsfi 9061.1Sabsif [ -d $BSDOBJDIR ] ; then 9071.1Sabs rm -rf $BSDOBJDIR 9081.1Sabsfi 9091.1Sabs 9101.58Slukemcd $NETBSDSRCDIR && make cleandir 9111.1Sabs 9121.1Sabs---cut here--- 9131.1Sabs 9141.1SabsCritical utilities: 9151.1Sabs^^^^^^^^^^^^^^^^^^^ 9161.3Sitojun usr.bin/compile_et 9171.1Sabs usr.bin/make 9181.1Sabs usr.bin/yacc 9191.1Sabs usr.bin/lex 9201.11Slukem usr.bin/xlint 9211.142Sdrochner usr.bin/config 9221.1Sabs 9231.34SsimonbOther problems and possible solutions: 9241.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9251.1SabsSymptom:Complaints involving a Makefile. 9261.17SerhFix: Rebuild usr.bin/make: 9271.17Serh cd usr.bin/make && make && make install 9281.111Ssimonb Or, a failsafe method if that doesn't work: 9291.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9301.17Serh 9311.1SabsFix: Make sure .mk files are up to date. 9321.1Sabs cd share/mk && make install 9331.2Smrg 9341.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9351.142SdrochnerFix: Rebuild usr.bin/config 9361.1Sabs 9371.1SabsSymptom: 9381.1SabsFix: Rebuild usr.bin/yacc 9391.1Sabs 9401.1SabsSymptom: 9411.1SabsFix: Rebuild usr.bin/lex 9421.1Sabs 9431.1SabsSymptom: 9441.1SabsFix: rm /usr/lib/libbfd.a 9451.4Sitojun 9461.4SitojunSymptom:Obsolete intermediate files are used during compilation 9471.4SitojunFix: Try the following sequence of commands in the directory in question. 9481.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9491.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9501.4Sitojun may remain. The command tries to clean everything up) 9511.5Swiz 9521.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 9531.207Smbalmer pointer type 9541.5SwizFix: Rebuild and install usr.bin/menuc 9551.12Sitojun 9561.12SitojunSymptom:mklocale not found during build in share/locale/ctype 9571.12SitojunFix: Build and install usr.bin/mklocale 9581.13Sdogcow 9591.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 9601.13SdogcowFix: Rebuild and install lib/libc 9611.13Sdogcow 9621.142SdrochnerSymptom:usr.bin/config fails to build. 9631.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 9641.13Sdogcow 9651.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 9661.19ScgdFix: Rebuild and install lib/libc 9671.24Sabs 9681.24SabsSymptom:lint does not understand the '-X' option 9691.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 9701.223Sjoerg 9711.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 9721.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 9731.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 9741.257Sapb 9751.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 9761.257Sapb No such file or directory. 9771.257SapbCause: If a directory is created by mistake, then it is sometimes 9781.257Sapb deleted from the CVS repository using administrative commands 9791.257Sapb that bypass the normal cvs access controls. If your cvs working tree 9801.257Sapb contains references to a directory that has been deleted on the 9811.257Sapb server in this way, then "cvs update" reports this error. 9821.257SapbFix: Recursively delete the affected directory from your working tree 9831.257Sapb and try the update again. 984