UPDATING revision 1.342
11.342Smartin$NetBSD: UPDATING,v 1.342 2023/07/19 17:49:40 martin Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.257SapbSections are marked with "^^^^^". After the section on "Recent changes" 151.257Sapbare several sections containing more general information. 161.257Sapb 171.123SjmcSee also: BUILDING, build.sh, Makefile. 181.1Sabs 191.1SabsRecent changes: 201.1Sabs^^^^^^^^^^^^^^^ 211.230Stls 221.341Slukem20230718: 231.341Slukem build.sh will use mk.conf in the same directory as build.sh instead 241.341Slukem of /etc/mk.conf, unless MAKECONF is already defined in the environment. 251.341Slukem 261.342Smartin20230714: 271.342Smartin Import of gcc 10.5 requires a clean build of at least tools/gcc 281.342Smartin and external/gpl3/gcc* object directories. An update build 291.342Smartin without cleaning will result in obscure failures in rare corner 301.342Smartin cases. 311.342Smartin 321.339Smartin20230604: 331.339Smartin Building native kernels with the installed make(1) instead of 341.339Smartin the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland 351.339Smartin has not been updated. Note that this is an unsupported build 361.339Smartin configuration (but usually works if userland is -current enough). 371.338Slukem 381.338Slukem20230523: 391.338Slukem ctfmerge was fixed as macOS host tool. This may require a clean tools 401.338Slukem rebuild to detect the update to tools/compat/configure. 411.338Slukem 421.340Smartin20230515: 431.340Smartin New openssl build requires removal of the crypto/external/bsd/openssl 441.340Smartin and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierachy. 451.340Smartin Otherwise test results may be wrong due to wrong "golden" output 461.340Smartin files being installed. 471.340Smartin 481.337Smrg20230322: 491.337Smrg Fixes for moved /lib/libisns* mean that builds will complain about 501.337Smrg ./usr/lib/libisns* being missing until src/lib/libisns is forced 511.337Smrg to (re)install the files, including the symlinks. The simplest 521.337Smrg way is to clean this subdir before building. 531.337Smrg 541.336Smartin20230112: 551.336Smartin New binutils require an updated ld.elf_so. If you are doing 561.336Smartin (unsupported) in-place self builds (with the -E flag to build.sh), 571.336Smartin make sure to have installed latest ld.elf_so before you rebuild 581.336Smartin userland. 591.336Smartin 601.335Schs20221116: 611.335Schs The addition to NetBSD's version of UFS2 of support for extended 621.335Schs attributes broke backward compatibility with previous releases 631.335Schs of NetBSD, so UFS2 has been restored to being compatible with 641.335Schs previous NetBSD releases by disabling extended attributes. 651.335Schs (Note that ACLs are implemented as extended attributes, so 661.335Schs this changes disables ACLs as well.) 671.335Schs 681.335Schs Support for UFS2 with extended attributes is now available in a new 691.335Schs UFS variant called UFS2ea. If you have created extended attributes 701.335Schs in an original UFS2 file system then "fsck -p" will now fail due to 711.335Schs the unexpected presence of extended attributes and "fsck -y" will 721.335Schs remove all extended attributes. If you wish to preserve extended 731.335Schs attributes rather than delete them, there is a utility to convert 741.335Schs a UFS2 file system to UFS2ea and leave extended attributes in place, 751.335Schs but this should be used with caution since it will preserve any 761.335Schs extended attributes that have been corrupted by the backward 771.335Schs incompatibility too. 781.335Schs 791.335Schs If you wish to use a UFS2ea file system as your root file system, 801.335Schs then you will need to update your boot loader to a version that 811.335Schs supports UFS2ea. 821.335Schs 831.335Schs For more information, see: 841.335Schs https://wiki.netbsd.org/features/UFS2ea 851.335Schs 861.334Smrg20221111: 871.334Smrg The new libdrm import worsened the conflict issues for the 881.334Smrg kdump/ktruss ioctl, and i915 now conflicts with base, and has 891.334Smrg been turned off. This will cause update build issues like: 901.334Smrg 911.334Smrg kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 921.334Smrg undeclared here (not in a function); 931.334Smrg did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 941.334Smrg 951.334Smrg You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 961.334Smrg 971.331Sriastrad20220921: 981.331Sriastrad Since the kernel version was bumped to 9.99.100, the bootloader 991.333Sriastrad must be updated on x86 or EFI boot platforms in order to load 1001.333Sriastrad modules from boot.cfg(5) or interactively at the bootloader 1011.333Sriastrad prompt. 1021.333Sriastrad 1031.333Sriastrad The kernel can still load modules at runtime, with modload(8) 1041.333Sriastrad or modules.conf(5), with no bootloader update. This will not 1051.333Sriastrad affect release branches because it only applies to patch 1061.333Sriastrad numbers >=100. 1071.333Sriastrad 1081.333Sriastrad On x86 (i386 or amd64) with BIOS boot, this requires copying a 1091.333Sriastrad new /usr/mdec/boot to /boot. You can build this in the destdir 1101.333Sriastrad by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 1111.333Sriastrad sys/arch/i386/stand. 1121.333Sriastrad 1131.333Sriastrad On platforms with EFI boot (including x86 with EFI boot), this 1141.333Sriastrad requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 1151.333Sriastrad directory on the EFI system partition. The boot*.efi file is: 1161.333Sriastrad 1171.333Sriastrad aarch64 bootaa64.efi 1181.333Sriastrad amd64 bootx64.efi 1191.333Sriastrad arm bootarm.efi (32-bit arm) 1201.333Sriastrad i386 bootx32.efi 1211.333Sriastrad 1221.333Sriastrad You can build this in the destdir by running 1231.333Sriastrad `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 1241.333Sriastrad sys/stand/efiboot/boot*. 1251.331Sriastrad 1261.330Slukem20220821: 1271.330Slukem Support for building extsrc/ has been deprecated. 1281.330Slukem EXTSRCSRCDIR and MKEXTSRC have been deprecated. 1291.330Slukem 1301.329Smrg20220714: 1311.329Smrg Updates to xorg-server and associated drivers may cause builds to 1321.329Smrg fail. Cleaning both DESTDIR and the xorg build tree may be needed. 1331.329Smrg 1341.328Smartin20220628: 1351.328Smartin Changes in the build of src/games/robots require a clean build 1361.328Smartin of that program. 1371.328Smartin 1381.324Smartin20211116: 1391.324Smartin Changes in the xorg build require clean obj dirs for external/mit/xorg 1401.325Smartin (or a full clean/non-update build). 1411.324Smartin 1421.323Snia20211112: 1431.323Snia Device tree sources were updated for evbarm. Some device nodes 1441.323Snia (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 1451.323Snia 1461.322Smartin20211014: 1471.323Snia MKPIE default for aarch64 has changed, a clean build is required. 1481.322Smartin 1491.321Schristos20210917: 1501.321Schristos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 1511.321Schristos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 1521.321Schristos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 1531.321Schristos 1541.319Smrg20210711: 1551.319Smrg Updated GMP sources may require cleaning in tools/gmp and/or in 1561.319Smrg external/lgpl3/gmp/lib, particularly if GCC itself does not build. 1571.319Smrg 1581.318Smrg20210417: 1591.318Smrg GCC 10 was enabled for several platforms. If builds fail in either 1601.318Smrg tools/gcc or external/gpl/gcc, first try cleaning those objects and 1611.318Smrg removing the $DESTDIR/usr/include/g++ subdirectory. 1621.318Smrg 1631.317Srillig20201230: 1641.317Srillig lint1/ops.c is no longer autogenerated. If this makes the build 1651.317Srillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 1661.317Srillig 1671.316Smrg20201016: 1681.316Smrg MIPS kernel modules have been disabled until they work. This will 1691.316Smrg turn up in extra files in the DESTDIR, which should be cleaned. 1701.316Smrg 1711.315Smrg20200925: 1721.315Smrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning 1731.315Smrg in both the tools and external dirs. 1741.315Smrg 1751.314Smrg20200912: 1761.314Smrg GCC 9 has arrived for Arm and x86 platforms, and will be coming 1771.314Smrg for several more, as will binutils 2.34. Clean as required. 1781.314Smrg 1791.313Smrg20200907: 1801.313Smrg GCC 9 is coming, and binutils has been updated for MIPS. This 1811.313Smrg probably requires cleaning the tools/binutils. 1821.313Smrg 1831.311Smrg20200811: 1841.312Smrg GCC updates may require cleaning the objdir. This may occur 1851.312Smrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 1861.312Smrg GCC 9 upgrade. 1871.311Smrg 1881.309Schristos20200614: 1891.310Schristos blacklist* has been renamed to blocklist*. postinstall(8) 1901.332Sgutterid should handle the migration. 1911.309Schristos 1921.308Schristos20200601: 1931.308Schristos Due to a mistake in LIBISPRIVATE handling, .so libraries were 1941.308Schristos created in the build directories and need cleaning. 1951.308Schristos 1961.307Smrg20200311: 1971.307Smrg GCC 8 ports will need cleaning in src/tools/gcc and 1981.307Smrg src/external/gpl3/gcc due to GCC 8.4 update. 1991.307Smrg 2001.306Schristos20191118: 2011.306Schristos More architectures were switched to gcc8: 2021.306Schristos i386, ia64 powerpc64, sparc, sparc64, arm 2031.306Schristos The same comments as in 20191022 apply. 2041.306Schristos 2051.305Smartin20191112: 2061.305Smartin The LLVM update requires a clean rebuild for all architectures using 2071.305Smartin LLVM during the tools build phase (i386, amd64, aarch64). 2081.305Smartin 2091.304Smartin20191022: 2101.304Smartin Ports amd64 and aarch64 switched to GCC 8.3 by default. 2111.304Smartin In-place ("expert mode", build.sh -E) builds are not supported 2121.304Smartin when going from a GCC 7 userland to GCC 8. Do a regular 2131.304Smartin build to a different DESTDIR (or preferably: build.sh -U) at least 2141.306Schristos once and install sets, or download comp.{tar.xz,tgz} from the 2151.304Smartin daily builds and install that before doing the next in-place build. 2161.304Smartin 2171.303Smrg20191001: 2181.303Smrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if 2191.303Smrg old builds with GCC 7 output now uses GCC 8. Clean this 2201.303Smrg directory, and also clean src/external/gpl3/gcc. 2211.303Smrg 2221.302Sriastrad20190903: 2231.306Schristos Files with names that coincide with existing files' names on 2241.302Sriastrad case-insensitive file systems were inadvertently committed, for 2251.302Sriastrad radeon GPU firmware. We cannot mark these as obsolete for 2261.302Sriastrad postinstall to fix, so if you updated src since 2019-08-26, and 2271.302Sriastrad ran build.sh distribution or ran build.sh release, you must 2281.302Sriastrad manually delete the following files in your DESTDIR (which is 2291.302Sriastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed 2301.302Sriastrad them: 2311.302Sriastrad 2321.302Sriastrad /libdata/firmware/radeon/bonaire_ce.bin 2331.302Sriastrad /libdata/firmware/radeon/bonaire_mc.bin 2341.302Sriastrad /libdata/firmware/radeon/bonaire_me.bin 2351.302Sriastrad /libdata/firmware/radeon/bonaire_mec.bin 2361.302Sriastrad /libdata/firmware/radeon/bonaire_pfp.bin 2371.302Sriastrad /libdata/firmware/radeon/bonaire_rlc.bin 2381.302Sriastrad /libdata/firmware/radeon/bonaire_sdma.bin 2391.302Sriastrad /libdata/firmware/radeon/bonaire_smc.bin 2401.302Sriastrad /libdata/firmware/radeon/bonaire_uvd.bin 2411.302Sriastrad /libdata/firmware/radeon/hainan_ce.bin 2421.302Sriastrad /libdata/firmware/radeon/hainan_mc.bin 2431.302Sriastrad /libdata/firmware/radeon/hainan_me.bin 2441.302Sriastrad /libdata/firmware/radeon/hainan_pfp.bin 2451.302Sriastrad /libdata/firmware/radeon/hainan_rlc.bin 2461.302Sriastrad /libdata/firmware/radeon/hainan_smc.bin 2471.302Sriastrad /libdata/firmware/radeon/hawaii_ce.bin 2481.302Sriastrad /libdata/firmware/radeon/hawaii_mc.bin 2491.302Sriastrad /libdata/firmware/radeon/hawaii_me.bin 2501.302Sriastrad /libdata/firmware/radeon/hawaii_mec.bin 2511.302Sriastrad /libdata/firmware/radeon/hawaii_pfp.bin 2521.302Sriastrad /libdata/firmware/radeon/hawaii_rlc.bin 2531.302Sriastrad /libdata/firmware/radeon/hawaii_sdma.bin 2541.302Sriastrad /libdata/firmware/radeon/hawaii_smc.bin 2551.302Sriastrad /libdata/firmware/radeon/kabini_ce.bin 2561.302Sriastrad /libdata/firmware/radeon/kabini_me.bin 2571.302Sriastrad /libdata/firmware/radeon/kabini_mec.bin 2581.302Sriastrad /libdata/firmware/radeon/kabini_pfp.bin 2591.302Sriastrad /libdata/firmware/radeon/kabini_rlc.bin 2601.302Sriastrad /libdata/firmware/radeon/kabini_sdma.bin 2611.302Sriastrad /libdata/firmware/radeon/kaveri_ce.bin 2621.302Sriastrad /libdata/firmware/radeon/kaveri_me.bin 2631.302Sriastrad /libdata/firmware/radeon/kaveri_mec.bin 2641.302Sriastrad /libdata/firmware/radeon/kaveri_mec2.bin 2651.302Sriastrad /libdata/firmware/radeon/kaveri_pfp.bin 2661.302Sriastrad /libdata/firmware/radeon/kaveri_rlc.bin 2671.302Sriastrad /libdata/firmware/radeon/kaveri_sdma.bin 2681.302Sriastrad /libdata/firmware/radeon/mullins_ce.bin 2691.302Sriastrad /libdata/firmware/radeon/mullins_me.bin 2701.302Sriastrad /libdata/firmware/radeon/mullins_mec.bin 2711.302Sriastrad /libdata/firmware/radeon/mullins_pfp.bin 2721.302Sriastrad /libdata/firmware/radeon/mullins_rlc.bin 2731.302Sriastrad /libdata/firmware/radeon/mullins_sdma.bin 2741.302Sriastrad /libdata/firmware/radeon/oland_ce.bin 2751.302Sriastrad /libdata/firmware/radeon/oland_mc.bin 2761.302Sriastrad /libdata/firmware/radeon/oland_me.bin 2771.302Sriastrad /libdata/firmware/radeon/oland_pfp.bin 2781.302Sriastrad /libdata/firmware/radeon/oland_rlc.bin 2791.302Sriastrad /libdata/firmware/radeon/oland_smc.bin 2801.302Sriastrad /libdata/firmware/radeon/pitcairn_ce.bin 2811.302Sriastrad /libdata/firmware/radeon/pitcairn_mc.bin 2821.302Sriastrad /libdata/firmware/radeon/pitcairn_me.bin 2831.302Sriastrad /libdata/firmware/radeon/pitcairn_pfp.bin 2841.302Sriastrad /libdata/firmware/radeon/pitcairn_rlc.bin 2851.302Sriastrad /libdata/firmware/radeon/pitcairn_smc.bin 2861.302Sriastrad /libdata/firmware/radeon/tahiti_ce.bin 2871.302Sriastrad /libdata/firmware/radeon/tahiti_mc.bin 2881.302Sriastrad /libdata/firmware/radeon/tahiti_me.bin 2891.302Sriastrad /libdata/firmware/radeon/tahiti_pfp.bin 2901.302Sriastrad /libdata/firmware/radeon/tahiti_rlc.bin 2911.302Sriastrad /libdata/firmware/radeon/tahiti_smc.bin 2921.302Sriastrad /libdata/firmware/radeon/verde_ce.bin 2931.302Sriastrad /libdata/firmware/radeon/verde_mc.bin 2941.302Sriastrad /libdata/firmware/radeon/verde_me.bin 2951.302Sriastrad /libdata/firmware/radeon/verde_pfp.bin 2961.302Sriastrad /libdata/firmware/radeon/verde_rlc.bin 2971.302Sriastrad /libdata/firmware/radeon/verde_smc.bin 2981.302Sriastrad 2991.302Sriastrad We will re-import these radeon firmware images another way 3001.302Sriastrad later. 3011.302Sriastrad 3021.301Smartin20190727: 3031.301Smartin The uefi bootloader has gained tftp support and needs a clean 3041.301Smartin build. If you do update builds, manually clean its object 3051.301Smartin directory by something like: 3061.301Smartin cd sys/arch/i386/stand/efiboot && make clean 3071.301Smartin 3081.300Smartin20190723: 3091.300Smartin The jemalloc allocator in libc is now build without extended 3101.300Smartin debugging (for performance reasons). In update builds make sure 3111.326Sandvar to rebuild it completely, by removing all affected object files, 3121.300Smartin including compat builds, something like: 3131.300Smartin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 3141.300Smartin 3151.299Smrg20190207: 3161.299Smrg GCC 7 switched for many ports. Update builds are likely to fail. 3171.299Smrg 3181.298Smartin20180924: 3191.298Smartin A newer OpenSSL version has been imported. If you are doing 3201.298Smartin update builds, make sure to remove all old obj dirs, like: 3211.298Smartin cd /usr/obj && find . -type d -name openssl | xargs rm -rf 3221.298Smartin 3231.297Sjoerg20180717: 3241.297Sjoerg On aarch64 int64_t and related types have changed from long long 3251.297Sjoerg to long. This requires recompiling all C++ binaries. 3261.297Sjoerg 3271.296Smartin20180713: 3281.296Smartin On amd64 and i386 static binaries are now build position 3291.296Smartin independend. This requires recompilation of all object 3301.296Smartin files used to create the crunched /rescue binary. 3311.296Smartin Clean the rescue directory in your obj directory before 3321.296Smartin doing an update build, otherwise linking will fail. 3331.296Smartin 3341.293Sjakllsch20180414: 3351.293Sjakllsch Existing binutils was migrated to binutils.old. Manual 3361.293Sjakllsch removal of tools/binutils objects directory may be required 3371.293Sjakllsch to fix tools build failure. 3381.293Sjakllsch 3391.292Smrg20180311: 3401.292Smrg bdftopcf was updated and may need cleaning in the 3411.292Smrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are 3421.292Smrg link errors. 3431.292Smrg 3441.291Smrg20180212: 3451.291Smrg between OpenSSL and GCC updates, many things may fail to build. 3461.291Smrg any failure that looks like GCC or openssl is best handled by 3471.291Smrg a clean destdir and objdir. Full cleandir and destdir deletion 3481.291Smrg is recommended if build failures occur. 3491.291Smrg 3501.288Smartin20171225: 3511.288Smartin removal of the vadvise syscall requires manual removal of all 3521.288Smartin associated files from the libc build object directory (including 3531.289Schristos the .depend files) - a command like: 3541.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 3551.289Schristos For architectures that support multiple "compat" binary targets, 3561.289Schristos you'll need to cleanup both the regular libc directory and the 3571.290Smartin compat ones (the above command will do that). 3581.288Smartin 3591.287Skre20171010: 3601.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 3611.287Skre means that its objdir (or *.d and .depend at least) might need 3621.287Skre to be manually removed - or a build done once without -u. 3631.287Skre 3641.286Smrg20170822: 3651.286Smrg a new version of GMP has been imported and probably 3661.286Smrg will break parts of builds related to themselves or GCC, both 3671.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3681.286Smrg and MPC objdirs or build once without -u. 3691.286Smrg 3701.285Smrg20170816: 3711.285Smrg a new version of MPFR and MPC have been imported and probably 3721.285Smrg will break parts of builds related to themselves or GCC, both 3731.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 3741.285Smrg and MPC objdirs or build once without -u. 3751.285Smrg 3761.284Smartin20170402: 3771.284Smartin a new version of dhcpcd has been imported, which does not support 3781.284Smartin update builds from the previous version. Remove your 3791.284Smartin external/bsd/dhcpcd object dir or build once without -u. 3801.284Smartin 3811.281Sroy20170211: 3821.281Sroy a new terminfo database has been imported. 3831.281Sroy The structure of it has changed slightly from prior versions and 3841.281Sroy an updated tic tool is required. 3851.281Sroy If you build.sh, don't use -u 3861.281Sroy 3871.280Skre20170207: 3881.278Skre various arch dependent libc/exect.S files were removed 3891.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 3901.279Skre if it exists) or do a clean build. 3911.279Skre (This is a bug in the make system, it should be corrected without 3921.279Skre human intervention, but isn't.) 3931.278Skre 3941.277Smartin20170104: 3951.277Smartin xinput build options have changed. 3961.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 3971.277Smartin if you build.sh -u 3981.277Smartin 3991.276Smartin20170103: 4001.276Smartin a new version of flex has been imported. 4011.276Smartin Remove the file from obj (external/bsd/flex) 4021.276Smartin if you build.sh -u 4031.276Smartin 4041.275Sspz20161014: 4051.275Sspz a new version of OpenSSL has been imported. 4061.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 4071.275Sspz if you build.sh -u 4081.275Sspz 4091.274Smartin20161009: 4101.274Smartin a new version of dhcpcd has been imported with slightly changed 4111.274Smartin build infrastructure. When doing a build.sh -u this requires 4121.274Smartin pruning the external/bsd/dhcpcd objdir. 4131.274Smartin 4141.273Smrg20160914: 4151.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 4161.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 4171.273Smrg and a clean objdir. 4181.273Smrg 4191.272Sdholland20160527: 4201.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 4211.272Sdholland been enabled. (see the amd64 entry two down for further info) 4221.272Sdholland 4231.270Schristos20160418: 4241.270Schristos libedit needs manual removal of all autogenerated files since 4251.271Schristos some of them are not autogenerated anymore. Remember that there 4261.271Schristos might be two copies of libedit if your platform builds "compat". 4271.270Schristos 4281.268Sriastrad20160410: 4291.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 4301.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 4311.268Sriastrad executables, means all code, including executables and not just 4321.268Sriastrad shared libraries, is position-independent and hence able to be 4331.268Sriastrad relocated by ASLR, address space layout randomization. 4341.268Sriastrad 4351.268Sriastrad The change was made in Makefile variables for compiler and 4361.268Sriastrad linker flags, for which make(1) does not record dependencies, 4371.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 4381.268Sriastrad 4391.268Sriastrad Partial rebuilds with some modified source files will likely 4401.268Sriastrad fail when linking executables, since the linker refuses to mix 4411.268Sriastrad position-independent code with position-dependent code in 4421.268Sriastrad position-independent executables: 4431.268Sriastrad 4441.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 4451.268Sriastrad 4461.267Smrg20160401: 4471.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 4481.269Sdholland Some people have found that cleandir is not sufficient, so if 4491.269Sdholland in doubt delete the entire object directory tree for gcc. 4501.267Smrg 4511.266Saymeric20160306: 4521.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 4531.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 4541.265Saymeric non-NetBSD hosts if linked with stale object files produced 4551.265Saymeric while they included a non-NetBSD regex.h. 4561.265Saymeric In any case, you should "make cleandir" at least these tools 4571.265Saymeric before updating your toolchain. 4581.265Saymeric 4591.264Smartin20160125: 4601.264Smartin Dtrace has been enabled by default on some architectures. 4611.264Smartin When doing an update build, make sure to clean the etc/mtree 4621.264Smartin object directory before starting the build - otherwise the 4631.264Smartin needed directories in destdir will not be created. 4641.264Smartin An easy way to do this is: 4651.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 4661.264Smartin 4671.263Sdholland20150818: 4681.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 4691.263Sdholland again. 4701.263Sdholland 4711.262Schristos20150413: 4721.262Schristos New acpica requires "make cleandir" and reinstalling yacc 4731.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 4741.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 4751.262Schristos 4761.261Smartin20150404: 4771.261Smartin Lint changes require a full rebuild of the tool, so make 4781.261Smartin sure to build without -u option to build.sh, or manually 4791.261Smartin do a make cleandir in src/tools/lint1 and 4801.261Smartin src/usr.bin/xlint. 4811.261Smartin 4821.260Sskrll20150310: 4831.260Sskrll Improvements to openssl for arm mean that update builds of 4841.260Sskrll the openssl libraries will fail. A make cleandir in 4851.260Sskrll external/bsd/openssl/lib is needed 4861.260Sskrll 4871.258Smartin20141026: 4881.259Smsaitoh A mishap during the import of pppd may cause your corruption 4891.258Smartin in your cvs directory if you happened to do a cvs update 4901.258Smartin during a short period of time. To fix, just remove the 4911.258Smartin directory src/external/bsd/ppp/dist/pppd completely 4921.258Smartin and let cvs restore it on next update. 4931.258Smartin 4941.256Sapb20140721: 4951.256Sapb The src/external/mit/lua/src directory was accidentally created 4961.256Sapb and then deleted in the CVS repository. If you get errors like 4971.256Sapb 4981.256Sapb cvs [update aborted]: cannot open directory 4991.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 5001.256Sapb 5011.256Sapb then delete your local copy of that directory tree and try again. 5021.256Sapb 5031.255Sjoerg20140530: 5041.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 5051.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 5061.255Sjoerg 5071.251Smartin20140131: 5081.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 5091.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 5101.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 5111.251Smartin 5121.250Schristos20131227: 5131.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 5141.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 5151.250Schristos mode7 in your config file. Make sure you put the necessary restrict 5161.250Schristos statements to avoid being exposed. 5171.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 5181.250Schristos to make clean in libc 5191.250Schristos 5201.249Smrg20131129: 5211.249Smrg The GMP sources were updated, and builds will likely fail without 5221.249Smrg cleaning their build trees for both tools and in-tree, like below. 5231.249Smrg 5241.248Smrg20131128: 5251.248Smrg The MPC and MPFR sources were updated, and builds may require their 5261.248Smrg tools and in-tree directories cleaned for successful updates. 5271.248Smrg 5281.246Smartin20130605: 5291.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 5301.247Sspz to IPSEC (and the older IPSEC version removed). 5311.247Sspz 5321.247Sspz20130605: 5331.320Sandvar Previous freetype installations erroneously installed private 5341.246Smartin header files. If you are building against a non-empty $DESTDIR, 5351.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 5361.246Smartin 5371.245Smrg20130531: 5381.245Smrg The xdm update may cause build failure due to xdm.man being 5391.245Smrg in the obj tree. Make sure to ensure any like this: 5401.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 5411.245Smrg is fixed by deleting the xdm.man in the obj tree. 5421.245Smrg 5431.244Smrg20130530: 5441.244Smrg Updates of many xsrc packages will leave old .pc files around. 5451.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 5461.244Smrg 5471.242Schristos20130301: 5481.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 5491.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 5501.242Schristos 5511.238Sdholland20120726: 5521.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 5531.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 5541.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 5551.241Swiz some cases may succeed and install broken OpenSSL libraries that 5561.240Sdholland cause third-party software to link incorrectly and/or crash. 5571.238Sdholland 5581.237Swiz20120507: 5591.241Swiz The database schema for makemandb was changed. You will 5601.237Swiz need to update the database using 'makemandb -f' or wait 5611.237Swiz for the next weekly run to fix it. 5621.237Swiz 5631.236Sbsh20120319: 5641.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 5651.236Sbsh size of db_symtab automatically. You need to update dbsym in 5661.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 5671.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 5681.236Sbsh mk.conf. 5691.236Sbsh 5701.235Sjoerg20120216: 5711.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 5721.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 5731.239Sdholland and 20120216, daily and weekly could have created an unreadable 5741.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 5751.235Sjoerg the next run of weekly will fix it. 5761.233Sjoerg 5771.232Schristos20111227: 5781.232Schristos If you built between 20111225 and 20111227 you need to remove 5791.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 5801.232Schristos bump has been reverted. 5811.232Schristos 5821.231Stls20111125: 5831.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 5841.231Stls means it should no longer be explicitly listed in kernel 5851.231Stls configuration files. The line "pseudo-device rnd" should be 5861.231Stls removed from any custom kernel config files users may have. 5871.231Stls 5881.230Stls20111119: 5891.230Stls A problem with the datastructures used by the rndctl(8) 5901.230Stls utility (pointers in datastructures in an array, making 32->64 5911.230Stls bit compatibility very painful) has been fixed in a 5921.230Stls non-backwards-compatible way. If you replace your kernel, 5931.230Stls replace your rndctl executable too. 5941.241Swiz 5951.229Sjym20111001: 5961.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 5971.229Sjym changed and their new version is not backward compatible with the old 5981.241Swiz one. So ensure that all consumers of these functions (currently: 5991.229Sjym quota2 code and its tests) are updated together with the new lib. 6001.229Sjym 6011.228Smrg20110817: 6021.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 6031.228Smrg DESTDIR for them should be deleted before updating. 6041.228Smrg 6051.227Sriastrad20110806: 6061.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 6071.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 6081.227Sriastrad 6091.226Smrg20110805: 6101.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 6111.226Smrg the tree to be cleaned. Best to delete both objdir and 6121.226Smrg DESTDIR before running this update. So far, only the 6131.226Smrg sparc64, mips and powerpc platforms have changed. 6141.226Smrg 6151.225Smatt20110803: 6161.241Swiz The layout of external/public-domain/xz has changed. To do an 6171.225Smatt update build you will have to remove the contents of the OBJDIR 6181.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 6191.225Smatt is now a directory. 6201.225Smatt 6211.223Sjoerg20110410: 6221.241Swiz The configuration of src/tools/gcc has changed. To do an 6231.224Sdholland update build you have to clean both tools/binutils and 6241.224Sdholland tools/gcc by hand. 6251.223Sjoerg 6261.222Splunky20110328: 6271.222Splunky Building the Xorg binary was moved into a subdirectory to fix 6281.241Swiz ordering issues with "make all". It may be necessary to remove 6291.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 6301.222Splunky if your update build fails, as the "Xorg" entry there is now a 6311.222Splunky directory. 6321.222Splunky 6331.220Sjoerg20110121: 6341.221Slukem Assembler files no longer use -traditional-cpp. This can break 6351.220Sjoerg the build of individual parts of the tree. This is handled 6361.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 6371.220Sjoerg and re-run config(1) for any kernel configurations as needed. 6381.218Sjoerg 6391.217Sjruoho20101217: 6401.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 6411.241Swiz by default. It may be necessary to manually update passwd(5) and 6421.217Sjruoho group(5) in order to make the program work with existing setups. 6431.217Sjruoho 6441.216Schristos20101125: 6451.327Sandvar The latest changes to setenv(3) disallow setting environment 6461.241Swiz variables with names that contain '='. Revision 1.18 of env.c 6471.241Swiz assumed that this was allowed. Installing a new libc with an 6481.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 6491.216Schristos break which affects the autoconf tests for dependency finding, 6501.216Schristos so building gcc will end up printing: 6511.216Schristos checking dependency style of gcc... none 6521.216Schristos configure: error: no usable dependency style found 6531.216Schristos Fix it by rebuilding and re-installing env. 6541.138Slukem 6551.215Smrg20101119: 6561.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 6571.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 6581.215Smrg have any build problems with xsrc, or problems with mismatched 6591.215Smrg versions between xorg-server and drivers. 6601.215Smrg 6611.213Sjmmv20100604: 6621.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 6631.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 6641.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 6651.213Sjmmv trees by hand. 6661.213Sjmmv 6671.211Stnozaki20100522: 6681.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 6691.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 6701.212Smrg build problems with xsrc. 6711.212Smrg 6721.212Smrg20100522: 6731.320Sandvar private section of <ctype.h> was split, and now mklocale(1) 6741.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 6751.211Stnozaki 6761.210Schristos20100520: 6771.241Swiz The location of the xkb compiled descriptions has changed. Please 6781.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 6791.210Schristos 6801.209Snjoly20100222: 6811.209Snjoly The shared objects file extension has been changed from .so to 6821.209Snjoly .pico, in order to avoid conflicts with shared libraries names 6831.209Snjoly libXX.so. All now stale regular .so files can be removed from 6841.209Snjoly your object directories. 6851.209Snjoly 6861.208Sroy20100204: 6871.208Sroy The termcap database has been removed from the sources, 6881.208Sroy but has not been marked obsolete so it is not removed 6891.208Sroy from the system when upgrading. 6901.208Sroy As such, you will need to remove them from your object 6911.208Sroy and destination directories. 6921.208Sroy 6931.203Sdyoung20091101: 6941.205Sdholland After updating, it may be necessary to make the 'cleandir' 6951.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 6961.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 6971.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 6981.203Sdyoung 6991.202Smrg20091001: 7001.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 7011.206Sdholland before building a kernel, or the build fails on cpufunc.S. 7021.206Sdholland 7031.206Sdholland20091001: 7041.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 7051.202Smrg symlink, failing the build. Delete the link, and the subdir 7061.202Smrg it is in, and retry your build. 7071.202Smrg 7081.201Sdsl20090718: 7091.201Sdsl libc build changed so that strchr() provides the extra entry 7101.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 7111.201Sdsl may fail because the archive contains the unwanted index.o. 7121.201Sdsl (Similarly for strrchr() and rindex().) 7131.201Sdsl 7141.198Smrg20090709: 7151.198Smrg Native Xorg was upgraded again. Builds will probably fail again 7161.198Smrg without a clean objdir, at least for src/external/mit/xorg. 7171.198Smrg 7181.197Smrg20090616: 7191.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 7201.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 7211.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 7221.197Smrg subdirectory has been changed into a file, and this needs to 7231.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 7241.197Smrg 7251.195Sperry20090501: 7261.195Sperry Several new functions were added to string.h/libc, and this 7271.195Sperry can cause autoconf problems during the tool build for people 7281.241Swiz who fail to clean out their tools objects properly. If you 7291.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 7301.195Sperry failure during the tool build, clean out all your tools 7311.195Sperry objects and start again. 7321.195Sperry 7331.194Smrg20090325: 7341.194Smrg The i386 port was switched to i486 default toolchain. This requires 7351.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 7361.194Smrg 7371.192Sskrll20090126: 7381.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 7391.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 7401.207Smbalmer to avoid using the old assembly stub. 7411.192Sskrll 7421.191Sjoerg20090202: 7431.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 7441.320Sandvar detection. It is recommended to rebuild the cache with 7451.191Sjoerg ``pkg_admin rebuild''. 7461.191Sjoerg 7471.184Schristos20090110: 7481.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 7491.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 7501.188Schristos This is needed even in the MODULAR kernel because there is 7511.188Schristos conditionally compiled code in rtsock.c. 7521.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 7531.184Schristos before installing. 7541.184Schristos 3. If you don't use build.sh and you build directly to root, and 7551.241Swiz your build breaks in the middle, don't despair. Make sure headers 7561.184Schristos are installed properly, and start building libraries first libc 7571.184Schristos and libutil, install them and then continue building all the 7581.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 7591.184Schristos the new libraries are installed, you can restart the build. 7601.184Schristos 4. If you compile packages and you notice link time warnings, 7611.189Shubertf rebuild the required packages to update their shared libraries. 7621.189Shubertf Any package you rebuild will require rebuilding all the packages 7631.189Shubertf that depend on it. 7641.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 7651.186Schristos will be upgraded and it will not be backwards compatible. 7661.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 7671.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 7681.241Swiz for utmp. You are better off removing the old files after 7691.190Sapb upgrading. The automated clearing of /var/run during 7701.190Sapb boot, and the automated rotating of files in /var/log by 7711.190Sapb newsyslog(8), may mean that you do not have to remove the 7721.190Sapb files manually. 7731.190Sapb 7. The optional accounting file (/var/account/acct, see 7741.190Sapb accton(8)) has not been versioned, and will need to be 7751.190Sapb removed. The automatic rotation of the accounting file by 7761.190Sapb /etc/daily limits the bad consequences of failure to remove 7771.190Sapb the file. 7781.196Sdholland 8. Application software that writes time_t to binary files on 7791.241Swiz disk will break or need attention. Most notably: if you are 7801.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 7811.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 7821.185Sjmcneill 7831.183Spgoyette20081219: 7841.183Spgoyette config(1) has been updated, and one of the files it creates - 7851.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 7861.183Spgoyette (done automatically by build.sh) and then you need to rerun 7871.183Spgoyette config on all kernel configuration files before rebuilding those 7881.183Spgoyette kernels. 7891.183Spgoyette 7901.181Scube20081205: 7911.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 7921.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 7931.181Scube set and will appear as extra files for MKX11=no update builds. 7941.178Slukem 7951.179Stsutsui20081122: 7961.182Stsutsui On i386, various kernel options(4) in GENERIC including 7971.180Swiz file systems have been disabled and moved into kernel modules. 7981.180Swiz Before trying a new GENERIC kernel, you have to prepare the 7991.179Stsutsui following files as well as a new GENERIC kernel: 8001.179Stsutsui 8011.179Stsutsui - build and install kernel modules from src/sys/modules 8021.179Stsutsui 8031.179Stsutsui - install the latest bootloader, which will load a module 8041.180Swiz for the file system from which the kernel is loaded automatically 8051.179Stsutsui 8061.180Swiz If you have to load your kernel from a file system which is not of 8071.180Swiz the same type as the root file system, you have to load the necessary 8081.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 8091.179Stsutsui 8101.178Slukem20080827: 8111.178Slukem If you built and installed a libc from sources between 8121.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 8131.178Slukem which results in false errors reported by lint(1). 8141.178Slukem Since this breaks the libc build itself, manual help is 8151.180Swiz needed -- lint must be disabled temporarily, e.g.: 8161.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 8171.178Slukem 8181.177Schristos20080813: 8191.177Schristos MKDEBUG build was broken because the .depend files did not know 8201.241Swiz about .go files. You need to remove all .depend files and rebuild. 8211.177Schristos 8221.200Sdholland20080802: 8231.200Sdholland A regression in binary compatibility for pthread_mutex_t has 8241.241Swiz been fixed. Unfortunately, the price is breaking compatibility 8251.200Sdholland for -current. 8261.200Sdholland 8271.200Sdholland Threaded programs (using libpthread) and C++ programs (using 8281.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 8291.200Sdholland be recompiled. 8301.200Sdholland 8311.200Sdholland One way to find affected pkgsrc packages: 8321.200Sdholland 8331.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 8341.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 8351.200Sdholland 8361.175Ssimonb20080731: 8371.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 8381.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 8391.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 8401.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 8411.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 8421.176Ssimonb also requires the super block to be in the UFS2 format. You 8431.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 8441.175Ssimonb 8451.174Slukem20080721: 8461.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 8471.174Slukem isn't defined. 8481.174Slukem 8491.173Sfreza20080531: 8501.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 8511.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 8521.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 8531.241Swiz won't work correctly. The following sequence of commands: 8541.173Sfreza 8551.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 8561.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 8571.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 8581.173Sfreza 8591.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 8601.173Sfreza 8611.172Slukem20080503: 8621.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 8631.172Slukem 8641.171She20080521: 8651.171She For a while, unprivileged UPDATE builds would fail to 8661.171She succeed at the checkflist stage, complaining that 8671.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 8681.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 8691.171She If you already hit this problem, update the .mk file, 8701.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 8711.171She 8721.174Slukem20080303: 8731.174Slukem Linker warnings are now fatal if $WARNS>0. 8741.174Slukem 8751.170Schristos20080126: 8761.170Schristos The posix_fadvise system call has been changed from an assembly 8771.241Swiz stub, to a c file that calls an assembly stub. You need to 8781.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 8791.170Schristos avoid using the old assembly stub. 8801.170Schristos 8811.168Sjoerg20071209: 8821.241Swiz The acpiec(4) driver has been split into two attachments. If you 8831.168Sjoerg get ACPI errors before the attachment, please update your kernel 8841.169Swiz configuration file appropriately or see GENERIC for more details. 8851.168Sjoerg 8861.166Sxtraeme20071115: 8871.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 8881.166Sxtraeme argument specified in the kernel configuration file is not valid 8891.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 8901.241Swiz rather than the EC address port. Please update your kernel 8911.167Swiz configuration file appropriately or see GENERIC for more details. 8921.166Sxtraeme 8931.165Sjmmv20071028: 8941.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 8951.165Sjmmv You need to update any custom kernel configuration file you have 8961.165Sjmmv to remove any references to pccons (which includes removing the 8971.165Sjmmv now useless XSERVER option) and replace them with the correct 8981.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 8991.165Sjmmv for more details. 9001.165Sjmmv 9011.164Sgdt20070913: 9021.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 9031.164Sgdt enumerate interfaces was fixed. The bug began to cause 9041.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 9051.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 9061.164Sgdt could not enumerate interfaces. (These are noted because 9071.164Sgdt normal kernel/userspace version matching hygiene is not 9081.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 9091.164Sgdt and userland are from after 20070913. 9101.164Sgdt 9111.163Sjoerg20070703: 9121.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 9131.199Sdholland calls the target-specific strip program, and the logic to pass 9141.199Sdholland down STRIP from make has been removed. This requires a 9151.199Sdholland re-installation of tools. 9161.163Sjoerg 9171.161Sdsl20070422: 9181.161Sdsl The way OS emulations lookup filenames inside the emulation root 9191.161Sdsl has been changed. Rather than modify the pathname (and copy back 9201.161Sdsl to userspace) namei() and lookup() directly check the emulation 9211.241Swiz root. One side effect is that absolute symlinks inside the emulated 9221.167Swiz root file system will be relative to that file system - unless they 9231.161Sdsl start /../ this is useful when the emulated root is a real install 9241.161Sdsl that has such links. 9251.161Sdsl This might affect symlinks that have been added to reference outside 9261.161Sdsl the emulated root. 9271.161Sdsl 9281.160Sjmcneill20070412: 9291.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 9301.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 9311.160Sjmcneill example. 9321.160Sjmcneill 9331.159Sgdt20070319: 9341.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 9351.159Sgdt on many platforms due to incorrect flags settings. If you 9361.159Sgdt updated and built after about 20070315, do "nbmake-$arch 9371.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 9381.159Sgdt rebuild of object files that might have been built 9391.159Sgdt incorrectly, and ensure that you have at least 9401.159Sgdt src/lib/libc/Makefile 1.130. 9411.159Sgdt 9421.241Swiz20070210: 9431.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 9441.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 9451.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 9461.158Sdbj will allow dependencies on those files to get get rebuilt 9471.158Sdbj 9481.157Sapb20070209: 9491.157Sapb The threading model was changed when the newlock2 branch 9501.157Sapb was merged to NetBSD-current. If you boot with a new 9511.157Sapb kernel (version 4.99.10), then you also need a new pthread 9521.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 9531.157Sapb an old kernel, then you need the old pthread library 9541.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 9551.157Sapb the pthread library in sync, old threaded applications should 9561.157Sapb continue to work with an old or new kernel. Note that named(8) 9571.157Sapb is the only threaded application in the base system. 9581.157Sapb 9591.154She20061214: 9601.154She Following the move of string_to_flags() and flags_to_string() 9611.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 9621.154She will need to do a "make cleandir" in 9631.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 9641.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 9651.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 9661.156She as the installation images in distrib/ 9671.154She in order to excise stale references to the old stat_flags.h header 9681.154She file in the ls sources -- stat_flags.h has been removed. 9691.154She 9701.152Schristos20061108: 9711.152Schristos The configure script used in the src/tools/gcc compiler has been 9721.152Schristos changed to indicate that our libc has ssp support built-in and 9731.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 9741.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 9751.152Schristos 9761.151Srpaulo20061009: 9771.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 9781.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 9791.151Srpaulo 9801.150Sbjh2120060814: 9811.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 9821.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 9831.150Sbjh21 kernel configuration for an example. X servers from the last 9841.150Sbjh21 few years should cope. 9851.150Sbjh21 9861.149Schristos20060703: 9871.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 9881.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 9891.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 9901.149Schristos 9911.148Sdogcow20060627: 9921.148Sdogcow socket(2) has changed, and its system call has been versioned. 9931.148Sdogcow For userlands with the old version of socket(2), make sure that 9941.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 9951.148Sdogcow errors will result. 9961.148Sdogcow 9971.1SabsHints for a more successful build: 9981.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9991.123Sjmc Use build.sh, but do not use its "expert mode": 10001.132Sjmmv This will automatically build the tools in the 10011.123Sjmc correct order, and it will keep the tools and the 10021.123Sjmc new build products from interfering with the running 10031.123Sjmc system. This will allow you to ignore most of the 10041.123Sjmc other advice in this file. 10051.2Smrg Build a new kernel first: 10061.2Smrg This makes sure that any new system calls or features 10071.2Smrg expected by the new userland will be present. This 10081.2Smrg helps to avoid critical errors when upgrading. 10091.1Sabs Use object directories: 10101.1Sabs This helps to keep stale object 10111.1Sabs files from polluting the build if a Makefile "forgets" 10121.1Sabs about one. It also makes it easier to clean up after 10131.1Sabs a build. It's also necessary if you want to use the 10141.1Sabs same source tree for multiple machines. 10151.123Sjmc To use object directories with build.sh: 10161.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 10171.123Sjmc To use object directories without using build.sh: 10181.1Sabs a) cd /usr/src ; make cleandir 10191.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 10201.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 10211.1Sabs d) cd /usr/src ; make build 10221.2Smrg Note that running "make obj" in a directory will create 10231.2Smrg in obj.$MACHINE directory. 10241.1Sabs Build to a DESTDIR: 10251.123Sjmc This helps to keep old installed files (especially libraries) 10261.123Sjmc from interfering with the new build. 10271.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 10281.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 10291.123Sjmc environment variable before running make build. It should be 10301.123Sjmc set to the pathname of an initially empty directory. 10311.123Sjmc Problems: if you do not use build.sh, you might need to 10321.123Sjmc update critical utilities without using DESTDIR since 10331.123Sjmc nothing is executed from what is installed in DESTDIR. 10341.123Sjmc (See critical utils, below.) 10351.1Sabs Build often: 10361.1Sabs This keeps critical utilities current enough to not choke 10371.1Sabs on any other part of the source tree that depends on up to 10381.123Sjmc date functionality. If you use build.sh, you should not have 10391.123Sjmc this problem. 10401.241Swiz 10411.1SabsWhat to do if things don't work: 10421.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10431.230StlsWhen things don't work there are usually a few things that commonly 10441.1Sabsshould be done. 10451.1Sabs 1) make includes 10461.1Sabs This should be done automatically by make build. 10471.1Sabs 2) cd share/mk && make install 10481.1Sabs Again, automatically done by make build. 10491.1Sabs 10501.1SabsFailsafe rebuild of a small part of the tree: 10511.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10521.1SabsTo make sure you rebuild something correctly you want to do 10531.1Sabssomething like the following: 10541.1Sabs 1) Make sure the includes and .mk files are up to date. 10551.1Sabs 2) Make sure any program used to build the particular 10561.1Sabs utility is up to date. (yacc, lex, etc...) 10571.1Sabs 3) cd ...path/to/util... 10581.1Sabs make cleandir 10591.1Sabs rm ...all obj directories... 10601.1Sabs make cleandir # yes, again 10611.1Sabs make obj 10621.1Sabs make depend && make 10631.1Sabs 10641.1SabsFailsafe rebuild of the entire tree: 10651.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 10661.1SabsIf you really want to make sure the source tree is clean and 10671.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 10681.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 10691.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 10701.1Sabs 10711.1Sabs---cut here--- 10721.1Sabs#!/bin/sh 10731.1Sabs. /etc/mk.conf 10741.1Sabs 10751.58Slukemif [ -z $NETBSDSRCDIR ] ; then 10761.58Slukem NETBSDSRCDIR=/usr/src 10771.1Sabsfi 10781.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 10791.1Sabs echo Unable to find sources 10801.1Sabs exit 1 10811.1Sabsfi 10821.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 10831.1Sabs 10841.1Sabsif [ -z $BSDOBJDIR ] ; then 10851.1Sabs BSDOBJDIR=/usr/obj 10861.1Sabsfi 10871.1Sabsif [ -d $BSDOBJDIR ] ; then 10881.1Sabs rm -rf $BSDOBJDIR 10891.1Sabsfi 10901.1Sabs 10911.58Slukemcd $NETBSDSRCDIR && make cleandir 10921.1Sabs 10931.1Sabs---cut here--- 10941.1Sabs 10951.1SabsCritical utilities: 10961.1Sabs^^^^^^^^^^^^^^^^^^^ 10971.3Sitojun usr.bin/compile_et 10981.1Sabs usr.bin/make 10991.1Sabs usr.bin/yacc 11001.1Sabs usr.bin/lex 11011.11Slukem usr.bin/xlint 11021.142Sdrochner usr.bin/config 11031.1Sabs 11041.34SsimonbOther problems and possible solutions: 11051.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 11061.1SabsSymptom:Complaints involving a Makefile. 11071.17SerhFix: Rebuild usr.bin/make: 11081.17Serh cd usr.bin/make && make && make install 11091.111Ssimonb Or, a failsafe method if that doesn't work: 11101.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 11111.17Serh 11121.1SabsFix: Make sure .mk files are up to date. 11131.1Sabs cd share/mk && make install 11141.2Smrg 11151.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 11161.142SdrochnerFix: Rebuild usr.bin/config 11171.1Sabs 11181.1SabsSymptom: 11191.1SabsFix: Rebuild usr.bin/yacc 11201.1Sabs 11211.1SabsSymptom: 11221.1SabsFix: Rebuild usr.bin/lex 11231.1Sabs 11241.1SabsSymptom: 11251.1SabsFix: rm /usr/lib/libbfd.a 11261.4Sitojun 11271.4SitojunSymptom:Obsolete intermediate files are used during compilation 11281.4SitojunFix: Try the following sequence of commands in the directory in question. 11291.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 11301.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 11311.4Sitojun may remain. The command tries to clean everything up) 11321.5Swiz 11331.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 11341.207Smbalmer pointer type 11351.5SwizFix: Rebuild and install usr.bin/menuc 11361.12Sitojun 11371.12SitojunSymptom:mklocale not found during build in share/locale/ctype 11381.12SitojunFix: Build and install usr.bin/mklocale 11391.13Sdogcow 11401.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 11411.13SdogcowFix: Rebuild and install lib/libc 11421.13Sdogcow 11431.142SdrochnerSymptom:usr.bin/config fails to build. 11441.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 11451.13Sdogcow 11461.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 11471.19ScgdFix: Rebuild and install lib/libc 11481.24Sabs 11491.24SabsSymptom:lint does not understand the '-X' option 11501.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 11511.223Sjoerg 11521.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 11531.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 11541.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 11551.257Sapb 11561.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 11571.257Sapb No such file or directory. 11581.257SapbCause: If a directory is created by mistake, then it is sometimes 11591.257Sapb deleted from the CVS repository using administrative commands 11601.257Sapb that bypass the normal cvs access controls. If your cvs working tree 11611.257Sapb contains references to a directory that has been deleted on the 11621.257Sapb server in this way, then "cvs update" reports this error. 11631.257SapbFix: Recursively delete the affected directory from your working tree 11641.257Sapb and try the update again. 1165