UPDATING revision 1.346
11.346Sriastrad$NetBSD: UPDATING,v 1.346 2024/04/11 02:15:39 riastradh Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.257SapbSections are marked with "^^^^^". After the section on "Recent changes" 151.257Sapbare several sections containing more general information. 161.257Sapb 171.123SjmcSee also: BUILDING, build.sh, Makefile. 181.1Sabs 191.1SabsRecent changes: 201.1Sabs^^^^^^^^^^^^^^^ 211.230Stls 221.346Sriastrad20240410: 231.346Sriastrad Update builds may require manually deleting 241.346Sriastrad $DESTDIR/var/run/named (and, potentially, 251.346Sriastrad $DESTDIR/var/run/lwresd) in order to avoid checkflist failure. 261.346Sriastrad 271.343Sriastrad20230828: 281.343Sriastrad If: 291.343Sriastrad - you updated to current and ran postinstall between 20230826 301.343Sriastrad and 20230828 inclusive, and 311.343Sriastrad - you are not using anything outside the base system to 321.343Sriastrad populate /etc/openssl/certs (e.g., manually adding 331.343Sriastrad certificates or using ca-certificates or mozilla-rootcerts or 341.343Sriastrad mozilla-rootcerts-openssl from pkgsrc), 351.343Sriastrad delete /etc/openssl/certs and rerun postinstall or just 361.343Sriastrad `certctl rehash'. 371.343Sriastrad 381.343Sriastrad Otherwise, certctl(8) will think someone else has left 391.343Sriastrad /etc/openssl/certs in the way and will avoid clobbering it on 401.343Sriastrad upgrade from older NetBSD. 411.343Sriastrad 421.341Slukem20230718: 431.341Slukem build.sh will use mk.conf in the same directory as build.sh instead 441.341Slukem of /etc/mk.conf, unless MAKECONF is already defined in the environment. 451.341Slukem 461.342Smartin20230714: 471.342Smartin Import of gcc 10.5 requires a clean build of at least tools/gcc 481.342Smartin and external/gpl3/gcc* object directories. An update build 491.342Smartin without cleaning will result in obscure failures in rare corner 501.342Smartin cases. 511.342Smartin 521.339Smartin20230604: 531.339Smartin Building native kernels with the installed make(1) instead of 541.339Smartin the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland 551.339Smartin has not been updated. Note that this is an unsupported build 561.339Smartin configuration (but usually works if userland is -current enough). 571.338Slukem 581.338Slukem20230523: 591.338Slukem ctfmerge was fixed as macOS host tool. This may require a clean tools 601.338Slukem rebuild to detect the update to tools/compat/configure. 611.338Slukem 621.340Smartin20230515: 631.340Smartin New openssl build requires removal of the crypto/external/bsd/openssl 641.345Sandvar and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierarchy. 651.340Smartin Otherwise test results may be wrong due to wrong "golden" output 661.340Smartin files being installed. 671.340Smartin 681.337Smrg20230322: 691.337Smrg Fixes for moved /lib/libisns* mean that builds will complain about 701.337Smrg ./usr/lib/libisns* being missing until src/lib/libisns is forced 711.337Smrg to (re)install the files, including the symlinks. The simplest 721.337Smrg way is to clean this subdir before building. 731.337Smrg 741.336Smartin20230112: 751.336Smartin New binutils require an updated ld.elf_so. If you are doing 761.336Smartin (unsupported) in-place self builds (with the -E flag to build.sh), 771.336Smartin make sure to have installed latest ld.elf_so before you rebuild 781.336Smartin userland. 791.336Smartin 801.335Schs20221116: 811.335Schs The addition to NetBSD's version of UFS2 of support for extended 821.335Schs attributes broke backward compatibility with previous releases 831.335Schs of NetBSD, so UFS2 has been restored to being compatible with 841.335Schs previous NetBSD releases by disabling extended attributes. 851.335Schs (Note that ACLs are implemented as extended attributes, so 861.335Schs this changes disables ACLs as well.) 871.335Schs 881.335Schs Support for UFS2 with extended attributes is now available in a new 891.335Schs UFS variant called UFS2ea. If you have created extended attributes 901.335Schs in an original UFS2 file system then "fsck -p" will now fail due to 911.335Schs the unexpected presence of extended attributes and "fsck -y" will 921.335Schs remove all extended attributes. If you wish to preserve extended 931.335Schs attributes rather than delete them, there is a utility to convert 941.335Schs a UFS2 file system to UFS2ea and leave extended attributes in place, 951.335Schs but this should be used with caution since it will preserve any 961.335Schs extended attributes that have been corrupted by the backward 971.335Schs incompatibility too. 981.335Schs 991.335Schs If you wish to use a UFS2ea file system as your root file system, 1001.335Schs then you will need to update your boot loader to a version that 1011.335Schs supports UFS2ea. 1021.335Schs 1031.335Schs For more information, see: 1041.335Schs https://wiki.netbsd.org/features/UFS2ea 1051.335Schs 1061.334Smrg20221111: 1071.334Smrg The new libdrm import worsened the conflict issues for the 1081.334Smrg kdump/ktruss ioctl, and i915 now conflicts with base, and has 1091.334Smrg been turned off. This will cause update build issues like: 1101.334Smrg 1111.334Smrg kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 1121.334Smrg undeclared here (not in a function); 1131.334Smrg did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 1141.334Smrg 1151.334Smrg You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 1161.334Smrg 1171.331Sriastrad20220921: 1181.331Sriastrad Since the kernel version was bumped to 9.99.100, the bootloader 1191.333Sriastrad must be updated on x86 or EFI boot platforms in order to load 1201.333Sriastrad modules from boot.cfg(5) or interactively at the bootloader 1211.333Sriastrad prompt. 1221.333Sriastrad 1231.333Sriastrad The kernel can still load modules at runtime, with modload(8) 1241.333Sriastrad or modules.conf(5), with no bootloader update. This will not 1251.333Sriastrad affect release branches because it only applies to patch 1261.333Sriastrad numbers >=100. 1271.333Sriastrad 1281.333Sriastrad On x86 (i386 or amd64) with BIOS boot, this requires copying a 1291.333Sriastrad new /usr/mdec/boot to /boot. You can build this in the destdir 1301.333Sriastrad by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 1311.333Sriastrad sys/arch/i386/stand. 1321.333Sriastrad 1331.333Sriastrad On platforms with EFI boot (including x86 with EFI boot), this 1341.333Sriastrad requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 1351.333Sriastrad directory on the EFI system partition. The boot*.efi file is: 1361.333Sriastrad 1371.333Sriastrad aarch64 bootaa64.efi 1381.333Sriastrad amd64 bootx64.efi 1391.333Sriastrad arm bootarm.efi (32-bit arm) 1401.333Sriastrad i386 bootx32.efi 1411.333Sriastrad 1421.333Sriastrad You can build this in the destdir by running 1431.333Sriastrad `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 1441.333Sriastrad sys/stand/efiboot/boot*. 1451.331Sriastrad 1461.330Slukem20220821: 1471.330Slukem Support for building extsrc/ has been deprecated. 1481.330Slukem EXTSRCSRCDIR and MKEXTSRC have been deprecated. 1491.330Slukem 1501.329Smrg20220714: 1511.329Smrg Updates to xorg-server and associated drivers may cause builds to 1521.329Smrg fail. Cleaning both DESTDIR and the xorg build tree may be needed. 1531.329Smrg 1541.328Smartin20220628: 1551.328Smartin Changes in the build of src/games/robots require a clean build 1561.328Smartin of that program. 1571.328Smartin 1581.324Smartin20211116: 1591.324Smartin Changes in the xorg build require clean obj dirs for external/mit/xorg 1601.325Smartin (or a full clean/non-update build). 1611.324Smartin 1621.323Snia20211112: 1631.323Snia Device tree sources were updated for evbarm. Some device nodes 1641.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 1651.323Snia 1661.322Smartin20211014: 1671.323Snia MKPIE default for aarch64 has changed, a clean build is required. 1681.322Smartin 1691.321Schristos20210917: 1701.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 1711.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 1721.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 1731.321Schristos 1741.319Smrg20210711: 1751.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 1761.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 1771.319Smrg 1781.318Smrg20210417: 1791.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 1801.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 1811.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 1821.318Smrg 1831.317Srillig20201230: 1841.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 1851.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 1861.317Srillig 1871.316Smrg20201016: 1881.316Smrg MIPS kernel modules have been disabled until they work. This will 1891.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 1901.316Smrg 1911.315Smrg20200925: 1921.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 1931.315Smrg in both the tools and external dirs. 1941.315Smrg 1951.314Smrg20200912: 1961.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 1971.314Smrg for several more, as will binutils 2.34. Clean as required. 1981.314Smrg 1991.313Smrg20200907: 2001.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 2011.313Smrg probably requires cleaning the tools/binutils. 2021.313Smrg 2031.311Smrg20200811: 2041.312Smrg GCC updates may require cleaning the objdir. This may occur 2051.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 2061.312Smrg GCC 9 upgrade. 2071.311Smrg 2081.309Schristos20200614: 2091.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 2101.332Sgutterid should handle the migration. 2111.309Schristos 2121.308Schristos20200601: 2131.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 2141.308Schristos created in the build directories and need cleaning. 2151.308Schristos 2161.307Smrg20200311: 2171.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 2181.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 2191.307Smrg 2201.306Schristos20191118: 2211.306Schristos More architectures were switched to gcc8: 2221.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 2231.306Schristos The same comments as in 20191022 apply. 2241.306Schristos 2251.305Smartin20191112: 2261.305Smartin The LLVM update requires a clean rebuild for all architectures using 2271.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 2281.305Smartin 2291.304Smartin20191022: 2301.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 2311.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 2321.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 2331.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 2341.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 2351.304Smartin daily builds and install that before doing the next in-place build. 2361.304Smartin 2371.303Smrg20191001: 2381.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 2391.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 2401.303Smrg directory, and also clean src/external/gpl3/gcc. 2411.303Smrg 2421.302Sriastrad20190903: 2431.306Schristos Files with names that coincide with existing files' names on 2441.302Sriastrad case-insensitive file systems were inadvertently committed, for 2451.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 2461.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 2471.302Sriastrad ran build.sh distribution or ran build.sh release, you must 2481.302Sriastrad manually delete the following files in your DESTDIR (which is 2491.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 2501.302Sriastrad them: 2511.302Sriastrad 2521.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 2531.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 2541.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 2551.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 2561.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 2571.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 2581.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 2591.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 2601.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 2611.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 2621.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 2631.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 2641.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 2651.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 2661.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 2671.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 2681.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 2691.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 2701.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 2711.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 2721.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 2731.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 2741.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 2751.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 2761.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 2771.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 2781.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 2791.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 2801.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 2811.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 2821.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 2831.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 2841.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 2851.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 2861.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 2871.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 2881.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 2891.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 2901.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 2911.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 2921.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 2931.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 2941.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 2951.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 2961.302Sriastrad /libdata/firmware/radeon/oland_me.bin 2971.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 2981.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 2991.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 3001.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 3011.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 3021.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 3031.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 3041.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 3051.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 3061.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 3071.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 3081.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 3091.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 3101.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 3111.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 3121.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 3131.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 3141.302Sriastrad /libdata/firmware/radeon/verde_me.bin 3151.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 3161.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 3171.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 3181.302Sriastrad 3191.302Sriastrad We will re-import these radeon firmware images another way 3201.302Sriastrad later. 3211.302Sriastrad 3221.301Smartin20190727: 3231.301Smartin The uefi bootloader has gained tftp support and needs a clean 3241.301Smartin build. If you do update builds, manually clean its object 3251.301Smartin directory by something like: 3261.301Smartin cd sys/arch/i386/stand/efiboot && make clean 3271.301Smartin 3281.300Smartin20190723: 3291.344Sgutterid The jemalloc allocator in libc is now built without extended 3301.300Smartin debugging (for performance reasons). In update builds make sure 3311.326Sandvar to rebuild it completely, by removing all affected object files, 3321.300Smartin including compat builds, something like: 3331.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 3341.300Smartin 3351.299Smrg20190207: 3361.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 3371.299Smrg 3381.298Smartin20180924: 3391.298Smartin A newer OpenSSL version has been imported. If you are doing 3401.298Smartin update builds, make sure to remove all old obj dirs, like: 3411.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 3421.298Smartin 3431.297Sjoerg20180717: 3441.297Sjoerg On aarch64 int64_t and related types have changed from long long 3451.297Sjoerg to long. This requires recompiling all C++ binaries. 3461.297Sjoerg 3471.296Smartin20180713: 3481.296Smartin On amd64 and i386 static binaries are now build position 3491.344Sgutterid independent. This requires recompilation of all object 3501.296Smartin files used to create the crunched /rescue binary. 3511.296Smartin Clean the rescue directory in your obj directory before 3521.296Smartin doing an update build, otherwise linking will fail. 3531.296Smartin 3541.293Sjakllsch20180414: 3551.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 3561.293Sjakllsch removal of tools/binutils objects directory may be required 3571.293Sjakllsch to fix tools build failure. 3581.293Sjakllsch 3591.292Smrg20180311: 3601.292Smrg bdftopcf was updated and may need cleaning in the 3611.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 3621.292Smrg link errors. 3631.292Smrg 3641.291Smrg20180212: 3651.291Smrg between OpenSSL and GCC updates, many things may fail to build. 3661.291Smrg any failure that looks like GCC or openssl is best handled by 3671.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 3681.291Smrg is recommended if build failures occur. 3691.291Smrg 3701.288Smartin20171225: 3711.288Smartin removal of the vadvise syscall requires manual removal of all 3721.288Smartin associated files from the libc build object directory (including 3731.289Schristos the .depend files) - a command like: 3741.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 3751.289Schristos For architectures that support multiple "compat" binary targets, 3761.289Schristos you'll need to cleanup both the regular libc directory and the 3771.290Smartin compat ones (the above command will do that). 3781.288Smartin 3791.287Skre20171010: 3801.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 3811.287Skre means that its objdir (or *.d and .depend at least) might need 3821.287Skre to be manually removed - or a build done once without -u. 3831.287Skre 3841.286Smrg20170822: 3851.286Smrg a new version of GMP has been imported and probably 3861.286Smrg will break parts of builds related to themselves or GCC, both 3871.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3881.286Smrg and MPC objdirs or build once without -u. 3891.286Smrg 3901.285Smrg20170816: 3911.285Smrg a new version of MPFR and MPC have been imported and probably 3921.285Smrg will break parts of builds related to themselves or GCC, both 3931.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3941.285Smrg and MPC objdirs or build once without -u. 3951.285Smrg 3961.284Smartin20170402: 3971.284Smartin a new version of dhcpcd has been imported, which does not support 3981.284Smartin update builds from the previous version. Remove your 3991.284Smartin external/bsd/dhcpcd object dir or build once without -u. 4001.284Smartin 4011.281Sroy20170211: 4021.281Sroy a new terminfo database has been imported. 4031.281Sroy The structure of it has changed slightly from prior versions and 4041.281Sroy an updated tic tool is required. 4051.281Sroy If you build.sh, don't use -u 4061.281Sroy 4071.280Skre20170207: 4081.278Skre various arch dependent libc/exect.S files were removed 4091.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 4101.279Skre if it exists) or do a clean build. 4111.279Skre (This is a bug in the make system, it should be corrected without 4121.279Skre human intervention, but isn't.) 4131.278Skre 4141.277Smartin20170104: 4151.277Smartin xinput build options have changed. 4161.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 4171.277Smartin if you build.sh -u 4181.277Smartin 4191.276Smartin20170103: 4201.276Smartin a new version of flex has been imported. 4211.276Smartin Remove the file from obj (external/bsd/flex) 4221.276Smartin if you build.sh -u 4231.276Smartin 4241.275Sspz20161014: 4251.275Sspz a new version of OpenSSL has been imported. 4261.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 4271.275Sspz if you build.sh -u 4281.275Sspz 4291.274Smartin20161009: 4301.274Smartin a new version of dhcpcd has been imported with slightly changed 4311.274Smartin build infrastructure. When doing a build.sh -u this requires 4321.274Smartin pruning the external/bsd/dhcpcd objdir. 4331.274Smartin 4341.273Smrg20160914: 4351.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 4361.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 4371.273Smrg and a clean objdir. 4381.273Smrg 4391.272Sdholland20160527: 4401.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 4411.272Sdholland been enabled. (see the amd64 entry two down for further info) 4421.272Sdholland 4431.270Schristos20160418: 4441.270Schristos libedit needs manual removal of all autogenerated files since 4451.271Schristos some of them are not autogenerated anymore. Remember that there 4461.271Schristos might be two copies of libedit if your platform builds "compat". 4471.270Schristos 4481.268Sriastrad20160410: 4491.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 4501.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 4511.268Sriastrad executables, means all code, including executables and not just 4521.268Sriastrad shared libraries, is position-independent and hence able to be 4531.268Sriastrad relocated by ASLR, address space layout randomization. 4541.268Sriastrad 4551.268Sriastrad The change was made in Makefile variables for compiler and 4561.268Sriastrad linker flags, for which make(1) does not record dependencies, 4571.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 4581.268Sriastrad 4591.268Sriastrad Partial rebuilds with some modified source files will likely 4601.268Sriastrad fail when linking executables, since the linker refuses to mix 4611.268Sriastrad position-independent code with position-dependent code in 4621.268Sriastrad position-independent executables: 4631.268Sriastrad 4641.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 4651.268Sriastrad 4661.267Smrg20160401: 4671.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 4681.269Sdholland Some people have found that cleandir is not sufficient, so if 4691.269Sdholland in doubt delete the entire object directory tree for gcc. 4701.267Smrg 4711.266Saymeric20160306: 4721.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 4731.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 4741.265Saymeric non-NetBSD hosts if linked with stale object files produced 4751.265Saymeric while they included a non-NetBSD regex.h. 4761.265Saymeric In any case, you should "make cleandir" at least these tools 4771.265Saymeric before updating your toolchain. 4781.265Saymeric 4791.264Smartin20160125: 4801.264Smartin Dtrace has been enabled by default on some architectures. 4811.264Smartin When doing an update build, make sure to clean the etc/mtree 4821.264Smartin object directory before starting the build - otherwise the 4831.264Smartin needed directories in destdir will not be created. 4841.264Smartin An easy way to do this is: 4851.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 4861.264Smartin 4871.263Sdholland20150818: 4881.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 4891.263Sdholland again. 4901.263Sdholland 4911.262Schristos20150413: 4921.262Schristos New acpica requires "make cleandir" and reinstalling yacc 4931.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 4941.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 4951.262Schristos 4961.261Smartin20150404: 4971.261Smartin Lint changes require a full rebuild of the tool, so make 4981.261Smartin sure to build without -u option to build.sh, or manually 4991.261Smartin do a make cleandir in src/tools/lint1 and 5001.261Smartin src/usr.bin/xlint. 5011.261Smartin 5021.260Sskrll20150310: 5031.260Sskrll Improvements to openssl for arm mean that update builds of 5041.260Sskrll the openssl libraries will fail. A make cleandir in 5051.260Sskrll external/bsd/openssl/lib is needed 5061.260Sskrll 5071.258Smartin20141026: 5081.259Smsaitoh A mishap during the import of pppd may cause your corruption 5091.258Smartin in your cvs directory if you happened to do a cvs update 5101.258Smartin during a short period of time. To fix, just remove the 5111.258Smartin directory src/external/bsd/ppp/dist/pppd completely 5121.258Smartin and let cvs restore it on next update. 5131.258Smartin 5141.256Sapb20140721: 5151.256Sapb The src/external/mit/lua/src directory was accidentally created 5161.256Sapb and then deleted in the CVS repository. If you get errors like 5171.256Sapb 5181.256Sapb cvs [update aborted]: cannot open directory 5191.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 5201.256Sapb 5211.256Sapb then delete your local copy of that directory tree and try again. 5221.256Sapb 5231.255Sjoerg20140530: 5241.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 5251.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 5261.255Sjoerg 5271.251Smartin20140131: 5281.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 5291.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 5301.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 5311.251Smartin 5321.250Schristos20131227: 5331.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 5341.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 5351.250Schristos mode7 in your config file. Make sure you put the necessary restrict 5361.250Schristos statements to avoid being exposed. 5371.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 5381.250Schristos to make clean in libc 5391.250Schristos 5401.249Smrg20131129: 5411.249Smrg The GMP sources were updated, and builds will likely fail without 5421.249Smrg cleaning their build trees for both tools and in-tree, like below. 5431.249Smrg 5441.248Smrg20131128: 5451.248Smrg The MPC and MPFR sources were updated, and builds may require their 5461.248Smrg tools and in-tree directories cleaned for successful updates. 5471.248Smrg 5481.246Smartin20130605: 5491.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 5501.247Sspz to IPSEC (and the older IPSEC version removed). 5511.247Sspz 5521.247Sspz20130605: 5531.320Sandvar Previous freetype installations erroneously installed private 5541.246Smartin header files. If you are building against a non-empty $DESTDIR, 5551.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 5561.246Smartin 5571.245Smrg20130531: 5581.245Smrg The xdm update may cause build failure due to xdm.man being 5591.245Smrg in the obj tree. Make sure to ensure any like this: 5601.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 5611.245Smrg is fixed by deleting the xdm.man in the obj tree. 5621.245Smrg 5631.244Smrg20130530: 5641.244Smrg Updates of many xsrc packages will leave old .pc files around. 5651.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 5661.244Smrg 5671.242Schristos20130301: 5681.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 5691.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 5701.242Schristos 5711.238Sdholland20120726: 5721.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 5731.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 5741.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 5751.241Swiz some cases may succeed and install broken OpenSSL libraries that 5761.240Sdholland cause third-party software to link incorrectly and/or crash. 5771.238Sdholland 5781.237Swiz20120507: 5791.241Swiz The database schema for makemandb was changed. You will 5801.237Swiz need to update the database using 'makemandb -f' or wait 5811.237Swiz for the next weekly run to fix it. 5821.237Swiz 5831.236Sbsh20120319: 5841.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 5851.236Sbsh size of db_symtab automatically. You need to update dbsym in 5861.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 5871.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 5881.236Sbsh mk.conf. 5891.236Sbsh 5901.235Sjoerg20120216: 5911.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 5921.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 5931.239Sdholland and 20120216, daily and weekly could have created an unreadable 5941.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 5951.235Sjoerg the next run of weekly will fix it. 5961.233Sjoerg 5971.232Schristos20111227: 5981.232Schristos If you built between 20111225 and 20111227 you need to remove 5991.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 6001.232Schristos bump has been reverted. 6011.232Schristos 6021.231Stls20111125: 6031.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 6041.231Stls means it should no longer be explicitly listed in kernel 6051.231Stls configuration files. The line "pseudo-device rnd" should be 6061.231Stls removed from any custom kernel config files users may have. 6071.231Stls 6081.230Stls20111119: 6091.230Stls A problem with the datastructures used by the rndctl(8) 6101.230Stls utility (pointers in datastructures in an array, making 32->64 6111.230Stls bit compatibility very painful) has been fixed in a 6121.230Stls non-backwards-compatible way. If you replace your kernel, 6131.230Stls replace your rndctl executable too. 6141.241Swiz 6151.229Sjym20111001: 6161.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 6171.229Sjym changed and their new version is not backward compatible with the old 6181.241Swiz one. So ensure that all consumers of these functions (currently: 6191.229Sjym quota2 code and its tests) are updated together with the new lib. 6201.229Sjym 6211.228Smrg20110817: 6221.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 6231.228Smrg DESTDIR for them should be deleted before updating. 6241.228Smrg 6251.227Sriastrad20110806: 6261.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 6271.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 6281.227Sriastrad 6291.226Smrg20110805: 6301.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 6311.226Smrg the tree to be cleaned. Best to delete both objdir and 6321.226Smrg DESTDIR before running this update. So far, only the 6331.226Smrg sparc64, mips and powerpc platforms have changed. 6341.226Smrg 6351.225Smatt20110803: 6361.241Swiz The layout of external/public-domain/xz has changed. To do an 6371.225Smatt update build you will have to remove the contents of the OBJDIR 6381.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 6391.225Smatt is now a directory. 6401.225Smatt 6411.223Sjoerg20110410: 6421.241Swiz The configuration of src/tools/gcc has changed. To do an 6431.224Sdholland update build you have to clean both tools/binutils and 6441.224Sdholland tools/gcc by hand. 6451.223Sjoerg 6461.222Splunky20110328: 6471.222Splunky Building the Xorg binary was moved into a subdirectory to fix 6481.241Swiz ordering issues with "make all". It may be necessary to remove 6491.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 6501.222Splunky if your update build fails, as the "Xorg" entry there is now a 6511.222Splunky directory. 6521.222Splunky 6531.220Sjoerg20110121: 6541.221Slukem Assembler files no longer use -traditional-cpp. This can break 6551.220Sjoerg the build of individual parts of the tree. This is handled 6561.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 6571.220Sjoerg and re-run config(1) for any kernel configurations as needed. 6581.218Sjoerg 6591.217Sjruoho20101217: 6601.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 6611.241Swiz by default. It may be necessary to manually update passwd(5) and 6621.217Sjruoho group(5) in order to make the program work with existing setups. 6631.217Sjruoho 6641.216Schristos20101125: 6651.327Sandvar The latest changes to setenv(3) disallow setting environment 6661.241Swiz variables with names that contain '='. Revision 1.18 of env.c 6671.241Swiz assumed that this was allowed. Installing a new libc with an 6681.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 6691.216Schristos break which affects the autoconf tests for dependency finding, 6701.216Schristos so building gcc will end up printing: 6711.216Schristos checking dependency style of gcc... none 6721.216Schristos configure: error: no usable dependency style found 6731.216Schristos Fix it by rebuilding and re-installing env. 6741.138Slukem 6751.215Smrg20101119: 6761.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 6771.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 6781.215Smrg have any build problems with xsrc, or problems with mismatched 6791.215Smrg versions between xorg-server and drivers. 6801.215Smrg 6811.213Sjmmv20100604: 6821.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 6831.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 6841.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 6851.213Sjmmv trees by hand. 6861.213Sjmmv 6871.211Stnozaki20100522: 6881.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 6891.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 6901.212Smrg build problems with xsrc. 6911.212Smrg 6921.212Smrg20100522: 6931.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 6941.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 6951.211Stnozaki 6961.210Schristos20100520: 6971.241Swiz The location of the xkb compiled descriptions has changed. Please 6981.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 6991.210Schristos 7001.209Snjoly20100222: 7011.209Snjoly The shared objects file extension has been changed from .so to 7021.209Snjoly .pico, in order to avoid conflicts with shared libraries names 7031.209Snjoly libXX.so. All now stale regular .so files can be removed from 7041.209Snjoly your object directories. 7051.209Snjoly 7061.208Sroy20100204: 7071.208Sroy The termcap database has been removed from the sources, 7081.208Sroy but has not been marked obsolete so it is not removed 7091.208Sroy from the system when upgrading. 7101.208Sroy As such, you will need to remove them from your object 7111.208Sroy and destination directories. 7121.208Sroy 7131.203Sdyoung20091101: 7141.205Sdholland After updating, it may be necessary to make the 'cleandir' 7151.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 7161.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 7171.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 7181.203Sdyoung 7191.202Smrg20091001: 7201.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 7211.206Sdholland before building a kernel, or the build fails on cpufunc.S. 7221.206Sdholland 7231.206Sdholland20091001: 7241.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 7251.202Smrg symlink, failing the build. Delete the link, and the subdir 7261.202Smrg it is in, and retry your build. 7271.202Smrg 7281.201Sdsl20090718: 7291.201Sdsl libc build changed so that strchr() provides the extra entry 7301.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 7311.201Sdsl may fail because the archive contains the unwanted index.o. 7321.201Sdsl (Similarly for strrchr() and rindex().) 7331.201Sdsl 7341.198Smrg20090709: 7351.198Smrg Native Xorg was upgraded again. Builds will probably fail again 7361.198Smrg without a clean objdir, at least for src/external/mit/xorg. 7371.198Smrg 7381.197Smrg20090616: 7391.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 7401.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 7411.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 7421.197Smrg subdirectory has been changed into a file, and this needs to 7431.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 7441.197Smrg 7451.195Sperry20090501: 7461.195Sperry Several new functions were added to string.h/libc, and this 7471.195Sperry can cause autoconf problems during the tool build for people 7481.241Swiz who fail to clean out their tools objects properly. If you 7491.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 7501.195Sperry failure during the tool build, clean out all your tools 7511.195Sperry objects and start again. 7521.195Sperry 7531.194Smrg20090325: 7541.194Smrg The i386 port was switched to i486 default toolchain. This requires 7551.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 7561.194Smrg 7571.192Sskrll20090126: 7581.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 7591.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 7601.207Smbalmer to avoid using the old assembly stub. 7611.192Sskrll 7621.191Sjoerg20090202: 7631.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 7641.320Sandvar detection. It is recommended to rebuild the cache with 7651.191Sjoerg ``pkg_admin rebuild''. 7661.191Sjoerg 7671.184Schristos20090110: 7681.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 7691.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 7701.188Schristos This is needed even in the MODULAR kernel because there is 7711.188Schristos conditionally compiled code in rtsock.c. 7721.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 7731.184Schristos before installing. 7741.184Schristos 3. If you don't use build.sh and you build directly to root, and 7751.241Swiz your build breaks in the middle, don't despair. Make sure headers 7761.184Schristos are installed properly, and start building libraries first libc 7771.184Schristos and libutil, install them and then continue building all the 7781.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 7791.184Schristos the new libraries are installed, you can restart the build. 7801.184Schristos 4. If you compile packages and you notice link time warnings, 7811.189Shubertf rebuild the required packages to update their shared libraries. 7821.189Shubertf Any package you rebuild will require rebuilding all the packages 7831.189Shubertf that depend on it. 7841.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 7851.186Schristos will be upgraded and it will not be backwards compatible. 7861.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 7871.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 7881.241Swiz for utmp. You are better off removing the old files after 7891.190Sapb upgrading. The automated clearing of /var/run during 7901.190Sapb boot, and the automated rotating of files in /var/log by 7911.190Sapb newsyslog(8), may mean that you do not have to remove the 7921.190Sapb files manually. 7931.190Sapb 7. The optional accounting file (/var/account/acct, see 7941.190Sapb accton(8)) has not been versioned, and will need to be 7951.190Sapb removed. The automatic rotation of the accounting file by 7961.190Sapb /etc/daily limits the bad consequences of failure to remove 7971.190Sapb the file. 7981.196Sdholland 8. Application software that writes time_t to binary files on 7991.241Swiz disk will break or need attention. Most notably: if you are 8001.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 8011.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 8021.185Sjmcneill 8031.183Spgoyette20081219: 8041.183Spgoyette config(1) has been updated, and one of the files it creates - 8051.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 8061.183Spgoyette (done automatically by build.sh) and then you need to rerun 8071.183Spgoyette config on all kernel configuration files before rebuilding those 8081.183Spgoyette kernels. 8091.183Spgoyette 8101.181Scube20081205: 8111.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 8121.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 8131.181Scube set and will appear as extra files for MKX11=no update builds. 8141.178Slukem 8151.179Stsutsui20081122: 8161.182Stsutsui On i386, various kernel options(4) in GENERIC including 8171.180Swiz file systems have been disabled and moved into kernel modules. 8181.180Swiz Before trying a new GENERIC kernel, you have to prepare the 8191.179Stsutsui following files as well as a new GENERIC kernel: 8201.179Stsutsui 8211.179Stsutsui - build and install kernel modules from src/sys/modules 8221.179Stsutsui 8231.179Stsutsui - install the latest bootloader, which will load a module 8241.180Swiz for the file system from which the kernel is loaded automatically 8251.179Stsutsui 8261.180Swiz If you have to load your kernel from a file system which is not of 8271.180Swiz the same type as the root file system, you have to load the necessary 8281.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 8291.179Stsutsui 8301.178Slukem20080827: 8311.178Slukem If you built and installed a libc from sources between 8321.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 8331.178Slukem which results in false errors reported by lint(1). 8341.178Slukem Since this breaks the libc build itself, manual help is 8351.180Swiz needed -- lint must be disabled temporarily, e.g.: 8361.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 8371.178Slukem 8381.177Schristos20080813: 8391.177Schristos MKDEBUG build was broken because the .depend files did not know 8401.241Swiz about .go files. You need to remove all .depend files and rebuild. 8411.177Schristos 8421.200Sdholland20080802: 8431.200Sdholland A regression in binary compatibility for pthread_mutex_t has 8441.241Swiz been fixed. Unfortunately, the price is breaking compatibility 8451.200Sdholland for -current. 8461.200Sdholland 8471.200Sdholland Threaded programs (using libpthread) and C++ programs (using 8481.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 8491.200Sdholland be recompiled. 8501.200Sdholland 8511.200Sdholland One way to find affected pkgsrc packages: 8521.200Sdholland 8531.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 8541.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 8551.200Sdholland 8561.175Ssimonb20080731: 8571.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 8581.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 8591.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 8601.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 8611.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 8621.176Ssimonb also requires the super block to be in the UFS2 format. You 8631.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 8641.175Ssimonb 8651.174Slukem20080721: 8661.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 8671.174Slukem isn't defined. 8681.174Slukem 8691.173Sfreza20080531: 8701.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 8711.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 8721.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 8731.241Swiz won't work correctly. The following sequence of commands: 8741.173Sfreza 8751.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 8761.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 8771.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 8781.173Sfreza 8791.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 8801.173Sfreza 8811.172Slukem20080503: 8821.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 8831.172Slukem 8841.171She20080521: 8851.171She For a while, unprivileged UPDATE builds would fail to 8861.171She succeed at the checkflist stage, complaining that 8871.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 8881.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 8891.171She If you already hit this problem, update the .mk file, 8901.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 8911.171She 8921.174Slukem20080303: 8931.174Slukem Linker warnings are now fatal if $WARNS>0. 8941.174Slukem 8951.170Schristos20080126: 8961.170Schristos The posix_fadvise system call has been changed from an assembly 8971.241Swiz stub, to a c file that calls an assembly stub. You need to 8981.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 8991.170Schristos avoid using the old assembly stub. 9001.170Schristos 9011.168Sjoerg20071209: 9021.241Swiz The acpiec(4) driver has been split into two attachments. If you 9031.168Sjoerg get ACPI errors before the attachment, please update your kernel 9041.169Swiz configuration file appropriately or see GENERIC for more details. 9051.168Sjoerg 9061.166Sxtraeme20071115: 9071.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 9081.166Sxtraeme argument specified in the kernel configuration file is not valid 9091.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 9101.241Swiz rather than the EC address port. Please update your kernel 9111.167Swiz configuration file appropriately or see GENERIC for more details. 9121.166Sxtraeme 9131.165Sjmmv20071028: 9141.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 9151.165Sjmmv You need to update any custom kernel configuration file you have 9161.165Sjmmv to remove any references to pccons (which includes removing the 9171.165Sjmmv now useless XSERVER option) and replace them with the correct 9181.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 9191.165Sjmmv for more details. 9201.165Sjmmv 9211.164Sgdt20070913: 9221.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 9231.164Sgdt enumerate interfaces was fixed. The bug began to cause 9241.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 9251.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 9261.164Sgdt could not enumerate interfaces. (These are noted because 9271.164Sgdt normal kernel/userspace version matching hygiene is not 9281.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 9291.164Sgdt and userland are from after 20070913. 9301.164Sgdt 9311.163Sjoerg20070703: 9321.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 9331.199Sdholland calls the target-specific strip program, and the logic to pass 9341.199Sdholland down STRIP from make has been removed. This requires a 9351.199Sdholland re-installation of tools. 9361.163Sjoerg 9371.161Sdsl20070422: 9381.161Sdsl The way OS emulations lookup filenames inside the emulation root 9391.161Sdsl has been changed. Rather than modify the pathname (and copy back 9401.161Sdsl to userspace) namei() and lookup() directly check the emulation 9411.241Swiz root. One side effect is that absolute symlinks inside the emulated 9421.167Swiz root file system will be relative to that file system - unless they 9431.161Sdsl start /../ this is useful when the emulated root is a real install 9441.161Sdsl that has such links. 9451.161Sdsl This might affect symlinks that have been added to reference outside 9461.161Sdsl the emulated root. 9471.161Sdsl 9481.160Sjmcneill20070412: 9491.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 9501.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 9511.160Sjmcneill example. 9521.160Sjmcneill 9531.159Sgdt20070319: 9541.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 9551.159Sgdt on many platforms due to incorrect flags settings. If you 9561.159Sgdt updated and built after about 20070315, do "nbmake-$arch 9571.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 9581.159Sgdt rebuild of object files that might have been built 9591.159Sgdt incorrectly, and ensure that you have at least 9601.159Sgdt src/lib/libc/Makefile 1.130. 9611.159Sgdt 9621.241Swiz20070210: 9631.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 9641.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 9651.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 9661.158Sdbj will allow dependencies on those files to get get rebuilt 9671.158Sdbj 9681.157Sapb20070209: 9691.157Sapb The threading model was changed when the newlock2 branch 9701.157Sapb was merged to NetBSD-current. If you boot with a new 9711.157Sapb kernel (version 4.99.10), then you also need a new pthread 9721.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 9731.157Sapb an old kernel, then you need the old pthread library 9741.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 9751.157Sapb the pthread library in sync, old threaded applications should 9761.157Sapb continue to work with an old or new kernel. Note that named(8) 9771.157Sapb is the only threaded application in the base system. 9781.157Sapb 9791.154She20061214: 9801.154She Following the move of string_to_flags() and flags_to_string() 9811.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 9821.154She will need to do a "make cleandir" in 9831.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 9841.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 9851.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 9861.156She as the installation images in distrib/ 9871.154She in order to excise stale references to the old stat_flags.h header 9881.154She file in the ls sources -- stat_flags.h has been removed. 9891.154She 9901.152Schristos20061108: 9911.152Schristos The configure script used in the src/tools/gcc compiler has been 9921.152Schristos changed to indicate that our libc has ssp support built-in and 9931.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 9941.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 9951.152Schristos 9961.151Srpaulo20061009: 9971.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 9981.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 9991.151Srpaulo 10001.150Sbjh2120060814: 10011.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 10021.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 10031.150Sbjh21 kernel configuration for an example. X servers from the last 10041.150Sbjh21 few years should cope. 10051.150Sbjh21 10061.149Schristos20060703: 10071.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 10081.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 10091.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 10101.149Schristos 10111.148Sdogcow20060627: 10121.148Sdogcow socket(2) has changed, and its system call has been versioned. 10131.148Sdogcow For userlands with the old version of socket(2), make sure that 10141.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 10151.148Sdogcow errors will result. 10161.148Sdogcow 10171.1SabsHints for a more successful build: 10181.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10191.123Sjmc Use build.sh, but do not use its "expert mode": 10201.132Sjmmv This will automatically build the tools in the 10211.123Sjmc correct order, and it will keep the tools and the 10221.123Sjmc new build products from interfering with the running 10231.123Sjmc system. This will allow you to ignore most of the 10241.123Sjmc other advice in this file. 10251.2Smrg Build a new kernel first: 10261.2Smrg This makes sure that any new system calls or features 10271.2Smrg expected by the new userland will be present. This 10281.2Smrg helps to avoid critical errors when upgrading. 10291.1Sabs Use object directories: 10301.1Sabs This helps to keep stale object 10311.1Sabs files from polluting the build if a Makefile "forgets" 10321.1Sabs about one. It also makes it easier to clean up after 10331.1Sabs a build. It's also necessary if you want to use the 10341.1Sabs same source tree for multiple machines. 10351.123Sjmc To use object directories with build.sh: 10361.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 10371.123Sjmc To use object directories without using build.sh: 10381.1Sabs a) cd /usr/src ; make cleandir 10391.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 10401.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 10411.1Sabs d) cd /usr/src ; make build 10421.2Smrg Note that running "make obj" in a directory will create 10431.2Smrg in obj.$MACHINE directory. 10441.1Sabs Build to a DESTDIR: 10451.123Sjmc This helps to keep old installed files (especially libraries) 10461.123Sjmc from interfering with the new build. 10471.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 10481.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 10491.123Sjmc environment variable before running make build. It should be 10501.123Sjmc set to the pathname of an initially empty directory. 10511.123Sjmc Problems: if you do not use build.sh, you might need to 10521.123Sjmc update critical utilities without using DESTDIR since 10531.123Sjmc nothing is executed from what is installed in DESTDIR. 10541.123Sjmc (See critical utils, below.) 10551.1Sabs Build often: 10561.1Sabs This keeps critical utilities current enough to not choke 10571.1Sabs on any other part of the source tree that depends on up to 10581.123Sjmc date functionality. If you use build.sh, you should not have 10591.123Sjmc this problem. 10601.241Swiz 10611.1SabsWhat to do if things don't work: 10621.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10631.230StlsWhen things don't work there are usually a few things that commonly 10641.1Sabsshould be done. 10651.1Sabs 1) make includes 10661.1Sabs This should be done automatically by make build. 10671.1Sabs 2) cd share/mk && make install 10681.1Sabs Again, automatically done by make build. 10691.1Sabs 10701.1SabsFailsafe rebuild of a small part of the tree: 10711.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10721.1SabsTo make sure you rebuild something correctly you want to do 10731.1Sabssomething like the following: 10741.1Sabs 1) Make sure the includes and .mk files are up to date. 10751.1Sabs 2) Make sure any program used to build the particular 10761.1Sabs utility is up to date. (yacc, lex, etc...) 10771.1Sabs 3) cd ...path/to/util... 10781.1Sabs make cleandir 10791.1Sabs rm ...all obj directories... 10801.1Sabs make cleandir # yes, again 10811.1Sabs make obj 10821.1Sabs make depend && make 10831.1Sabs 10841.1SabsFailsafe rebuild of the entire tree: 10851.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10861.1SabsIf you really want to make sure the source tree is clean and 10871.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 10881.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 10891.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 10901.1Sabs 10911.1Sabs---cut here--- 10921.1Sabs#!/bin/sh 10931.1Sabs. /etc/mk.conf 10941.1Sabs 10951.58Slukemif [ -z $NETBSDSRCDIR ] ; then 10961.58Slukem NETBSDSRCDIR=/usr/src 10971.1Sabsfi 10981.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 10991.1Sabs echo Unable to find sources 11001.1Sabs exit 1 11011.1Sabsfi 11021.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 11031.1Sabs 11041.1Sabsif [ -z $BSDOBJDIR ] ; then 11051.1Sabs BSDOBJDIR=/usr/obj 11061.1Sabsfi 11071.1Sabsif [ -d $BSDOBJDIR ] ; then 11081.1Sabs rm -rf $BSDOBJDIR 11091.1Sabsfi 11101.1Sabs 11111.58Slukemcd $NETBSDSRCDIR && make cleandir 11121.1Sabs 11131.1Sabs---cut here--- 11141.1Sabs 11151.1SabsCritical utilities: 11161.1Sabs^^^^^^^^^^^^^^^^^^^ 11171.3Sitojun usr.bin/compile_et 11181.1Sabs usr.bin/make 11191.1Sabs usr.bin/yacc 11201.1Sabs usr.bin/lex 11211.11Slukem usr.bin/xlint 11221.142Sdrochner usr.bin/config 11231.1Sabs 11241.34SsimonbOther problems and possible solutions: 11251.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 11261.1SabsSymptom:Complaints involving a Makefile. 11271.17SerhFix: Rebuild usr.bin/make: 11281.17Serh cd usr.bin/make && make && make install 11291.111Ssimonb Or, a failsafe method if that doesn't work: 11301.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 11311.17Serh 11321.1SabsFix: Make sure .mk files are up to date. 11331.1Sabs cd share/mk && make install 11341.2Smrg 11351.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 11361.142SdrochnerFix: Rebuild usr.bin/config 11371.1Sabs 11381.1SabsSymptom: 11391.1SabsFix: Rebuild usr.bin/yacc 11401.1Sabs 11411.1SabsSymptom: 11421.1SabsFix: Rebuild usr.bin/lex 11431.1Sabs 11441.1SabsSymptom: 11451.1SabsFix: rm /usr/lib/libbfd.a 11461.4Sitojun 11471.4SitojunSymptom:Obsolete intermediate files are used during compilation 11481.4SitojunFix: Try the following sequence of commands in the directory in question. 11491.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 11501.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 11511.4Sitojun may remain. The command tries to clean everything up) 11521.5Swiz 11531.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 11541.207Smbalmer pointer type 11551.5SwizFix: Rebuild and install usr.bin/menuc 11561.12Sitojun 11571.12SitojunSymptom:mklocale not found during build in share/locale/ctype 11581.12SitojunFix: Build and install usr.bin/mklocale 11591.13Sdogcow 11601.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 11611.13SdogcowFix: Rebuild and install lib/libc 11621.13Sdogcow 11631.142SdrochnerSymptom:usr.bin/config fails to build. 11641.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 11651.13Sdogcow 11661.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 11671.19ScgdFix: Rebuild and install lib/libc 11681.24Sabs 11691.24SabsSymptom:lint does not understand the '-X' option 11701.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 11711.223Sjoerg 11721.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 11731.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 11741.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 11751.257Sapb 11761.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 11771.257Sapb No such file or directory. 11781.257SapbCause: If a directory is created by mistake, then it is sometimes 11791.257Sapb deleted from the CVS repository using administrative commands 11801.257Sapb that bypass the normal cvs access controls. If your cvs working tree 11811.257Sapb contains references to a directory that has been deleted on the 11821.257Sapb server in this way, then "cvs update" reports this error. 11831.257SapbFix: Recursively delete the affected directory from your working tree 11841.257Sapb and try the update again. 1185