UPDATING revision 1.331
11.331Sriastrad$NetBSD: UPDATING,v 1.331 2022/09/21 14:32:26 riastradh 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.331Sriastrad20220921: 231.331Sriastrad Since the kernel version was bumped to 9.99.100, the bootloader 241.331Sriastrad must be updated on x86 and efiboot platforms in order to load 251.331Sriastrad modules. 261.331Sriastrad 271.331Sriastrad The kernel can still load modules at runtime with no bootloader 281.331Sriastrad update. This will not affect release branches because it only 291.331Sriastrad applies to patch numbers >100. 301.331Sriastrad 311.330Slukem20220821: 321.330Slukem Support for building extsrc/ has been deprecated. 331.330Slukem EXTSRCSRCDIR and MKEXTSRC have been deprecated. 341.330Slukem 351.329Smrg20220714: 361.329Smrg Updates to xorg-server and associated drivers may cause builds to 371.329Smrg fail. Cleaning both DESTDIR and the xorg build tree may be needed. 381.329Smrg 391.328Smartin20220628: 401.328Smartin Changes in the build of src/games/robots require a clean build 411.328Smartin of that program. 421.328Smartin 431.324Smartin20211116: 441.324Smartin Changes in the xorg build require clean obj dirs for external/mit/xorg 451.325Smartin (or a full clean/non-update build). 461.324Smartin 471.323Snia20211112: 481.323Snia Device tree sources were updated for evbarm. Some device nodes 491.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 501.323Snia 511.322Smartin20211014: 521.323Snia MKPIE default for aarch64 has changed, a clean build is required. 531.322Smartin 541.321Schristos20210917: 551.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 561.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 571.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 581.321Schristos 591.319Smrg20210711: 601.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 611.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 621.319Smrg 631.318Smrg20210417: 641.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 651.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 661.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 671.318Smrg 681.317Srillig20201230: 691.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 701.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 711.317Srillig 721.316Smrg20201016: 731.316Smrg MIPS kernel modules have been disabled until they work. This will 741.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 751.316Smrg 761.315Smrg20200925: 771.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 781.315Smrg in both the tools and external dirs. 791.315Smrg 801.314Smrg20200912: 811.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 821.314Smrg for several more, as will binutils 2.34. Clean as required. 831.314Smrg 841.313Smrg20200907: 851.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 861.313Smrg probably requires cleaning the tools/binutils. 871.313Smrg 881.311Smrg20200811: 891.312Smrg GCC updates may require cleaning the objdir. This may occur 901.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 911.312Smrg GCC 9 upgrade. 921.311Smrg 931.309Schristos20200614: 941.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 951.310Schristos should handle the migration 961.309Schristos 971.308Schristos20200601: 981.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 991.308Schristos created in the build directories and need cleaning. 1001.308Schristos 1011.307Smrg20200311: 1021.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 1031.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 1041.307Smrg 1051.306Schristos20191118: 1061.306Schristos More architectures were switched to gcc8: 1071.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 1081.306Schristos The same comments as in 20191022 apply. 1091.306Schristos 1101.305Smartin20191112: 1111.305Smartin The LLVM update requires a clean rebuild for all architectures using 1121.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 1131.305Smartin 1141.304Smartin20191022: 1151.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 1161.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 1171.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 1181.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 1191.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 1201.304Smartin daily builds and install that before doing the next in-place build. 1211.304Smartin 1221.303Smrg20191001: 1231.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 1241.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 1251.303Smrg directory, and also clean src/external/gpl3/gcc. 1261.303Smrg 1271.302Sriastrad20190903: 1281.306Schristos Files with names that coincide with existing files' names on 1291.302Sriastrad case-insensitive file systems were inadvertently committed, for 1301.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 1311.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 1321.302Sriastrad ran build.sh distribution or ran build.sh release, you must 1331.302Sriastrad manually delete the following files in your DESTDIR (which is 1341.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 1351.302Sriastrad them: 1361.302Sriastrad 1371.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 1381.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 1391.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 1401.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 1411.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 1421.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 1431.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 1441.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 1451.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 1461.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 1471.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 1481.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 1491.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 1501.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 1511.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 1521.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 1531.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 1541.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 1551.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 1561.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 1571.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 1581.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 1591.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 1601.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 1611.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 1621.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 1631.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 1641.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 1651.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 1661.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 1671.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 1681.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 1691.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 1701.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 1711.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 1721.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 1731.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 1741.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 1751.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 1761.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 1771.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 1781.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1791.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1801.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1811.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1821.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1831.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1841.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1851.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1861.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1871.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1881.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1891.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1901.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1911.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1921.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1931.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1941.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1951.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1961.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1971.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1981.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1991.302Sriastrad /libdata/firmware/radeon/verde_me.bin 2001.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 2011.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 2021.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 2031.302Sriastrad 2041.302Sriastrad We will re-import these radeon firmware images another way 2051.302Sriastrad later. 2061.302Sriastrad 2071.301Smartin20190727: 2081.301Smartin The uefi bootloader has gained tftp support and needs a clean 2091.301Smartin build. If you do update builds, manually clean its object 2101.301Smartin directory by something like: 2111.301Smartin cd sys/arch/i386/stand/efiboot && make clean 2121.301Smartin 2131.300Smartin20190723: 2141.300Smartin The jemalloc allocator in libc is now build without extended 2151.300Smartin debugging (for performance reasons). In update builds make sure 2161.326Sandvar to rebuild it completely, by removing all affected object files, 2171.300Smartin including compat builds, something like: 2181.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 2191.300Smartin 2201.299Smrg20190207: 2211.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 2221.299Smrg 2231.298Smartin20180924: 2241.298Smartin A newer OpenSSL version has been imported. If you are doing 2251.298Smartin update builds, make sure to remove all old obj dirs, like: 2261.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 2271.298Smartin 2281.297Sjoerg20180717: 2291.297Sjoerg On aarch64 int64_t and related types have changed from long long 2301.297Sjoerg to long. This requires recompiling all C++ binaries. 2311.297Sjoerg 2321.296Smartin20180713: 2331.296Smartin On amd64 and i386 static binaries are now build position 2341.296Smartin independend. This requires recompilation of all object 2351.296Smartin files used to create the crunched /rescue binary. 2361.296Smartin Clean the rescue directory in your obj directory before 2371.296Smartin doing an update build, otherwise linking will fail. 2381.296Smartin 2391.293Sjakllsch20180414: 2401.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 2411.293Sjakllsch removal of tools/binutils objects directory may be required 2421.293Sjakllsch to fix tools build failure. 2431.293Sjakllsch 2441.292Smrg20180311: 2451.292Smrg bdftopcf was updated and may need cleaning in the 2461.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 2471.292Smrg link errors. 2481.292Smrg 2491.291Smrg20180212: 2501.291Smrg between OpenSSL and GCC updates, many things may fail to build. 2511.291Smrg any failure that looks like GCC or openssl is best handled by 2521.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 2531.291Smrg is recommended if build failures occur. 2541.291Smrg 2551.288Smartin20171225: 2561.288Smartin removal of the vadvise syscall requires manual removal of all 2571.288Smartin associated files from the libc build object directory (including 2581.289Schristos the .depend files) - a command like: 2591.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 2601.289Schristos For architectures that support multiple "compat" binary targets, 2611.289Schristos you'll need to cleanup both the regular libc directory and the 2621.290Smartin compat ones (the above command will do that). 2631.288Smartin 2641.287Skre20171010: 2651.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 2661.287Skre means that its objdir (or *.d and .depend at least) might need 2671.287Skre to be manually removed - or a build done once without -u. 2681.287Skre 2691.286Smrg20170822: 2701.286Smrg a new version of GMP has been imported and probably 2711.286Smrg will break parts of builds related to themselves or GCC, both 2721.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2731.286Smrg and MPC objdirs or build once without -u. 2741.286Smrg 2751.285Smrg20170816: 2761.285Smrg a new version of MPFR and MPC have been imported and probably 2771.285Smrg will break parts of builds related to themselves or GCC, both 2781.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2791.285Smrg and MPC objdirs or build once without -u. 2801.285Smrg 2811.284Smartin20170402: 2821.284Smartin a new version of dhcpcd has been imported, which does not support 2831.284Smartin update builds from the previous version. Remove your 2841.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2851.284Smartin 2861.281Sroy20170211: 2871.281Sroy a new terminfo database has been imported. 2881.281Sroy The structure of it has changed slightly from prior versions and 2891.281Sroy an updated tic tool is required. 2901.281Sroy If you build.sh, don't use -u 2911.281Sroy 2921.280Skre20170207: 2931.278Skre various arch dependent libc/exect.S files were removed 2941.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2951.279Skre if it exists) or do a clean build. 2961.279Skre (This is a bug in the make system, it should be corrected without 2971.279Skre human intervention, but isn't.) 2981.278Skre 2991.277Smartin20170104: 3001.277Smartin xinput build options have changed. 3011.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 3021.277Smartin if you build.sh -u 3031.277Smartin 3041.276Smartin20170103: 3051.276Smartin a new version of flex has been imported. 3061.276Smartin Remove the file from obj (external/bsd/flex) 3071.276Smartin if you build.sh -u 3081.276Smartin 3091.275Sspz20161014: 3101.275Sspz a new version of OpenSSL has been imported. 3111.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 3121.275Sspz if you build.sh -u 3131.275Sspz 3141.274Smartin20161009: 3151.274Smartin a new version of dhcpcd has been imported with slightly changed 3161.274Smartin build infrastructure. When doing a build.sh -u this requires 3171.274Smartin pruning the external/bsd/dhcpcd objdir. 3181.274Smartin 3191.273Smrg20160914: 3201.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 3211.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 3221.273Smrg and a clean objdir. 3231.273Smrg 3241.272Sdholland20160527: 3251.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 3261.272Sdholland been enabled. (see the amd64 entry two down for further info) 3271.272Sdholland 3281.270Schristos20160418: 3291.270Schristos libedit needs manual removal of all autogenerated files since 3301.271Schristos some of them are not autogenerated anymore. Remember that there 3311.271Schristos might be two copies of libedit if your platform builds "compat". 3321.270Schristos 3331.268Sriastrad20160410: 3341.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 3351.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 3361.268Sriastrad executables, means all code, including executables and not just 3371.268Sriastrad shared libraries, is position-independent and hence able to be 3381.268Sriastrad relocated by ASLR, address space layout randomization. 3391.268Sriastrad 3401.268Sriastrad The change was made in Makefile variables for compiler and 3411.268Sriastrad linker flags, for which make(1) does not record dependencies, 3421.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 3431.268Sriastrad 3441.268Sriastrad Partial rebuilds with some modified source files will likely 3451.268Sriastrad fail when linking executables, since the linker refuses to mix 3461.268Sriastrad position-independent code with position-dependent code in 3471.268Sriastrad position-independent executables: 3481.268Sriastrad 3491.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 3501.268Sriastrad 3511.267Smrg20160401: 3521.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 3531.269Sdholland Some people have found that cleandir is not sufficient, so if 3541.269Sdholland in doubt delete the entire object directory tree for gcc. 3551.267Smrg 3561.266Saymeric20160306: 3571.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 3581.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 3591.265Saymeric non-NetBSD hosts if linked with stale object files produced 3601.265Saymeric while they included a non-NetBSD regex.h. 3611.265Saymeric In any case, you should "make cleandir" at least these tools 3621.265Saymeric before updating your toolchain. 3631.265Saymeric 3641.264Smartin20160125: 3651.264Smartin Dtrace has been enabled by default on some architectures. 3661.264Smartin When doing an update build, make sure to clean the etc/mtree 3671.264Smartin object directory before starting the build - otherwise the 3681.264Smartin needed directories in destdir will not be created. 3691.264Smartin An easy way to do this is: 3701.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 3711.264Smartin 3721.263Sdholland20150818: 3731.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 3741.263Sdholland again. 3751.263Sdholland 3761.262Schristos20150413: 3771.262Schristos New acpica requires "make cleandir" and reinstalling yacc 3781.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3791.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3801.262Schristos 3811.261Smartin20150404: 3821.261Smartin Lint changes require a full rebuild of the tool, so make 3831.261Smartin sure to build without -u option to build.sh, or manually 3841.261Smartin do a make cleandir in src/tools/lint1 and 3851.261Smartin src/usr.bin/xlint. 3861.261Smartin 3871.260Sskrll20150310: 3881.260Sskrll Improvements to openssl for arm mean that update builds of 3891.260Sskrll the openssl libraries will fail. A make cleandir in 3901.260Sskrll external/bsd/openssl/lib is needed 3911.260Sskrll 3921.258Smartin20141026: 3931.259Smsaitoh A mishap during the import of pppd may cause your corruption 3941.258Smartin in your cvs directory if you happened to do a cvs update 3951.258Smartin during a short period of time. To fix, just remove the 3961.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3971.258Smartin and let cvs restore it on next update. 3981.258Smartin 3991.256Sapb20140721: 4001.256Sapb The src/external/mit/lua/src directory was accidentally created 4011.256Sapb and then deleted in the CVS repository. If you get errors like 4021.256Sapb 4031.256Sapb cvs [update aborted]: cannot open directory 4041.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 4051.256Sapb 4061.256Sapb then delete your local copy of that directory tree and try again. 4071.256Sapb 4081.255Sjoerg20140530: 4091.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 4101.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 4111.255Sjoerg 4121.251Smartin20140131: 4131.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 4141.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 4151.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 4161.251Smartin 4171.250Schristos20131227: 4181.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 4191.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 4201.250Schristos mode7 in your config file. Make sure you put the necessary restrict 4211.250Schristos statements to avoid being exposed. 4221.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 4231.250Schristos to make clean in libc 4241.250Schristos 4251.249Smrg20131129: 4261.249Smrg The GMP sources were updated, and builds will likely fail without 4271.249Smrg cleaning their build trees for both tools and in-tree, like below. 4281.249Smrg 4291.248Smrg20131128: 4301.248Smrg The MPC and MPFR sources were updated, and builds may require their 4311.248Smrg tools and in-tree directories cleaned for successful updates. 4321.248Smrg 4331.246Smartin20130605: 4341.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 4351.247Sspz to IPSEC (and the older IPSEC version removed). 4361.247Sspz 4371.247Sspz20130605: 4381.320Sandvar Previous freetype installations erroneously installed private 4391.246Smartin header files. If you are building against a non-empty $DESTDIR, 4401.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 4411.246Smartin 4421.245Smrg20130531: 4431.245Smrg The xdm update may cause build failure due to xdm.man being 4441.245Smrg in the obj tree. Make sure to ensure any like this: 4451.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 4461.245Smrg is fixed by deleting the xdm.man in the obj tree. 4471.245Smrg 4481.244Smrg20130530: 4491.244Smrg Updates of many xsrc packages will leave old .pc files around. 4501.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 4511.244Smrg 4521.242Schristos20130301: 4531.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 4541.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 4551.242Schristos 4561.238Sdholland20120726: 4571.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 4581.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 4591.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 4601.241Swiz some cases may succeed and install broken OpenSSL libraries that 4611.240Sdholland cause third-party software to link incorrectly and/or crash. 4621.238Sdholland 4631.237Swiz20120507: 4641.241Swiz The database schema for makemandb was changed. You will 4651.237Swiz need to update the database using 'makemandb -f' or wait 4661.237Swiz for the next weekly run to fix it. 4671.237Swiz 4681.236Sbsh20120319: 4691.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 4701.236Sbsh size of db_symtab automatically. You need to update dbsym in 4711.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 4721.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 4731.236Sbsh mk.conf. 4741.236Sbsh 4751.235Sjoerg20120216: 4761.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 4771.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 4781.239Sdholland and 20120216, daily and weekly could have created an unreadable 4791.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4801.235Sjoerg the next run of weekly will fix it. 4811.233Sjoerg 4821.232Schristos20111227: 4831.232Schristos If you built between 20111225 and 20111227 you need to remove 4841.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4851.232Schristos bump has been reverted. 4861.232Schristos 4871.231Stls20111125: 4881.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4891.231Stls means it should no longer be explicitly listed in kernel 4901.231Stls configuration files. The line "pseudo-device rnd" should be 4911.231Stls removed from any custom kernel config files users may have. 4921.231Stls 4931.230Stls20111119: 4941.230Stls A problem with the datastructures used by the rndctl(8) 4951.230Stls utility (pointers in datastructures in an array, making 32->64 4961.230Stls bit compatibility very painful) has been fixed in a 4971.230Stls non-backwards-compatible way. If you replace your kernel, 4981.230Stls replace your rndctl executable too. 4991.241Swiz 5001.229Sjym20111001: 5011.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 5021.229Sjym changed and their new version is not backward compatible with the old 5031.241Swiz one. So ensure that all consumers of these functions (currently: 5041.229Sjym quota2 code and its tests) are updated together with the new lib. 5051.229Sjym 5061.228Smrg20110817: 5071.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 5081.228Smrg DESTDIR for them should be deleted before updating. 5091.228Smrg 5101.227Sriastrad20110806: 5111.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 5121.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 5131.227Sriastrad 5141.226Smrg20110805: 5151.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 5161.226Smrg the tree to be cleaned. Best to delete both objdir and 5171.226Smrg DESTDIR before running this update. So far, only the 5181.226Smrg sparc64, mips and powerpc platforms have changed. 5191.226Smrg 5201.225Smatt20110803: 5211.241Swiz The layout of external/public-domain/xz has changed. To do an 5221.225Smatt update build you will have to remove the contents of the OBJDIR 5231.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 5241.225Smatt is now a directory. 5251.225Smatt 5261.223Sjoerg20110410: 5271.241Swiz The configuration of src/tools/gcc has changed. To do an 5281.224Sdholland update build you have to clean both tools/binutils and 5291.224Sdholland tools/gcc by hand. 5301.223Sjoerg 5311.222Splunky20110328: 5321.222Splunky Building the Xorg binary was moved into a subdirectory to fix 5331.241Swiz ordering issues with "make all". It may be necessary to remove 5341.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 5351.222Splunky if your update build fails, as the "Xorg" entry there is now a 5361.222Splunky directory. 5371.222Splunky 5381.220Sjoerg20110121: 5391.221Slukem Assembler files no longer use -traditional-cpp. This can break 5401.220Sjoerg the build of individual parts of the tree. This is handled 5411.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 5421.220Sjoerg and re-run config(1) for any kernel configurations as needed. 5431.218Sjoerg 5441.217Sjruoho20101217: 5451.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 5461.241Swiz by default. It may be necessary to manually update passwd(5) and 5471.217Sjruoho group(5) in order to make the program work with existing setups. 5481.217Sjruoho 5491.216Schristos20101125: 5501.327Sandvar The latest changes to setenv(3) disallow setting environment 5511.241Swiz variables with names that contain '='. Revision 1.18 of env.c 5521.241Swiz assumed that this was allowed. Installing a new libc with an 5531.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 5541.216Schristos break which affects the autoconf tests for dependency finding, 5551.216Schristos so building gcc will end up printing: 5561.216Schristos checking dependency style of gcc... none 5571.216Schristos configure: error: no usable dependency style found 5581.216Schristos Fix it by rebuilding and re-installing env. 5591.138Slukem 5601.215Smrg20101119: 5611.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 5621.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 5631.215Smrg have any build problems with xsrc, or problems with mismatched 5641.215Smrg versions between xorg-server and drivers. 5651.215Smrg 5661.213Sjmmv20100604: 5671.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 5681.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 5691.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 5701.213Sjmmv trees by hand. 5711.213Sjmmv 5721.211Stnozaki20100522: 5731.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 5741.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 5751.212Smrg build problems with xsrc. 5761.212Smrg 5771.212Smrg20100522: 5781.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 5791.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5801.211Stnozaki 5811.210Schristos20100520: 5821.241Swiz The location of the xkb compiled descriptions has changed. Please 5831.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5841.210Schristos 5851.209Snjoly20100222: 5861.209Snjoly The shared objects file extension has been changed from .so to 5871.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5881.209Snjoly libXX.so. All now stale regular .so files can be removed from 5891.209Snjoly your object directories. 5901.209Snjoly 5911.208Sroy20100204: 5921.208Sroy The termcap database has been removed from the sources, 5931.208Sroy but has not been marked obsolete so it is not removed 5941.208Sroy from the system when upgrading. 5951.208Sroy As such, you will need to remove them from your object 5961.208Sroy and destination directories. 5971.208Sroy 5981.203Sdyoung20091101: 5991.205Sdholland After updating, it may be necessary to make the 'cleandir' 6001.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 6011.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 6021.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 6031.203Sdyoung 6041.202Smrg20091001: 6051.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 6061.206Sdholland before building a kernel, or the build fails on cpufunc.S. 6071.206Sdholland 6081.206Sdholland20091001: 6091.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 6101.202Smrg symlink, failing the build. Delete the link, and the subdir 6111.202Smrg it is in, and retry your build. 6121.202Smrg 6131.201Sdsl20090718: 6141.201Sdsl libc build changed so that strchr() provides the extra entry 6151.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 6161.201Sdsl may fail because the archive contains the unwanted index.o. 6171.201Sdsl (Similarly for strrchr() and rindex().) 6181.201Sdsl 6191.198Smrg20090709: 6201.198Smrg Native Xorg was upgraded again. Builds will probably fail again 6211.198Smrg without a clean objdir, at least for src/external/mit/xorg. 6221.198Smrg 6231.197Smrg20090616: 6241.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 6251.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 6261.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 6271.197Smrg subdirectory has been changed into a file, and this needs to 6281.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 6291.197Smrg 6301.195Sperry20090501: 6311.195Sperry Several new functions were added to string.h/libc, and this 6321.195Sperry can cause autoconf problems during the tool build for people 6331.241Swiz who fail to clean out their tools objects properly. If you 6341.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 6351.195Sperry failure during the tool build, clean out all your tools 6361.195Sperry objects and start again. 6371.195Sperry 6381.194Smrg20090325: 6391.194Smrg The i386 port was switched to i486 default toolchain. This requires 6401.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 6411.194Smrg 6421.192Sskrll20090126: 6431.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 6441.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 6451.207Smbalmer to avoid using the old assembly stub. 6461.192Sskrll 6471.191Sjoerg20090202: 6481.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 6491.320Sandvar detection. It is recommended to rebuild the cache with 6501.191Sjoerg ``pkg_admin rebuild''. 6511.191Sjoerg 6521.184Schristos20090110: 6531.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 6541.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 6551.188Schristos This is needed even in the MODULAR kernel because there is 6561.188Schristos conditionally compiled code in rtsock.c. 6571.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 6581.184Schristos before installing. 6591.184Schristos 3. If you don't use build.sh and you build directly to root, and 6601.241Swiz your build breaks in the middle, don't despair. Make sure headers 6611.184Schristos are installed properly, and start building libraries first libc 6621.184Schristos and libutil, install them and then continue building all the 6631.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 6641.184Schristos the new libraries are installed, you can restart the build. 6651.184Schristos 4. If you compile packages and you notice link time warnings, 6661.189Shubertf rebuild the required packages to update their shared libraries. 6671.189Shubertf Any package you rebuild will require rebuilding all the packages 6681.189Shubertf that depend on it. 6691.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 6701.186Schristos will be upgraded and it will not be backwards compatible. 6711.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 6721.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 6731.241Swiz for utmp. You are better off removing the old files after 6741.190Sapb upgrading. The automated clearing of /var/run during 6751.190Sapb boot, and the automated rotating of files in /var/log by 6761.190Sapb newsyslog(8), may mean that you do not have to remove the 6771.190Sapb files manually. 6781.190Sapb 7. The optional accounting file (/var/account/acct, see 6791.190Sapb accton(8)) has not been versioned, and will need to be 6801.190Sapb removed. The automatic rotation of the accounting file by 6811.190Sapb /etc/daily limits the bad consequences of failure to remove 6821.190Sapb the file. 6831.196Sdholland 8. Application software that writes time_t to binary files on 6841.241Swiz disk will break or need attention. Most notably: if you are 6851.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6861.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6871.185Sjmcneill 6881.183Spgoyette20081219: 6891.183Spgoyette config(1) has been updated, and one of the files it creates - 6901.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6911.183Spgoyette (done automatically by build.sh) and then you need to rerun 6921.183Spgoyette config on all kernel configuration files before rebuilding those 6931.183Spgoyette kernels. 6941.183Spgoyette 6951.181Scube20081205: 6961.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6971.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6981.181Scube set and will appear as extra files for MKX11=no update builds. 6991.178Slukem 7001.179Stsutsui20081122: 7011.182Stsutsui On i386, various kernel options(4) in GENERIC including 7021.180Swiz file systems have been disabled and moved into kernel modules. 7031.180Swiz Before trying a new GENERIC kernel, you have to prepare the 7041.179Stsutsui following files as well as a new GENERIC kernel: 7051.179Stsutsui 7061.179Stsutsui - build and install kernel modules from src/sys/modules 7071.179Stsutsui 7081.179Stsutsui - install the latest bootloader, which will load a module 7091.180Swiz for the file system from which the kernel is loaded automatically 7101.179Stsutsui 7111.180Swiz If you have to load your kernel from a file system which is not of 7121.180Swiz the same type as the root file system, you have to load the necessary 7131.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 7141.179Stsutsui 7151.178Slukem20080827: 7161.178Slukem If you built and installed a libc from sources between 7171.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 7181.178Slukem which results in false errors reported by lint(1). 7191.178Slukem Since this breaks the libc build itself, manual help is 7201.180Swiz needed -- lint must be disabled temporarily, e.g.: 7211.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 7221.178Slukem 7231.177Schristos20080813: 7241.177Schristos MKDEBUG build was broken because the .depend files did not know 7251.241Swiz about .go files. You need to remove all .depend files and rebuild. 7261.177Schristos 7271.200Sdholland20080802: 7281.200Sdholland A regression in binary compatibility for pthread_mutex_t has 7291.241Swiz been fixed. Unfortunately, the price is breaking compatibility 7301.200Sdholland for -current. 7311.200Sdholland 7321.200Sdholland Threaded programs (using libpthread) and C++ programs (using 7331.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 7341.200Sdholland be recompiled. 7351.200Sdholland 7361.200Sdholland One way to find affected pkgsrc packages: 7371.200Sdholland 7381.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 7391.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 7401.200Sdholland 7411.175Ssimonb20080731: 7421.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 7431.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 7441.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 7451.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 7461.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 7471.176Ssimonb also requires the super block to be in the UFS2 format. You 7481.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 7491.175Ssimonb 7501.174Slukem20080721: 7511.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 7521.174Slukem isn't defined. 7531.174Slukem 7541.173Sfreza20080531: 7551.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 7561.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 7571.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 7581.241Swiz won't work correctly. The following sequence of commands: 7591.173Sfreza 7601.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 7611.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 7621.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 7631.173Sfreza 7641.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 7651.173Sfreza 7661.172Slukem20080503: 7671.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 7681.172Slukem 7691.171She20080521: 7701.171She For a while, unprivileged UPDATE builds would fail to 7711.171She succeed at the checkflist stage, complaining that 7721.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 7731.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 7741.171She If you already hit this problem, update the .mk file, 7751.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 7761.171She 7771.174Slukem20080303: 7781.174Slukem Linker warnings are now fatal if $WARNS>0. 7791.174Slukem 7801.170Schristos20080126: 7811.170Schristos The posix_fadvise system call has been changed from an assembly 7821.241Swiz stub, to a c file that calls an assembly stub. You need to 7831.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7841.170Schristos avoid using the old assembly stub. 7851.170Schristos 7861.168Sjoerg20071209: 7871.241Swiz The acpiec(4) driver has been split into two attachments. If you 7881.168Sjoerg get ACPI errors before the attachment, please update your kernel 7891.169Swiz configuration file appropriately or see GENERIC for more details. 7901.168Sjoerg 7911.166Sxtraeme20071115: 7921.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7931.166Sxtraeme argument specified in the kernel configuration file is not valid 7941.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7951.241Swiz rather than the EC address port. Please update your kernel 7961.167Swiz configuration file appropriately or see GENERIC for more details. 7971.166Sxtraeme 7981.165Sjmmv20071028: 7991.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 8001.165Sjmmv You need to update any custom kernel configuration file you have 8011.165Sjmmv to remove any references to pccons (which includes removing the 8021.165Sjmmv now useless XSERVER option) and replace them with the correct 8031.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 8041.165Sjmmv for more details. 8051.165Sjmmv 8061.164Sgdt20070913: 8071.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 8081.164Sgdt enumerate interfaces was fixed. The bug began to cause 8091.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 8101.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 8111.164Sgdt could not enumerate interfaces. (These are noted because 8121.164Sgdt normal kernel/userspace version matching hygiene is not 8131.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 8141.164Sgdt and userland are from after 20070913. 8151.164Sgdt 8161.163Sjoerg20070703: 8171.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 8181.199Sdholland calls the target-specific strip program, and the logic to pass 8191.199Sdholland down STRIP from make has been removed. This requires a 8201.199Sdholland re-installation of tools. 8211.163Sjoerg 8221.161Sdsl20070422: 8231.161Sdsl The way OS emulations lookup filenames inside the emulation root 8241.161Sdsl has been changed. Rather than modify the pathname (and copy back 8251.161Sdsl to userspace) namei() and lookup() directly check the emulation 8261.241Swiz root. One side effect is that absolute symlinks inside the emulated 8271.167Swiz root file system will be relative to that file system - unless they 8281.161Sdsl start /../ this is useful when the emulated root is a real install 8291.161Sdsl that has such links. 8301.161Sdsl This might affect symlinks that have been added to reference outside 8311.161Sdsl the emulated root. 8321.161Sdsl 8331.160Sjmcneill20070412: 8341.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 8351.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 8361.160Sjmcneill example. 8371.160Sjmcneill 8381.159Sgdt20070319: 8391.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 8401.159Sgdt on many platforms due to incorrect flags settings. If you 8411.159Sgdt updated and built after about 20070315, do "nbmake-$arch 8421.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 8431.159Sgdt rebuild of object files that might have been built 8441.159Sgdt incorrectly, and ensure that you have at least 8451.159Sgdt src/lib/libc/Makefile 1.130. 8461.159Sgdt 8471.241Swiz20070210: 8481.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 8491.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 8501.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 8511.158Sdbj will allow dependencies on those files to get get rebuilt 8521.158Sdbj 8531.157Sapb20070209: 8541.157Sapb The threading model was changed when the newlock2 branch 8551.157Sapb was merged to NetBSD-current. If you boot with a new 8561.157Sapb kernel (version 4.99.10), then you also need a new pthread 8571.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 8581.157Sapb an old kernel, then you need the old pthread library 8591.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 8601.157Sapb the pthread library in sync, old threaded applications should 8611.157Sapb continue to work with an old or new kernel. Note that named(8) 8621.157Sapb is the only threaded application in the base system. 8631.157Sapb 8641.154She20061214: 8651.154She Following the move of string_to_flags() and flags_to_string() 8661.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 8671.154She will need to do a "make cleandir" in 8681.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 8691.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 8701.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 8711.156She as the installation images in distrib/ 8721.154She in order to excise stale references to the old stat_flags.h header 8731.154She file in the ls sources -- stat_flags.h has been removed. 8741.154She 8751.152Schristos20061108: 8761.152Schristos The configure script used in the src/tools/gcc compiler has been 8771.152Schristos changed to indicate that our libc has ssp support built-in and 8781.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8791.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8801.152Schristos 8811.151Srpaulo20061009: 8821.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8831.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8841.151Srpaulo 8851.150Sbjh2120060814: 8861.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8871.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8881.150Sbjh21 kernel configuration for an example. X servers from the last 8891.150Sbjh21 few years should cope. 8901.150Sbjh21 8911.149Schristos20060703: 8921.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8931.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8941.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8951.149Schristos 8961.148Sdogcow20060627: 8971.148Sdogcow socket(2) has changed, and its system call has been versioned. 8981.148Sdogcow For userlands with the old version of socket(2), make sure that 8991.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 9001.148Sdogcow errors will result. 9011.148Sdogcow 9021.1SabsHints for a more successful build: 9031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9041.123Sjmc Use build.sh, but do not use its "expert mode": 9051.132Sjmmv This will automatically build the tools in the 9061.123Sjmc correct order, and it will keep the tools and the 9071.123Sjmc new build products from interfering with the running 9081.123Sjmc system. This will allow you to ignore most of the 9091.123Sjmc other advice in this file. 9101.2Smrg Build a new kernel first: 9111.2Smrg This makes sure that any new system calls or features 9121.2Smrg expected by the new userland will be present. This 9131.2Smrg helps to avoid critical errors when upgrading. 9141.1Sabs Use object directories: 9151.1Sabs This helps to keep stale object 9161.1Sabs files from polluting the build if a Makefile "forgets" 9171.1Sabs about one. It also makes it easier to clean up after 9181.1Sabs a build. It's also necessary if you want to use the 9191.1Sabs same source tree for multiple machines. 9201.123Sjmc To use object directories with build.sh: 9211.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 9221.123Sjmc To use object directories without using build.sh: 9231.1Sabs a) cd /usr/src ; make cleandir 9241.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 9251.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 9261.1Sabs d) cd /usr/src ; make build 9271.2Smrg Note that running "make obj" in a directory will create 9281.2Smrg in obj.$MACHINE directory. 9291.1Sabs Build to a DESTDIR: 9301.123Sjmc This helps to keep old installed files (especially libraries) 9311.123Sjmc from interfering with the new build. 9321.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 9331.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 9341.123Sjmc environment variable before running make build. It should be 9351.123Sjmc set to the pathname of an initially empty directory. 9361.123Sjmc Problems: if you do not use build.sh, you might need to 9371.123Sjmc update critical utilities without using DESTDIR since 9381.123Sjmc nothing is executed from what is installed in DESTDIR. 9391.123Sjmc (See critical utils, below.) 9401.1Sabs Build often: 9411.1Sabs This keeps critical utilities current enough to not choke 9421.1Sabs on any other part of the source tree that depends on up to 9431.123Sjmc date functionality. If you use build.sh, you should not have 9441.123Sjmc this problem. 9451.241Swiz 9461.1SabsWhat to do if things don't work: 9471.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9481.230StlsWhen things don't work there are usually a few things that commonly 9491.1Sabsshould be done. 9501.1Sabs 1) make includes 9511.1Sabs This should be done automatically by make build. 9521.1Sabs 2) cd share/mk && make install 9531.1Sabs Again, automatically done by make build. 9541.1Sabs 9551.1SabsFailsafe rebuild of a small part of the tree: 9561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9571.1SabsTo make sure you rebuild something correctly you want to do 9581.1Sabssomething like the following: 9591.1Sabs 1) Make sure the includes and .mk files are up to date. 9601.1Sabs 2) Make sure any program used to build the particular 9611.1Sabs utility is up to date. (yacc, lex, etc...) 9621.1Sabs 3) cd ...path/to/util... 9631.1Sabs make cleandir 9641.1Sabs rm ...all obj directories... 9651.1Sabs make cleandir # yes, again 9661.1Sabs make obj 9671.1Sabs make depend && make 9681.1Sabs 9691.1SabsFailsafe rebuild of the entire tree: 9701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9711.1SabsIf you really want to make sure the source tree is clean and 9721.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 9731.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 9741.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 9751.1Sabs 9761.1Sabs---cut here--- 9771.1Sabs#!/bin/sh 9781.1Sabs. /etc/mk.conf 9791.1Sabs 9801.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9811.58Slukem NETBSDSRCDIR=/usr/src 9821.1Sabsfi 9831.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9841.1Sabs echo Unable to find sources 9851.1Sabs exit 1 9861.1Sabsfi 9871.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9881.1Sabs 9891.1Sabsif [ -z $BSDOBJDIR ] ; then 9901.1Sabs BSDOBJDIR=/usr/obj 9911.1Sabsfi 9921.1Sabsif [ -d $BSDOBJDIR ] ; then 9931.1Sabs rm -rf $BSDOBJDIR 9941.1Sabsfi 9951.1Sabs 9961.58Slukemcd $NETBSDSRCDIR && make cleandir 9971.1Sabs 9981.1Sabs---cut here--- 9991.1Sabs 10001.1SabsCritical utilities: 10011.1Sabs^^^^^^^^^^^^^^^^^^^ 10021.3Sitojun usr.bin/compile_et 10031.1Sabs usr.bin/make 10041.1Sabs usr.bin/yacc 10051.1Sabs usr.bin/lex 10061.11Slukem usr.bin/xlint 10071.142Sdrochner usr.bin/config 10081.1Sabs 10091.34SsimonbOther problems and possible solutions: 10101.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10111.1SabsSymptom:Complaints involving a Makefile. 10121.17SerhFix: Rebuild usr.bin/make: 10131.17Serh cd usr.bin/make && make && make install 10141.111Ssimonb Or, a failsafe method if that doesn't work: 10151.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 10161.17Serh 10171.1SabsFix: Make sure .mk files are up to date. 10181.1Sabs cd share/mk && make install 10191.2Smrg 10201.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 10211.142SdrochnerFix: Rebuild usr.bin/config 10221.1Sabs 10231.1SabsSymptom: 10241.1SabsFix: Rebuild usr.bin/yacc 10251.1Sabs 10261.1SabsSymptom: 10271.1SabsFix: Rebuild usr.bin/lex 10281.1Sabs 10291.1SabsSymptom: 10301.1SabsFix: rm /usr/lib/libbfd.a 10311.4Sitojun 10321.4SitojunSymptom:Obsolete intermediate files are used during compilation 10331.4SitojunFix: Try the following sequence of commands in the directory in question. 10341.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 10351.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 10361.4Sitojun may remain. The command tries to clean everything up) 10371.5Swiz 10381.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 10391.207Smbalmer pointer type 10401.5SwizFix: Rebuild and install usr.bin/menuc 10411.12Sitojun 10421.12SitojunSymptom:mklocale not found during build in share/locale/ctype 10431.12SitojunFix: Build and install usr.bin/mklocale 10441.13Sdogcow 10451.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 10461.13SdogcowFix: Rebuild and install lib/libc 10471.13Sdogcow 10481.142SdrochnerSymptom:usr.bin/config fails to build. 10491.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 10501.13Sdogcow 10511.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 10521.19ScgdFix: Rebuild and install lib/libc 10531.24Sabs 10541.24SabsSymptom:lint does not understand the '-X' option 10551.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 10561.223Sjoerg 10571.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 10581.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 10591.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 10601.257Sapb 10611.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 10621.257Sapb No such file or directory. 10631.257SapbCause: If a directory is created by mistake, then it is sometimes 10641.257Sapb deleted from the CVS repository using administrative commands 10651.257Sapb that bypass the normal cvs access controls. If your cvs working tree 10661.257Sapb contains references to a directory that has been deleted on the 10671.257Sapb server in this way, then "cvs update" reports this error. 10681.257SapbFix: Recursively delete the affected directory from your working tree 10691.257Sapb and try the update again. 1070