UPDATING revision 1.307
11.307Smrg$NetBSD: UPDATING,v 1.307 2020/03/11 21:07:40 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.307Smrg20200311: 231.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 241.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 251.307Smrg 261.306Schristos20191118: 271.306Schristos More architectures were switched to gcc8: 281.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 291.306Schristos The same comments as in 20191022 apply. 301.306Schristos 311.305Smartin20191112: 321.305Smartin The LLVM update requires a clean rebuild for all architectures using 331.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 341.305Smartin 351.304Smartin20191022: 361.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 371.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 381.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 391.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 401.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 411.304Smartin daily builds and install that before doing the next in-place build. 421.304Smartin 431.303Smrg20191001: 441.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 451.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 461.303Smrg directory, and also clean src/external/gpl3/gcc. 471.303Smrg 481.302Sriastrad20190903: 491.306Schristos Files with names that coincide with existing files' names on 501.302Sriastrad case-insensitive file systems were inadvertently committed, for 511.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 521.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 531.302Sriastrad ran build.sh distribution or ran build.sh release, you must 541.302Sriastrad manually delete the following files in your DESTDIR (which is 551.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 561.302Sriastrad them: 571.302Sriastrad 581.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 591.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 601.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 611.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 621.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 631.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 641.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 651.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 661.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 671.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 681.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 691.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 701.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 711.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 721.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 731.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 741.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 751.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 761.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 771.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 781.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 791.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 801.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 811.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 821.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 831.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 841.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 851.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 861.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 871.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 881.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 891.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 901.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 911.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 921.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 931.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 941.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 951.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 961.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 971.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 981.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 991.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1001.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1011.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1021.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1031.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1041.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1051.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1061.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1071.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1081.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1091.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1101.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1111.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1121.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1131.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1141.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1151.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1161.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1171.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1181.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1191.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1201.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1211.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1221.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1231.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1241.302Sriastrad 1251.302Sriastrad We will re-import these radeon firmware images another way 1261.302Sriastrad later. 1271.302Sriastrad 1281.301Smartin20190727: 1291.301Smartin The uefi bootloader has gained tftp support and needs a clean 1301.301Smartin build. If you do update builds, manually clean its object 1311.301Smartin directory by something like: 1321.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1331.301Smartin 1341.300Smartin20190723: 1351.300Smartin The jemalloc allocator in libc is now build without extended 1361.300Smartin debugging (for performance reasons). In update builds make sure 1371.300Smartin to rebuild it completly, by removing all affected object files, 1381.300Smartin including compat builds, something like: 1391.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1401.300Smartin 1411.299Smrg20190207: 1421.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1431.299Smrg 1441.298Smartin20180924: 1451.298Smartin A newer OpenSSL version has been imported. If you are doing 1461.298Smartin update builds, make sure to remove all old obj dirs, like: 1471.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 1481.298Smartin 1491.297Sjoerg20180717: 1501.297Sjoerg On aarch64 int64_t and related types have changed from long long 1511.297Sjoerg to long. This requires recompiling all C++ binaries. 1521.297Sjoerg 1531.296Smartin20180713: 1541.296Smartin On amd64 and i386 static binaries are now build position 1551.296Smartin independend. This requires recompilation of all object 1561.296Smartin files used to create the crunched /rescue binary. 1571.296Smartin Clean the rescue directory in your obj directory before 1581.296Smartin doing an update build, otherwise linking will fail. 1591.296Smartin 1601.293Sjakllsch20180414: 1611.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 1621.293Sjakllsch removal of tools/binutils objects directory may be required 1631.293Sjakllsch to fix tools build failure. 1641.293Sjakllsch 1651.292Smrg20180311: 1661.292Smrg bdftopcf was updated and may need cleaning in the 1671.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 1681.292Smrg link errors. 1691.292Smrg 1701.291Smrg20180212: 1711.291Smrg between OpenSSL and GCC updates, many things may fail to build. 1721.291Smrg any failure that looks like GCC or openssl is best handled by 1731.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 1741.291Smrg is recommended if build failures occur. 1751.291Smrg 1761.288Smartin20171225: 1771.288Smartin removal of the vadvise syscall requires manual removal of all 1781.288Smartin associated files from the libc build object directory (including 1791.289Schristos the .depend files) - a command like: 1801.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 1811.289Schristos For architectures that support multiple "compat" binary targets, 1821.289Schristos you'll need to cleanup both the regular libc directory and the 1831.290Smartin compat ones (the above command will do that). 1841.288Smartin 1851.287Skre20171010: 1861.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 1871.287Skre means that its objdir (or *.d and .depend at least) might need 1881.287Skre to be manually removed - or a build done once without -u. 1891.287Skre 1901.286Smrg20170822: 1911.286Smrg a new version of GMP has been imported and probably 1921.286Smrg will break parts of builds related to themselves or GCC, both 1931.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 1941.286Smrg and MPC objdirs or build once without -u. 1951.286Smrg 1961.285Smrg20170816: 1971.285Smrg a new version of MPFR and MPC have been imported and probably 1981.285Smrg will break parts of builds related to themselves or GCC, both 1991.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2001.285Smrg and MPC objdirs or build once without -u. 2011.285Smrg 2021.284Smartin20170402: 2031.284Smartin a new version of dhcpcd has been imported, which does not support 2041.284Smartin update builds from the previous version. Remove your 2051.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2061.284Smartin 2071.281Sroy20170211: 2081.281Sroy a new terminfo database has been imported. 2091.281Sroy The structure of it has changed slightly from prior versions and 2101.281Sroy an updated tic tool is required. 2111.281Sroy If you build.sh, don't use -u 2121.281Sroy 2131.280Skre20170207: 2141.278Skre various arch dependent libc/exect.S files were removed 2151.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2161.279Skre if it exists) or do a clean build. 2171.279Skre (This is a bug in the make system, it should be corrected without 2181.279Skre human intervention, but isn't.) 2191.278Skre 2201.277Smartin20170104: 2211.277Smartin xinput build options have changed. 2221.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2231.277Smartin if you build.sh -u 2241.277Smartin 2251.276Smartin20170103: 2261.276Smartin a new version of flex has been imported. 2271.276Smartin Remove the file from obj (external/bsd/flex) 2281.276Smartin if you build.sh -u 2291.276Smartin 2301.275Sspz20161014: 2311.275Sspz a new version of OpenSSL has been imported. 2321.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2331.275Sspz if you build.sh -u 2341.275Sspz 2351.274Smartin20161009: 2361.274Smartin a new version of dhcpcd has been imported with slightly changed 2371.274Smartin build infrastructure. When doing a build.sh -u this requires 2381.274Smartin pruning the external/bsd/dhcpcd objdir. 2391.274Smartin 2401.273Smrg20160914: 2411.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2421.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2431.273Smrg and a clean objdir. 2441.273Smrg 2451.272Sdholland20160527: 2461.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 2471.272Sdholland been enabled. (see the amd64 entry two down for further info) 2481.272Sdholland 2491.270Schristos20160418: 2501.270Schristos libedit needs manual removal of all autogenerated files since 2511.271Schristos some of them are not autogenerated anymore. Remember that there 2521.271Schristos might be two copies of libedit if your platform builds "compat". 2531.270Schristos 2541.268Sriastrad20160410: 2551.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 2561.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 2571.268Sriastrad executables, means all code, including executables and not just 2581.268Sriastrad shared libraries, is position-independent and hence able to be 2591.268Sriastrad relocated by ASLR, address space layout randomization. 2601.268Sriastrad 2611.268Sriastrad The change was made in Makefile variables for compiler and 2621.268Sriastrad linker flags, for which make(1) does not record dependencies, 2631.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 2641.268Sriastrad 2651.268Sriastrad Partial rebuilds with some modified source files will likely 2661.268Sriastrad fail when linking executables, since the linker refuses to mix 2671.268Sriastrad position-independent code with position-dependent code in 2681.268Sriastrad position-independent executables: 2691.268Sriastrad 2701.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 2711.268Sriastrad 2721.267Smrg20160401: 2731.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 2741.269Sdholland Some people have found that cleandir is not sufficient, so if 2751.269Sdholland in doubt delete the entire object directory tree for gcc. 2761.267Smrg 2771.266Saymeric20160306: 2781.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 2791.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 2801.265Saymeric non-NetBSD hosts if linked with stale object files produced 2811.265Saymeric while they included a non-NetBSD regex.h. 2821.265Saymeric In any case, you should "make cleandir" at least these tools 2831.265Saymeric before updating your toolchain. 2841.265Saymeric 2851.264Smartin20160125: 2861.264Smartin Dtrace has been enabled by default on some architectures. 2871.264Smartin When doing an update build, make sure to clean the etc/mtree 2881.264Smartin object directory before starting the build - otherwise the 2891.264Smartin needed directories in destdir will not be created. 2901.264Smartin An easy way to do this is: 2911.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 2921.264Smartin 2931.263Sdholland20150818: 2941.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 2951.263Sdholland again. 2961.263Sdholland 2971.262Schristos20150413: 2981.262Schristos New acpica requires "make cleandir" and reinstalling yacc 2991.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3001.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3011.262Schristos 3021.261Smartin20150404: 3031.261Smartin Lint changes require a full rebuild of the tool, so make 3041.261Smartin sure to build without -u option to build.sh, or manually 3051.261Smartin do a make cleandir in src/tools/lint1 and 3061.261Smartin src/usr.bin/xlint. 3071.261Smartin 3081.260Sskrll20150310: 3091.260Sskrll Improvements to openssl for arm mean that update builds of 3101.260Sskrll the openssl libraries will fail. A make cleandir in 3111.260Sskrll external/bsd/openssl/lib is needed 3121.260Sskrll 3131.258Smartin20141026: 3141.259Smsaitoh A mishap during the import of pppd may cause your corruption 3151.258Smartin in your cvs directory if you happened to do a cvs update 3161.258Smartin during a short period of time. To fix, just remove the 3171.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3181.258Smartin and let cvs restore it on next update. 3191.258Smartin 3201.256Sapb20140721: 3211.256Sapb The src/external/mit/lua/src directory was accidentally created 3221.256Sapb and then deleted in the CVS repository. If you get errors like 3231.256Sapb 3241.256Sapb cvs [update aborted]: cannot open directory 3251.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3261.256Sapb 3271.256Sapb then delete your local copy of that directory tree and try again. 3281.256Sapb 3291.255Sjoerg20140530: 3301.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3311.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3321.255Sjoerg 3331.251Smartin20140131: 3341.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3351.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3361.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3371.251Smartin 3381.250Schristos20131227: 3391.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3401.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3411.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3421.250Schristos statements to avoid being exposed. 3431.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3441.250Schristos to make clean in libc 3451.250Schristos 3461.249Smrg20131129: 3471.249Smrg The GMP sources were updated, and builds will likely fail without 3481.249Smrg cleaning their build trees for both tools and in-tree, like below. 3491.249Smrg 3501.248Smrg20131128: 3511.248Smrg The MPC and MPFR sources were updated, and builds may require their 3521.248Smrg tools and in-tree directories cleaned for successful updates. 3531.248Smrg 3541.246Smartin20130605: 3551.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 3561.247Sspz to IPSEC (and the older IPSEC version removed). 3571.247Sspz 3581.247Sspz20130605: 3591.246Smartin Previous freetype installations eroneously installed private 3601.246Smartin header files. If you are building against a non-empty $DESTDIR, 3611.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 3621.246Smartin 3631.245Smrg20130531: 3641.245Smrg The xdm update may cause build failure due to xdm.man being 3651.245Smrg in the obj tree. Make sure to ensure any like this: 3661.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 3671.245Smrg is fixed by deleting the xdm.man in the obj tree. 3681.245Smrg 3691.244Smrg20130530: 3701.244Smrg Updates of many xsrc packages will leave old .pc files around. 3711.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 3721.244Smrg 3731.242Schristos20130301: 3741.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 3751.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 3761.242Schristos 3771.238Sdholland20120726: 3781.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 3791.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 3801.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 3811.241Swiz some cases may succeed and install broken OpenSSL libraries that 3821.240Sdholland cause third-party software to link incorrectly and/or crash. 3831.238Sdholland 3841.237Swiz20120507: 3851.241Swiz The database schema for makemandb was changed. You will 3861.237Swiz need to update the database using 'makemandb -f' or wait 3871.237Swiz for the next weekly run to fix it. 3881.237Swiz 3891.236Sbsh20120319: 3901.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 3911.236Sbsh size of db_symtab automatically. You need to update dbsym in 3921.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 3931.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 3941.236Sbsh mk.conf. 3951.236Sbsh 3961.235Sjoerg20120216: 3971.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 3981.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 3991.239Sdholland and 20120216, daily and weekly could have created an unreadable 4001.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4011.235Sjoerg the next run of weekly will fix it. 4021.233Sjoerg 4031.232Schristos20111227: 4041.232Schristos If you built between 20111225 and 20111227 you need to remove 4051.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4061.232Schristos bump has been reverted. 4071.232Schristos 4081.231Stls20111125: 4091.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4101.231Stls means it should no longer be explicitly listed in kernel 4111.231Stls configuration files. The line "pseudo-device rnd" should be 4121.231Stls removed from any custom kernel config files users may have. 4131.231Stls 4141.230Stls20111119: 4151.230Stls A problem with the datastructures used by the rndctl(8) 4161.230Stls utility (pointers in datastructures in an array, making 32->64 4171.230Stls bit compatibility very painful) has been fixed in a 4181.230Stls non-backwards-compatible way. If you replace your kernel, 4191.230Stls replace your rndctl executable too. 4201.241Swiz 4211.229Sjym20111001: 4221.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4231.229Sjym changed and their new version is not backward compatible with the old 4241.241Swiz one. So ensure that all consumers of these functions (currently: 4251.229Sjym quota2 code and its tests) are updated together with the new lib. 4261.229Sjym 4271.228Smrg20110817: 4281.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4291.228Smrg DESTDIR for them should be deleted before updating. 4301.228Smrg 4311.227Sriastrad20110806: 4321.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4331.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4341.227Sriastrad 4351.226Smrg20110805: 4361.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4371.226Smrg the tree to be cleaned. Best to delete both objdir and 4381.226Smrg DESTDIR before running this update. So far, only the 4391.226Smrg sparc64, mips and powerpc platforms have changed. 4401.226Smrg 4411.225Smatt20110803: 4421.241Swiz The layout of external/public-domain/xz has changed. To do an 4431.225Smatt update build you will have to remove the contents of the OBJDIR 4441.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4451.225Smatt is now a directory. 4461.225Smatt 4471.223Sjoerg20110410: 4481.241Swiz The configuration of src/tools/gcc has changed. To do an 4491.224Sdholland update build you have to clean both tools/binutils and 4501.224Sdholland tools/gcc by hand. 4511.223Sjoerg 4521.222Splunky20110328: 4531.222Splunky Building the Xorg binary was moved into a subdirectory to fix 4541.241Swiz ordering issues with "make all". It may be necessary to remove 4551.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 4561.222Splunky if your update build fails, as the "Xorg" entry there is now a 4571.222Splunky directory. 4581.222Splunky 4591.220Sjoerg20110121: 4601.221Slukem Assembler files no longer use -traditional-cpp. This can break 4611.220Sjoerg the build of individual parts of the tree. This is handled 4621.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 4631.220Sjoerg and re-run config(1) for any kernel configurations as needed. 4641.218Sjoerg 4651.217Sjruoho20101217: 4661.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 4671.241Swiz by default. It may be necessary to manually update passwd(5) and 4681.217Sjruoho group(5) in order to make the program work with existing setups. 4691.217Sjruoho 4701.216Schristos20101125: 4711.216Schristos The latest changes to setenv(3) dissallow setting environment 4721.241Swiz variables with names that contain '='. Revision 1.18 of env.c 4731.241Swiz assumed that this was allowed. Installing a new libc with an 4741.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 4751.216Schristos break which affects the autoconf tests for dependency finding, 4761.216Schristos so building gcc will end up printing: 4771.216Schristos checking dependency style of gcc... none 4781.216Schristos configure: error: no usable dependency style found 4791.216Schristos Fix it by rebuilding and re-installing env. 4801.138Slukem 4811.215Smrg20101119: 4821.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 4831.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 4841.215Smrg have any build problems with xsrc, or problems with mismatched 4851.215Smrg versions between xorg-server and drivers. 4861.215Smrg 4871.213Sjmmv20100604: 4881.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 4891.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 4901.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 4911.213Sjmmv trees by hand. 4921.213Sjmmv 4931.211Stnozaki20100522: 4941.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 4951.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 4961.212Smrg build problems with xsrc. 4971.212Smrg 4981.212Smrg20100522: 4991.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 5001.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5011.211Stnozaki 5021.210Schristos20100520: 5031.241Swiz The location of the xkb compiled descriptions has changed. Please 5041.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5051.210Schristos 5061.209Snjoly20100222: 5071.209Snjoly The shared objects file extension has been changed from .so to 5081.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5091.209Snjoly libXX.so. All now stale regular .so files can be removed from 5101.209Snjoly your object directories. 5111.209Snjoly 5121.208Sroy20100204: 5131.208Sroy The termcap database has been removed from the sources, 5141.208Sroy but has not been marked obsolete so it is not removed 5151.208Sroy from the system when upgrading. 5161.208Sroy As such, you will need to remove them from your object 5171.208Sroy and destination directories. 5181.208Sroy 5191.203Sdyoung20091101: 5201.205Sdholland After updating, it may be necessary to make the 'cleandir' 5211.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5221.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5231.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5241.203Sdyoung 5251.202Smrg20091001: 5261.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5271.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5281.206Sdholland 5291.206Sdholland20091001: 5301.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5311.202Smrg symlink, failing the build. Delete the link, and the subdir 5321.202Smrg it is in, and retry your build. 5331.202Smrg 5341.201Sdsl20090718: 5351.201Sdsl libc build changed so that strchr() provides the extra entry 5361.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5371.201Sdsl may fail because the archive contains the unwanted index.o. 5381.201Sdsl (Similarly for strrchr() and rindex().) 5391.201Sdsl 5401.198Smrg20090709: 5411.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5421.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5431.198Smrg 5441.197Smrg20090616: 5451.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 5461.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 5471.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 5481.197Smrg subdirectory has been changed into a file, and this needs to 5491.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 5501.197Smrg 5511.195Sperry20090501: 5521.195Sperry Several new functions were added to string.h/libc, and this 5531.195Sperry can cause autoconf problems during the tool build for people 5541.241Swiz who fail to clean out their tools objects properly. If you 5551.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 5561.195Sperry failure during the tool build, clean out all your tools 5571.195Sperry objects and start again. 5581.195Sperry 5591.194Smrg20090325: 5601.194Smrg The i386 port was switched to i486 default toolchain. This requires 5611.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 5621.194Smrg 5631.192Sskrll20090126: 5641.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 5651.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 5661.207Smbalmer to avoid using the old assembly stub. 5671.192Sskrll 5681.191Sjoerg20090202: 5691.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 5701.191Sjoerg detection. It is recommented to rebuild the cache with 5711.191Sjoerg ``pkg_admin rebuild''. 5721.191Sjoerg 5731.184Schristos20090110: 5741.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 5751.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 5761.188Schristos This is needed even in the MODULAR kernel because there is 5771.188Schristos conditionally compiled code in rtsock.c. 5781.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 5791.184Schristos before installing. 5801.184Schristos 3. If you don't use build.sh and you build directly to root, and 5811.241Swiz your build breaks in the middle, don't despair. Make sure headers 5821.184Schristos are installed properly, and start building libraries first libc 5831.184Schristos and libutil, install them and then continue building all the 5841.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 5851.184Schristos the new libraries are installed, you can restart the build. 5861.184Schristos 4. If you compile packages and you notice link time warnings, 5871.189Shubertf rebuild the required packages to update their shared libraries. 5881.189Shubertf Any package you rebuild will require rebuilding all the packages 5891.189Shubertf that depend on it. 5901.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 5911.186Schristos will be upgraded and it will not be backwards compatible. 5921.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 5931.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 5941.241Swiz for utmp. You are better off removing the old files after 5951.190Sapb upgrading. The automated clearing of /var/run during 5961.190Sapb boot, and the automated rotating of files in /var/log by 5971.190Sapb newsyslog(8), may mean that you do not have to remove the 5981.190Sapb files manually. 5991.190Sapb 7. The optional accounting file (/var/account/acct, see 6001.190Sapb accton(8)) has not been versioned, and will need to be 6011.190Sapb removed. The automatic rotation of the accounting file by 6021.190Sapb /etc/daily limits the bad consequences of failure to remove 6031.190Sapb the file. 6041.196Sdholland 8. Application software that writes time_t to binary files on 6051.241Swiz disk will break or need attention. Most notably: if you are 6061.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6071.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6081.185Sjmcneill 6091.183Spgoyette20081219: 6101.183Spgoyette config(1) has been updated, and one of the files it creates - 6111.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6121.183Spgoyette (done automatically by build.sh) and then you need to rerun 6131.183Spgoyette config on all kernel configuration files before rebuilding those 6141.183Spgoyette kernels. 6151.183Spgoyette 6161.181Scube20081205: 6171.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6181.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6191.181Scube set and will appear as extra files for MKX11=no update builds. 6201.178Slukem 6211.179Stsutsui20081122: 6221.182Stsutsui On i386, various kernel options(4) in GENERIC including 6231.180Swiz file systems have been disabled and moved into kernel modules. 6241.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6251.179Stsutsui following files as well as a new GENERIC kernel: 6261.179Stsutsui 6271.179Stsutsui - build and install kernel modules from src/sys/modules 6281.179Stsutsui 6291.179Stsutsui - install the latest bootloader, which will load a module 6301.180Swiz for the file system from which the kernel is loaded automatically 6311.179Stsutsui 6321.180Swiz If you have to load your kernel from a file system which is not of 6331.180Swiz the same type as the root file system, you have to load the necessary 6341.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6351.179Stsutsui 6361.178Slukem20080827: 6371.178Slukem If you built and installed a libc from sources between 6381.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6391.178Slukem which results in false errors reported by lint(1). 6401.178Slukem Since this breaks the libc build itself, manual help is 6411.180Swiz needed -- lint must be disabled temporarily, e.g.: 6421.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6431.178Slukem 6441.177Schristos20080813: 6451.177Schristos MKDEBUG build was broken because the .depend files did not know 6461.241Swiz about .go files. You need to remove all .depend files and rebuild. 6471.177Schristos 6481.200Sdholland20080802: 6491.200Sdholland A regression in binary compatibility for pthread_mutex_t has 6501.241Swiz been fixed. Unfortunately, the price is breaking compatibility 6511.200Sdholland for -current. 6521.200Sdholland 6531.200Sdholland Threaded programs (using libpthread) and C++ programs (using 6541.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 6551.200Sdholland be recompiled. 6561.200Sdholland 6571.200Sdholland One way to find affected pkgsrc packages: 6581.200Sdholland 6591.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 6601.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 6611.200Sdholland 6621.175Ssimonb20080731: 6631.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 6641.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 6651.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 6661.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 6671.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 6681.176Ssimonb also requires the super block to be in the UFS2 format. You 6691.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 6701.175Ssimonb 6711.174Slukem20080721: 6721.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 6731.174Slukem isn't defined. 6741.174Slukem 6751.173Sfreza20080531: 6761.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 6771.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 6781.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 6791.241Swiz won't work correctly. The following sequence of commands: 6801.173Sfreza 6811.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 6821.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 6831.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 6841.173Sfreza 6851.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 6861.173Sfreza 6871.172Slukem20080503: 6881.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 6891.172Slukem 6901.171She20080521: 6911.171She For a while, unprivileged UPDATE builds would fail to 6921.171She succeed at the checkflist stage, complaining that 6931.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 6941.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 6951.171She If you already hit this problem, update the .mk file, 6961.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 6971.171She 6981.174Slukem20080303: 6991.174Slukem Linker warnings are now fatal if $WARNS>0. 7001.174Slukem 7011.170Schristos20080126: 7021.170Schristos The posix_fadvise system call has been changed from an assembly 7031.241Swiz stub, to a c file that calls an assembly stub. You need to 7041.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7051.170Schristos avoid using the old assembly stub. 7061.170Schristos 7071.168Sjoerg20071209: 7081.241Swiz The acpiec(4) driver has been split into two attachments. If you 7091.168Sjoerg get ACPI errors before the attachment, please update your kernel 7101.169Swiz configuration file appropriately or see GENERIC for more details. 7111.168Sjoerg 7121.166Sxtraeme20071115: 7131.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7141.166Sxtraeme argument specified in the kernel configuration file is not valid 7151.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7161.241Swiz rather than the EC address port. Please update your kernel 7171.167Swiz configuration file appropriately or see GENERIC for more details. 7181.166Sxtraeme 7191.165Sjmmv20071028: 7201.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7211.165Sjmmv You need to update any custom kernel configuration file you have 7221.165Sjmmv to remove any references to pccons (which includes removing the 7231.165Sjmmv now useless XSERVER option) and replace them with the correct 7241.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7251.165Sjmmv for more details. 7261.165Sjmmv 7271.164Sgdt20070913: 7281.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7291.164Sgdt enumerate interfaces was fixed. The bug began to cause 7301.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7311.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7321.164Sgdt could not enumerate interfaces. (These are noted because 7331.164Sgdt normal kernel/userspace version matching hygiene is not 7341.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7351.164Sgdt and userland are from after 20070913. 7361.164Sgdt 7371.163Sjoerg20070703: 7381.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7391.199Sdholland calls the target-specific strip program, and the logic to pass 7401.199Sdholland down STRIP from make has been removed. This requires a 7411.199Sdholland re-installation of tools. 7421.163Sjoerg 7431.161Sdsl20070422: 7441.161Sdsl The way OS emulations lookup filenames inside the emulation root 7451.161Sdsl has been changed. Rather than modify the pathname (and copy back 7461.161Sdsl to userspace) namei() and lookup() directly check the emulation 7471.241Swiz root. One side effect is that absolute symlinks inside the emulated 7481.167Swiz root file system will be relative to that file system - unless they 7491.161Sdsl start /../ this is useful when the emulated root is a real install 7501.161Sdsl that has such links. 7511.161Sdsl This might affect symlinks that have been added to reference outside 7521.161Sdsl the emulated root. 7531.161Sdsl 7541.160Sjmcneill20070412: 7551.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 7561.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 7571.160Sjmcneill example. 7581.160Sjmcneill 7591.159Sgdt20070319: 7601.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 7611.159Sgdt on many platforms due to incorrect flags settings. If you 7621.159Sgdt updated and built after about 20070315, do "nbmake-$arch 7631.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 7641.159Sgdt rebuild of object files that might have been built 7651.159Sgdt incorrectly, and ensure that you have at least 7661.159Sgdt src/lib/libc/Makefile 1.130. 7671.159Sgdt 7681.241Swiz20070210: 7691.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 7701.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 7711.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 7721.158Sdbj will allow dependencies on those files to get get rebuilt 7731.158Sdbj 7741.157Sapb20070209: 7751.157Sapb The threading model was changed when the newlock2 branch 7761.157Sapb was merged to NetBSD-current. If you boot with a new 7771.157Sapb kernel (version 4.99.10), then you also need a new pthread 7781.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 7791.157Sapb an old kernel, then you need the old pthread library 7801.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 7811.157Sapb the pthread library in sync, old threaded applications should 7821.157Sapb continue to work with an old or new kernel. Note that named(8) 7831.157Sapb is the only threaded application in the base system. 7841.157Sapb 7851.154She20061214: 7861.154She Following the move of string_to_flags() and flags_to_string() 7871.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 7881.154She will need to do a "make cleandir" in 7891.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 7901.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 7911.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 7921.156She as the installation images in distrib/ 7931.154She in order to excise stale references to the old stat_flags.h header 7941.154She file in the ls sources -- stat_flags.h has been removed. 7951.154She 7961.152Schristos20061108: 7971.152Schristos The configure script used in the src/tools/gcc compiler has been 7981.152Schristos changed to indicate that our libc has ssp support built-in and 7991.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8001.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8011.152Schristos 8021.151Srpaulo20061009: 8031.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8041.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8051.151Srpaulo 8061.150Sbjh2120060814: 8071.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8081.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8091.150Sbjh21 kernel configuration for an example. X servers from the last 8101.150Sbjh21 few years should cope. 8111.150Sbjh21 8121.149Schristos20060703: 8131.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8141.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8151.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8161.149Schristos 8171.148Sdogcow20060627: 8181.148Sdogcow socket(2) has changed, and its system call has been versioned. 8191.148Sdogcow For userlands with the old version of socket(2), make sure that 8201.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8211.148Sdogcow errors will result. 8221.148Sdogcow 8231.1SabsHints for a more successful build: 8241.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8251.123Sjmc Use build.sh, but do not use its "expert mode": 8261.132Sjmmv This will automatically build the tools in the 8271.123Sjmc correct order, and it will keep the tools and the 8281.123Sjmc new build products from interfering with the running 8291.123Sjmc system. This will allow you to ignore most of the 8301.123Sjmc other advice in this file. 8311.2Smrg Build a new kernel first: 8321.2Smrg This makes sure that any new system calls or features 8331.2Smrg expected by the new userland will be present. This 8341.2Smrg helps to avoid critical errors when upgrading. 8351.1Sabs Use object directories: 8361.1Sabs This helps to keep stale object 8371.1Sabs files from polluting the build if a Makefile "forgets" 8381.1Sabs about one. It also makes it easier to clean up after 8391.1Sabs a build. It's also necessary if you want to use the 8401.1Sabs same source tree for multiple machines. 8411.123Sjmc To use object directories with build.sh: 8421.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8431.123Sjmc To use object directories without using build.sh: 8441.1Sabs a) cd /usr/src ; make cleandir 8451.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8461.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8471.1Sabs d) cd /usr/src ; make build 8481.2Smrg Note that running "make obj" in a directory will create 8491.2Smrg in obj.$MACHINE directory. 8501.1Sabs Build to a DESTDIR: 8511.123Sjmc This helps to keep old installed files (especially libraries) 8521.123Sjmc from interfering with the new build. 8531.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8541.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8551.123Sjmc environment variable before running make build. It should be 8561.123Sjmc set to the pathname of an initially empty directory. 8571.123Sjmc Problems: if you do not use build.sh, you might need to 8581.123Sjmc update critical utilities without using DESTDIR since 8591.123Sjmc nothing is executed from what is installed in DESTDIR. 8601.123Sjmc (See critical utils, below.) 8611.1Sabs Build often: 8621.1Sabs This keeps critical utilities current enough to not choke 8631.1Sabs on any other part of the source tree that depends on up to 8641.123Sjmc date functionality. If you use build.sh, you should not have 8651.123Sjmc this problem. 8661.241Swiz 8671.1SabsWhat to do if things don't work: 8681.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8691.230StlsWhen things don't work there are usually a few things that commonly 8701.1Sabsshould be done. 8711.1Sabs 1) make includes 8721.1Sabs This should be done automatically by make build. 8731.1Sabs 2) cd share/mk && make install 8741.1Sabs Again, automatically done by make build. 8751.1Sabs 8761.1SabsFailsafe rebuild of a small part of the tree: 8771.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8781.1SabsTo make sure you rebuild something correctly you want to do 8791.1Sabssomething like the following: 8801.1Sabs 1) Make sure the includes and .mk files are up to date. 8811.1Sabs 2) Make sure any program used to build the particular 8821.1Sabs utility is up to date. (yacc, lex, etc...) 8831.1Sabs 3) cd ...path/to/util... 8841.1Sabs make cleandir 8851.1Sabs rm ...all obj directories... 8861.1Sabs make cleandir # yes, again 8871.1Sabs make obj 8881.1Sabs make depend && make 8891.1Sabs 8901.1SabsFailsafe rebuild of the entire tree: 8911.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8921.1SabsIf you really want to make sure the source tree is clean and 8931.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 8941.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 8951.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 8961.1Sabs 8971.1Sabs---cut here--- 8981.1Sabs#!/bin/sh 8991.1Sabs. /etc/mk.conf 9001.1Sabs 9011.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9021.58Slukem NETBSDSRCDIR=/usr/src 9031.1Sabsfi 9041.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9051.1Sabs echo Unable to find sources 9061.1Sabs exit 1 9071.1Sabsfi 9081.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9091.1Sabs 9101.1Sabsif [ -z $BSDOBJDIR ] ; then 9111.1Sabs BSDOBJDIR=/usr/obj 9121.1Sabsfi 9131.1Sabsif [ -d $BSDOBJDIR ] ; then 9141.1Sabs rm -rf $BSDOBJDIR 9151.1Sabsfi 9161.1Sabs 9171.58Slukemcd $NETBSDSRCDIR && make cleandir 9181.1Sabs 9191.1Sabs---cut here--- 9201.1Sabs 9211.1SabsCritical utilities: 9221.1Sabs^^^^^^^^^^^^^^^^^^^ 9231.3Sitojun usr.bin/compile_et 9241.1Sabs usr.bin/make 9251.1Sabs usr.bin/yacc 9261.1Sabs usr.bin/lex 9271.11Slukem usr.bin/xlint 9281.142Sdrochner usr.bin/config 9291.1Sabs 9301.34SsimonbOther problems and possible solutions: 9311.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9321.1SabsSymptom:Complaints involving a Makefile. 9331.17SerhFix: Rebuild usr.bin/make: 9341.17Serh cd usr.bin/make && make && make install 9351.111Ssimonb Or, a failsafe method if that doesn't work: 9361.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9371.17Serh 9381.1SabsFix: Make sure .mk files are up to date. 9391.1Sabs cd share/mk && make install 9401.2Smrg 9411.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9421.142SdrochnerFix: Rebuild usr.bin/config 9431.1Sabs 9441.1SabsSymptom: 9451.1SabsFix: Rebuild usr.bin/yacc 9461.1Sabs 9471.1SabsSymptom: 9481.1SabsFix: Rebuild usr.bin/lex 9491.1Sabs 9501.1SabsSymptom: 9511.1SabsFix: rm /usr/lib/libbfd.a 9521.4Sitojun 9531.4SitojunSymptom:Obsolete intermediate files are used during compilation 9541.4SitojunFix: Try the following sequence of commands in the directory in question. 9551.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9561.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9571.4Sitojun may remain. The command tries to clean everything up) 9581.5Swiz 9591.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 9601.207Smbalmer pointer type 9611.5SwizFix: Rebuild and install usr.bin/menuc 9621.12Sitojun 9631.12SitojunSymptom:mklocale not found during build in share/locale/ctype 9641.12SitojunFix: Build and install usr.bin/mklocale 9651.13Sdogcow 9661.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 9671.13SdogcowFix: Rebuild and install lib/libc 9681.13Sdogcow 9691.142SdrochnerSymptom:usr.bin/config fails to build. 9701.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 9711.13Sdogcow 9721.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 9731.19ScgdFix: Rebuild and install lib/libc 9741.24Sabs 9751.24SabsSymptom:lint does not understand the '-X' option 9761.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 9771.223Sjoerg 9781.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 9791.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 9801.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 9811.257Sapb 9821.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 9831.257Sapb No such file or directory. 9841.257SapbCause: If a directory is created by mistake, then it is sometimes 9851.257Sapb deleted from the CVS repository using administrative commands 9861.257Sapb that bypass the normal cvs access controls. If your cvs working tree 9871.257Sapb contains references to a directory that has been deleted on the 9881.257Sapb server in this way, then "cvs update" reports this error. 9891.257SapbFix: Recursively delete the affected directory from your working tree 9901.257Sapb and try the update again. 991