UPDATING revision 1.338
11.338Slukem$NetBSD: UPDATING,v 1.338 2023/05/23 20:26:52 lukem 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.338Slukem 231.338Slukem20230523: 241.338Slukem ctfmerge was fixed as macOS host tool. This may require a clean tools 251.338Slukem rebuild to detect the update to tools/compat/configure. 261.338Slukem 271.337Smrg20230322: 281.337Smrg Fixes for moved /lib/libisns* mean that builds will complain about 291.337Smrg ./usr/lib/libisns* being missing until src/lib/libisns is forced 301.337Smrg to (re)install the files, including the symlinks. The simplest 311.337Smrg way is to clean this subdir before building. 321.337Smrg 331.336Smartin20230112: 341.336Smartin New binutils require an updated ld.elf_so. If you are doing 351.336Smartin (unsupported) in-place self builds (with the -E flag to build.sh), 361.336Smartin make sure to have installed latest ld.elf_so before you rebuild 371.336Smartin userland. 381.336Smartin 391.335Schs20221116: 401.335Schs The addition to NetBSD's version of UFS2 of support for extended 411.335Schs attributes broke backward compatibility with previous releases 421.335Schs of NetBSD, so UFS2 has been restored to being compatible with 431.335Schs previous NetBSD releases by disabling extended attributes. 441.335Schs (Note that ACLs are implemented as extended attributes, so 451.335Schs this changes disables ACLs as well.) 461.335Schs 471.335Schs Support for UFS2 with extended attributes is now available in a new 481.335Schs UFS variant called UFS2ea. If you have created extended attributes 491.335Schs in an original UFS2 file system then "fsck -p" will now fail due to 501.335Schs the unexpected presence of extended attributes and "fsck -y" will 511.335Schs remove all extended attributes. If you wish to preserve extended 521.335Schs attributes rather than delete them, there is a utility to convert 531.335Schs a UFS2 file system to UFS2ea and leave extended attributes in place, 541.335Schs but this should be used with caution since it will preserve any 551.335Schs extended attributes that have been corrupted by the backward 561.335Schs incompatibility too. 571.335Schs 581.335Schs If you wish to use a UFS2ea file system as your root file system, 591.335Schs then you will need to update your boot loader to a version that 601.335Schs supports UFS2ea. 611.335Schs 621.335Schs For more information, see: 631.335Schs https://wiki.netbsd.org/features/UFS2ea 641.335Schs 651.334Smrg20221111: 661.334Smrg The new libdrm import worsened the conflict issues for the 671.334Smrg kdump/ktruss ioctl, and i915 now conflicts with base, and has 681.334Smrg been turned off. This will cause update build issues like: 691.334Smrg 701.334Smrg kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 711.334Smrg undeclared here (not in a function); 721.334Smrg did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 731.334Smrg 741.334Smrg You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 751.334Smrg 761.331Sriastrad20220921: 771.331Sriastrad Since the kernel version was bumped to 9.99.100, the bootloader 781.333Sriastrad must be updated on x86 or EFI boot platforms in order to load 791.333Sriastrad modules from boot.cfg(5) or interactively at the bootloader 801.333Sriastrad prompt. 811.333Sriastrad 821.333Sriastrad The kernel can still load modules at runtime, with modload(8) 831.333Sriastrad or modules.conf(5), with no bootloader update. This will not 841.333Sriastrad affect release branches because it only applies to patch 851.333Sriastrad numbers >=100. 861.333Sriastrad 871.333Sriastrad On x86 (i386 or amd64) with BIOS boot, this requires copying a 881.333Sriastrad new /usr/mdec/boot to /boot. You can build this in the destdir 891.333Sriastrad by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 901.333Sriastrad sys/arch/i386/stand. 911.333Sriastrad 921.333Sriastrad On platforms with EFI boot (including x86 with EFI boot), this 931.333Sriastrad requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 941.333Sriastrad directory on the EFI system partition. The boot*.efi file is: 951.333Sriastrad 961.333Sriastrad aarch64 bootaa64.efi 971.333Sriastrad amd64 bootx64.efi 981.333Sriastrad arm bootarm.efi (32-bit arm) 991.333Sriastrad i386 bootx32.efi 1001.333Sriastrad 1011.333Sriastrad You can build this in the destdir by running 1021.333Sriastrad `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 1031.333Sriastrad sys/stand/efiboot/boot*. 1041.331Sriastrad 1051.330Slukem20220821: 1061.330Slukem Support for building extsrc/ has been deprecated. 1071.330Slukem EXTSRCSRCDIR and MKEXTSRC have been deprecated. 1081.330Slukem 1091.329Smrg20220714: 1101.329Smrg Updates to xorg-server and associated drivers may cause builds to 1111.329Smrg fail. Cleaning both DESTDIR and the xorg build tree may be needed. 1121.329Smrg 1131.328Smartin20220628: 1141.328Smartin Changes in the build of src/games/robots require a clean build 1151.328Smartin of that program. 1161.328Smartin 1171.324Smartin20211116: 1181.324Smartin Changes in the xorg build require clean obj dirs for external/mit/xorg 1191.325Smartin (or a full clean/non-update build). 1201.324Smartin 1211.323Snia20211112: 1221.323Snia Device tree sources were updated for evbarm. Some device nodes 1231.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 1241.323Snia 1251.322Smartin20211014: 1261.323Snia MKPIE default for aarch64 has changed, a clean build is required. 1271.322Smartin 1281.321Schristos20210917: 1291.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 1301.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 1311.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 1321.321Schristos 1331.319Smrg20210711: 1341.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 1351.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 1361.319Smrg 1371.318Smrg20210417: 1381.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 1391.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 1401.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 1411.318Smrg 1421.317Srillig20201230: 1431.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 1441.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 1451.317Srillig 1461.316Smrg20201016: 1471.316Smrg MIPS kernel modules have been disabled until they work. This will 1481.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 1491.316Smrg 1501.315Smrg20200925: 1511.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 1521.315Smrg in both the tools and external dirs. 1531.315Smrg 1541.314Smrg20200912: 1551.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 1561.314Smrg for several more, as will binutils 2.34. Clean as required. 1571.314Smrg 1581.313Smrg20200907: 1591.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 1601.313Smrg probably requires cleaning the tools/binutils. 1611.313Smrg 1621.311Smrg20200811: 1631.312Smrg GCC updates may require cleaning the objdir. This may occur 1641.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 1651.312Smrg GCC 9 upgrade. 1661.311Smrg 1671.309Schristos20200614: 1681.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 1691.332Sgutterid should handle the migration. 1701.309Schristos 1711.308Schristos20200601: 1721.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 1731.308Schristos created in the build directories and need cleaning. 1741.308Schristos 1751.307Smrg20200311: 1761.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 1771.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 1781.307Smrg 1791.306Schristos20191118: 1801.306Schristos More architectures were switched to gcc8: 1811.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 1821.306Schristos The same comments as in 20191022 apply. 1831.306Schristos 1841.305Smartin20191112: 1851.305Smartin The LLVM update requires a clean rebuild for all architectures using 1861.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 1871.305Smartin 1881.304Smartin20191022: 1891.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 1901.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 1911.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 1921.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 1931.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 1941.304Smartin daily builds and install that before doing the next in-place build. 1951.304Smartin 1961.303Smrg20191001: 1971.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 1981.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 1991.303Smrg directory, and also clean src/external/gpl3/gcc. 2001.303Smrg 2011.302Sriastrad20190903: 2021.306Schristos Files with names that coincide with existing files' names on 2031.302Sriastrad case-insensitive file systems were inadvertently committed, for 2041.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 2051.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 2061.302Sriastrad ran build.sh distribution or ran build.sh release, you must 2071.302Sriastrad manually delete the following files in your DESTDIR (which is 2081.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 2091.302Sriastrad them: 2101.302Sriastrad 2111.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 2121.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 2131.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 2141.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 2151.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 2161.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 2171.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 2181.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 2191.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 2201.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 2211.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 2221.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 2231.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 2241.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 2251.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 2261.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 2271.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 2281.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 2291.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 2301.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 2311.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 2321.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 2331.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 2341.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 2351.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 2361.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 2371.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 2381.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 2391.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 2401.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 2411.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 2421.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 2431.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 2441.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 2451.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 2461.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 2471.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 2481.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 2491.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 2501.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 2511.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 2521.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 2531.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 2541.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 2551.302Sriastrad /libdata/firmware/radeon/oland_me.bin 2561.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 2571.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 2581.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 2591.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 2601.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 2611.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 2621.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 2631.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 2641.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 2651.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 2661.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 2671.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 2681.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 2691.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 2701.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 2711.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 2721.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 2731.302Sriastrad /libdata/firmware/radeon/verde_me.bin 2741.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 2751.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 2761.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 2771.302Sriastrad 2781.302Sriastrad We will re-import these radeon firmware images another way 2791.302Sriastrad later. 2801.302Sriastrad 2811.301Smartin20190727: 2821.301Smartin The uefi bootloader has gained tftp support and needs a clean 2831.301Smartin build. If you do update builds, manually clean its object 2841.301Smartin directory by something like: 2851.301Smartin cd sys/arch/i386/stand/efiboot && make clean 2861.301Smartin 2871.300Smartin20190723: 2881.300Smartin The jemalloc allocator in libc is now build without extended 2891.300Smartin debugging (for performance reasons). In update builds make sure 2901.326Sandvar to rebuild it completely, by removing all affected object files, 2911.300Smartin including compat builds, something like: 2921.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 2931.300Smartin 2941.299Smrg20190207: 2951.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 2961.299Smrg 2971.298Smartin20180924: 2981.298Smartin A newer OpenSSL version has been imported. If you are doing 2991.298Smartin update builds, make sure to remove all old obj dirs, like: 3001.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 3011.298Smartin 3021.297Sjoerg20180717: 3031.297Sjoerg On aarch64 int64_t and related types have changed from long long 3041.297Sjoerg to long. This requires recompiling all C++ binaries. 3051.297Sjoerg 3061.296Smartin20180713: 3071.296Smartin On amd64 and i386 static binaries are now build position 3081.296Smartin independend. This requires recompilation of all object 3091.296Smartin files used to create the crunched /rescue binary. 3101.296Smartin Clean the rescue directory in your obj directory before 3111.296Smartin doing an update build, otherwise linking will fail. 3121.296Smartin 3131.293Sjakllsch20180414: 3141.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 3151.293Sjakllsch removal of tools/binutils objects directory may be required 3161.293Sjakllsch to fix tools build failure. 3171.293Sjakllsch 3181.292Smrg20180311: 3191.292Smrg bdftopcf was updated and may need cleaning in the 3201.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 3211.292Smrg link errors. 3221.292Smrg 3231.291Smrg20180212: 3241.291Smrg between OpenSSL and GCC updates, many things may fail to build. 3251.291Smrg any failure that looks like GCC or openssl is best handled by 3261.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 3271.291Smrg is recommended if build failures occur. 3281.291Smrg 3291.288Smartin20171225: 3301.288Smartin removal of the vadvise syscall requires manual removal of all 3311.288Smartin associated files from the libc build object directory (including 3321.289Schristos the .depend files) - a command like: 3331.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 3341.289Schristos For architectures that support multiple "compat" binary targets, 3351.289Schristos you'll need to cleanup both the regular libc directory and the 3361.290Smartin compat ones (the above command will do that). 3371.288Smartin 3381.287Skre20171010: 3391.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 3401.287Skre means that its objdir (or *.d and .depend at least) might need 3411.287Skre to be manually removed - or a build done once without -u. 3421.287Skre 3431.286Smrg20170822: 3441.286Smrg a new version of GMP has been imported and probably 3451.286Smrg will break parts of builds related to themselves or GCC, both 3461.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3471.286Smrg and MPC objdirs or build once without -u. 3481.286Smrg 3491.285Smrg20170816: 3501.285Smrg a new version of MPFR and MPC have been imported and probably 3511.285Smrg will break parts of builds related to themselves or GCC, both 3521.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3531.285Smrg and MPC objdirs or build once without -u. 3541.285Smrg 3551.284Smartin20170402: 3561.284Smartin a new version of dhcpcd has been imported, which does not support 3571.284Smartin update builds from the previous version. Remove your 3581.284Smartin external/bsd/dhcpcd object dir or build once without -u. 3591.284Smartin 3601.281Sroy20170211: 3611.281Sroy a new terminfo database has been imported. 3621.281Sroy The structure of it has changed slightly from prior versions and 3631.281Sroy an updated tic tool is required. 3641.281Sroy If you build.sh, don't use -u 3651.281Sroy 3661.280Skre20170207: 3671.278Skre various arch dependent libc/exect.S files were removed 3681.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 3691.279Skre if it exists) or do a clean build. 3701.279Skre (This is a bug in the make system, it should be corrected without 3711.279Skre human intervention, but isn't.) 3721.278Skre 3731.277Smartin20170104: 3741.277Smartin xinput build options have changed. 3751.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 3761.277Smartin if you build.sh -u 3771.277Smartin 3781.276Smartin20170103: 3791.276Smartin a new version of flex has been imported. 3801.276Smartin Remove the file from obj (external/bsd/flex) 3811.276Smartin if you build.sh -u 3821.276Smartin 3831.275Sspz20161014: 3841.275Sspz a new version of OpenSSL has been imported. 3851.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 3861.275Sspz if you build.sh -u 3871.275Sspz 3881.274Smartin20161009: 3891.274Smartin a new version of dhcpcd has been imported with slightly changed 3901.274Smartin build infrastructure. When doing a build.sh -u this requires 3911.274Smartin pruning the external/bsd/dhcpcd objdir. 3921.274Smartin 3931.273Smrg20160914: 3941.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 3951.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 3961.273Smrg and a clean objdir. 3971.273Smrg 3981.272Sdholland20160527: 3991.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 4001.272Sdholland been enabled. (see the amd64 entry two down for further info) 4011.272Sdholland 4021.270Schristos20160418: 4031.270Schristos libedit needs manual removal of all autogenerated files since 4041.271Schristos some of them are not autogenerated anymore. Remember that there 4051.271Schristos might be two copies of libedit if your platform builds "compat". 4061.270Schristos 4071.268Sriastrad20160410: 4081.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 4091.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 4101.268Sriastrad executables, means all code, including executables and not just 4111.268Sriastrad shared libraries, is position-independent and hence able to be 4121.268Sriastrad relocated by ASLR, address space layout randomization. 4131.268Sriastrad 4141.268Sriastrad The change was made in Makefile variables for compiler and 4151.268Sriastrad linker flags, for which make(1) does not record dependencies, 4161.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 4171.268Sriastrad 4181.268Sriastrad Partial rebuilds with some modified source files will likely 4191.268Sriastrad fail when linking executables, since the linker refuses to mix 4201.268Sriastrad position-independent code with position-dependent code in 4211.268Sriastrad position-independent executables: 4221.268Sriastrad 4231.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 4241.268Sriastrad 4251.267Smrg20160401: 4261.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 4271.269Sdholland Some people have found that cleandir is not sufficient, so if 4281.269Sdholland in doubt delete the entire object directory tree for gcc. 4291.267Smrg 4301.266Saymeric20160306: 4311.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 4321.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 4331.265Saymeric non-NetBSD hosts if linked with stale object files produced 4341.265Saymeric while they included a non-NetBSD regex.h. 4351.265Saymeric In any case, you should "make cleandir" at least these tools 4361.265Saymeric before updating your toolchain. 4371.265Saymeric 4381.264Smartin20160125: 4391.264Smartin Dtrace has been enabled by default on some architectures. 4401.264Smartin When doing an update build, make sure to clean the etc/mtree 4411.264Smartin object directory before starting the build - otherwise the 4421.264Smartin needed directories in destdir will not be created. 4431.264Smartin An easy way to do this is: 4441.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 4451.264Smartin 4461.263Sdholland20150818: 4471.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 4481.263Sdholland again. 4491.263Sdholland 4501.262Schristos20150413: 4511.262Schristos New acpica requires "make cleandir" and reinstalling yacc 4521.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 4531.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 4541.262Schristos 4551.261Smartin20150404: 4561.261Smartin Lint changes require a full rebuild of the tool, so make 4571.261Smartin sure to build without -u option to build.sh, or manually 4581.261Smartin do a make cleandir in src/tools/lint1 and 4591.261Smartin src/usr.bin/xlint. 4601.261Smartin 4611.260Sskrll20150310: 4621.260Sskrll Improvements to openssl for arm mean that update builds of 4631.260Sskrll the openssl libraries will fail. A make cleandir in 4641.260Sskrll external/bsd/openssl/lib is needed 4651.260Sskrll 4661.258Smartin20141026: 4671.259Smsaitoh A mishap during the import of pppd may cause your corruption 4681.258Smartin in your cvs directory if you happened to do a cvs update 4691.258Smartin during a short period of time. To fix, just remove the 4701.258Smartin directory src/external/bsd/ppp/dist/pppd completely 4711.258Smartin and let cvs restore it on next update. 4721.258Smartin 4731.256Sapb20140721: 4741.256Sapb The src/external/mit/lua/src directory was accidentally created 4751.256Sapb and then deleted in the CVS repository. If you get errors like 4761.256Sapb 4771.256Sapb cvs [update aborted]: cannot open directory 4781.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 4791.256Sapb 4801.256Sapb then delete your local copy of that directory tree and try again. 4811.256Sapb 4821.255Sjoerg20140530: 4831.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 4841.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 4851.255Sjoerg 4861.251Smartin20140131: 4871.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 4881.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 4891.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 4901.251Smartin 4911.250Schristos20131227: 4921.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 4931.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 4941.250Schristos mode7 in your config file. Make sure you put the necessary restrict 4951.250Schristos statements to avoid being exposed. 4961.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 4971.250Schristos to make clean in libc 4981.250Schristos 4991.249Smrg20131129: 5001.249Smrg The GMP sources were updated, and builds will likely fail without 5011.249Smrg cleaning their build trees for both tools and in-tree, like below. 5021.249Smrg 5031.248Smrg20131128: 5041.248Smrg The MPC and MPFR sources were updated, and builds may require their 5051.248Smrg tools and in-tree directories cleaned for successful updates. 5061.248Smrg 5071.246Smartin20130605: 5081.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 5091.247Sspz to IPSEC (and the older IPSEC version removed). 5101.247Sspz 5111.247Sspz20130605: 5121.320Sandvar Previous freetype installations erroneously installed private 5131.246Smartin header files. If you are building against a non-empty $DESTDIR, 5141.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 5151.246Smartin 5161.245Smrg20130531: 5171.245Smrg The xdm update may cause build failure due to xdm.man being 5181.245Smrg in the obj tree. Make sure to ensure any like this: 5191.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 5201.245Smrg is fixed by deleting the xdm.man in the obj tree. 5211.245Smrg 5221.244Smrg20130530: 5231.244Smrg Updates of many xsrc packages will leave old .pc files around. 5241.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 5251.244Smrg 5261.242Schristos20130301: 5271.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 5281.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 5291.242Schristos 5301.238Sdholland20120726: 5311.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 5321.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 5331.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 5341.241Swiz some cases may succeed and install broken OpenSSL libraries that 5351.240Sdholland cause third-party software to link incorrectly and/or crash. 5361.238Sdholland 5371.237Swiz20120507: 5381.241Swiz The database schema for makemandb was changed. You will 5391.237Swiz need to update the database using 'makemandb -f' or wait 5401.237Swiz for the next weekly run to fix it. 5411.237Swiz 5421.236Sbsh20120319: 5431.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 5441.236Sbsh size of db_symtab automatically. You need to update dbsym in 5451.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 5461.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 5471.236Sbsh mk.conf. 5481.236Sbsh 5491.235Sjoerg20120216: 5501.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 5511.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 5521.239Sdholland and 20120216, daily and weekly could have created an unreadable 5531.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 5541.235Sjoerg the next run of weekly will fix it. 5551.233Sjoerg 5561.232Schristos20111227: 5571.232Schristos If you built between 20111225 and 20111227 you need to remove 5581.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 5591.232Schristos bump has been reverted. 5601.232Schristos 5611.231Stls20111125: 5621.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 5631.231Stls means it should no longer be explicitly listed in kernel 5641.231Stls configuration files. The line "pseudo-device rnd" should be 5651.231Stls removed from any custom kernel config files users may have. 5661.231Stls 5671.230Stls20111119: 5681.230Stls A problem with the datastructures used by the rndctl(8) 5691.230Stls utility (pointers in datastructures in an array, making 32->64 5701.230Stls bit compatibility very painful) has been fixed in a 5711.230Stls non-backwards-compatible way. If you replace your kernel, 5721.230Stls replace your rndctl executable too. 5731.241Swiz 5741.229Sjym20111001: 5751.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 5761.229Sjym changed and their new version is not backward compatible with the old 5771.241Swiz one. So ensure that all consumers of these functions (currently: 5781.229Sjym quota2 code and its tests) are updated together with the new lib. 5791.229Sjym 5801.228Smrg20110817: 5811.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 5821.228Smrg DESTDIR for them should be deleted before updating. 5831.228Smrg 5841.227Sriastrad20110806: 5851.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 5861.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 5871.227Sriastrad 5881.226Smrg20110805: 5891.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 5901.226Smrg the tree to be cleaned. Best to delete both objdir and 5911.226Smrg DESTDIR before running this update. So far, only the 5921.226Smrg sparc64, mips and powerpc platforms have changed. 5931.226Smrg 5941.225Smatt20110803: 5951.241Swiz The layout of external/public-domain/xz has changed. To do an 5961.225Smatt update build you will have to remove the contents of the OBJDIR 5971.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 5981.225Smatt is now a directory. 5991.225Smatt 6001.223Sjoerg20110410: 6011.241Swiz The configuration of src/tools/gcc has changed. To do an 6021.224Sdholland update build you have to clean both tools/binutils and 6031.224Sdholland tools/gcc by hand. 6041.223Sjoerg 6051.222Splunky20110328: 6061.222Splunky Building the Xorg binary was moved into a subdirectory to fix 6071.241Swiz ordering issues with "make all". It may be necessary to remove 6081.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 6091.222Splunky if your update build fails, as the "Xorg" entry there is now a 6101.222Splunky directory. 6111.222Splunky 6121.220Sjoerg20110121: 6131.221Slukem Assembler files no longer use -traditional-cpp. This can break 6141.220Sjoerg the build of individual parts of the tree. This is handled 6151.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 6161.220Sjoerg and re-run config(1) for any kernel configurations as needed. 6171.218Sjoerg 6181.217Sjruoho20101217: 6191.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 6201.241Swiz by default. It may be necessary to manually update passwd(5) and 6211.217Sjruoho group(5) in order to make the program work with existing setups. 6221.217Sjruoho 6231.216Schristos20101125: 6241.327Sandvar The latest changes to setenv(3) disallow setting environment 6251.241Swiz variables with names that contain '='. Revision 1.18 of env.c 6261.241Swiz assumed that this was allowed. Installing a new libc with an 6271.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 6281.216Schristos break which affects the autoconf tests for dependency finding, 6291.216Schristos so building gcc will end up printing: 6301.216Schristos checking dependency style of gcc... none 6311.216Schristos configure: error: no usable dependency style found 6321.216Schristos Fix it by rebuilding and re-installing env. 6331.138Slukem 6341.215Smrg20101119: 6351.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 6361.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 6371.215Smrg have any build problems with xsrc, or problems with mismatched 6381.215Smrg versions between xorg-server and drivers. 6391.215Smrg 6401.213Sjmmv20100604: 6411.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 6421.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 6431.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 6441.213Sjmmv trees by hand. 6451.213Sjmmv 6461.211Stnozaki20100522: 6471.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 6481.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 6491.212Smrg build problems with xsrc. 6501.212Smrg 6511.212Smrg20100522: 6521.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 6531.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 6541.211Stnozaki 6551.210Schristos20100520: 6561.241Swiz The location of the xkb compiled descriptions has changed. Please 6571.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 6581.210Schristos 6591.209Snjoly20100222: 6601.209Snjoly The shared objects file extension has been changed from .so to 6611.209Snjoly .pico, in order to avoid conflicts with shared libraries names 6621.209Snjoly libXX.so. All now stale regular .so files can be removed from 6631.209Snjoly your object directories. 6641.209Snjoly 6651.208Sroy20100204: 6661.208Sroy The termcap database has been removed from the sources, 6671.208Sroy but has not been marked obsolete so it is not removed 6681.208Sroy from the system when upgrading. 6691.208Sroy As such, you will need to remove them from your object 6701.208Sroy and destination directories. 6711.208Sroy 6721.203Sdyoung20091101: 6731.205Sdholland After updating, it may be necessary to make the 'cleandir' 6741.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 6751.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 6761.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 6771.203Sdyoung 6781.202Smrg20091001: 6791.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 6801.206Sdholland before building a kernel, or the build fails on cpufunc.S. 6811.206Sdholland 6821.206Sdholland20091001: 6831.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 6841.202Smrg symlink, failing the build. Delete the link, and the subdir 6851.202Smrg it is in, and retry your build. 6861.202Smrg 6871.201Sdsl20090718: 6881.201Sdsl libc build changed so that strchr() provides the extra entry 6891.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 6901.201Sdsl may fail because the archive contains the unwanted index.o. 6911.201Sdsl (Similarly for strrchr() and rindex().) 6921.201Sdsl 6931.198Smrg20090709: 6941.198Smrg Native Xorg was upgraded again. Builds will probably fail again 6951.198Smrg without a clean objdir, at least for src/external/mit/xorg. 6961.198Smrg 6971.197Smrg20090616: 6981.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 6991.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 7001.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 7011.197Smrg subdirectory has been changed into a file, and this needs to 7021.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 7031.197Smrg 7041.195Sperry20090501: 7051.195Sperry Several new functions were added to string.h/libc, and this 7061.195Sperry can cause autoconf problems during the tool build for people 7071.241Swiz who fail to clean out their tools objects properly. If you 7081.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 7091.195Sperry failure during the tool build, clean out all your tools 7101.195Sperry objects and start again. 7111.195Sperry 7121.194Smrg20090325: 7131.194Smrg The i386 port was switched to i486 default toolchain. This requires 7141.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 7151.194Smrg 7161.192Sskrll20090126: 7171.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 7181.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 7191.207Smbalmer to avoid using the old assembly stub. 7201.192Sskrll 7211.191Sjoerg20090202: 7221.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 7231.320Sandvar detection. It is recommended to rebuild the cache with 7241.191Sjoerg ``pkg_admin rebuild''. 7251.191Sjoerg 7261.184Schristos20090110: 7271.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 7281.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 7291.188Schristos This is needed even in the MODULAR kernel because there is 7301.188Schristos conditionally compiled code in rtsock.c. 7311.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 7321.184Schristos before installing. 7331.184Schristos 3. If you don't use build.sh and you build directly to root, and 7341.241Swiz your build breaks in the middle, don't despair. Make sure headers 7351.184Schristos are installed properly, and start building libraries first libc 7361.184Schristos and libutil, install them and then continue building all the 7371.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 7381.184Schristos the new libraries are installed, you can restart the build. 7391.184Schristos 4. If you compile packages and you notice link time warnings, 7401.189Shubertf rebuild the required packages to update their shared libraries. 7411.189Shubertf Any package you rebuild will require rebuilding all the packages 7421.189Shubertf that depend on it. 7431.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 7441.186Schristos will be upgraded and it will not be backwards compatible. 7451.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 7461.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 7471.241Swiz for utmp. You are better off removing the old files after 7481.190Sapb upgrading. The automated clearing of /var/run during 7491.190Sapb boot, and the automated rotating of files in /var/log by 7501.190Sapb newsyslog(8), may mean that you do not have to remove the 7511.190Sapb files manually. 7521.190Sapb 7. The optional accounting file (/var/account/acct, see 7531.190Sapb accton(8)) has not been versioned, and will need to be 7541.190Sapb removed. The automatic rotation of the accounting file by 7551.190Sapb /etc/daily limits the bad consequences of failure to remove 7561.190Sapb the file. 7571.196Sdholland 8. Application software that writes time_t to binary files on 7581.241Swiz disk will break or need attention. Most notably: if you are 7591.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 7601.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 7611.185Sjmcneill 7621.183Spgoyette20081219: 7631.183Spgoyette config(1) has been updated, and one of the files it creates - 7641.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 7651.183Spgoyette (done automatically by build.sh) and then you need to rerun 7661.183Spgoyette config on all kernel configuration files before rebuilding those 7671.183Spgoyette kernels. 7681.183Spgoyette 7691.181Scube20081205: 7701.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 7711.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 7721.181Scube set and will appear as extra files for MKX11=no update builds. 7731.178Slukem 7741.179Stsutsui20081122: 7751.182Stsutsui On i386, various kernel options(4) in GENERIC including 7761.180Swiz file systems have been disabled and moved into kernel modules. 7771.180Swiz Before trying a new GENERIC kernel, you have to prepare the 7781.179Stsutsui following files as well as a new GENERIC kernel: 7791.179Stsutsui 7801.179Stsutsui - build and install kernel modules from src/sys/modules 7811.179Stsutsui 7821.179Stsutsui - install the latest bootloader, which will load a module 7831.180Swiz for the file system from which the kernel is loaded automatically 7841.179Stsutsui 7851.180Swiz If you have to load your kernel from a file system which is not of 7861.180Swiz the same type as the root file system, you have to load the necessary 7871.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 7881.179Stsutsui 7891.178Slukem20080827: 7901.178Slukem If you built and installed a libc from sources between 7911.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 7921.178Slukem which results in false errors reported by lint(1). 7931.178Slukem Since this breaks the libc build itself, manual help is 7941.180Swiz needed -- lint must be disabled temporarily, e.g.: 7951.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 7961.178Slukem 7971.177Schristos20080813: 7981.177Schristos MKDEBUG build was broken because the .depend files did not know 7991.241Swiz about .go files. You need to remove all .depend files and rebuild. 8001.177Schristos 8011.200Sdholland20080802: 8021.200Sdholland A regression in binary compatibility for pthread_mutex_t has 8031.241Swiz been fixed. Unfortunately, the price is breaking compatibility 8041.200Sdholland for -current. 8051.200Sdholland 8061.200Sdholland Threaded programs (using libpthread) and C++ programs (using 8071.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 8081.200Sdholland be recompiled. 8091.200Sdholland 8101.200Sdholland One way to find affected pkgsrc packages: 8111.200Sdholland 8121.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 8131.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 8141.200Sdholland 8151.175Ssimonb20080731: 8161.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 8171.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 8181.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 8191.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 8201.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 8211.176Ssimonb also requires the super block to be in the UFS2 format. You 8221.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 8231.175Ssimonb 8241.174Slukem20080721: 8251.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 8261.174Slukem isn't defined. 8271.174Slukem 8281.173Sfreza20080531: 8291.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 8301.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 8311.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 8321.241Swiz won't work correctly. The following sequence of commands: 8331.173Sfreza 8341.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 8351.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 8361.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 8371.173Sfreza 8381.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 8391.173Sfreza 8401.172Slukem20080503: 8411.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 8421.172Slukem 8431.171She20080521: 8441.171She For a while, unprivileged UPDATE builds would fail to 8451.171She succeed at the checkflist stage, complaining that 8461.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 8471.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 8481.171She If you already hit this problem, update the .mk file, 8491.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 8501.171She 8511.174Slukem20080303: 8521.174Slukem Linker warnings are now fatal if $WARNS>0. 8531.174Slukem 8541.170Schristos20080126: 8551.170Schristos The posix_fadvise system call has been changed from an assembly 8561.241Swiz stub, to a c file that calls an assembly stub. You need to 8571.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 8581.170Schristos avoid using the old assembly stub. 8591.170Schristos 8601.168Sjoerg20071209: 8611.241Swiz The acpiec(4) driver has been split into two attachments. If you 8621.168Sjoerg get ACPI errors before the attachment, please update your kernel 8631.169Swiz configuration file appropriately or see GENERIC for more details. 8641.168Sjoerg 8651.166Sxtraeme20071115: 8661.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 8671.166Sxtraeme argument specified in the kernel configuration file is not valid 8681.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 8691.241Swiz rather than the EC address port. Please update your kernel 8701.167Swiz configuration file appropriately or see GENERIC for more details. 8711.166Sxtraeme 8721.165Sjmmv20071028: 8731.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 8741.165Sjmmv You need to update any custom kernel configuration file you have 8751.165Sjmmv to remove any references to pccons (which includes removing the 8761.165Sjmmv now useless XSERVER option) and replace them with the correct 8771.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 8781.165Sjmmv for more details. 8791.165Sjmmv 8801.164Sgdt20070913: 8811.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 8821.164Sgdt enumerate interfaces was fixed. The bug began to cause 8831.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 8841.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 8851.164Sgdt could not enumerate interfaces. (These are noted because 8861.164Sgdt normal kernel/userspace version matching hygiene is not 8871.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 8881.164Sgdt and userland are from after 20070913. 8891.164Sgdt 8901.163Sjoerg20070703: 8911.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 8921.199Sdholland calls the target-specific strip program, and the logic to pass 8931.199Sdholland down STRIP from make has been removed. This requires a 8941.199Sdholland re-installation of tools. 8951.163Sjoerg 8961.161Sdsl20070422: 8971.161Sdsl The way OS emulations lookup filenames inside the emulation root 8981.161Sdsl has been changed. Rather than modify the pathname (and copy back 8991.161Sdsl to userspace) namei() and lookup() directly check the emulation 9001.241Swiz root. One side effect is that absolute symlinks inside the emulated 9011.167Swiz root file system will be relative to that file system - unless they 9021.161Sdsl start /../ this is useful when the emulated root is a real install 9031.161Sdsl that has such links. 9041.161Sdsl This might affect symlinks that have been added to reference outside 9051.161Sdsl the emulated root. 9061.161Sdsl 9071.160Sjmcneill20070412: 9081.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 9091.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 9101.160Sjmcneill example. 9111.160Sjmcneill 9121.159Sgdt20070319: 9131.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 9141.159Sgdt on many platforms due to incorrect flags settings. If you 9151.159Sgdt updated and built after about 20070315, do "nbmake-$arch 9161.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 9171.159Sgdt rebuild of object files that might have been built 9181.159Sgdt incorrectly, and ensure that you have at least 9191.159Sgdt src/lib/libc/Makefile 1.130. 9201.159Sgdt 9211.241Swiz20070210: 9221.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 9231.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 9241.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 9251.158Sdbj will allow dependencies on those files to get get rebuilt 9261.158Sdbj 9271.157Sapb20070209: 9281.157Sapb The threading model was changed when the newlock2 branch 9291.157Sapb was merged to NetBSD-current. If you boot with a new 9301.157Sapb kernel (version 4.99.10), then you also need a new pthread 9311.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 9321.157Sapb an old kernel, then you need the old pthread library 9331.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 9341.157Sapb the pthread library in sync, old threaded applications should 9351.157Sapb continue to work with an old or new kernel. Note that named(8) 9361.157Sapb is the only threaded application in the base system. 9371.157Sapb 9381.154She20061214: 9391.154She Following the move of string_to_flags() and flags_to_string() 9401.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 9411.154She will need to do a "make cleandir" in 9421.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 9431.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 9441.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 9451.156She as the installation images in distrib/ 9461.154She in order to excise stale references to the old stat_flags.h header 9471.154She file in the ls sources -- stat_flags.h has been removed. 9481.154She 9491.152Schristos20061108: 9501.152Schristos The configure script used in the src/tools/gcc compiler has been 9511.152Schristos changed to indicate that our libc has ssp support built-in and 9521.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 9531.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 9541.152Schristos 9551.151Srpaulo20061009: 9561.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 9571.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 9581.151Srpaulo 9591.150Sbjh2120060814: 9601.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 9611.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 9621.150Sbjh21 kernel configuration for an example. X servers from the last 9631.150Sbjh21 few years should cope. 9641.150Sbjh21 9651.149Schristos20060703: 9661.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 9671.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 9681.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 9691.149Schristos 9701.148Sdogcow20060627: 9711.148Sdogcow socket(2) has changed, and its system call has been versioned. 9721.148Sdogcow For userlands with the old version of socket(2), make sure that 9731.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 9741.148Sdogcow errors will result. 9751.148Sdogcow 9761.1SabsHints for a more successful build: 9771.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9781.123Sjmc Use build.sh, but do not use its "expert mode": 9791.132Sjmmv This will automatically build the tools in the 9801.123Sjmc correct order, and it will keep the tools and the 9811.123Sjmc new build products from interfering with the running 9821.123Sjmc system. This will allow you to ignore most of the 9831.123Sjmc other advice in this file. 9841.2Smrg Build a new kernel first: 9851.2Smrg This makes sure that any new system calls or features 9861.2Smrg expected by the new userland will be present. This 9871.2Smrg helps to avoid critical errors when upgrading. 9881.1Sabs Use object directories: 9891.1Sabs This helps to keep stale object 9901.1Sabs files from polluting the build if a Makefile "forgets" 9911.1Sabs about one. It also makes it easier to clean up after 9921.1Sabs a build. It's also necessary if you want to use the 9931.1Sabs same source tree for multiple machines. 9941.123Sjmc To use object directories with build.sh: 9951.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 9961.123Sjmc To use object directories without using build.sh: 9971.1Sabs a) cd /usr/src ; make cleandir 9981.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 9991.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 10001.1Sabs d) cd /usr/src ; make build 10011.2Smrg Note that running "make obj" in a directory will create 10021.2Smrg in obj.$MACHINE directory. 10031.1Sabs Build to a DESTDIR: 10041.123Sjmc This helps to keep old installed files (especially libraries) 10051.123Sjmc from interfering with the new build. 10061.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 10071.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 10081.123Sjmc environment variable before running make build. It should be 10091.123Sjmc set to the pathname of an initially empty directory. 10101.123Sjmc Problems: if you do not use build.sh, you might need to 10111.123Sjmc update critical utilities without using DESTDIR since 10121.123Sjmc nothing is executed from what is installed in DESTDIR. 10131.123Sjmc (See critical utils, below.) 10141.1Sabs Build often: 10151.1Sabs This keeps critical utilities current enough to not choke 10161.1Sabs on any other part of the source tree that depends on up to 10171.123Sjmc date functionality. If you use build.sh, you should not have 10181.123Sjmc this problem. 10191.241Swiz 10201.1SabsWhat to do if things don't work: 10211.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10221.230StlsWhen things don't work there are usually a few things that commonly 10231.1Sabsshould be done. 10241.1Sabs 1) make includes 10251.1Sabs This should be done automatically by make build. 10261.1Sabs 2) cd share/mk && make install 10271.1Sabs Again, automatically done by make build. 10281.1Sabs 10291.1SabsFailsafe rebuild of a small part of the tree: 10301.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10311.1SabsTo make sure you rebuild something correctly you want to do 10321.1Sabssomething like the following: 10331.1Sabs 1) Make sure the includes and .mk files are up to date. 10341.1Sabs 2) Make sure any program used to build the particular 10351.1Sabs utility is up to date. (yacc, lex, etc...) 10361.1Sabs 3) cd ...path/to/util... 10371.1Sabs make cleandir 10381.1Sabs rm ...all obj directories... 10391.1Sabs make cleandir # yes, again 10401.1Sabs make obj 10411.1Sabs make depend && make 10421.1Sabs 10431.1SabsFailsafe rebuild of the entire tree: 10441.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10451.1SabsIf you really want to make sure the source tree is clean and 10461.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 10471.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 10481.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 10491.1Sabs 10501.1Sabs---cut here--- 10511.1Sabs#!/bin/sh 10521.1Sabs. /etc/mk.conf 10531.1Sabs 10541.58Slukemif [ -z $NETBSDSRCDIR ] ; then 10551.58Slukem NETBSDSRCDIR=/usr/src 10561.1Sabsfi 10571.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 10581.1Sabs echo Unable to find sources 10591.1Sabs exit 1 10601.1Sabsfi 10611.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 10621.1Sabs 10631.1Sabsif [ -z $BSDOBJDIR ] ; then 10641.1Sabs BSDOBJDIR=/usr/obj 10651.1Sabsfi 10661.1Sabsif [ -d $BSDOBJDIR ] ; then 10671.1Sabs rm -rf $BSDOBJDIR 10681.1Sabsfi 10691.1Sabs 10701.58Slukemcd $NETBSDSRCDIR && make cleandir 10711.1Sabs 10721.1Sabs---cut here--- 10731.1Sabs 10741.1SabsCritical utilities: 10751.1Sabs^^^^^^^^^^^^^^^^^^^ 10761.3Sitojun usr.bin/compile_et 10771.1Sabs usr.bin/make 10781.1Sabs usr.bin/yacc 10791.1Sabs usr.bin/lex 10801.11Slukem usr.bin/xlint 10811.142Sdrochner usr.bin/config 10821.1Sabs 10831.34SsimonbOther problems and possible solutions: 10841.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10851.1SabsSymptom:Complaints involving a Makefile. 10861.17SerhFix: Rebuild usr.bin/make: 10871.17Serh cd usr.bin/make && make && make install 10881.111Ssimonb Or, a failsafe method if that doesn't work: 10891.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 10901.17Serh 10911.1SabsFix: Make sure .mk files are up to date. 10921.1Sabs cd share/mk && make install 10931.2Smrg 10941.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 10951.142SdrochnerFix: Rebuild usr.bin/config 10961.1Sabs 10971.1SabsSymptom: 10981.1SabsFix: Rebuild usr.bin/yacc 10991.1Sabs 11001.1SabsSymptom: 11011.1SabsFix: Rebuild usr.bin/lex 11021.1Sabs 11031.1SabsSymptom: 11041.1SabsFix: rm /usr/lib/libbfd.a 11051.4Sitojun 11061.4SitojunSymptom:Obsolete intermediate files are used during compilation 11071.4SitojunFix: Try the following sequence of commands in the directory in question. 11081.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 11091.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 11101.4Sitojun may remain. The command tries to clean everything up) 11111.5Swiz 11121.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 11131.207Smbalmer pointer type 11141.5SwizFix: Rebuild and install usr.bin/menuc 11151.12Sitojun 11161.12SitojunSymptom:mklocale not found during build in share/locale/ctype 11171.12SitojunFix: Build and install usr.bin/mklocale 11181.13Sdogcow 11191.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 11201.13SdogcowFix: Rebuild and install lib/libc 11211.13Sdogcow 11221.142SdrochnerSymptom:usr.bin/config fails to build. 11231.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 11241.13Sdogcow 11251.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 11261.19ScgdFix: Rebuild and install lib/libc 11271.24Sabs 11281.24SabsSymptom:lint does not understand the '-X' option 11291.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 11301.223Sjoerg 11311.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 11321.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 11331.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 11341.257Sapb 11351.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 11361.257Sapb No such file or directory. 11371.257SapbCause: If a directory is created by mistake, then it is sometimes 11381.257Sapb deleted from the CVS repository using administrative commands 11391.257Sapb that bypass the normal cvs access controls. If your cvs working tree 11401.257Sapb contains references to a directory that has been deleted on the 11411.257Sapb server in this way, then "cvs update" reports this error. 11421.257SapbFix: Recursively delete the affected directory from your working tree 11431.257Sapb and try the update again. 1144