UPDATING revision 1.336
11.336Smartin$NetBSD: UPDATING,v 1.336 2023/01/16 08:49:55 martin Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.257SapbSections are marked with "^^^^^". After the section on "Recent changes" 151.257Sapbare several sections containing more general information. 161.257Sapb 171.123SjmcSee also: BUILDING, build.sh, Makefile. 181.1Sabs 191.1SabsRecent changes: 201.1Sabs^^^^^^^^^^^^^^^ 211.230Stls 221.336Smartin20230112: 231.336Smartin New binutils require an updated ld.elf_so. If you are doing 241.336Smartin (unsupported) in-place self builds (with the -E flag to build.sh), 251.336Smartin make sure to have installed latest ld.elf_so before you rebuild 261.336Smartin userland. 271.336Smartin 281.335Schs20221116: 291.335Schs 301.335Schs The addition to NetBSD's version of UFS2 of support for extended 311.335Schs attributes broke backward compatibility with previous releases 321.335Schs of NetBSD, so UFS2 has been restored to being compatible with 331.335Schs previous NetBSD releases by disabling extended attributes. 341.335Schs (Note that ACLs are implemented as extended attributes, so 351.335Schs this changes disables ACLs as well.) 361.335Schs 371.335Schs Support for UFS2 with extended attributes is now available in a new 381.335Schs UFS variant called UFS2ea. If you have created extended attributes 391.335Schs in an original UFS2 file system then "fsck -p" will now fail due to 401.335Schs the unexpected presence of extended attributes and "fsck -y" will 411.335Schs remove all extended attributes. If you wish to preserve extended 421.335Schs attributes rather than delete them, there is a utility to convert 431.335Schs a UFS2 file system to UFS2ea and leave extended attributes in place, 441.335Schs but this should be used with caution since it will preserve any 451.335Schs extended attributes that have been corrupted by the backward 461.335Schs incompatibility too. 471.335Schs 481.335Schs If you wish to use a UFS2ea file system as your root file system, 491.335Schs then you will need to update your boot loader to a version that 501.335Schs supports UFS2ea. 511.335Schs 521.335Schs For more information, see: 531.335Schs https://wiki.netbsd.org/features/UFS2ea 541.335Schs 551.334Smrg20221111: 561.334Smrg The new libdrm import worsened the conflict issues for the 571.334Smrg kdump/ktruss ioctl, and i915 now conflicts with base, and has 581.334Smrg been turned off. This will cause update build issues like: 591.334Smrg 601.334Smrg kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 611.334Smrg undeclared here (not in a function); 621.334Smrg did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 631.334Smrg 641.334Smrg You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 651.334Smrg 661.331Sriastrad20220921: 671.331Sriastrad Since the kernel version was bumped to 9.99.100, the bootloader 681.333Sriastrad must be updated on x86 or EFI boot platforms in order to load 691.333Sriastrad modules from boot.cfg(5) or interactively at the bootloader 701.333Sriastrad prompt. 711.333Sriastrad 721.333Sriastrad The kernel can still load modules at runtime, with modload(8) 731.333Sriastrad or modules.conf(5), with no bootloader update. This will not 741.333Sriastrad affect release branches because it only applies to patch 751.333Sriastrad numbers >=100. 761.333Sriastrad 771.333Sriastrad On x86 (i386 or amd64) with BIOS boot, this requires copying a 781.333Sriastrad new /usr/mdec/boot to /boot. You can build this in the destdir 791.333Sriastrad by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 801.333Sriastrad sys/arch/i386/stand. 811.333Sriastrad 821.333Sriastrad On platforms with EFI boot (including x86 with EFI boot), this 831.333Sriastrad requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 841.333Sriastrad directory on the EFI system partition. The boot*.efi file is: 851.333Sriastrad 861.333Sriastrad aarch64 bootaa64.efi 871.333Sriastrad amd64 bootx64.efi 881.333Sriastrad arm bootarm.efi (32-bit arm) 891.333Sriastrad i386 bootx32.efi 901.333Sriastrad 911.333Sriastrad You can build this in the destdir by running 921.333Sriastrad `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 931.333Sriastrad sys/stand/efiboot/boot*. 941.331Sriastrad 951.330Slukem20220821: 961.330Slukem Support for building extsrc/ has been deprecated. 971.330Slukem EXTSRCSRCDIR and MKEXTSRC have been deprecated. 981.330Slukem 991.329Smrg20220714: 1001.329Smrg Updates to xorg-server and associated drivers may cause builds to 1011.329Smrg fail. Cleaning both DESTDIR and the xorg build tree may be needed. 1021.329Smrg 1031.328Smartin20220628: 1041.328Smartin Changes in the build of src/games/robots require a clean build 1051.328Smartin of that program. 1061.328Smartin 1071.324Smartin20211116: 1081.324Smartin Changes in the xorg build require clean obj dirs for external/mit/xorg 1091.325Smartin (or a full clean/non-update build). 1101.324Smartin 1111.323Snia20211112: 1121.323Snia Device tree sources were updated for evbarm. Some device nodes 1131.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 1141.323Snia 1151.322Smartin20211014: 1161.323Snia MKPIE default for aarch64 has changed, a clean build is required. 1171.322Smartin 1181.321Schristos20210917: 1191.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 1201.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 1211.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 1221.321Schristos 1231.319Smrg20210711: 1241.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 1251.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 1261.319Smrg 1271.318Smrg20210417: 1281.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 1291.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 1301.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 1311.318Smrg 1321.317Srillig20201230: 1331.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 1341.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 1351.317Srillig 1361.316Smrg20201016: 1371.316Smrg MIPS kernel modules have been disabled until they work. This will 1381.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 1391.316Smrg 1401.315Smrg20200925: 1411.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 1421.315Smrg in both the tools and external dirs. 1431.315Smrg 1441.314Smrg20200912: 1451.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 1461.314Smrg for several more, as will binutils 2.34. Clean as required. 1471.314Smrg 1481.313Smrg20200907: 1491.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 1501.313Smrg probably requires cleaning the tools/binutils. 1511.313Smrg 1521.311Smrg20200811: 1531.312Smrg GCC updates may require cleaning the objdir. This may occur 1541.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 1551.312Smrg GCC 9 upgrade. 1561.311Smrg 1571.309Schristos20200614: 1581.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 1591.332Sgutterid should handle the migration. 1601.309Schristos 1611.308Schristos20200601: 1621.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 1631.308Schristos created in the build directories and need cleaning. 1641.308Schristos 1651.307Smrg20200311: 1661.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 1671.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 1681.307Smrg 1691.306Schristos20191118: 1701.306Schristos More architectures were switched to gcc8: 1711.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 1721.306Schristos The same comments as in 20191022 apply. 1731.306Schristos 1741.305Smartin20191112: 1751.305Smartin The LLVM update requires a clean rebuild for all architectures using 1761.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 1771.305Smartin 1781.304Smartin20191022: 1791.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 1801.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 1811.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 1821.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 1831.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 1841.304Smartin daily builds and install that before doing the next in-place build. 1851.304Smartin 1861.303Smrg20191001: 1871.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 1881.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 1891.303Smrg directory, and also clean src/external/gpl3/gcc. 1901.303Smrg 1911.302Sriastrad20190903: 1921.306Schristos Files with names that coincide with existing files' names on 1931.302Sriastrad case-insensitive file systems were inadvertently committed, for 1941.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 1951.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 1961.302Sriastrad ran build.sh distribution or ran build.sh release, you must 1971.302Sriastrad manually delete the following files in your DESTDIR (which is 1981.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 1991.302Sriastrad them: 2001.302Sriastrad 2011.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 2021.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 2031.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 2041.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 2051.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 2061.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 2071.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 2081.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 2091.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 2101.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 2111.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 2121.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 2131.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 2141.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 2151.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 2161.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 2171.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 2181.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 2191.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 2201.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 2211.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 2221.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 2231.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 2241.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 2251.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 2261.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 2271.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 2281.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 2291.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 2301.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 2311.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 2321.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 2331.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 2341.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 2351.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 2361.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 2371.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 2381.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 2391.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 2401.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 2411.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 2421.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 2431.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 2441.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 2451.302Sriastrad /libdata/firmware/radeon/oland_me.bin 2461.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 2471.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 2481.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 2491.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 2501.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 2511.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 2521.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 2531.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 2541.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 2551.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 2561.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 2571.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 2581.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 2591.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 2601.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 2611.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 2621.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 2631.302Sriastrad /libdata/firmware/radeon/verde_me.bin 2641.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 2651.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 2661.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 2671.302Sriastrad 2681.302Sriastrad We will re-import these radeon firmware images another way 2691.302Sriastrad later. 2701.302Sriastrad 2711.301Smartin20190727: 2721.301Smartin The uefi bootloader has gained tftp support and needs a clean 2731.301Smartin build. If you do update builds, manually clean its object 2741.301Smartin directory by something like: 2751.301Smartin cd sys/arch/i386/stand/efiboot && make clean 2761.301Smartin 2771.300Smartin20190723: 2781.300Smartin The jemalloc allocator in libc is now build without extended 2791.300Smartin debugging (for performance reasons). In update builds make sure 2801.326Sandvar to rebuild it completely, by removing all affected object files, 2811.300Smartin including compat builds, something like: 2821.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 2831.300Smartin 2841.299Smrg20190207: 2851.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 2861.299Smrg 2871.298Smartin20180924: 2881.298Smartin A newer OpenSSL version has been imported. If you are doing 2891.298Smartin update builds, make sure to remove all old obj dirs, like: 2901.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 2911.298Smartin 2921.297Sjoerg20180717: 2931.297Sjoerg On aarch64 int64_t and related types have changed from long long 2941.297Sjoerg to long. This requires recompiling all C++ binaries. 2951.297Sjoerg 2961.296Smartin20180713: 2971.296Smartin On amd64 and i386 static binaries are now build position 2981.296Smartin independend. This requires recompilation of all object 2991.296Smartin files used to create the crunched /rescue binary. 3001.296Smartin Clean the rescue directory in your obj directory before 3011.296Smartin doing an update build, otherwise linking will fail. 3021.296Smartin 3031.293Sjakllsch20180414: 3041.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 3051.293Sjakllsch removal of tools/binutils objects directory may be required 3061.293Sjakllsch to fix tools build failure. 3071.293Sjakllsch 3081.292Smrg20180311: 3091.292Smrg bdftopcf was updated and may need cleaning in the 3101.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 3111.292Smrg link errors. 3121.292Smrg 3131.291Smrg20180212: 3141.291Smrg between OpenSSL and GCC updates, many things may fail to build. 3151.291Smrg any failure that looks like GCC or openssl is best handled by 3161.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 3171.291Smrg is recommended if build failures occur. 3181.291Smrg 3191.288Smartin20171225: 3201.288Smartin removal of the vadvise syscall requires manual removal of all 3211.288Smartin associated files from the libc build object directory (including 3221.289Schristos the .depend files) - a command like: 3231.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 3241.289Schristos For architectures that support multiple "compat" binary targets, 3251.289Schristos you'll need to cleanup both the regular libc directory and the 3261.290Smartin compat ones (the above command will do that). 3271.288Smartin 3281.287Skre20171010: 3291.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 3301.287Skre means that its objdir (or *.d and .depend at least) might need 3311.287Skre to be manually removed - or a build done once without -u. 3321.287Skre 3331.286Smrg20170822: 3341.286Smrg a new version of GMP has been imported and probably 3351.286Smrg will break parts of builds related to themselves or GCC, both 3361.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3371.286Smrg and MPC objdirs or build once without -u. 3381.286Smrg 3391.285Smrg20170816: 3401.285Smrg a new version of MPFR and MPC have been imported and probably 3411.285Smrg will break parts of builds related to themselves or GCC, both 3421.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3431.285Smrg and MPC objdirs or build once without -u. 3441.285Smrg 3451.284Smartin20170402: 3461.284Smartin a new version of dhcpcd has been imported, which does not support 3471.284Smartin update builds from the previous version. Remove your 3481.284Smartin external/bsd/dhcpcd object dir or build once without -u. 3491.284Smartin 3501.281Sroy20170211: 3511.281Sroy a new terminfo database has been imported. 3521.281Sroy The structure of it has changed slightly from prior versions and 3531.281Sroy an updated tic tool is required. 3541.281Sroy If you build.sh, don't use -u 3551.281Sroy 3561.280Skre20170207: 3571.278Skre various arch dependent libc/exect.S files were removed 3581.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 3591.279Skre if it exists) or do a clean build. 3601.279Skre (This is a bug in the make system, it should be corrected without 3611.279Skre human intervention, but isn't.) 3621.278Skre 3631.277Smartin20170104: 3641.277Smartin xinput build options have changed. 3651.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 3661.277Smartin if you build.sh -u 3671.277Smartin 3681.276Smartin20170103: 3691.276Smartin a new version of flex has been imported. 3701.276Smartin Remove the file from obj (external/bsd/flex) 3711.276Smartin if you build.sh -u 3721.276Smartin 3731.275Sspz20161014: 3741.275Sspz a new version of OpenSSL has been imported. 3751.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 3761.275Sspz if you build.sh -u 3771.275Sspz 3781.274Smartin20161009: 3791.274Smartin a new version of dhcpcd has been imported with slightly changed 3801.274Smartin build infrastructure. When doing a build.sh -u this requires 3811.274Smartin pruning the external/bsd/dhcpcd objdir. 3821.274Smartin 3831.273Smrg20160914: 3841.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 3851.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 3861.273Smrg and a clean objdir. 3871.273Smrg 3881.272Sdholland20160527: 3891.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 3901.272Sdholland been enabled. (see the amd64 entry two down for further info) 3911.272Sdholland 3921.270Schristos20160418: 3931.270Schristos libedit needs manual removal of all autogenerated files since 3941.271Schristos some of them are not autogenerated anymore. Remember that there 3951.271Schristos might be two copies of libedit if your platform builds "compat". 3961.270Schristos 3971.268Sriastrad20160410: 3981.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 3991.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 4001.268Sriastrad executables, means all code, including executables and not just 4011.268Sriastrad shared libraries, is position-independent and hence able to be 4021.268Sriastrad relocated by ASLR, address space layout randomization. 4031.268Sriastrad 4041.268Sriastrad The change was made in Makefile variables for compiler and 4051.268Sriastrad linker flags, for which make(1) does not record dependencies, 4061.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 4071.268Sriastrad 4081.268Sriastrad Partial rebuilds with some modified source files will likely 4091.268Sriastrad fail when linking executables, since the linker refuses to mix 4101.268Sriastrad position-independent code with position-dependent code in 4111.268Sriastrad position-independent executables: 4121.268Sriastrad 4131.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 4141.268Sriastrad 4151.267Smrg20160401: 4161.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 4171.269Sdholland Some people have found that cleandir is not sufficient, so if 4181.269Sdholland in doubt delete the entire object directory tree for gcc. 4191.267Smrg 4201.266Saymeric20160306: 4211.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 4221.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 4231.265Saymeric non-NetBSD hosts if linked with stale object files produced 4241.265Saymeric while they included a non-NetBSD regex.h. 4251.265Saymeric In any case, you should "make cleandir" at least these tools 4261.265Saymeric before updating your toolchain. 4271.265Saymeric 4281.264Smartin20160125: 4291.264Smartin Dtrace has been enabled by default on some architectures. 4301.264Smartin When doing an update build, make sure to clean the etc/mtree 4311.264Smartin object directory before starting the build - otherwise the 4321.264Smartin needed directories in destdir will not be created. 4331.264Smartin An easy way to do this is: 4341.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 4351.264Smartin 4361.263Sdholland20150818: 4371.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 4381.263Sdholland again. 4391.263Sdholland 4401.262Schristos20150413: 4411.262Schristos New acpica requires "make cleandir" and reinstalling yacc 4421.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 4431.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 4441.262Schristos 4451.261Smartin20150404: 4461.261Smartin Lint changes require a full rebuild of the tool, so make 4471.261Smartin sure to build without -u option to build.sh, or manually 4481.261Smartin do a make cleandir in src/tools/lint1 and 4491.261Smartin src/usr.bin/xlint. 4501.261Smartin 4511.260Sskrll20150310: 4521.260Sskrll Improvements to openssl for arm mean that update builds of 4531.260Sskrll the openssl libraries will fail. A make cleandir in 4541.260Sskrll external/bsd/openssl/lib is needed 4551.260Sskrll 4561.258Smartin20141026: 4571.259Smsaitoh A mishap during the import of pppd may cause your corruption 4581.258Smartin in your cvs directory if you happened to do a cvs update 4591.258Smartin during a short period of time. To fix, just remove the 4601.258Smartin directory src/external/bsd/ppp/dist/pppd completely 4611.258Smartin and let cvs restore it on next update. 4621.258Smartin 4631.256Sapb20140721: 4641.256Sapb The src/external/mit/lua/src directory was accidentally created 4651.256Sapb and then deleted in the CVS repository. If you get errors like 4661.256Sapb 4671.256Sapb cvs [update aborted]: cannot open directory 4681.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 4691.256Sapb 4701.256Sapb then delete your local copy of that directory tree and try again. 4711.256Sapb 4721.255Sjoerg20140530: 4731.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 4741.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 4751.255Sjoerg 4761.251Smartin20140131: 4771.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 4781.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 4791.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 4801.251Smartin 4811.250Schristos20131227: 4821.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 4831.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 4841.250Schristos mode7 in your config file. Make sure you put the necessary restrict 4851.250Schristos statements to avoid being exposed. 4861.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 4871.250Schristos to make clean in libc 4881.250Schristos 4891.249Smrg20131129: 4901.249Smrg The GMP sources were updated, and builds will likely fail without 4911.249Smrg cleaning their build trees for both tools and in-tree, like below. 4921.249Smrg 4931.248Smrg20131128: 4941.248Smrg The MPC and MPFR sources were updated, and builds may require their 4951.248Smrg tools and in-tree directories cleaned for successful updates. 4961.248Smrg 4971.246Smartin20130605: 4981.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 4991.247Sspz to IPSEC (and the older IPSEC version removed). 5001.247Sspz 5011.247Sspz20130605: 5021.320Sandvar Previous freetype installations erroneously installed private 5031.246Smartin header files. If you are building against a non-empty $DESTDIR, 5041.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 5051.246Smartin 5061.245Smrg20130531: 5071.245Smrg The xdm update may cause build failure due to xdm.man being 5081.245Smrg in the obj tree. Make sure to ensure any like this: 5091.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 5101.245Smrg is fixed by deleting the xdm.man in the obj tree. 5111.245Smrg 5121.244Smrg20130530: 5131.244Smrg Updates of many xsrc packages will leave old .pc files around. 5141.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 5151.244Smrg 5161.242Schristos20130301: 5171.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 5181.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 5191.242Schristos 5201.238Sdholland20120726: 5211.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 5221.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 5231.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 5241.241Swiz some cases may succeed and install broken OpenSSL libraries that 5251.240Sdholland cause third-party software to link incorrectly and/or crash. 5261.238Sdholland 5271.237Swiz20120507: 5281.241Swiz The database schema for makemandb was changed. You will 5291.237Swiz need to update the database using 'makemandb -f' or wait 5301.237Swiz for the next weekly run to fix it. 5311.237Swiz 5321.236Sbsh20120319: 5331.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 5341.236Sbsh size of db_symtab automatically. You need to update dbsym in 5351.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 5361.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 5371.236Sbsh mk.conf. 5381.236Sbsh 5391.235Sjoerg20120216: 5401.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 5411.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 5421.239Sdholland and 20120216, daily and weekly could have created an unreadable 5431.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 5441.235Sjoerg the next run of weekly will fix it. 5451.233Sjoerg 5461.232Schristos20111227: 5471.232Schristos If you built between 20111225 and 20111227 you need to remove 5481.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 5491.232Schristos bump has been reverted. 5501.232Schristos 5511.231Stls20111125: 5521.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 5531.231Stls means it should no longer be explicitly listed in kernel 5541.231Stls configuration files. The line "pseudo-device rnd" should be 5551.231Stls removed from any custom kernel config files users may have. 5561.231Stls 5571.230Stls20111119: 5581.230Stls A problem with the datastructures used by the rndctl(8) 5591.230Stls utility (pointers in datastructures in an array, making 32->64 5601.230Stls bit compatibility very painful) has been fixed in a 5611.230Stls non-backwards-compatible way. If you replace your kernel, 5621.230Stls replace your rndctl executable too. 5631.241Swiz 5641.229Sjym20111001: 5651.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 5661.229Sjym changed and their new version is not backward compatible with the old 5671.241Swiz one. So ensure that all consumers of these functions (currently: 5681.229Sjym quota2 code and its tests) are updated together with the new lib. 5691.229Sjym 5701.228Smrg20110817: 5711.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 5721.228Smrg DESTDIR for them should be deleted before updating. 5731.228Smrg 5741.227Sriastrad20110806: 5751.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 5761.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 5771.227Sriastrad 5781.226Smrg20110805: 5791.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 5801.226Smrg the tree to be cleaned. Best to delete both objdir and 5811.226Smrg DESTDIR before running this update. So far, only the 5821.226Smrg sparc64, mips and powerpc platforms have changed. 5831.226Smrg 5841.225Smatt20110803: 5851.241Swiz The layout of external/public-domain/xz has changed. To do an 5861.225Smatt update build you will have to remove the contents of the OBJDIR 5871.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 5881.225Smatt is now a directory. 5891.225Smatt 5901.223Sjoerg20110410: 5911.241Swiz The configuration of src/tools/gcc has changed. To do an 5921.224Sdholland update build you have to clean both tools/binutils and 5931.224Sdholland tools/gcc by hand. 5941.223Sjoerg 5951.222Splunky20110328: 5961.222Splunky Building the Xorg binary was moved into a subdirectory to fix 5971.241Swiz ordering issues with "make all". It may be necessary to remove 5981.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 5991.222Splunky if your update build fails, as the "Xorg" entry there is now a 6001.222Splunky directory. 6011.222Splunky 6021.220Sjoerg20110121: 6031.221Slukem Assembler files no longer use -traditional-cpp. This can break 6041.220Sjoerg the build of individual parts of the tree. This is handled 6051.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 6061.220Sjoerg and re-run config(1) for any kernel configurations as needed. 6071.218Sjoerg 6081.217Sjruoho20101217: 6091.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 6101.241Swiz by default. It may be necessary to manually update passwd(5) and 6111.217Sjruoho group(5) in order to make the program work with existing setups. 6121.217Sjruoho 6131.216Schristos20101125: 6141.327Sandvar The latest changes to setenv(3) disallow setting environment 6151.241Swiz variables with names that contain '='. Revision 1.18 of env.c 6161.241Swiz assumed that this was allowed. Installing a new libc with an 6171.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 6181.216Schristos break which affects the autoconf tests for dependency finding, 6191.216Schristos so building gcc will end up printing: 6201.216Schristos checking dependency style of gcc... none 6211.216Schristos configure: error: no usable dependency style found 6221.216Schristos Fix it by rebuilding and re-installing env. 6231.138Slukem 6241.215Smrg20101119: 6251.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 6261.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 6271.215Smrg have any build problems with xsrc, or problems with mismatched 6281.215Smrg versions between xorg-server and drivers. 6291.215Smrg 6301.213Sjmmv20100604: 6311.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 6321.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 6331.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 6341.213Sjmmv trees by hand. 6351.213Sjmmv 6361.211Stnozaki20100522: 6371.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 6381.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 6391.212Smrg build problems with xsrc. 6401.212Smrg 6411.212Smrg20100522: 6421.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 6431.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 6441.211Stnozaki 6451.210Schristos20100520: 6461.241Swiz The location of the xkb compiled descriptions has changed. Please 6471.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 6481.210Schristos 6491.209Snjoly20100222: 6501.209Snjoly The shared objects file extension has been changed from .so to 6511.209Snjoly .pico, in order to avoid conflicts with shared libraries names 6521.209Snjoly libXX.so. All now stale regular .so files can be removed from 6531.209Snjoly your object directories. 6541.209Snjoly 6551.208Sroy20100204: 6561.208Sroy The termcap database has been removed from the sources, 6571.208Sroy but has not been marked obsolete so it is not removed 6581.208Sroy from the system when upgrading. 6591.208Sroy As such, you will need to remove them from your object 6601.208Sroy and destination directories. 6611.208Sroy 6621.203Sdyoung20091101: 6631.205Sdholland After updating, it may be necessary to make the 'cleandir' 6641.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 6651.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 6661.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 6671.203Sdyoung 6681.202Smrg20091001: 6691.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 6701.206Sdholland before building a kernel, or the build fails on cpufunc.S. 6711.206Sdholland 6721.206Sdholland20091001: 6731.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 6741.202Smrg symlink, failing the build. Delete the link, and the subdir 6751.202Smrg it is in, and retry your build. 6761.202Smrg 6771.201Sdsl20090718: 6781.201Sdsl libc build changed so that strchr() provides the extra entry 6791.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 6801.201Sdsl may fail because the archive contains the unwanted index.o. 6811.201Sdsl (Similarly for strrchr() and rindex().) 6821.201Sdsl 6831.198Smrg20090709: 6841.198Smrg Native Xorg was upgraded again. Builds will probably fail again 6851.198Smrg without a clean objdir, at least for src/external/mit/xorg. 6861.198Smrg 6871.197Smrg20090616: 6881.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 6891.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 6901.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 6911.197Smrg subdirectory has been changed into a file, and this needs to 6921.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 6931.197Smrg 6941.195Sperry20090501: 6951.195Sperry Several new functions were added to string.h/libc, and this 6961.195Sperry can cause autoconf problems during the tool build for people 6971.241Swiz who fail to clean out their tools objects properly. If you 6981.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 6991.195Sperry failure during the tool build, clean out all your tools 7001.195Sperry objects and start again. 7011.195Sperry 7021.194Smrg20090325: 7031.194Smrg The i386 port was switched to i486 default toolchain. This requires 7041.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 7051.194Smrg 7061.192Sskrll20090126: 7071.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 7081.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 7091.207Smbalmer to avoid using the old assembly stub. 7101.192Sskrll 7111.191Sjoerg20090202: 7121.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 7131.320Sandvar detection. It is recommended to rebuild the cache with 7141.191Sjoerg ``pkg_admin rebuild''. 7151.191Sjoerg 7161.184Schristos20090110: 7171.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 7181.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 7191.188Schristos This is needed even in the MODULAR kernel because there is 7201.188Schristos conditionally compiled code in rtsock.c. 7211.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 7221.184Schristos before installing. 7231.184Schristos 3. If you don't use build.sh and you build directly to root, and 7241.241Swiz your build breaks in the middle, don't despair. Make sure headers 7251.184Schristos are installed properly, and start building libraries first libc 7261.184Schristos and libutil, install them and then continue building all the 7271.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 7281.184Schristos the new libraries are installed, you can restart the build. 7291.184Schristos 4. If you compile packages and you notice link time warnings, 7301.189Shubertf rebuild the required packages to update their shared libraries. 7311.189Shubertf Any package you rebuild will require rebuilding all the packages 7321.189Shubertf that depend on it. 7331.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 7341.186Schristos will be upgraded and it will not be backwards compatible. 7351.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 7361.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 7371.241Swiz for utmp. You are better off removing the old files after 7381.190Sapb upgrading. The automated clearing of /var/run during 7391.190Sapb boot, and the automated rotating of files in /var/log by 7401.190Sapb newsyslog(8), may mean that you do not have to remove the 7411.190Sapb files manually. 7421.190Sapb 7. The optional accounting file (/var/account/acct, see 7431.190Sapb accton(8)) has not been versioned, and will need to be 7441.190Sapb removed. The automatic rotation of the accounting file by 7451.190Sapb /etc/daily limits the bad consequences of failure to remove 7461.190Sapb the file. 7471.196Sdholland 8. Application software that writes time_t to binary files on 7481.241Swiz disk will break or need attention. Most notably: if you are 7491.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 7501.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 7511.185Sjmcneill 7521.183Spgoyette20081219: 7531.183Spgoyette config(1) has been updated, and one of the files it creates - 7541.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 7551.183Spgoyette (done automatically by build.sh) and then you need to rerun 7561.183Spgoyette config on all kernel configuration files before rebuilding those 7571.183Spgoyette kernels. 7581.183Spgoyette 7591.181Scube20081205: 7601.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 7611.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 7621.181Scube set and will appear as extra files for MKX11=no update builds. 7631.178Slukem 7641.179Stsutsui20081122: 7651.182Stsutsui On i386, various kernel options(4) in GENERIC including 7661.180Swiz file systems have been disabled and moved into kernel modules. 7671.180Swiz Before trying a new GENERIC kernel, you have to prepare the 7681.179Stsutsui following files as well as a new GENERIC kernel: 7691.179Stsutsui 7701.179Stsutsui - build and install kernel modules from src/sys/modules 7711.179Stsutsui 7721.179Stsutsui - install the latest bootloader, which will load a module 7731.180Swiz for the file system from which the kernel is loaded automatically 7741.179Stsutsui 7751.180Swiz If you have to load your kernel from a file system which is not of 7761.180Swiz the same type as the root file system, you have to load the necessary 7771.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 7781.179Stsutsui 7791.178Slukem20080827: 7801.178Slukem If you built and installed a libc from sources between 7811.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 7821.178Slukem which results in false errors reported by lint(1). 7831.178Slukem Since this breaks the libc build itself, manual help is 7841.180Swiz needed -- lint must be disabled temporarily, e.g.: 7851.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 7861.178Slukem 7871.177Schristos20080813: 7881.177Schristos MKDEBUG build was broken because the .depend files did not know 7891.241Swiz about .go files. You need to remove all .depend files and rebuild. 7901.177Schristos 7911.200Sdholland20080802: 7921.200Sdholland A regression in binary compatibility for pthread_mutex_t has 7931.241Swiz been fixed. Unfortunately, the price is breaking compatibility 7941.200Sdholland for -current. 7951.200Sdholland 7961.200Sdholland Threaded programs (using libpthread) and C++ programs (using 7971.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 7981.200Sdholland be recompiled. 7991.200Sdholland 8001.200Sdholland One way to find affected pkgsrc packages: 8011.200Sdholland 8021.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 8031.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 8041.200Sdholland 8051.175Ssimonb20080731: 8061.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 8071.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 8081.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 8091.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 8101.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 8111.176Ssimonb also requires the super block to be in the UFS2 format. You 8121.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 8131.175Ssimonb 8141.174Slukem20080721: 8151.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 8161.174Slukem isn't defined. 8171.174Slukem 8181.173Sfreza20080531: 8191.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 8201.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 8211.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 8221.241Swiz won't work correctly. The following sequence of commands: 8231.173Sfreza 8241.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 8251.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 8261.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 8271.173Sfreza 8281.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 8291.173Sfreza 8301.172Slukem20080503: 8311.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 8321.172Slukem 8331.171She20080521: 8341.171She For a while, unprivileged UPDATE builds would fail to 8351.171She succeed at the checkflist stage, complaining that 8361.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 8371.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 8381.171She If you already hit this problem, update the .mk file, 8391.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 8401.171She 8411.174Slukem20080303: 8421.174Slukem Linker warnings are now fatal if $WARNS>0. 8431.174Slukem 8441.170Schristos20080126: 8451.170Schristos The posix_fadvise system call has been changed from an assembly 8461.241Swiz stub, to a c file that calls an assembly stub. You need to 8471.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 8481.170Schristos avoid using the old assembly stub. 8491.170Schristos 8501.168Sjoerg20071209: 8511.241Swiz The acpiec(4) driver has been split into two attachments. If you 8521.168Sjoerg get ACPI errors before the attachment, please update your kernel 8531.169Swiz configuration file appropriately or see GENERIC for more details. 8541.168Sjoerg 8551.166Sxtraeme20071115: 8561.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 8571.166Sxtraeme argument specified in the kernel configuration file is not valid 8581.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 8591.241Swiz rather than the EC address port. Please update your kernel 8601.167Swiz configuration file appropriately or see GENERIC for more details. 8611.166Sxtraeme 8621.165Sjmmv20071028: 8631.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 8641.165Sjmmv You need to update any custom kernel configuration file you have 8651.165Sjmmv to remove any references to pccons (which includes removing the 8661.165Sjmmv now useless XSERVER option) and replace them with the correct 8671.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 8681.165Sjmmv for more details. 8691.165Sjmmv 8701.164Sgdt20070913: 8711.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 8721.164Sgdt enumerate interfaces was fixed. The bug began to cause 8731.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 8741.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 8751.164Sgdt could not enumerate interfaces. (These are noted because 8761.164Sgdt normal kernel/userspace version matching hygiene is not 8771.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 8781.164Sgdt and userland are from after 20070913. 8791.164Sgdt 8801.163Sjoerg20070703: 8811.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 8821.199Sdholland calls the target-specific strip program, and the logic to pass 8831.199Sdholland down STRIP from make has been removed. This requires a 8841.199Sdholland re-installation of tools. 8851.163Sjoerg 8861.161Sdsl20070422: 8871.161Sdsl The way OS emulations lookup filenames inside the emulation root 8881.161Sdsl has been changed. Rather than modify the pathname (and copy back 8891.161Sdsl to userspace) namei() and lookup() directly check the emulation 8901.241Swiz root. One side effect is that absolute symlinks inside the emulated 8911.167Swiz root file system will be relative to that file system - unless they 8921.161Sdsl start /../ this is useful when the emulated root is a real install 8931.161Sdsl that has such links. 8941.161Sdsl This might affect symlinks that have been added to reference outside 8951.161Sdsl the emulated root. 8961.161Sdsl 8971.160Sjmcneill20070412: 8981.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 8991.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 9001.160Sjmcneill example. 9011.160Sjmcneill 9021.159Sgdt20070319: 9031.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 9041.159Sgdt on many platforms due to incorrect flags settings. If you 9051.159Sgdt updated and built after about 20070315, do "nbmake-$arch 9061.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 9071.159Sgdt rebuild of object files that might have been built 9081.159Sgdt incorrectly, and ensure that you have at least 9091.159Sgdt src/lib/libc/Makefile 1.130. 9101.159Sgdt 9111.241Swiz20070210: 9121.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 9131.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 9141.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 9151.158Sdbj will allow dependencies on those files to get get rebuilt 9161.158Sdbj 9171.157Sapb20070209: 9181.157Sapb The threading model was changed when the newlock2 branch 9191.157Sapb was merged to NetBSD-current. If you boot with a new 9201.157Sapb kernel (version 4.99.10), then you also need a new pthread 9211.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 9221.157Sapb an old kernel, then you need the old pthread library 9231.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 9241.157Sapb the pthread library in sync, old threaded applications should 9251.157Sapb continue to work with an old or new kernel. Note that named(8) 9261.157Sapb is the only threaded application in the base system. 9271.157Sapb 9281.154She20061214: 9291.154She Following the move of string_to_flags() and flags_to_string() 9301.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 9311.154She will need to do a "make cleandir" in 9321.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 9331.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 9341.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 9351.156She as the installation images in distrib/ 9361.154She in order to excise stale references to the old stat_flags.h header 9371.154She file in the ls sources -- stat_flags.h has been removed. 9381.154She 9391.152Schristos20061108: 9401.152Schristos The configure script used in the src/tools/gcc compiler has been 9411.152Schristos changed to indicate that our libc has ssp support built-in and 9421.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 9431.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 9441.152Schristos 9451.151Srpaulo20061009: 9461.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 9471.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 9481.151Srpaulo 9491.150Sbjh2120060814: 9501.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 9511.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 9521.150Sbjh21 kernel configuration for an example. X servers from the last 9531.150Sbjh21 few years should cope. 9541.150Sbjh21 9551.149Schristos20060703: 9561.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 9571.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 9581.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 9591.149Schristos 9601.148Sdogcow20060627: 9611.148Sdogcow socket(2) has changed, and its system call has been versioned. 9621.148Sdogcow For userlands with the old version of socket(2), make sure that 9631.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 9641.148Sdogcow errors will result. 9651.148Sdogcow 9661.1SabsHints for a more successful build: 9671.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9681.123Sjmc Use build.sh, but do not use its "expert mode": 9691.132Sjmmv This will automatically build the tools in the 9701.123Sjmc correct order, and it will keep the tools and the 9711.123Sjmc new build products from interfering with the running 9721.123Sjmc system. This will allow you to ignore most of the 9731.123Sjmc other advice in this file. 9741.2Smrg Build a new kernel first: 9751.2Smrg This makes sure that any new system calls or features 9761.2Smrg expected by the new userland will be present. This 9771.2Smrg helps to avoid critical errors when upgrading. 9781.1Sabs Use object directories: 9791.1Sabs This helps to keep stale object 9801.1Sabs files from polluting the build if a Makefile "forgets" 9811.1Sabs about one. It also makes it easier to clean up after 9821.1Sabs a build. It's also necessary if you want to use the 9831.1Sabs same source tree for multiple machines. 9841.123Sjmc To use object directories with build.sh: 9851.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 9861.123Sjmc To use object directories without using build.sh: 9871.1Sabs a) cd /usr/src ; make cleandir 9881.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 9891.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 9901.1Sabs d) cd /usr/src ; make build 9911.2Smrg Note that running "make obj" in a directory will create 9921.2Smrg in obj.$MACHINE directory. 9931.1Sabs Build to a DESTDIR: 9941.123Sjmc This helps to keep old installed files (especially libraries) 9951.123Sjmc from interfering with the new build. 9961.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 9971.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 9981.123Sjmc environment variable before running make build. It should be 9991.123Sjmc set to the pathname of an initially empty directory. 10001.123Sjmc Problems: if you do not use build.sh, you might need to 10011.123Sjmc update critical utilities without using DESTDIR since 10021.123Sjmc nothing is executed from what is installed in DESTDIR. 10031.123Sjmc (See critical utils, below.) 10041.1Sabs Build often: 10051.1Sabs This keeps critical utilities current enough to not choke 10061.1Sabs on any other part of the source tree that depends on up to 10071.123Sjmc date functionality. If you use build.sh, you should not have 10081.123Sjmc this problem. 10091.241Swiz 10101.1SabsWhat to do if things don't work: 10111.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10121.230StlsWhen things don't work there are usually a few things that commonly 10131.1Sabsshould be done. 10141.1Sabs 1) make includes 10151.1Sabs This should be done automatically by make build. 10161.1Sabs 2) cd share/mk && make install 10171.1Sabs Again, automatically done by make build. 10181.1Sabs 10191.1SabsFailsafe rebuild of a small part of the tree: 10201.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10211.1SabsTo make sure you rebuild something correctly you want to do 10221.1Sabssomething like the following: 10231.1Sabs 1) Make sure the includes and .mk files are up to date. 10241.1Sabs 2) Make sure any program used to build the particular 10251.1Sabs utility is up to date. (yacc, lex, etc...) 10261.1Sabs 3) cd ...path/to/util... 10271.1Sabs make cleandir 10281.1Sabs rm ...all obj directories... 10291.1Sabs make cleandir # yes, again 10301.1Sabs make obj 10311.1Sabs make depend && make 10321.1Sabs 10331.1SabsFailsafe rebuild of the entire tree: 10341.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10351.1SabsIf you really want to make sure the source tree is clean and 10361.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 10371.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 10381.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 10391.1Sabs 10401.1Sabs---cut here--- 10411.1Sabs#!/bin/sh 10421.1Sabs. /etc/mk.conf 10431.1Sabs 10441.58Slukemif [ -z $NETBSDSRCDIR ] ; then 10451.58Slukem NETBSDSRCDIR=/usr/src 10461.1Sabsfi 10471.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 10481.1Sabs echo Unable to find sources 10491.1Sabs exit 1 10501.1Sabsfi 10511.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 10521.1Sabs 10531.1Sabsif [ -z $BSDOBJDIR ] ; then 10541.1Sabs BSDOBJDIR=/usr/obj 10551.1Sabsfi 10561.1Sabsif [ -d $BSDOBJDIR ] ; then 10571.1Sabs rm -rf $BSDOBJDIR 10581.1Sabsfi 10591.1Sabs 10601.58Slukemcd $NETBSDSRCDIR && make cleandir 10611.1Sabs 10621.1Sabs---cut here--- 10631.1Sabs 10641.1SabsCritical utilities: 10651.1Sabs^^^^^^^^^^^^^^^^^^^ 10661.3Sitojun usr.bin/compile_et 10671.1Sabs usr.bin/make 10681.1Sabs usr.bin/yacc 10691.1Sabs usr.bin/lex 10701.11Slukem usr.bin/xlint 10711.142Sdrochner usr.bin/config 10721.1Sabs 10731.34SsimonbOther problems and possible solutions: 10741.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10751.1SabsSymptom:Complaints involving a Makefile. 10761.17SerhFix: Rebuild usr.bin/make: 10771.17Serh cd usr.bin/make && make && make install 10781.111Ssimonb Or, a failsafe method if that doesn't work: 10791.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 10801.17Serh 10811.1SabsFix: Make sure .mk files are up to date. 10821.1Sabs cd share/mk && make install 10831.2Smrg 10841.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 10851.142SdrochnerFix: Rebuild usr.bin/config 10861.1Sabs 10871.1SabsSymptom: 10881.1SabsFix: Rebuild usr.bin/yacc 10891.1Sabs 10901.1SabsSymptom: 10911.1SabsFix: Rebuild usr.bin/lex 10921.1Sabs 10931.1SabsSymptom: 10941.1SabsFix: rm /usr/lib/libbfd.a 10951.4Sitojun 10961.4SitojunSymptom:Obsolete intermediate files are used during compilation 10971.4SitojunFix: Try the following sequence of commands in the directory in question. 10981.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 10991.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 11001.4Sitojun may remain. The command tries to clean everything up) 11011.5Swiz 11021.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 11031.207Smbalmer pointer type 11041.5SwizFix: Rebuild and install usr.bin/menuc 11051.12Sitojun 11061.12SitojunSymptom:mklocale not found during build in share/locale/ctype 11071.12SitojunFix: Build and install usr.bin/mklocale 11081.13Sdogcow 11091.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 11101.13SdogcowFix: Rebuild and install lib/libc 11111.13Sdogcow 11121.142SdrochnerSymptom:usr.bin/config fails to build. 11131.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 11141.13Sdogcow 11151.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 11161.19ScgdFix: Rebuild and install lib/libc 11171.24Sabs 11181.24SabsSymptom:lint does not understand the '-X' option 11191.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 11201.223Sjoerg 11211.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 11221.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 11231.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 11241.257Sapb 11251.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 11261.257Sapb No such file or directory. 11271.257SapbCause: If a directory is created by mistake, then it is sometimes 11281.257Sapb deleted from the CVS repository using administrative commands 11291.257Sapb that bypass the normal cvs access controls. If your cvs working tree 11301.257Sapb contains references to a directory that has been deleted on the 11311.257Sapb server in this way, then "cvs update" reports this error. 11321.257SapbFix: Recursively delete the affected directory from your working tree 11331.257Sapb and try the update again. 1134