UPDATING revision 1.343
1$NetBSD: UPDATING,v 1.343 2023/08/28 22:25:49 riastradh Exp $ 2 3This file (UPDATING) is intended to be a brief reference to recent 4changes that might cause problems in the build process, and a guide for 5what to do if something doesn't work. 6 7For a more detailed description of the recommended way to build NetBSD 8using build.sh, see the BUILDING file. 9 10Note that much of the advice in this UPDATING file was written before 11build.sh existed. Nevertheless, the advice here may be useful for 12working around specific problems with build.sh. 13 14Sections are marked with "^^^^^". After the section on "Recent changes" 15are several sections containing more general information. 16 17See also: BUILDING, build.sh, Makefile. 18 19Recent changes: 20^^^^^^^^^^^^^^^ 21 2220230828: 23 If: 24 - you updated to current and ran postinstall between 20230826 25 and 20230828 inclusive, and 26 - you are not using anything outside the base system to 27 populate /etc/openssl/certs (e.g., manually adding 28 certificates or using ca-certificates or mozilla-rootcerts or 29 mozilla-rootcerts-openssl from pkgsrc), 30 delete /etc/openssl/certs and rerun postinstall or just 31 `certctl rehash'. 32 33 Otherwise, certctl(8) will think someone else has left 34 /etc/openssl/certs in the way and will avoid clobbering it on 35 upgrade from older NetBSD. 36 3720230718: 38 build.sh will use mk.conf in the same directory as build.sh instead 39 of /etc/mk.conf, unless MAKECONF is already defined in the environment. 40 4120230714: 42 Import of gcc 10.5 requires a clean build of at least tools/gcc 43 and external/gpl3/gcc* object directories. An update build 44 without cleaning will result in obscure failures in rare corner 45 cases. 46 4720230604: 48 Building native kernels with the installed make(1) instead of 49 the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland 50 has not been updated. Note that this is an unsupported build 51 configuration (but usually works if userland is -current enough). 52 5320230523: 54 ctfmerge was fixed as macOS host tool. This may require a clean tools 55 rebuild to detect the update to tools/compat/configure. 56 5720230515: 58 New openssl build requires removal of the crypto/external/bsd/openssl 59 and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierachy. 60 Otherwise test results may be wrong due to wrong "golden" output 61 files being installed. 62 6320230322: 64 Fixes for moved /lib/libisns* mean that builds will complain about 65 ./usr/lib/libisns* being missing until src/lib/libisns is forced 66 to (re)install the files, including the symlinks. The simplest 67 way is to clean this subdir before building. 68 6920230112: 70 New binutils require an updated ld.elf_so. If you are doing 71 (unsupported) in-place self builds (with the -E flag to build.sh), 72 make sure to have installed latest ld.elf_so before you rebuild 73 userland. 74 7520221116: 76 The addition to NetBSD's version of UFS2 of support for extended 77 attributes broke backward compatibility with previous releases 78 of NetBSD, so UFS2 has been restored to being compatible with 79 previous NetBSD releases by disabling extended attributes. 80 (Note that ACLs are implemented as extended attributes, so 81 this changes disables ACLs as well.) 82 83 Support for UFS2 with extended attributes is now available in a new 84 UFS variant called UFS2ea. If you have created extended attributes 85 in an original UFS2 file system then "fsck -p" will now fail due to 86 the unexpected presence of extended attributes and "fsck -y" will 87 remove all extended attributes. If you wish to preserve extended 88 attributes rather than delete them, there is a utility to convert 89 a UFS2 file system to UFS2ea and leave extended attributes in place, 90 but this should be used with caution since it will preserve any 91 extended attributes that have been corrupted by the backward 92 incompatibility too. 93 94 If you wish to use a UFS2ea file system as your root file system, 95 then you will need to update your boot loader to a version that 96 supports UFS2ea. 97 98 For more information, see: 99 https://wiki.netbsd.org/features/UFS2ea 100 10120221111: 102 The new libdrm import worsened the conflict issues for the 103 kdump/ktruss ioctl, and i915 now conflicts with base, and has 104 been turned off. This will cause update build issues like: 105 106 kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 107 undeclared here (not in a function); 108 did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 109 110 You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 111 11220220921: 113 Since the kernel version was bumped to 9.99.100, the bootloader 114 must be updated on x86 or EFI boot platforms in order to load 115 modules from boot.cfg(5) or interactively at the bootloader 116 prompt. 117 118 The kernel can still load modules at runtime, with modload(8) 119 or modules.conf(5), with no bootloader update. This will not 120 affect release branches because it only applies to patch 121 numbers >=100. 122 123 On x86 (i386 or amd64) with BIOS boot, this requires copying a 124 new /usr/mdec/boot to /boot. You can build this in the destdir 125 by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 126 sys/arch/i386/stand. 127 128 On platforms with EFI boot (including x86 with EFI boot), this 129 requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 130 directory on the EFI system partition. The boot*.efi file is: 131 132 aarch64 bootaa64.efi 133 amd64 bootx64.efi 134 arm bootarm.efi (32-bit arm) 135 i386 bootx32.efi 136 137 You can build this in the destdir by running 138 `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 139 sys/stand/efiboot/boot*. 140 14120220821: 142 Support for building extsrc/ has been deprecated. 143 EXTSRCSRCDIR and MKEXTSRC have been deprecated. 144 14520220714: 146 Updates to xorg-server and associated drivers may cause builds to 147 fail. Cleaning both DESTDIR and the xorg build tree may be needed. 148 14920220628: 150 Changes in the build of src/games/robots require a clean build 151 of that program. 152 15320211116: 154 Changes in the xorg build require clean obj dirs for external/mit/xorg 155 (or a full clean/non-update build). 156 15720211112: 158 Device tree sources were updated for evbarm. Some device nodes 159 (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 160 16120211014: 162 MKPIE default for aarch64 has changed, a clean build is required. 163 16420210917: 165 Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 166 ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 167 and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 168 16920210711: 170 Updated GMP sources may require cleaning in tools/gmp and/or in 171 external/lgpl3/gmp/lib, particularly if GCC itself does not build. 172 17320210417: 174 GCC 10 was enabled for several platforms. If builds fail in either 175 tools/gcc or external/gpl/gcc, first try cleaning those objects and 176 removing the $DESTDIR/usr/include/g++ subdirectory. 177 17820201230: 179 lint1/ops.c is no longer autogenerated. If this makes the build 180 fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*. 181 18220201016: 183 MIPS kernel modules have been disabled until they work. This will 184 turn up in extra files in the DESTDIR, which should be cleaned. 185 18620200925: 187 GNU MPC and MPFR have been updated. At least MPFR needs cleaning 188 in both the tools and external dirs. 189 19020200912: 191 GCC 9 has arrived for Arm and x86 platforms, and will be coming 192 for several more, as will binutils 2.34. Clean as required. 193 19420200907: 195 GCC 9 is coming, and binutils has been updated for MIPS. This 196 probably requires cleaning the tools/binutils. 197 19820200811: 199 GCC updates may require cleaning the objdir. This may occur 200 due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 201 GCC 9 upgrade. 202 20320200614: 204 blacklist* has been renamed to blocklist*. postinstall(8) 205 should handle the migration. 206 20720200601: 208 Due to a mistake in LIBISPRIVATE handling, .so libraries were 209 created in the build directories and need cleaning. 210 21120200311: 212 GCC 8 ports will need cleaning in src/tools/gcc and 213 src/external/gpl3/gcc due to GCC 8.4 update. 214 21520191118: 216 More architectures were switched to gcc8: 217 i386, ia64 powerpc64, sparc, sparc64, arm 218 The same comments as in 20191022 apply. 219 22020191112: 221 The LLVM update requires a clean rebuild for all architectures using 222 LLVM during the tools build phase (i386, amd64, aarch64). 223 22420191022: 225 Ports amd64 and aarch64 switched to GCC 8.3 by default. 226 In-place ("expert mode", build.sh -E) builds are not supported 227 when going from a GCC 7 userland to GCC 8. Do a regular 228 build to a different DESTDIR (or preferably: build.sh -U) at least 229 once and install sets, or download comp.{tar.xz,tgz} from the 230 daily builds and install that before doing the next in-place build. 231 23220191001: 233 GCC 8.3 was imported. Builds of src/tools/gcc may fail if 234 old builds with GCC 7 output now uses GCC 8. Clean this 235 directory, and also clean src/external/gpl3/gcc. 236 23720190903: 238 Files with names that coincide with existing files' names on 239 case-insensitive file systems were inadvertently committed, for 240 radeon GPU firmware. We cannot mark these as obsolete for 241 postinstall to fix, so if you updated src since 2019-08-26, and 242 ran build.sh distribution or ran build.sh release, you must 243 manually delete the following files in your DESTDIR (which is 244 usually $OBJDIR/destir.$ARCH), or from / if you have installed 245 them: 246 247 /libdata/firmware/radeon/bonaire_ce.bin 248 /libdata/firmware/radeon/bonaire_mc.bin 249 /libdata/firmware/radeon/bonaire_me.bin 250 /libdata/firmware/radeon/bonaire_mec.bin 251 /libdata/firmware/radeon/bonaire_pfp.bin 252 /libdata/firmware/radeon/bonaire_rlc.bin 253 /libdata/firmware/radeon/bonaire_sdma.bin 254 /libdata/firmware/radeon/bonaire_smc.bin 255 /libdata/firmware/radeon/bonaire_uvd.bin 256 /libdata/firmware/radeon/hainan_ce.bin 257 /libdata/firmware/radeon/hainan_mc.bin 258 /libdata/firmware/radeon/hainan_me.bin 259 /libdata/firmware/radeon/hainan_pfp.bin 260 /libdata/firmware/radeon/hainan_rlc.bin 261 /libdata/firmware/radeon/hainan_smc.bin 262 /libdata/firmware/radeon/hawaii_ce.bin 263 /libdata/firmware/radeon/hawaii_mc.bin 264 /libdata/firmware/radeon/hawaii_me.bin 265 /libdata/firmware/radeon/hawaii_mec.bin 266 /libdata/firmware/radeon/hawaii_pfp.bin 267 /libdata/firmware/radeon/hawaii_rlc.bin 268 /libdata/firmware/radeon/hawaii_sdma.bin 269 /libdata/firmware/radeon/hawaii_smc.bin 270 /libdata/firmware/radeon/kabini_ce.bin 271 /libdata/firmware/radeon/kabini_me.bin 272 /libdata/firmware/radeon/kabini_mec.bin 273 /libdata/firmware/radeon/kabini_pfp.bin 274 /libdata/firmware/radeon/kabini_rlc.bin 275 /libdata/firmware/radeon/kabini_sdma.bin 276 /libdata/firmware/radeon/kaveri_ce.bin 277 /libdata/firmware/radeon/kaveri_me.bin 278 /libdata/firmware/radeon/kaveri_mec.bin 279 /libdata/firmware/radeon/kaveri_mec2.bin 280 /libdata/firmware/radeon/kaveri_pfp.bin 281 /libdata/firmware/radeon/kaveri_rlc.bin 282 /libdata/firmware/radeon/kaveri_sdma.bin 283 /libdata/firmware/radeon/mullins_ce.bin 284 /libdata/firmware/radeon/mullins_me.bin 285 /libdata/firmware/radeon/mullins_mec.bin 286 /libdata/firmware/radeon/mullins_pfp.bin 287 /libdata/firmware/radeon/mullins_rlc.bin 288 /libdata/firmware/radeon/mullins_sdma.bin 289 /libdata/firmware/radeon/oland_ce.bin 290 /libdata/firmware/radeon/oland_mc.bin 291 /libdata/firmware/radeon/oland_me.bin 292 /libdata/firmware/radeon/oland_pfp.bin 293 /libdata/firmware/radeon/oland_rlc.bin 294 /libdata/firmware/radeon/oland_smc.bin 295 /libdata/firmware/radeon/pitcairn_ce.bin 296 /libdata/firmware/radeon/pitcairn_mc.bin 297 /libdata/firmware/radeon/pitcairn_me.bin 298 /libdata/firmware/radeon/pitcairn_pfp.bin 299 /libdata/firmware/radeon/pitcairn_rlc.bin 300 /libdata/firmware/radeon/pitcairn_smc.bin 301 /libdata/firmware/radeon/tahiti_ce.bin 302 /libdata/firmware/radeon/tahiti_mc.bin 303 /libdata/firmware/radeon/tahiti_me.bin 304 /libdata/firmware/radeon/tahiti_pfp.bin 305 /libdata/firmware/radeon/tahiti_rlc.bin 306 /libdata/firmware/radeon/tahiti_smc.bin 307 /libdata/firmware/radeon/verde_ce.bin 308 /libdata/firmware/radeon/verde_mc.bin 309 /libdata/firmware/radeon/verde_me.bin 310 /libdata/firmware/radeon/verde_pfp.bin 311 /libdata/firmware/radeon/verde_rlc.bin 312 /libdata/firmware/radeon/verde_smc.bin 313 314 We will re-import these radeon firmware images another way 315 later. 316 31720190727: 318 The uefi bootloader has gained tftp support and needs a clean 319 build. If you do update builds, manually clean its object 320 directory by something like: 321 cd sys/arch/i386/stand/efiboot && make clean 322 32320190723: 324 The jemalloc allocator in libc is now build without extended 325 debugging (for performance reasons). In update builds make sure 326 to rebuild it completely, by removing all affected object files, 327 including compat builds, something like: 328 cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 329 33020190207: 331 GCC 7 switched for many ports. Update builds are likely to fail. 332 33320180924: 334 A newer OpenSSL version has been imported. If you are doing 335 update builds, make sure to remove all old obj dirs, like: 336 cd /usr/obj && find . -type d -name openssl | xargs rm -rf 337 33820180717: 339 On aarch64 int64_t and related types have changed from long long 340 to long. This requires recompiling all C++ binaries. 341 34220180713: 343 On amd64 and i386 static binaries are now build position 344 independend. This requires recompilation of all object 345 files used to create the crunched /rescue binary. 346 Clean the rescue directory in your obj directory before 347 doing an update build, otherwise linking will fail. 348 34920180414: 350 Existing binutils was migrated to binutils.old. Manual 351 removal of tools/binutils objects directory may be required 352 to fix tools build failure. 353 35420180311: 355 bdftopcf was updated and may need cleaning in the 356 src/external/mit/xorg/tools/bdftopcf subdirectory if there are 357 link errors. 358 35920180212: 360 between OpenSSL and GCC updates, many things may fail to build. 361 any failure that looks like GCC or openssl is best handled by 362 a clean destdir and objdir. Full cleandir and destdir deletion 363 is recommended if build failures occur. 364 36520171225: 366 removal of the vadvise syscall requires manual removal of all 367 associated files from the libc build object directory (including 368 the .depend files) - a command like: 369 cd $OBJ && find . -type d -name libc | xargs rm -rf 370 For architectures that support multiple "compat" binary targets, 371 you'll need to cleanup both the regular libc directory and the 372 compat ones (the above command will do that). 373 37420171010: 375 a change to the build structure of external/bsd/acpica/bin/iasl 376 means that its objdir (or *.d and .depend at least) might need 377 to be manually removed - or a build done once without -u. 378 37920170822: 380 a new version of GMP has been imported and probably 381 will break parts of builds related to themselves or GCC, both 382 in the tools and the native section. Remove all GCC, GMP, MPFR 383 and MPC objdirs or build once without -u. 384 38520170816: 386 a new version of MPFR and MPC have been imported and probably 387 will break parts of builds related to themselves or GCC, both 388 in the tools and the native section. Remove all GCC, GMP, MPFR 389 and MPC objdirs or build once without -u. 390 39120170402: 392 a new version of dhcpcd has been imported, which does not support 393 update builds from the previous version. Remove your 394 external/bsd/dhcpcd object dir or build once without -u. 395 39620170211: 397 a new terminfo database has been imported. 398 The structure of it has changed slightly from prior versions and 399 an updated tic tool is required. 400 If you build.sh, don't use -u 401 40220170207: 403 various arch dependent libc/exect.S files were removed 404 Either remove the obj directories (lib/libc and compat/amd64/i386/lib 405 if it exists) or do a clean build. 406 (This is a bug in the make system, it should be corrected without 407 human intervention, but isn't.) 408 40920170104: 410 xinput build options have changed. 411 Remove the obj directory (external/mit/xorg/bin/xinput) 412 if you build.sh -u 413 41420170103: 415 a new version of flex has been imported. 416 Remove the file from obj (external/bsd/flex) 417 if you build.sh -u 418 41920161014: 420 a new version of OpenSSL has been imported. 421 Remove the files from obj (crypto/external/bsd/openssl) 422 if you build.sh -u 423 42420161009: 425 a new version of dhcpcd has been imported with slightly changed 426 build infrastructure. When doing a build.sh -u this requires 427 pruning the external/bsd/dhcpcd objdir. 428 42920160914: 430 i386, amd64, shark, ofppc and macppc have joined shark and x68k 431 ports in using xorg-server 1.18. This requires a clean destdir 432 and a clean objdir. 433 43420160527: 435 i386 needs a full cleandir or objdir deletion because PIE has 436 been enabled. (see the amd64 entry two down for further info) 437 43820160418: 439 libedit needs manual removal of all autogenerated files since 440 some of them are not autogenerated anymore. Remember that there 441 might be two copies of libedit if your platform builds "compat". 442 44320160410: 444 amd64 needs full "make cleandir" or deletion of objdir now that 445 PIE has been enabled for amd64. PIE, or position-independent 446 executables, means all code, including executables and not just 447 shared libraries, is position-independent and hence able to be 448 relocated by ASLR, address space layout randomization. 449 450 The change was made in Makefile variables for compiler and 451 linker flags, for which make(1) does not record dependencies, 452 hence it is unable to detect that all .o files need rebuilding. 453 454 Partial rebuilds with some modified source files will likely 455 fail when linking executables, since the linker refuses to mix 456 position-independent code with position-dependent code in 457 position-independent executables: 458 459 .../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC 460 46120160401: 462 Ports switching to GCC 5.3 will need a full "make cleandir". 463 Some people have found that cleandir is not sufficient, so if 464 in doubt delete the entire object directory tree for gcc. 465 46620160306: 467 NetBSD's regexp implementation is now part of libnbcompat. 468 Nblex, nbm4, nbpax, nbsed use it and they may crash on 469 non-NetBSD hosts if linked with stale object files produced 470 while they included a non-NetBSD regex.h. 471 In any case, you should "make cleandir" at least these tools 472 before updating your toolchain. 473 47420160125: 475 Dtrace has been enabled by default on some architectures. 476 When doing an update build, make sure to clean the etc/mtree 477 object directory before starting the build - otherwise the 478 needed directories in destdir will not be created. 479 An easy way to do this is: 480 cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 481 48220150818: 483 New acpica requires "make cleandir" in src/external/bsd/acpica 484 again. 485 48620150413: 487 New acpica requires "make cleandir" and reinstalling yacc 488 in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 489 also "make cleandir" in /usr/src/external/bsd/acpica. 490 49120150404: 492 Lint changes require a full rebuild of the tool, so make 493 sure to build without -u option to build.sh, or manually 494 do a make cleandir in src/tools/lint1 and 495 src/usr.bin/xlint. 496 49720150310: 498 Improvements to openssl for arm mean that update builds of 499 the openssl libraries will fail. A make cleandir in 500 external/bsd/openssl/lib is needed 501 50220141026: 503 A mishap during the import of pppd may cause your corruption 504 in your cvs directory if you happened to do a cvs update 505 during a short period of time. To fix, just remove the 506 directory src/external/bsd/ppp/dist/pppd completely 507 and let cvs restore it on next update. 508 50920140721: 510 The src/external/mit/lua/src directory was accidentally created 511 and then deleted in the CVS repository. If you get errors like 512 513 cvs [update aborted]: cannot open directory 514 /cvsroot/src/external/mit/lua/src: No such file or directory 515 516 then delete your local copy of that directory tree and try again. 517 51820140530: 519 ARM eABI switched to DWARF based exception handling. This requires 520 rebuilding all C++ code. It is strongly advised to do a clean build. 521 52220140131: 523 The new compiler_rt/libc integration moved a few things. It is strongly 524 advised to do a clean build. At least lib/libc, the compat version(s) 525 of libc, libkern, rump and the kernels need to be cleaned. 526 52720131227: 528 1. The new ntpd runs in a restricted mode to prevent amplification 529 attacks. If you need ntpdc to work you need to explicitly enable 530 mode7 in your config file. Make sure you put the necessary restrict 531 statements to avoid being exposed. 532 2. strncat has moved from lib/libc to common/lib/libc; you might need 533 to make clean in libc 534 53520131129: 536 The GMP sources were updated, and builds will likely fail without 537 cleaning their build trees for both tools and in-tree, like below. 538 53920131128: 540 The MPC and MPFR sources were updated, and builds may require their 541 tools and in-tree directories cleaned for successful updates. 542 54320130605: 544 The kernel option FAST_IPSEC no longer exists, it's been renamed 545 to IPSEC (and the older IPSEC version removed). 546 54720130605: 548 Previous freetype installations erroneously installed private 549 header files. If you are building against a non-empty $DESTDIR, 550 please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 551 55220130531: 553 The xdm update may cause build failure due to xdm.man being 554 in the obj tree. Make sure to ensure any like this: 555 nbmake: nbmake: don't know how to make xdm.man. Stop 556 is fixed by deleting the xdm.man in the obj tree. 557 55820130530: 559 Updates of many xsrc packages will leave old .pc files around. 560 Best to clean out the xsrc objdir entirely before rebuilds. 561 56220130301: 563 The removal of netiso requires manual removal of /usr/include/netiso 564 prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 565 56620120726: 567 The update of OpenSSL requires cleaning both the OpenSSL build 568 directory and DESTDIR. *Even non-update builds require cleaning 569 DESTDIR.* Builds done without taking these steps may fail, or in 570 some cases may succeed and install broken OpenSSL libraries that 571 cause third-party software to link incorrectly and/or crash. 572 57320120507: 574 The database schema for makemandb was changed. You will 575 need to update the database using 'makemandb -f' or wait 576 for the next weekly run to fix it. 577 57820120319: 579 sys/conf/Makefile.kern.inc has been modified to adjust the 580 size of db_symtab automatically. You need to update dbsym in 581 your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 582 you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 583 mk.conf. 584 58520120216: 586 Default for MKCATPAGES changed to NO. Update builds will fail 587 unless DESTDIR is cleaned manually. If you built between 20120207 588 and 20120216, daily and weekly could have created an unreadable 589 /var/db/man.db index for apropos. Running makemandb -f or 590 the next run of weekly will fix it. 591 59220111227: 593 If you built between 20111225 and 20111227 you need to remove 594 /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 595 bump has been reverted. 596 59720111125: 598 The "rnd" pseudodevice has been added to sys/conf/std, which 599 means it should no longer be explicitly listed in kernel 600 configuration files. The line "pseudo-device rnd" should be 601 removed from any custom kernel config files users may have. 602 60320111119: 604 A problem with the datastructures used by the rndctl(8) 605 utility (pointers in datastructures in an array, making 32->64 606 bit compatibility very painful) has been fixed in a 607 non-backwards-compatible way. If you replace your kernel, 608 replace your rndctl executable too. 609 61020111001: 611 the prop_*_send_syscall() functions from proplib(3) have been 612 changed and their new version is not backward compatible with the old 613 one. So ensure that all consumers of these functions (currently: 614 quota2 code and its tests) are updated together with the new lib. 615 61620110817: 617 sparc has been changed to use GCC 4.5.3, so any objdir or 618 DESTDIR for them should be deleted before updating. 619 62020110806: 621 i386 and amd64 have been changed to use GCC 4.5.3, so any 622 objdir or DESTDIR for them should be deleted before updating. 623 62420110805: 625 The update to GCC 4.5.3 requires a non-trivial portion of 626 the tree to be cleaned. Best to delete both objdir and 627 DESTDIR before running this update. So far, only the 628 sparc64, mips and powerpc platforms have changed. 629 63020110803: 631 The layout of external/public-domain/xz has changed. To do an 632 update build you will have to remove the contents of the OBJDIR 633 for external/public-domain/xz/bin by hand as the xz entry there 634 is now a directory. 635 63620110410: 637 The configuration of src/tools/gcc has changed. To do an 638 update build you have to clean both tools/binutils and 639 tools/gcc by hand. 640 64120110328: 642 Building the Xorg binary was moved into a subdirectory to fix 643 ordering issues with "make all". It may be necessary to remove 644 the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 645 if your update build fails, as the "Xorg" entry there is now a 646 directory. 647 64820110121: 649 Assembler files no longer use -traditional-cpp. This can break 650 the build of individual parts of the tree. This is handled 651 correctly by build.sh. Manual builds have to update /usr/share/mk 652 and re-run config(1) for any kernel configurations as needed. 653 65420101217: 655 The tcpdump(8) program was changed to drop privileges and chroot(2) 656 by default. It may be necessary to manually update passwd(5) and 657 group(5) in order to make the program work with existing setups. 658 65920101125: 660 The latest changes to setenv(3) disallow setting environment 661 variables with names that contain '='. Revision 1.18 of env.c 662 assumed that this was allowed. Installing a new libc with an 663 old copy of /usr/bin/env causes env x=1 printenv | grep x= to 664 break which affects the autoconf tests for dependency finding, 665 so building gcc will end up printing: 666 checking dependency style of gcc... none 667 configure: error: no usable dependency style found 668 Fix it by rebuilding and re-installing env. 669 67020101119: 671 Recent Xorg updates in xsrc/external/mit/ may cause various build 672 or run-time problems. Delete your entire DESTDIR and OBJDIR if you 673 have any build problems with xsrc, or problems with mismatched 674 versions between xorg-server and drivers. 675 67620100604: 677 The update of ATF to 0.9 causes old tests written in shell to fail 678 unless they are rebuilt. If you are building with MKUPDATE=yes, 679 you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 680 trees by hand. 681 68220100522: 683 Recent Xorg updates in xsrc/external/mit/ will cause various build 684 problems. Delete your entire DESTDIR and OBJDIR if you have any 685 build problems with xsrc. 686 68720100522: 688 private section of <ctype.h> was split, and now mklocale(1) 689 include ctype_local.h, so you have to make cleandir in tools/mklocale. 690 69120100520: 692 The location of the xkb compiled descriptions has changed. Please 693 remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 694 69520100222: 696 The shared objects file extension has been changed from .so to 697 .pico, in order to avoid conflicts with shared libraries names 698 libXX.so. All now stale regular .so files can be removed from 699 your object directories. 700 70120100204: 702 The termcap database has been removed from the sources, 703 but has not been marked obsolete so it is not removed 704 from the system when upgrading. 705 As such, you will need to remove them from your object 706 and destination directories. 707 70820091101: 709 After updating, it may be necessary to make the 'cleandir' 710 target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 711 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 712 src/tools/lex/ and src/usr.bin/lex/. 713 71420091001: 715 On amd64 you must rebuild tools (to get the new binutils) 716 before building a kernel, or the build fails on cpufunc.S. 717 71820091001: 719 An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 720 symlink, failing the build. Delete the link, and the subdir 721 it is in, and retry your build. 722 72320090718: 724 libc build changed so that strchr() provides the extra entry 725 point for index(). Update build of libc.a (and libc_pic.a) 726 may fail because the archive contains the unwanted index.o. 727 (Similarly for strrchr() and rindex().) 728 72920090709: 730 Native Xorg was upgraded again. Builds will probably fail again 731 without a clean objdir, at least for src/external/mit/xorg. 732 73320090616: 734 Native Xorg was upgraded. Builds will need a clean objdir for 735 src/external/mit/xorg. Upgrading a system from sets will not 736 work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 737 subdirectory has been changed into a file, and this needs to 738 be manually "rm -r"'ed before installing xbase.tgz. 739 74020090501: 741 Several new functions were added to string.h/libc, and this 742 can cause autoconf problems during the tool build for people 743 who fail to clean out their tools objects properly. If you 744 note messages about stpcpy, stpncpy or strnlen accompanying a 745 failure during the tool build, clean out all your tools 746 objects and start again. 747 74820090325: 749 The i386 port was switched to i486 default toolchain. This requires 750 cleaning your src/tools directory and $TOOLDIR and rebuilding them. 751 75220090126: 753 The __posix_fadvise50 system call changed assembly stub type. You 754 need to 'rm -f __posix_fadvise50.*' in the libc build directory 755 to avoid using the old assembly stub. 756 75720090202: 758 pkg_install now depends on the pkgdb cache for automatic conflict 759 detection. It is recommended to rebuild the cache with 760 ``pkg_admin rebuild''. 761 76220090110: 763 time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 764 1. Make sure your kernel has COMPAT_50 in it. Build and install. 765 This is needed even in the MODULAR kernel because there is 766 conditionally compiled code in rtsock.c. 767 2. make sure build.sh completes and the binaries in a chroot work 768 before installing. 769 3. If you don't use build.sh and you build directly to root, and 770 your build breaks in the middle, don't despair. Make sure headers 771 are installed properly, and start building libraries first libc 772 and libutil, install them and then continue building all the 773 libraries in src/lib and src/gnu/lib and install them. Once 774 the new libraries are installed, you can restart the build. 775 4. If you compile packages and you notice link time warnings, 776 rebuild the required packages to update their shared libraries. 777 Any package you rebuild will require rebuilding all the packages 778 that depend on it. 779 5. Next time you run pwd_mkdb with the new binary, the file 780 will be upgraded and it will not be backwards compatible. 781 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 782 lastlogx(5)) have been versioned, and there is a heuristic 783 for utmp. You are better off removing the old files after 784 upgrading. The automated clearing of /var/run during 785 boot, and the automated rotating of files in /var/log by 786 newsyslog(8), may mean that you do not have to remove the 787 files manually. 788 7. The optional accounting file (/var/account/acct, see 789 accton(8)) has not been versioned, and will need to be 790 removed. The automatic rotation of the accounting file by 791 /etc/daily limits the bad consequences of failure to remove 792 the file. 793 8. Application software that writes time_t to binary files on 794 disk will break or need attention. Most notably: if you are 795 using PostgreSQL < 8.4, you need to dump your databases, 796 rebuild PostgreSQL with the new time_t, then restore. 797 79820081219: 799 config(1) has been updated, and one of the files it creates - 800 swapnetbsd.o - has changed format. You need to rebuild config 801 (done automatically by build.sh) and then you need to rerun 802 config on all kernel configuration files before rebuilding those 803 kernels. 804 80520081205: 806 If you build with MKX11=no, you should remove /etc/rc.d/xdm and 807 /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 808 set and will appear as extra files for MKX11=no update builds. 809 81020081122: 811 On i386, various kernel options(4) in GENERIC including 812 file systems have been disabled and moved into kernel modules. 813 Before trying a new GENERIC kernel, you have to prepare the 814 following files as well as a new GENERIC kernel: 815 816 - build and install kernel modules from src/sys/modules 817 818 - install the latest bootloader, which will load a module 819 for the file system from which the kernel is loaded automatically 820 821 If you have to load your kernel from a file system which is not of 822 the same type as the root file system, you have to load the necessary 823 file system module manually on the boot prompt or in the boot.cfg file. 824 82520080827: 826 If you built and installed a libc from sources between 827 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 828 which results in false errors reported by lint(1). 829 Since this breaks the libc build itself, manual help is 830 needed -- lint must be disabled temporarily, e.g.: 831 $ (cd lib/libc && make MKLINT=no dependall install) 832 83320080813: 834 MKDEBUG build was broken because the .depend files did not know 835 about .go files. You need to remove all .depend files and rebuild. 836 83720080802: 838 A regression in binary compatibility for pthread_mutex_t has 839 been fixed. Unfortunately, the price is breaking compatibility 840 for -current. 841 842 Threaded programs (using libpthread) and C++ programs (using 843 libstdc++) compiled after 20070907 and before 20080802 need to 844 be recompiled. 845 846 One way to find affected pkgsrc packages: 847 848 $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 849 $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 850 85120080731: 852 WAPBL (metadata journaling support) has been added, but at this 853 time isn't backwards compatible with pre-WAPBL aware kernels 854 and userland (fsck_ffs in particular). Please make sure you 855 don't use a journaled filesystem with an older kernel/userland, 856 especially an uncleanly mounted journaled filesystem. WAPBL 857 also requires the super block to be in the UFS2 format. You 858 can use fsck_ffs -c 4 to update the superblock format. 859 86020080721: 861 Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 862 isn't defined. 863 86420080531: 865 The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 866 from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 867 utility needs to be rebuilt and reinstalled as older binaries 868 won't work correctly. The following sequence of commands: 869 870 $ (cd sys/sys/ && nbmake-$arch includes) 871 $ (cd sbin/drvctl/ && nbmake-$arch clean) 872 $ (cd sbin/drvctl/ && nbmake-$arch all) 873 874 leaves new drvctl utility in sbin/drvctl build directory. 875 87620080503: 877 The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 878 87920080521: 880 For a while, unprivileged UPDATE builds would fail to 881 succeed at the checkflist stage, complaining that 882 ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 883 problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 884 If you already hit this problem, update the .mk file, 885 remove ${DESTDIR}/stand/<arch>, and re-run the build. 886 88720080303: 888 Linker warnings are now fatal if $WARNS>0. 889 89020080126: 891 The posix_fadvise system call has been changed from an assembly 892 stub, to a c file that calls an assembly stub. You need to 893 'rm -f posix_fadvise.* .depend' in the libc build directory to 894 avoid using the old assembly stub. 895 89620071209: 897 The acpiec(4) driver has been split into two attachments. If you 898 get ACPI errors before the attachment, please update your kernel 899 configuration file appropriately or see GENERIC for more details. 900 90120071115: 902 The it(4) driver has been renamed to itesio(4) and the old port 903 argument specified in the kernel configuration file is not valid 904 anymore. The itesio(4) driver now uses the Super I/O address port 905 rather than the EC address port. Please update your kernel 906 configuration file appropriately or see GENERIC for more details. 907 90820071028: 909 The pccons(4) driver has been removed from the NetBSD/shark port. 910 You need to update any custom kernel configuration file you have 911 to remove any references to pccons (which includes removing the 912 now useless XSERVER option) and replace them with the correct 913 entries for the wscons driver. See the GENERIC configuration file 914 for more details. 915 91620070913: 917 A latent bug in dhclient/dhcpd that caused it to be unable to 918 enumerate interfaces was fixed. The bug began to cause 919 problems after 20070911 when the kernel's SIOCGIFCONF 920 implementation was repaired. From 20070529 to 20070911 racoon 921 could not enumerate interfaces. (These are noted because 922 normal kernel/userspace version matching hygiene is not 923 sufficient to avoid this problem.) Ensure that both kernel 924 and userland are from after 20070913. 925 92620070703: 927 nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 928 calls the target-specific strip program, and the logic to pass 929 down STRIP from make has been removed. This requires a 930 re-installation of tools. 931 93220070422: 933 The way OS emulations lookup filenames inside the emulation root 934 has been changed. Rather than modify the pathname (and copy back 935 to userspace) namei() and lookup() directly check the emulation 936 root. One side effect is that absolute symlinks inside the emulated 937 root file system will be relative to that file system - unless they 938 start /../ this is useful when the emulated root is a real install 939 that has such links. 940 This might affect symlinks that have been added to reference outside 941 the emulated root. 942 94320070412: 944 The pckbc driver on sgimips IP32 has been removed. Use macekbc 945 instead. See the GENERIC32_IP3x kernel configuration for an 946 example. 947 94820070319: 949 src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 950 on many platforms due to incorrect flags settings. If you 951 updated and built after about 20070315, do "nbmake-$arch 952 cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 953 rebuild of object files that might have been built 954 incorrectly, and ensure that you have at least 955 src/lib/libc/Makefile 1.130. 956 95720070210: 958 src/sys/sys/{sa.h,savar.h} were removed. 959 find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 960 | xargs egrep -l '/sa.h|/savar.h' | xargs rm 961 will allow dependencies on those files to get get rebuilt 962 96320070209: 964 The threading model was changed when the newlock2 branch 965 was merged to NetBSD-current. If you boot with a new 966 kernel (version 4.99.10), then you also need a new pthread 967 library (/usr/lib/libpthread.so.0.7). If you boot with 968 an old kernel, then you need the old pthread library 969 (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 970 the pthread library in sync, old threaded applications should 971 continue to work with an old or new kernel. Note that named(8) 972 is the only threaded application in the base system. 973 97420061214: 975 Following the move of string_to_flags() and flags_to_string() 976 from the bin/ls/ sources to libutil, users doing UPDATE builds 977 will need to do a "make cleandir" in 978 tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 979 bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 980 usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 981 as the installation images in distrib/ 982 in order to excise stale references to the old stat_flags.h header 983 file in the ls sources -- stat_flags.h has been removed. 984 98520061108: 986 The configure script used in the src/tools/gcc compiler has been 987 changed to indicate that our libc has ssp support built-in and 988 does not depend on -lssp and -lssp-nonshared. You'll need to 989 make clean in src/tools/gcc first to rebuild the compiler. 990 99120061009: 992 The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 993 available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 994 99520060814: 996 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 997 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 998 kernel configuration for an example. X servers from the last 999 few years should cope. 1000 100120060703: 1002 MPACPI is no more. We always configure PCI interrupts using ACPI 1003 if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 1004 to ACPI_SCANPCI. Thanks to work from fvdl. 1005 100620060627: 1007 socket(2) has changed, and its system call has been versioned. 1008 For userlands with the old version of socket(2), make sure that 1009 your kernel has 'options COMPAT_30' set, or else 'bad system call' 1010 errors will result. 1011 1012Hints for a more successful build: 1013^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1014 Use build.sh, but do not use its "expert mode": 1015 This will automatically build the tools in the 1016 correct order, and it will keep the tools and the 1017 new build products from interfering with the running 1018 system. This will allow you to ignore most of the 1019 other advice in this file. 1020 Build a new kernel first: 1021 This makes sure that any new system calls or features 1022 expected by the new userland will be present. This 1023 helps to avoid critical errors when upgrading. 1024 Use object directories: 1025 This helps to keep stale object 1026 files from polluting the build if a Makefile "forgets" 1027 about one. It also makes it easier to clean up after 1028 a build. It's also necessary if you want to use the 1029 same source tree for multiple machines. 1030 To use object directories with build.sh: 1031 a) invoke build.sh with the "-M" or "-O" options. 1032 To use object directories without using build.sh: 1033 a) cd /usr/src ; make cleandir 1034 b) Add "OBJMACHINE=yes" to /etc/mk.conf 1035 c) Add "MKOBJDIRS=yes" to /etc/mk.conf 1036 d) cd /usr/src ; make build 1037 Note that running "make obj" in a directory will create 1038 in obj.$MACHINE directory. 1039 Build to a DESTDIR: 1040 This helps to keep old installed files (especially libraries) 1041 from interfering with the new build. 1042 To build to a DESTDIR with build.sh, use the "-D" option. 1043 To build to a DESTDIR without using build.sh, set the DESTDIR 1044 environment variable before running make build. It should be 1045 set to the pathname of an initially empty directory. 1046 Problems: if you do not use build.sh, you might need to 1047 update critical utilities without using DESTDIR since 1048 nothing is executed from what is installed in DESTDIR. 1049 (See critical utils, below.) 1050 Build often: 1051 This keeps critical utilities current enough to not choke 1052 on any other part of the source tree that depends on up to 1053 date functionality. If you use build.sh, you should not have 1054 this problem. 1055 1056What to do if things don't work: 1057^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1058When things don't work there are usually a few things that commonly 1059should be done. 1060 1) make includes 1061 This should be done automatically by make build. 1062 2) cd share/mk && make install 1063 Again, automatically done by make build. 1064 1065Failsafe rebuild of a small part of the tree: 1066^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1067To make sure you rebuild something correctly you want to do 1068something like the following: 1069 1) Make sure the includes and .mk files are up to date. 1070 2) Make sure any program used to build the particular 1071 utility is up to date. (yacc, lex, etc...) 1072 3) cd ...path/to/util... 1073 make cleandir 1074 rm ...all obj directories... 1075 make cleandir # yes, again 1076 make obj 1077 make depend && make 1078 1079Failsafe rebuild of the entire tree: 1080^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1081If you really want to make sure the source tree is clean and 1082ready for a build try the following. Note that sourcing /etc/mk.conf 1083(a make(1) Makefile) in this manner is not right, and will not work 1084for anyone who uses any make(1) features in /etc/mk.conf. 1085 1086---cut here--- 1087#!/bin/sh 1088. /etc/mk.conf 1089 1090if [ -z $NETBSDSRCDIR ] ; then 1091 NETBSDSRCDIR=/usr/src 1092fi 1093if [ \! -d $NETBSDSRCDIR ] ; then 1094 echo Unable to find sources 1095 exit 1 1096fi 1097find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 1098 1099if [ -z $BSDOBJDIR ] ; then 1100 BSDOBJDIR=/usr/obj 1101fi 1102if [ -d $BSDOBJDIR ] ; then 1103 rm -rf $BSDOBJDIR 1104fi 1105 1106cd $NETBSDSRCDIR && make cleandir 1107 1108---cut here--- 1109 1110Critical utilities: 1111^^^^^^^^^^^^^^^^^^^ 1112 usr.bin/compile_et 1113 usr.bin/make 1114 usr.bin/yacc 1115 usr.bin/lex 1116 usr.bin/xlint 1117 usr.bin/config 1118 1119Other problems and possible solutions: 1120^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1121Symptom:Complaints involving a Makefile. 1122Fix: Rebuild usr.bin/make: 1123 cd usr.bin/make && make && make install 1124 Or, a failsafe method if that doesn't work: 1125 cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 1126 1127Fix: Make sure .mk files are up to date. 1128 cd share/mk && make install 1129 1130Symptom:Kernel `config' fails to configure any kernel, including GENERIC. 1131Fix: Rebuild usr.bin/config 1132 1133Symptom: 1134Fix: Rebuild usr.bin/yacc 1135 1136Symptom: 1137Fix: Rebuild usr.bin/lex 1138 1139Symptom: 1140Fix: rm /usr/lib/libbfd.a 1141 1142Symptom:Obsolete intermediate files are used during compilation 1143Fix: Try the following sequence of commands in the directory in question. 1144 make cleandir; rm `make print-objdir`; make cleandir; make obj 1145 (If you built the tree without "make obj" in the past, obsolete files 1146 may remain. The command tries to clean everything up) 1147 1148Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible 1149 pointer type 1150Fix: Rebuild and install usr.bin/menuc 1151 1152Symptom:mklocale not found during build in share/locale/ctype 1153Fix: Build and install usr.bin/mklocale 1154 1155Symptom:undefined reference to `__assert13' or `__unsetenv13' 1156Fix: Rebuild and install lib/libc 1157 1158Symptom:usr.bin/config fails to build. 1159Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 1160 1161Symptom:undefined reference to `getprogname' or `setprogname' 1162Fix: Rebuild and install lib/libc 1163 1164Symptom:lint does not understand the '-X' option 1165Fix: May need to build & install libs with NOLINT=1 before rebuilding lint 1166 1167Symptom:Update build fails in src/tools/gcc complaining that a variable 1168 (e.g. CPPFLAGS) has changed since the previous run. 1169Fix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 1170 1171Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 1172 No such file or directory. 1173Cause: If a directory is created by mistake, then it is sometimes 1174 deleted from the CVS repository using administrative commands 1175 that bypass the normal cvs access controls. If your cvs working tree 1176 contains references to a directory that has been deleted on the 1177 server in this way, then "cvs update" reports this error. 1178Fix: Recursively delete the affected directory from your working tree 1179 and try the update again. 1180