UPDATING revision 1.323
11.323Snia$NetBSD: UPDATING,v 1.323 2021/11/14 11:16:28 nia 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.323Snia20211112: 231.323Snia Device tree sources were updated for evbarm. Some device nodes 241.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 251.323Snia 261.322Smartin20211014: 271.323Snia MKPIE default for aarch64 has changed, a clean build is required. 281.322Smartin 291.321Schristos20210917: 301.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 311.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 321.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 331.321Schristos 341.319Smrg20210711: 351.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 361.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 371.319Smrg 381.318Smrg20210417: 391.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 401.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 411.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 421.318Smrg 431.317Srillig20201230: 441.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 451.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 461.317Srillig 471.316Smrg20201016: 481.316Smrg MIPS kernel modules have been disabled until they work. This will 491.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 501.316Smrg 511.315Smrg20200925: 521.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 531.315Smrg in both the tools and external dirs. 541.315Smrg 551.314Smrg20200912: 561.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 571.314Smrg for several more, as will binutils 2.34. Clean as required. 581.314Smrg 591.313Smrg20200907: 601.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 611.313Smrg probably requires cleaning the tools/binutils. 621.313Smrg 631.311Smrg20200811: 641.312Smrg GCC updates may require cleaning the objdir. This may occur 651.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 661.312Smrg GCC 9 upgrade. 671.311Smrg 681.309Schristos20200614: 691.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 701.310Schristos should handle the migration 711.309Schristos 721.308Schristos20200601: 731.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 741.308Schristos created in the build directories and need cleaning. 751.308Schristos 761.307Smrg20200311: 771.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 781.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 791.307Smrg 801.306Schristos20191118: 811.306Schristos More architectures were switched to gcc8: 821.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 831.306Schristos The same comments as in 20191022 apply. 841.306Schristos 851.305Smartin20191112: 861.305Smartin The LLVM update requires a clean rebuild for all architectures using 871.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 881.305Smartin 891.304Smartin20191022: 901.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 911.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 921.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 931.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 941.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 951.304Smartin daily builds and install that before doing the next in-place build. 961.304Smartin 971.303Smrg20191001: 981.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 991.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 1001.303Smrg directory, and also clean src/external/gpl3/gcc. 1011.303Smrg 1021.302Sriastrad20190903: 1031.306Schristos Files with names that coincide with existing files' names on 1041.302Sriastrad case-insensitive file systems were inadvertently committed, for 1051.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 1061.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 1071.302Sriastrad ran build.sh distribution or ran build.sh release, you must 1081.302Sriastrad manually delete the following files in your DESTDIR (which is 1091.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 1101.302Sriastrad them: 1111.302Sriastrad 1121.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 1131.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 1141.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 1151.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 1161.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 1171.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 1181.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 1191.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 1201.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 1211.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 1221.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 1231.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 1241.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 1251.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 1261.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 1271.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 1281.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 1291.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 1301.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 1311.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 1321.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 1331.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 1341.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 1351.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 1361.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 1371.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 1381.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 1391.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 1401.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 1411.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 1421.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 1431.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 1441.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 1451.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 1461.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 1471.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 1481.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 1491.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 1501.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 1511.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 1521.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 1531.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 1541.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 1551.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 1561.302Sriastrad /libdata/firmware/radeon/oland_me.bin 1571.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 1581.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 1591.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 1601.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 1611.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 1621.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 1631.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 1641.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 1651.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 1661.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 1671.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 1681.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 1691.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 1701.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 1711.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 1721.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 1731.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 1741.302Sriastrad /libdata/firmware/radeon/verde_me.bin 1751.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 1761.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 1771.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 1781.302Sriastrad 1791.302Sriastrad We will re-import these radeon firmware images another way 1801.302Sriastrad later. 1811.302Sriastrad 1821.301Smartin20190727: 1831.301Smartin The uefi bootloader has gained tftp support and needs a clean 1841.301Smartin build. If you do update builds, manually clean its object 1851.301Smartin directory by something like: 1861.301Smartin cd sys/arch/i386/stand/efiboot && make clean 1871.301Smartin 1881.300Smartin20190723: 1891.300Smartin The jemalloc allocator in libc is now build without extended 1901.300Smartin debugging (for performance reasons). In update builds make sure 1911.300Smartin to rebuild it completly, by removing all affected object files, 1921.300Smartin including compat builds, something like: 1931.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 1941.300Smartin 1951.299Smrg20190207: 1961.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 1971.299Smrg 1981.298Smartin20180924: 1991.298Smartin A newer OpenSSL version has been imported. If you are doing 2001.298Smartin update builds, make sure to remove all old obj dirs, like: 2011.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 2021.298Smartin 2031.297Sjoerg20180717: 2041.297Sjoerg On aarch64 int64_t and related types have changed from long long 2051.297Sjoerg to long. This requires recompiling all C++ binaries. 2061.297Sjoerg 2071.296Smartin20180713: 2081.296Smartin On amd64 and i386 static binaries are now build position 2091.296Smartin independend. This requires recompilation of all object 2101.296Smartin files used to create the crunched /rescue binary. 2111.296Smartin Clean the rescue directory in your obj directory before 2121.296Smartin doing an update build, otherwise linking will fail. 2131.296Smartin 2141.293Sjakllsch20180414: 2151.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 2161.293Sjakllsch removal of tools/binutils objects directory may be required 2171.293Sjakllsch to fix tools build failure. 2181.293Sjakllsch 2191.292Smrg20180311: 2201.292Smrg bdftopcf was updated and may need cleaning in the 2211.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 2221.292Smrg link errors. 2231.292Smrg 2241.291Smrg20180212: 2251.291Smrg between OpenSSL and GCC updates, many things may fail to build. 2261.291Smrg any failure that looks like GCC or openssl is best handled by 2271.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 2281.291Smrg is recommended if build failures occur. 2291.291Smrg 2301.288Smartin20171225: 2311.288Smartin removal of the vadvise syscall requires manual removal of all 2321.288Smartin associated files from the libc build object directory (including 2331.289Schristos the .depend files) - a command like: 2341.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 2351.289Schristos For architectures that support multiple "compat" binary targets, 2361.289Schristos you'll need to cleanup both the regular libc directory and the 2371.290Smartin compat ones (the above command will do that). 2381.288Smartin 2391.287Skre20171010: 2401.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 2411.287Skre means that its objdir (or *.d and .depend at least) might need 2421.287Skre to be manually removed - or a build done once without -u. 2431.287Skre 2441.286Smrg20170822: 2451.286Smrg a new version of GMP has been imported and probably 2461.286Smrg will break parts of builds related to themselves or GCC, both 2471.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2481.286Smrg and MPC objdirs or build once without -u. 2491.286Smrg 2501.285Smrg20170816: 2511.285Smrg a new version of MPFR and MPC have been imported and probably 2521.285Smrg will break parts of builds related to themselves or GCC, both 2531.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 2541.285Smrg and MPC objdirs or build once without -u. 2551.285Smrg 2561.284Smartin20170402: 2571.284Smartin a new version of dhcpcd has been imported, which does not support 2581.284Smartin update builds from the previous version. Remove your 2591.284Smartin external/bsd/dhcpcd object dir or build once without -u. 2601.284Smartin 2611.281Sroy20170211: 2621.281Sroy a new terminfo database has been imported. 2631.281Sroy The structure of it has changed slightly from prior versions and 2641.281Sroy an updated tic tool is required. 2651.281Sroy If you build.sh, don't use -u 2661.281Sroy 2671.280Skre20170207: 2681.278Skre various arch dependent libc/exect.S files were removed 2691.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 2701.279Skre if it exists) or do a clean build. 2711.279Skre (This is a bug in the make system, it should be corrected without 2721.279Skre human intervention, but isn't.) 2731.278Skre 2741.277Smartin20170104: 2751.277Smartin xinput build options have changed. 2761.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 2771.277Smartin if you build.sh -u 2781.277Smartin 2791.276Smartin20170103: 2801.276Smartin a new version of flex has been imported. 2811.276Smartin Remove the file from obj (external/bsd/flex) 2821.276Smartin if you build.sh -u 2831.276Smartin 2841.275Sspz20161014: 2851.275Sspz a new version of OpenSSL has been imported. 2861.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 2871.275Sspz if you build.sh -u 2881.275Sspz 2891.274Smartin20161009: 2901.274Smartin a new version of dhcpcd has been imported with slightly changed 2911.274Smartin build infrastructure. When doing a build.sh -u this requires 2921.274Smartin pruning the external/bsd/dhcpcd objdir. 2931.274Smartin 2941.273Smrg20160914: 2951.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 2961.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 2971.273Smrg and a clean objdir. 2981.273Smrg 2991.272Sdholland20160527: 3001.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 3011.272Sdholland been enabled. (see the amd64 entry two down for further info) 3021.272Sdholland 3031.270Schristos20160418: 3041.270Schristos libedit needs manual removal of all autogenerated files since 3051.271Schristos some of them are not autogenerated anymore. Remember that there 3061.271Schristos might be two copies of libedit if your platform builds "compat". 3071.270Schristos 3081.268Sriastrad20160410: 3091.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 3101.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 3111.268Sriastrad executables, means all code, including executables and not just 3121.268Sriastrad shared libraries, is position-independent and hence able to be 3131.268Sriastrad relocated by ASLR, address space layout randomization. 3141.268Sriastrad 3151.268Sriastrad The change was made in Makefile variables for compiler and 3161.268Sriastrad linker flags, for which make(1) does not record dependencies, 3171.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 3181.268Sriastrad 3191.268Sriastrad Partial rebuilds with some modified source files will likely 3201.268Sriastrad fail when linking executables, since the linker refuses to mix 3211.268Sriastrad position-independent code with position-dependent code in 3221.268Sriastrad position-independent executables: 3231.268Sriastrad 3241.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 3251.268Sriastrad 3261.267Smrg20160401: 3271.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 3281.269Sdholland Some people have found that cleandir is not sufficient, so if 3291.269Sdholland in doubt delete the entire object directory tree for gcc. 3301.267Smrg 3311.266Saymeric20160306: 3321.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 3331.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 3341.265Saymeric non-NetBSD hosts if linked with stale object files produced 3351.265Saymeric while they included a non-NetBSD regex.h. 3361.265Saymeric In any case, you should "make cleandir" at least these tools 3371.265Saymeric before updating your toolchain. 3381.265Saymeric 3391.264Smartin20160125: 3401.264Smartin Dtrace has been enabled by default on some architectures. 3411.264Smartin When doing an update build, make sure to clean the etc/mtree 3421.264Smartin object directory before starting the build - otherwise the 3431.264Smartin needed directories in destdir will not be created. 3441.264Smartin An easy way to do this is: 3451.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 3461.264Smartin 3471.263Sdholland20150818: 3481.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 3491.263Sdholland again. 3501.263Sdholland 3511.262Schristos20150413: 3521.262Schristos New acpica requires "make cleandir" and reinstalling yacc 3531.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 3541.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 3551.262Schristos 3561.261Smartin20150404: 3571.261Smartin Lint changes require a full rebuild of the tool, so make 3581.261Smartin sure to build without -u option to build.sh, or manually 3591.261Smartin do a make cleandir in src/tools/lint1 and 3601.261Smartin src/usr.bin/xlint. 3611.261Smartin 3621.260Sskrll20150310: 3631.260Sskrll Improvements to openssl for arm mean that update builds of 3641.260Sskrll the openssl libraries will fail. A make cleandir in 3651.260Sskrll external/bsd/openssl/lib is needed 3661.260Sskrll 3671.258Smartin20141026: 3681.259Smsaitoh A mishap during the import of pppd may cause your corruption 3691.258Smartin in your cvs directory if you happened to do a cvs update 3701.258Smartin during a short period of time. To fix, just remove the 3711.258Smartin directory src/external/bsd/ppp/dist/pppd completely 3721.258Smartin and let cvs restore it on next update. 3731.258Smartin 3741.256Sapb20140721: 3751.256Sapb The src/external/mit/lua/src directory was accidentally created 3761.256Sapb and then deleted in the CVS repository. If you get errors like 3771.256Sapb 3781.256Sapb cvs [update aborted]: cannot open directory 3791.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 3801.256Sapb 3811.256Sapb then delete your local copy of that directory tree and try again. 3821.256Sapb 3831.255Sjoerg20140530: 3841.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 3851.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 3861.255Sjoerg 3871.251Smartin20140131: 3881.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 3891.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 3901.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 3911.251Smartin 3921.250Schristos20131227: 3931.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 3941.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 3951.250Schristos mode7 in your config file. Make sure you put the necessary restrict 3961.250Schristos statements to avoid being exposed. 3971.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 3981.250Schristos to make clean in libc 3991.250Schristos 4001.249Smrg20131129: 4011.249Smrg The GMP sources were updated, and builds will likely fail without 4021.249Smrg cleaning their build trees for both tools and in-tree, like below. 4031.249Smrg 4041.248Smrg20131128: 4051.248Smrg The MPC and MPFR sources were updated, and builds may require their 4061.248Smrg tools and in-tree directories cleaned for successful updates. 4071.248Smrg 4081.246Smartin20130605: 4091.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 4101.247Sspz to IPSEC (and the older IPSEC version removed). 4111.247Sspz 4121.247Sspz20130605: 4131.320Sandvar Previous freetype installations erroneously installed private 4141.246Smartin header files. If you are building against a non-empty $DESTDIR, 4151.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 4161.246Smartin 4171.245Smrg20130531: 4181.245Smrg The xdm update may cause build failure due to xdm.man being 4191.245Smrg in the obj tree. Make sure to ensure any like this: 4201.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 4211.245Smrg is fixed by deleting the xdm.man in the obj tree. 4221.245Smrg 4231.244Smrg20130530: 4241.244Smrg Updates of many xsrc packages will leave old .pc files around. 4251.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 4261.244Smrg 4271.242Schristos20130301: 4281.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 4291.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 4301.242Schristos 4311.238Sdholland20120726: 4321.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 4331.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 4341.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 4351.241Swiz some cases may succeed and install broken OpenSSL libraries that 4361.240Sdholland cause third-party software to link incorrectly and/or crash. 4371.238Sdholland 4381.237Swiz20120507: 4391.241Swiz The database schema for makemandb was changed. You will 4401.237Swiz need to update the database using 'makemandb -f' or wait 4411.237Swiz for the next weekly run to fix it. 4421.237Swiz 4431.236Sbsh20120319: 4441.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 4451.236Sbsh size of db_symtab automatically. You need to update dbsym in 4461.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 4471.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 4481.236Sbsh mk.conf. 4491.236Sbsh 4501.235Sjoerg20120216: 4511.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 4521.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 4531.239Sdholland and 20120216, daily and weekly could have created an unreadable 4541.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 4551.235Sjoerg the next run of weekly will fix it. 4561.233Sjoerg 4571.232Schristos20111227: 4581.232Schristos If you built between 20111225 and 20111227 you need to remove 4591.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 4601.232Schristos bump has been reverted. 4611.232Schristos 4621.231Stls20111125: 4631.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 4641.231Stls means it should no longer be explicitly listed in kernel 4651.231Stls configuration files. The line "pseudo-device rnd" should be 4661.231Stls removed from any custom kernel config files users may have. 4671.231Stls 4681.230Stls20111119: 4691.230Stls A problem with the datastructures used by the rndctl(8) 4701.230Stls utility (pointers in datastructures in an array, making 32->64 4711.230Stls bit compatibility very painful) has been fixed in a 4721.230Stls non-backwards-compatible way. If you replace your kernel, 4731.230Stls replace your rndctl executable too. 4741.241Swiz 4751.229Sjym20111001: 4761.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 4771.229Sjym changed and their new version is not backward compatible with the old 4781.241Swiz one. So ensure that all consumers of these functions (currently: 4791.229Sjym quota2 code and its tests) are updated together with the new lib. 4801.229Sjym 4811.228Smrg20110817: 4821.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 4831.228Smrg DESTDIR for them should be deleted before updating. 4841.228Smrg 4851.227Sriastrad20110806: 4861.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 4871.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 4881.227Sriastrad 4891.226Smrg20110805: 4901.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 4911.226Smrg the tree to be cleaned. Best to delete both objdir and 4921.226Smrg DESTDIR before running this update. So far, only the 4931.226Smrg sparc64, mips and powerpc platforms have changed. 4941.226Smrg 4951.225Smatt20110803: 4961.241Swiz The layout of external/public-domain/xz has changed. To do an 4971.225Smatt update build you will have to remove the contents of the OBJDIR 4981.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 4991.225Smatt is now a directory. 5001.225Smatt 5011.223Sjoerg20110410: 5021.241Swiz The configuration of src/tools/gcc has changed. To do an 5031.224Sdholland update build you have to clean both tools/binutils and 5041.224Sdholland tools/gcc by hand. 5051.223Sjoerg 5061.222Splunky20110328: 5071.222Splunky Building the Xorg binary was moved into a subdirectory to fix 5081.241Swiz ordering issues with "make all". It may be necessary to remove 5091.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 5101.222Splunky if your update build fails, as the "Xorg" entry there is now a 5111.222Splunky directory. 5121.222Splunky 5131.220Sjoerg20110121: 5141.221Slukem Assembler files no longer use -traditional-cpp. This can break 5151.220Sjoerg the build of individual parts of the tree. This is handled 5161.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 5171.220Sjoerg and re-run config(1) for any kernel configurations as needed. 5181.218Sjoerg 5191.217Sjruoho20101217: 5201.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 5211.241Swiz by default. It may be necessary to manually update passwd(5) and 5221.217Sjruoho group(5) in order to make the program work with existing setups. 5231.217Sjruoho 5241.216Schristos20101125: 5251.216Schristos The latest changes to setenv(3) dissallow setting environment 5261.241Swiz variables with names that contain '='. Revision 1.18 of env.c 5271.241Swiz assumed that this was allowed. Installing a new libc with an 5281.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 5291.216Schristos break which affects the autoconf tests for dependency finding, 5301.216Schristos so building gcc will end up printing: 5311.216Schristos checking dependency style of gcc... none 5321.216Schristos configure: error: no usable dependency style found 5331.216Schristos Fix it by rebuilding and re-installing env. 5341.138Slukem 5351.215Smrg20101119: 5361.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 5371.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 5381.215Smrg have any build problems with xsrc, or problems with mismatched 5391.215Smrg versions between xorg-server and drivers. 5401.215Smrg 5411.213Sjmmv20100604: 5421.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 5431.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 5441.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 5451.213Sjmmv trees by hand. 5461.213Sjmmv 5471.211Stnozaki20100522: 5481.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 5491.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 5501.212Smrg build problems with xsrc. 5511.212Smrg 5521.212Smrg20100522: 5531.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 5541.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 5551.211Stnozaki 5561.210Schristos20100520: 5571.241Swiz The location of the xkb compiled descriptions has changed. Please 5581.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 5591.210Schristos 5601.209Snjoly20100222: 5611.209Snjoly The shared objects file extension has been changed from .so to 5621.209Snjoly .pico, in order to avoid conflicts with shared libraries names 5631.209Snjoly libXX.so. All now stale regular .so files can be removed from 5641.209Snjoly your object directories. 5651.209Snjoly 5661.208Sroy20100204: 5671.208Sroy The termcap database has been removed from the sources, 5681.208Sroy but has not been marked obsolete so it is not removed 5691.208Sroy from the system when upgrading. 5701.208Sroy As such, you will need to remove them from your object 5711.208Sroy and destination directories. 5721.208Sroy 5731.203Sdyoung20091101: 5741.205Sdholland After updating, it may be necessary to make the 'cleandir' 5751.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 5761.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 5771.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 5781.203Sdyoung 5791.202Smrg20091001: 5801.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 5811.206Sdholland before building a kernel, or the build fails on cpufunc.S. 5821.206Sdholland 5831.206Sdholland20091001: 5841.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 5851.202Smrg symlink, failing the build. Delete the link, and the subdir 5861.202Smrg it is in, and retry your build. 5871.202Smrg 5881.201Sdsl20090718: 5891.201Sdsl libc build changed so that strchr() provides the extra entry 5901.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 5911.201Sdsl may fail because the archive contains the unwanted index.o. 5921.201Sdsl (Similarly for strrchr() and rindex().) 5931.201Sdsl 5941.198Smrg20090709: 5951.198Smrg Native Xorg was upgraded again. Builds will probably fail again 5961.198Smrg without a clean objdir, at least for src/external/mit/xorg. 5971.198Smrg 5981.197Smrg20090616: 5991.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 6001.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 6011.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 6021.197Smrg subdirectory has been changed into a file, and this needs to 6031.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 6041.197Smrg 6051.195Sperry20090501: 6061.195Sperry Several new functions were added to string.h/libc, and this 6071.195Sperry can cause autoconf problems during the tool build for people 6081.241Swiz who fail to clean out their tools objects properly. If you 6091.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 6101.195Sperry failure during the tool build, clean out all your tools 6111.195Sperry objects and start again. 6121.195Sperry 6131.194Smrg20090325: 6141.194Smrg The i386 port was switched to i486 default toolchain. This requires 6151.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 6161.194Smrg 6171.192Sskrll20090126: 6181.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 6191.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 6201.207Smbalmer to avoid using the old assembly stub. 6211.192Sskrll 6221.191Sjoerg20090202: 6231.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 6241.320Sandvar detection. It is recommended to rebuild the cache with 6251.191Sjoerg ``pkg_admin rebuild''. 6261.191Sjoerg 6271.184Schristos20090110: 6281.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 6291.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 6301.188Schristos This is needed even in the MODULAR kernel because there is 6311.188Schristos conditionally compiled code in rtsock.c. 6321.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 6331.184Schristos before installing. 6341.184Schristos 3. If you don't use build.sh and you build directly to root, and 6351.241Swiz your build breaks in the middle, don't despair. Make sure headers 6361.184Schristos are installed properly, and start building libraries first libc 6371.184Schristos and libutil, install them and then continue building all the 6381.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 6391.184Schristos the new libraries are installed, you can restart the build. 6401.184Schristos 4. If you compile packages and you notice link time warnings, 6411.189Shubertf rebuild the required packages to update their shared libraries. 6421.189Shubertf Any package you rebuild will require rebuilding all the packages 6431.189Shubertf that depend on it. 6441.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 6451.186Schristos will be upgraded and it will not be backwards compatible. 6461.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 6471.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 6481.241Swiz for utmp. You are better off removing the old files after 6491.190Sapb upgrading. The automated clearing of /var/run during 6501.190Sapb boot, and the automated rotating of files in /var/log by 6511.190Sapb newsyslog(8), may mean that you do not have to remove the 6521.190Sapb files manually. 6531.190Sapb 7. The optional accounting file (/var/account/acct, see 6541.190Sapb accton(8)) has not been versioned, and will need to be 6551.190Sapb removed. The automatic rotation of the accounting file by 6561.190Sapb /etc/daily limits the bad consequences of failure to remove 6571.190Sapb the file. 6581.196Sdholland 8. Application software that writes time_t to binary files on 6591.241Swiz disk will break or need attention. Most notably: if you are 6601.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 6611.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 6621.185Sjmcneill 6631.183Spgoyette20081219: 6641.183Spgoyette config(1) has been updated, and one of the files it creates - 6651.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 6661.183Spgoyette (done automatically by build.sh) and then you need to rerun 6671.183Spgoyette config on all kernel configuration files before rebuilding those 6681.183Spgoyette kernels. 6691.183Spgoyette 6701.181Scube20081205: 6711.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 6721.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 6731.181Scube set and will appear as extra files for MKX11=no update builds. 6741.178Slukem 6751.179Stsutsui20081122: 6761.182Stsutsui On i386, various kernel options(4) in GENERIC including 6771.180Swiz file systems have been disabled and moved into kernel modules. 6781.180Swiz Before trying a new GENERIC kernel, you have to prepare the 6791.179Stsutsui following files as well as a new GENERIC kernel: 6801.179Stsutsui 6811.179Stsutsui - build and install kernel modules from src/sys/modules 6821.179Stsutsui 6831.179Stsutsui - install the latest bootloader, which will load a module 6841.180Swiz for the file system from which the kernel is loaded automatically 6851.179Stsutsui 6861.180Swiz If you have to load your kernel from a file system which is not of 6871.180Swiz the same type as the root file system, you have to load the necessary 6881.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 6891.179Stsutsui 6901.178Slukem20080827: 6911.178Slukem If you built and installed a libc from sources between 6921.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 6931.178Slukem which results in false errors reported by lint(1). 6941.178Slukem Since this breaks the libc build itself, manual help is 6951.180Swiz needed -- lint must be disabled temporarily, e.g.: 6961.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 6971.178Slukem 6981.177Schristos20080813: 6991.177Schristos MKDEBUG build was broken because the .depend files did not know 7001.241Swiz about .go files. You need to remove all .depend files and rebuild. 7011.177Schristos 7021.200Sdholland20080802: 7031.200Sdholland A regression in binary compatibility for pthread_mutex_t has 7041.241Swiz been fixed. Unfortunately, the price is breaking compatibility 7051.200Sdholland for -current. 7061.200Sdholland 7071.200Sdholland Threaded programs (using libpthread) and C++ programs (using 7081.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 7091.200Sdholland be recompiled. 7101.200Sdholland 7111.200Sdholland One way to find affected pkgsrc packages: 7121.200Sdholland 7131.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 7141.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 7151.200Sdholland 7161.175Ssimonb20080731: 7171.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 7181.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 7191.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 7201.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 7211.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 7221.176Ssimonb also requires the super block to be in the UFS2 format. You 7231.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 7241.175Ssimonb 7251.174Slukem20080721: 7261.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 7271.174Slukem isn't defined. 7281.174Slukem 7291.173Sfreza20080531: 7301.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 7311.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 7321.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 7331.241Swiz won't work correctly. The following sequence of commands: 7341.173Sfreza 7351.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 7361.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 7371.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 7381.173Sfreza 7391.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 7401.173Sfreza 7411.172Slukem20080503: 7421.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 7431.172Slukem 7441.171She20080521: 7451.171She For a while, unprivileged UPDATE builds would fail to 7461.171She succeed at the checkflist stage, complaining that 7471.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 7481.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 7491.171She If you already hit this problem, update the .mk file, 7501.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 7511.171She 7521.174Slukem20080303: 7531.174Slukem Linker warnings are now fatal if $WARNS>0. 7541.174Slukem 7551.170Schristos20080126: 7561.170Schristos The posix_fadvise system call has been changed from an assembly 7571.241Swiz stub, to a c file that calls an assembly stub. You need to 7581.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 7591.170Schristos avoid using the old assembly stub. 7601.170Schristos 7611.168Sjoerg20071209: 7621.241Swiz The acpiec(4) driver has been split into two attachments. If you 7631.168Sjoerg get ACPI errors before the attachment, please update your kernel 7641.169Swiz configuration file appropriately or see GENERIC for more details. 7651.168Sjoerg 7661.166Sxtraeme20071115: 7671.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 7681.166Sxtraeme argument specified in the kernel configuration file is not valid 7691.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 7701.241Swiz rather than the EC address port. Please update your kernel 7711.167Swiz configuration file appropriately or see GENERIC for more details. 7721.166Sxtraeme 7731.165Sjmmv20071028: 7741.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 7751.165Sjmmv You need to update any custom kernel configuration file you have 7761.165Sjmmv to remove any references to pccons (which includes removing the 7771.165Sjmmv now useless XSERVER option) and replace them with the correct 7781.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 7791.165Sjmmv for more details. 7801.165Sjmmv 7811.164Sgdt20070913: 7821.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 7831.164Sgdt enumerate interfaces was fixed. The bug began to cause 7841.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 7851.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 7861.164Sgdt could not enumerate interfaces. (These are noted because 7871.164Sgdt normal kernel/userspace version matching hygiene is not 7881.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 7891.164Sgdt and userland are from after 20070913. 7901.164Sgdt 7911.163Sjoerg20070703: 7921.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 7931.199Sdholland calls the target-specific strip program, and the logic to pass 7941.199Sdholland down STRIP from make has been removed. This requires a 7951.199Sdholland re-installation of tools. 7961.163Sjoerg 7971.161Sdsl20070422: 7981.161Sdsl The way OS emulations lookup filenames inside the emulation root 7991.161Sdsl has been changed. Rather than modify the pathname (and copy back 8001.161Sdsl to userspace) namei() and lookup() directly check the emulation 8011.241Swiz root. One side effect is that absolute symlinks inside the emulated 8021.167Swiz root file system will be relative to that file system - unless they 8031.161Sdsl start /../ this is useful when the emulated root is a real install 8041.161Sdsl that has such links. 8051.161Sdsl This might affect symlinks that have been added to reference outside 8061.161Sdsl the emulated root. 8071.161Sdsl 8081.160Sjmcneill20070412: 8091.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 8101.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 8111.160Sjmcneill example. 8121.160Sjmcneill 8131.159Sgdt20070319: 8141.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 8151.159Sgdt on many platforms due to incorrect flags settings. If you 8161.159Sgdt updated and built after about 20070315, do "nbmake-$arch 8171.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 8181.159Sgdt rebuild of object files that might have been built 8191.159Sgdt incorrectly, and ensure that you have at least 8201.159Sgdt src/lib/libc/Makefile 1.130. 8211.159Sgdt 8221.241Swiz20070210: 8231.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 8241.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 8251.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 8261.158Sdbj will allow dependencies on those files to get get rebuilt 8271.158Sdbj 8281.157Sapb20070209: 8291.157Sapb The threading model was changed when the newlock2 branch 8301.157Sapb was merged to NetBSD-current. If you boot with a new 8311.157Sapb kernel (version 4.99.10), then you also need a new pthread 8321.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 8331.157Sapb an old kernel, then you need the old pthread library 8341.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 8351.157Sapb the pthread library in sync, old threaded applications should 8361.157Sapb continue to work with an old or new kernel. Note that named(8) 8371.157Sapb is the only threaded application in the base system. 8381.157Sapb 8391.154She20061214: 8401.154She Following the move of string_to_flags() and flags_to_string() 8411.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 8421.154She will need to do a "make cleandir" in 8431.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 8441.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 8451.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 8461.156She as the installation images in distrib/ 8471.154She in order to excise stale references to the old stat_flags.h header 8481.154She file in the ls sources -- stat_flags.h has been removed. 8491.154She 8501.152Schristos20061108: 8511.152Schristos The configure script used in the src/tools/gcc compiler has been 8521.152Schristos changed to indicate that our libc has ssp support built-in and 8531.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 8541.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 8551.152Schristos 8561.151Srpaulo20061009: 8571.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 8581.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 8591.151Srpaulo 8601.150Sbjh2120060814: 8611.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 8621.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 8631.150Sbjh21 kernel configuration for an example. X servers from the last 8641.150Sbjh21 few years should cope. 8651.150Sbjh21 8661.149Schristos20060703: 8671.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 8681.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 8691.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 8701.149Schristos 8711.148Sdogcow20060627: 8721.148Sdogcow socket(2) has changed, and its system call has been versioned. 8731.148Sdogcow For userlands with the old version of socket(2), make sure that 8741.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 8751.148Sdogcow errors will result. 8761.148Sdogcow 8771.1SabsHints for a more successful build: 8781.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8791.123Sjmc Use build.sh, but do not use its "expert mode": 8801.132Sjmmv This will automatically build the tools in the 8811.123Sjmc correct order, and it will keep the tools and the 8821.123Sjmc new build products from interfering with the running 8831.123Sjmc system. This will allow you to ignore most of the 8841.123Sjmc other advice in this file. 8851.2Smrg Build a new kernel first: 8861.2Smrg This makes sure that any new system calls or features 8871.2Smrg expected by the new userland will be present. This 8881.2Smrg helps to avoid critical errors when upgrading. 8891.1Sabs Use object directories: 8901.1Sabs This helps to keep stale object 8911.1Sabs files from polluting the build if a Makefile "forgets" 8921.1Sabs about one. It also makes it easier to clean up after 8931.1Sabs a build. It's also necessary if you want to use the 8941.1Sabs same source tree for multiple machines. 8951.123Sjmc To use object directories with build.sh: 8961.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8971.123Sjmc To use object directories without using build.sh: 8981.1Sabs a) cd /usr/src ; make cleandir 8991.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 9001.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 9011.1Sabs d) cd /usr/src ; make build 9021.2Smrg Note that running "make obj" in a directory will create 9031.2Smrg in obj.$MACHINE directory. 9041.1Sabs Build to a DESTDIR: 9051.123Sjmc This helps to keep old installed files (especially libraries) 9061.123Sjmc from interfering with the new build. 9071.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 9081.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 9091.123Sjmc environment variable before running make build. It should be 9101.123Sjmc set to the pathname of an initially empty directory. 9111.123Sjmc Problems: if you do not use build.sh, you might need to 9121.123Sjmc update critical utilities without using DESTDIR since 9131.123Sjmc nothing is executed from what is installed in DESTDIR. 9141.123Sjmc (See critical utils, below.) 9151.1Sabs Build often: 9161.1Sabs This keeps critical utilities current enough to not choke 9171.1Sabs on any other part of the source tree that depends on up to 9181.123Sjmc date functionality. If you use build.sh, you should not have 9191.123Sjmc this problem. 9201.241Swiz 9211.1SabsWhat to do if things don't work: 9221.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9231.230StlsWhen things don't work there are usually a few things that commonly 9241.1Sabsshould be done. 9251.1Sabs 1) make includes 9261.1Sabs This should be done automatically by make build. 9271.1Sabs 2) cd share/mk && make install 9281.1Sabs Again, automatically done by make build. 9291.1Sabs 9301.1SabsFailsafe rebuild of a small part of the tree: 9311.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9321.1SabsTo make sure you rebuild something correctly you want to do 9331.1Sabssomething like the following: 9341.1Sabs 1) Make sure the includes and .mk files are up to date. 9351.1Sabs 2) Make sure any program used to build the particular 9361.1Sabs utility is up to date. (yacc, lex, etc...) 9371.1Sabs 3) cd ...path/to/util... 9381.1Sabs make cleandir 9391.1Sabs rm ...all obj directories... 9401.1Sabs make cleandir # yes, again 9411.1Sabs make obj 9421.1Sabs make depend && make 9431.1Sabs 9441.1SabsFailsafe rebuild of the entire tree: 9451.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9461.1SabsIf you really want to make sure the source tree is clean and 9471.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 9481.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 9491.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 9501.1Sabs 9511.1Sabs---cut here--- 9521.1Sabs#!/bin/sh 9531.1Sabs. /etc/mk.conf 9541.1Sabs 9551.58Slukemif [ -z $NETBSDSRCDIR ] ; then 9561.58Slukem NETBSDSRCDIR=/usr/src 9571.1Sabsfi 9581.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 9591.1Sabs echo Unable to find sources 9601.1Sabs exit 1 9611.1Sabsfi 9621.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 9631.1Sabs 9641.1Sabsif [ -z $BSDOBJDIR ] ; then 9651.1Sabs BSDOBJDIR=/usr/obj 9661.1Sabsfi 9671.1Sabsif [ -d $BSDOBJDIR ] ; then 9681.1Sabs rm -rf $BSDOBJDIR 9691.1Sabsfi 9701.1Sabs 9711.58Slukemcd $NETBSDSRCDIR && make cleandir 9721.1Sabs 9731.1Sabs---cut here--- 9741.1Sabs 9751.1SabsCritical utilities: 9761.1Sabs^^^^^^^^^^^^^^^^^^^ 9771.3Sitojun usr.bin/compile_et 9781.1Sabs usr.bin/make 9791.1Sabs usr.bin/yacc 9801.1Sabs usr.bin/lex 9811.11Slukem usr.bin/xlint 9821.142Sdrochner usr.bin/config 9831.1Sabs 9841.34SsimonbOther problems and possible solutions: 9851.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9861.1SabsSymptom:Complaints involving a Makefile. 9871.17SerhFix: Rebuild usr.bin/make: 9881.17Serh cd usr.bin/make && make && make install 9891.111Ssimonb Or, a failsafe method if that doesn't work: 9901.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9911.17Serh 9921.1SabsFix: Make sure .mk files are up to date. 9931.1Sabs cd share/mk && make install 9941.2Smrg 9951.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9961.142SdrochnerFix: Rebuild usr.bin/config 9971.1Sabs 9981.1SabsSymptom: 9991.1SabsFix: Rebuild usr.bin/yacc 10001.1Sabs 10011.1SabsSymptom: 10021.1SabsFix: Rebuild usr.bin/lex 10031.1Sabs 10041.1SabsSymptom: 10051.1SabsFix: rm /usr/lib/libbfd.a 10061.4Sitojun 10071.4SitojunSymptom:Obsolete intermediate files are used during compilation 10081.4SitojunFix: Try the following sequence of commands in the directory in question. 10091.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 10101.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 10111.4Sitojun may remain. The command tries to clean everything up) 10121.5Swiz 10131.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 10141.207Smbalmer pointer type 10151.5SwizFix: Rebuild and install usr.bin/menuc 10161.12Sitojun 10171.12SitojunSymptom:mklocale not found during build in share/locale/ctype 10181.12SitojunFix: Build and install usr.bin/mklocale 10191.13Sdogcow 10201.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 10211.13SdogcowFix: Rebuild and install lib/libc 10221.13Sdogcow 10231.142SdrochnerSymptom:usr.bin/config fails to build. 10241.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 10251.13Sdogcow 10261.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 10271.19ScgdFix: Rebuild and install lib/libc 10281.24Sabs 10291.24SabsSymptom:lint does not understand the '-X' option 10301.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 10311.223Sjoerg 10321.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 10331.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 10341.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 10351.257Sapb 10361.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 10371.257Sapb No such file or directory. 10381.257SapbCause: If a directory is created by mistake, then it is sometimes 10391.257Sapb deleted from the CVS repository using administrative commands 10401.257Sapb that bypass the normal cvs access controls. If your cvs working tree 10411.257Sapb contains references to a directory that has been deleted on the 10421.257Sapb server in this way, then "cvs update" reports this error. 10431.257SapbFix: Recursively delete the affected directory from your working tree 10441.257Sapb and try the update again. 1045