UPDATING revision 1.381
1 $NetBSD: UPDATING,v 1.381 2025/06/02 00:49:03 gutteridge Exp $ 2 3 This file (UPDATING) is intended to be a brief reference to recent 4 changes that might cause problems in the build process, and a guide for 5 what to do if something doesn't work. 6 7 For a more detailed description of the recommended way to build NetBSD 8 using build.sh, see the BUILDING file. 9 10 Note that much of the advice in this UPDATING file was written before 11 build.sh existed. Nevertheless, the advice here may be useful for 12 working around specific problems with build.sh. 13 14 Sections are marked with "^^^^^". After the section on "Recent changes" 15 are several sections containing more general information. 16 17 See also: BUILDING, build.sh, Makefile. 18 19 Recent changes: 20 ^^^^^^^^^^^^^^^ 21 22 20250528: 23 Changes in the tools build require removing all config.cache 24 files in the object tools directories. 25 26 20250427: 27 The KERNEL_DIR option to build.sh is now functional. Set it 28 with ``-V KERNEL_DIR=yes'' on your build.sh command. 29 With this, you can now colocate kernel and associated modules 30 in /netbsd/{kernel,kernel.dbg,modules} instead of having the 31 kernel in / but modules in /stand. 32 33 Note that you'll need new bootstrap code to use this feature. 34 35 This completes work begun many years ago by christos@ :-) 36 37 20250413: 38 A change to bsd.lib.mk requires a clean build of all libraries. 39 40 20250131: 41 The switch to the new jemalloc requires cleaning in libc. 42 43 20241122: 44 Changes to various libraries' build options require cleaning 45 their objdirs in update builds: 46 47 cd external/bsd/file/lib && $TOOLDIR/bin/nbmake-$ARCH clean 48 cd external/bsd/libarchive/lib && $TOOLDIR/bin/nbmake-$ARCH clean 49 cd external/public-domain/xz/lib && $TOOLDIR/bin/nbmake-$ARCH clean 50 51 Also, for architectures with MKCOMPAT, it is necessary to clean 52 the compat objdirs too. The easiest way is: 53 54 rm -rf OBJDIR/compat/*/*/external/bsd/file/lib 55 rm -rf OBJDIR/compat/*/*/external/bsd/libarchive/lib 56 rm -rf OBJDIR/compat/*/*/external/public-domain/xz/lib 57 58 Changes to bsd.lib.mk to improve detecting differences in 59 shared library symbol exports may cause some .actsym files in 60 the objdir to become stale in update builds. 61 62 To work around this, delete all files matching `*.actsym' in 63 the objdir. For example: 64 65 find OBJDIR -name '*.actsym' -type f -print0 | xargs -0 rm 66 67 20241104: 68 Changes around the integration of the zstd compression 69 library may require manual deletion of some object directories 70 if you update from a build from a few days ago: 71 rm -rf DESTDIR/usr/lib/*/libarchive* 72 rm -rf DESTDIR/usr/lib/*/libmagic* 73 rm -rf DESTDIR/usr/lib/*/libzstd* 74 rm -rf DESTDIR/usr/lib/libarchive* 75 rm -rf DESTDIR/usr/lib/libmagic* 76 rm -rf DESTDIR/usr/lib/libzstd* 77 rm -rf OBJDIR/compat/*/*/external/bsd/file/ 78 rm -rf OBJDIR/compat/*/*/external/bsd/libarchive/ 79 rm -rf OBJDIR/compat/*/*/external/bsd/zstd/ 80 rm -rf OBJDIR/external/bsd/file/ 81 rm -rf OBJDIR/external/bsd/libarchive/ 82 rm -rf OBJDIR/external/bsd/zstd/ 83 rm -rf OBJDIR/external/gpl3/gcc/ 84 rm -rf OBJDIR/tools/gcc/ 85 86 20240926: 87 Building -current when running on amd64 from about 20240924 88 to about 20240926 will not work due to a "malloc_np.h" 89 error. Please downgrade to a version from 20240924 or older, 90 or upgrade to a newer version e.g. using a binary release from 91 the NetBSD build servers. 92 93 20240923: 94 Update builds will require cleaning the object directories for 95 jemalloc (like: "rm -rf $OBJ/external/bsd/jemalloc*") and the 96 libc dependency files (like: "rm $OBJ/lib/libc/jemalloc.*"). 97 On architectures with COMPAT libs, those also have to be cleaned, 98 e.g. on sparc64: "rm -rf $OBJ/compat/sparc64/sparc/external/bsd/jemalloc*" 99 and "rm $OBJ/compat/sparc64/sparc/lib/libc/jemalloc.*". 100 101 20240920: 102 Update builds will require cleaning in src/external/historical/nawk/bin 103 in order to remove the awk subdirectory since there is now a binary 104 called awk. 105 106 20240817: 107 Update builds will require cleaning in src/external/historical/nawk/bin 108 in order to remove the awk binary since now there is a subdirectory 109 called awk. 110 111 20240812: 112 Update builds will require removing the tools objdir for gdb 113 if building with MKCROSSGDB=yes. All architectures use gdb.old 114 now. 115 116 20240630: 117 Update builds will require removing the tools objdir for binutils 118 (as most architectures should use binutils.old now). 119 120 20240610: 121 Update builds are likely to require removing the objdir for 122 distrib/<arch>/cdroms - or at least references to libarchive 123 from within there after the recent libarchive update. 124 125 20240504: 126 Update builds on x86 require making the `cleandir' target in 127 lib/libm, or deleting the objdir for lib/libm. 128 129 20240423: 130 Update builds with x11 may fail after switching to Mesa 21. 131 132 20240410: 133 Update builds may require manually deleting 134 $DESTDIR/var/run/named (and, potentially, 135 $DESTDIR/var/run/lwresd) in order to avoid checkflist failure. 136 137 20240409: 138 32-bit compatibility libraries were moved into the base32 139 and debug32 sets. HTML man pages were moved into the manhtml set. 140 141 20230828: 142 If: 143 - you updated to current and ran postinstall between 20230826 144 and 20230828 inclusive, and 145 - you are not using anything outside the base system to 146 populate /etc/openssl/certs (e.g., manually adding 147 certificates or using ca-certificates or mozilla-rootcerts or 148 mozilla-rootcerts-openssl from pkgsrc), 149 delete /etc/openssl/certs and rerun postinstall or just 150 `certctl rehash'. 151 152 Otherwise, certctl(8) will think someone else has left 153 /etc/openssl/certs in the way and will avoid clobbering it on 154 upgrade from older NetBSD. 155 156 20230718: 157 build.sh will use mk.conf in the same directory as build.sh instead 158 of /etc/mk.conf, unless MAKECONF is already defined in the environment. 159 160 20230714: 161 Import of gcc 10.5 requires a clean build of at least tools/gcc 162 and external/gpl3/gcc* object directories. An update build 163 without cleaning will result in obscure failures in rare corner 164 cases. 165 166 20230604: 167 Building native kernels with the installed make(1) instead of 168 the $TOOLDIR/bin/nbmake-${arch} wrapper will fail if userland 169 has not been updated. Note that this is an unsupported build 170 configuration (but usually works if userland is -current enough). 171 172 20230523: 173 ctfmerge was fixed as macOS host tool. This may require a clean tools 174 rebuild to detect the update to tools/compat/configure. 175 176 20230515: 177 New openssl build requires removal of the crypto/external/bsd/openssl 178 and tests/crypto/libcrypto subdirectories in the ${OBJDIR} hierarchy. 179 Otherwise test results may be wrong due to wrong "golden" output 180 files being installed. 181 182 20230322: 183 Fixes for moved /lib/libisns* mean that builds will complain about 184 ./usr/lib/libisns* being missing until src/lib/libisns is forced 185 to (re)install the files, including the symlinks. The simplest 186 way is to clean this subdir before building. 187 188 20230112: 189 New binutils require an updated ld.elf_so. If you are doing 190 (unsupported) in-place self builds (with the -E flag to build.sh), 191 make sure to have installed latest ld.elf_so before you rebuild 192 userland. 193 194 20221116: 195 The addition to NetBSD's version of UFS2 of support for extended 196 attributes broke backward compatibility with previous releases 197 of NetBSD, so UFS2 has been restored to being compatible with 198 previous NetBSD releases by disabling extended attributes. 199 (Note that ACLs are implemented as extended attributes, so 200 this changes disables ACLs as well.) 201 202 Support for UFS2 with extended attributes is now available in a new 203 UFS variant called UFS2ea. If you have created extended attributes 204 in an original UFS2 file system then "fsck -p" will now fail due to 205 the unexpected presence of extended attributes and "fsck -y" will 206 remove all extended attributes. If you wish to preserve extended 207 attributes rather than delete them, there is a utility to convert 208 a UFS2 file system to UFS2ea and leave extended attributes in place, 209 but this should be used with caution since it will preserve any 210 extended attributes that have been corrupted by the backward 211 incompatibility too. 212 213 If you wish to use a UFS2ea file system as your root file system, 214 then you will need to update your boot loader to a version that 215 supports UFS2ea. 216 217 For more information, see: 218 https://wiki.netbsd.org/features/UFS2ea 219 220 20221111: 221 The new libdrm import worsened the conflict issues for the 222 kdump/ktruss ioctl, and i915 now conflicts with base, and has 223 been turned off. This will cause update build issues like: 224 225 kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP' 226 undeclared here (not in a function); 227 did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'? 228 229 You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue. 230 231 20220921: 232 Since the kernel version was bumped to 9.99.100, the bootloader 233 must be updated on x86 or EFI boot platforms in order to load 234 modules from boot.cfg(5) or interactively at the bootloader 235 prompt. 236 237 The kernel can still load modules at runtime, with modload(8) 238 or modules.conf(5), with no bootloader update. This will not 239 affect release branches because it only applies to patch 240 numbers >=100. 241 242 On x86 (i386 or amd64) with BIOS boot, this requires copying a 243 new /usr/mdec/boot to /boot. You can build this in the destdir 244 by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 245 sys/arch/i386/stand. 246 247 On platforms with EFI boot (including x86 with EFI boot), this 248 requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/ 249 directory on the EFI system partition. The boot*.efi file is: 250 251 aarch64 bootaa64.efi 252 amd64 bootx64.efi 253 arm bootarm.efi (32-bit arm) 254 i386 bootx32.efi 255 256 You can build this in the destdir by running 257 `$TOOLDIR/bin/nbmake-$ARCH dependall install' in 258 sys/stand/efiboot/boot*. 259 260 20220821: 261 Support for building extsrc/ has been deprecated. 262 EXTSRCSRCDIR and MKEXTSRC have been deprecated. 263 264 20220714: 265 Updates to xorg-server and associated drivers may cause builds to 266 fail. Cleaning both DESTDIR and the xorg build tree may be needed. 267 268 20220628: 269 Changes in the build of src/games/robots require a clean build 270 of that program. 271 272 20211116: 273 Changes in the xorg build require clean obj dirs for external/mit/xorg 274 (or a full clean/non-update build). 275 276 20211112: 277 Device tree sources were updated for evbarm. Some device nodes 278 (in particular, ld(4) devices on the ROCKPro64) will be renumbered. 279 280 20211014: 281 MKPIE default for aarch64 has changed, a clean build is required. 282 283 20210917: 284 Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4 285 ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs 286 and have "acls" in /etc/fstab you'll need to change it to "nfs4acls". 287 288 20210711: 289 Updated GMP sources may require cleaning in tools/gmp and/or in 290 external/lgpl3/gmp/lib, particularly if GCC itself does not build. 291 292 20210417: 293 GCC 10 was enabled for several platforms. If builds fail in either 294 tools/gcc or external/gpl3/gcc, first try cleaning those objects and 295 removing the $DESTDIR/usr/include/g++ subdirectory. 296 297 20201016: 298 MIPS kernel modules have been disabled until they work. This will 299 turn up in extra files in the DESTDIR, which should be cleaned. 300 301 20200925: 302 GNU MPC and MPFR have been updated. At least MPFR needs cleaning 303 in both the tools and external dirs. 304 305 20200912: 306 GCC 9 has arrived for Arm and x86 platforms, and will be coming 307 for several more, as will binutils 2.34. Clean as required. 308 309 20200907: 310 GCC 9 is coming, and binutils has been updated for MIPS. This 311 probably requires cleaning the tools/binutils. 312 313 20200811: 314 GCC updates may require cleaning the objdir. This may occur 315 due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming 316 GCC 9 upgrade. 317 318 20200614: 319 blacklist* has been renamed to blocklist*. postinstall(8) 320 should handle the migration. 321 322 20200601: 323 Due to a mistake in LIBISPRIVATE handling, .so libraries were 324 created in the build directories and need cleaning. 325 326 20200311: 327 GCC 8 ports will need cleaning in src/tools/gcc and 328 src/external/gpl3/gcc due to GCC 8.4 update. 329 330 20191118: 331 More architectures were switched to gcc8: 332 i386, ia64 powerpc64, sparc, sparc64, arm 333 The same comments as in 20191022 apply. 334 335 20191112: 336 The LLVM update requires a clean rebuild for all architectures using 337 LLVM during the tools build phase (i386, amd64, aarch64). 338 339 20191022: 340 Ports amd64 and aarch64 switched to GCC 8.3 by default. 341 In-place ("expert mode", build.sh -E) builds are not supported 342 when going from a GCC 7 userland to GCC 8. Do a regular 343 build to a different DESTDIR (or preferably: build.sh -U) at least 344 once and install sets, or download comp.{tar.xz,tgz} from the 345 daily builds and install that before doing the next in-place build. 346 347 20191001: 348 GCC 8.3 was imported. Builds of src/tools/gcc may fail if 349 old builds with GCC 7 output now uses GCC 8. Clean this 350 directory, and also clean src/external/gpl3/gcc. 351 352 20190903: 353 Files with names that coincide with existing files' names on 354 case-insensitive file systems were inadvertently committed, for 355 radeon GPU firmware. We cannot mark these as obsolete for 356 postinstall to fix, so if you updated src since 2019-08-26, and 357 ran build.sh distribution or ran build.sh release, you must 358 manually delete the following files in your DESTDIR (which is 359 usually $OBJDIR/destir.$ARCH), or from / if you have installed 360 them: 361 362 /libdata/firmware/radeon/bonaire_ce.bin 363 /libdata/firmware/radeon/bonaire_mc.bin 364 /libdata/firmware/radeon/bonaire_me.bin 365 /libdata/firmware/radeon/bonaire_mec.bin 366 /libdata/firmware/radeon/bonaire_pfp.bin 367 /libdata/firmware/radeon/bonaire_rlc.bin 368 /libdata/firmware/radeon/bonaire_sdma.bin 369 /libdata/firmware/radeon/bonaire_smc.bin 370 /libdata/firmware/radeon/bonaire_uvd.bin 371 /libdata/firmware/radeon/hainan_ce.bin 372 /libdata/firmware/radeon/hainan_mc.bin 373 /libdata/firmware/radeon/hainan_me.bin 374 /libdata/firmware/radeon/hainan_pfp.bin 375 /libdata/firmware/radeon/hainan_rlc.bin 376 /libdata/firmware/radeon/hainan_smc.bin 377 /libdata/firmware/radeon/hawaii_ce.bin 378 /libdata/firmware/radeon/hawaii_mc.bin 379 /libdata/firmware/radeon/hawaii_me.bin 380 /libdata/firmware/radeon/hawaii_mec.bin 381 /libdata/firmware/radeon/hawaii_pfp.bin 382 /libdata/firmware/radeon/hawaii_rlc.bin 383 /libdata/firmware/radeon/hawaii_sdma.bin 384 /libdata/firmware/radeon/hawaii_smc.bin 385 /libdata/firmware/radeon/kabini_ce.bin 386 /libdata/firmware/radeon/kabini_me.bin 387 /libdata/firmware/radeon/kabini_mec.bin 388 /libdata/firmware/radeon/kabini_pfp.bin 389 /libdata/firmware/radeon/kabini_rlc.bin 390 /libdata/firmware/radeon/kabini_sdma.bin 391 /libdata/firmware/radeon/kaveri_ce.bin 392 /libdata/firmware/radeon/kaveri_me.bin 393 /libdata/firmware/radeon/kaveri_mec.bin 394 /libdata/firmware/radeon/kaveri_mec2.bin 395 /libdata/firmware/radeon/kaveri_pfp.bin 396 /libdata/firmware/radeon/kaveri_rlc.bin 397 /libdata/firmware/radeon/kaveri_sdma.bin 398 /libdata/firmware/radeon/mullins_ce.bin 399 /libdata/firmware/radeon/mullins_me.bin 400 /libdata/firmware/radeon/mullins_mec.bin 401 /libdata/firmware/radeon/mullins_pfp.bin 402 /libdata/firmware/radeon/mullins_rlc.bin 403 /libdata/firmware/radeon/mullins_sdma.bin 404 /libdata/firmware/radeon/oland_ce.bin 405 /libdata/firmware/radeon/oland_mc.bin 406 /libdata/firmware/radeon/oland_me.bin 407 /libdata/firmware/radeon/oland_pfp.bin 408 /libdata/firmware/radeon/oland_rlc.bin 409 /libdata/firmware/radeon/oland_smc.bin 410 /libdata/firmware/radeon/pitcairn_ce.bin 411 /libdata/firmware/radeon/pitcairn_mc.bin 412 /libdata/firmware/radeon/pitcairn_me.bin 413 /libdata/firmware/radeon/pitcairn_pfp.bin 414 /libdata/firmware/radeon/pitcairn_rlc.bin 415 /libdata/firmware/radeon/pitcairn_smc.bin 416 /libdata/firmware/radeon/tahiti_ce.bin 417 /libdata/firmware/radeon/tahiti_mc.bin 418 /libdata/firmware/radeon/tahiti_me.bin 419 /libdata/firmware/radeon/tahiti_pfp.bin 420 /libdata/firmware/radeon/tahiti_rlc.bin 421 /libdata/firmware/radeon/tahiti_smc.bin 422 /libdata/firmware/radeon/verde_ce.bin 423 /libdata/firmware/radeon/verde_mc.bin 424 /libdata/firmware/radeon/verde_me.bin 425 /libdata/firmware/radeon/verde_pfp.bin 426 /libdata/firmware/radeon/verde_rlc.bin 427 /libdata/firmware/radeon/verde_smc.bin 428 429 We will re-import these radeon firmware images another way 430 later. 431 432 20190727: 433 The uefi bootloader has gained tftp support and needs a clean 434 build. If you do update builds, manually clean its object 435 directory by something like: 436 cd sys/arch/i386/stand/efiboot && make clean 437 438 20190723: 439 The jemalloc allocator in libc is now built without extended 440 debugging (for performance reasons). In update builds make sure 441 to rebuild it completely, by removing all affected object files, 442 including compat builds, something like: 443 cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf 444 445 20190207: 446 GCC 7 switched for many ports. Update builds are likely to fail. 447 448 Hints for a more successful build: 449 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 450 Use build.sh, but do not use its "expert mode": 451 This will automatically build the tools in the 452 correct order, and it will keep the tools and the 453 new build products from interfering with the running 454 system. This will allow you to ignore most of the 455 other advice in this file. 456 Build a new kernel first: 457 This makes sure that any new system calls or features 458 expected by the new userland will be present. This 459 helps to avoid critical errors when upgrading. 460 Use object directories: 461 This helps to keep stale object 462 files from polluting the build if a Makefile "forgets" 463 about one. It also makes it easier to clean up after 464 a build. It's also necessary if you want to use the 465 same source tree for multiple machines. 466 To use object directories with build.sh: 467 a) invoke build.sh with the "-M" or "-O" options. 468 To use object directories without using build.sh: 469 a) cd /usr/src ; make cleandir 470 b) Add "OBJMACHINE=yes" to /etc/mk.conf 471 c) Add "MKOBJDIRS=yes" to /etc/mk.conf 472 d) cd /usr/src ; make build 473 Note that running "make obj" in a directory will create 474 in obj.$MACHINE directory. 475 Build to a DESTDIR: 476 This helps to keep old installed files (especially libraries) 477 from interfering with the new build. 478 To build to a DESTDIR with build.sh, use the "-D" option. 479 To build to a DESTDIR without using build.sh, set the DESTDIR 480 environment variable before running make build. It should be 481 set to the pathname of an initially empty directory. 482 Problems: if you do not use build.sh, you might need to 483 update critical utilities without using DESTDIR since 484 nothing is executed from what is installed in DESTDIR. 485 (See critical utils, below.) 486 Build often: 487 This keeps critical utilities current enough to not choke 488 on any other part of the source tree that depends on up to 489 date functionality. If you use build.sh, you should not have 490 this problem. 491 492 What to do if things don't work: 493 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 494 When things don't work there are usually a few things that commonly 495 should be done. 496 1) make includes 497 This should be done automatically by make build. 498 2) cd share/mk && make install 499 Again, automatically done by make build. 500 501 Failsafe rebuild of a small part of the tree: 502 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 503 To make sure you rebuild something correctly you want to do 504 something like the following: 505 1) Make sure the includes and .mk files are up to date. 506 2) Make sure any program used to build the particular 507 utility is up to date. (yacc, lex, etc...) 508 3) cd ...path/to/util... 509 make cleandir 510 rm ...all obj directories... 511 make cleandir # yes, again 512 make obj 513 make depend && make 514 515 Failsafe rebuild of the entire tree: 516 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 517 If you really want to make sure the source tree is clean and 518 ready for a build try the following. Note that sourcing /etc/mk.conf 519 (a make(1) Makefile) in this manner is not right, and will not work 520 for anyone who uses any make(1) features in /etc/mk.conf. 521 522 ---cut here--- 523 #!/bin/sh 524 . /etc/mk.conf 525 526 if [ -z $NETBSDSRCDIR ] ; then 527 NETBSDSRCDIR=/usr/src 528 fi 529 if [ \! -d $NETBSDSRCDIR ] ; then 530 echo Unable to find sources 531 exit 1 532 fi 533 find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 534 535 if [ -z $BSDOBJDIR ] ; then 536 BSDOBJDIR=/usr/obj 537 fi 538 if [ -d $BSDOBJDIR ] ; then 539 rm -rf $BSDOBJDIR 540 fi 541 542 cd $NETBSDSRCDIR && make cleandir 543 544 ---cut here--- 545 546 Critical utilities: 547 ^^^^^^^^^^^^^^^^^^^ 548 usr.bin/make 549 usr.bin/yacc 550 usr.bin/lex 551 usr.bin/xlint 552 usr.bin/config 553 554 Other problems and possible solutions: 555 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 556 Symptom:Complaints involving a Makefile. 557 Fix: Rebuild usr.bin/make: 558 cd usr.bin/make && make && make install 559 Or, a failsafe method if that doesn't work: 560 cd usr.bin/make && cc -DMAKE_NATIVE *.c -I. -o make \ 561 && install make /usr/bin 562 563 Fix: Make sure .mk files are up to date. 564 cd share/mk && make install 565 566 Symptom:Kernel `config' fails to configure any kernel, including GENERIC. 567 Fix: Rebuild usr.bin/config 568 569 Symptom:Obsolete intermediate files are used during compilation 570 Fix: Try the following sequence of commands in the directory in question. 571 make cleandir; rm `make print-objdir`; make cleandir; make obj 572 (If you built the tree without "make obj" in the past, obsolete files 573 may remain. The command tries to clean everything up) 574 575 Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible 576 pointer type 577 Fix: Rebuild and install usr.bin/menuc 578 579 Symptom:mklocale not found during build in share/locale/ctype 580 Fix: Build and install usr.bin/mklocale 581 582 Symptom:undefined reference to `__assert13' or `__unsetenv13' 583 Fix: Rebuild and install lib/libc 584 585 Symptom:usr.bin/config fails to build. 586 Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 587 588 Symptom:undefined reference to `getprogname' or `setprogname' 589 Fix: Rebuild and install lib/libc 590 591 Symptom:Update build fails in src/tools/gcc complaining that a variable 592 (e.g. CPPFLAGS) has changed since the previous run. 593 Fix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 594 595 Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 596 No such file or directory. 597 Cause: If a directory is created by mistake, then it is sometimes 598 deleted from the CVS repository using administrative commands 599 that bypass the normal cvs access controls. If your cvs working tree 600 contains references to a directory that has been deleted on the 601 server in this way, then "cvs update" reports this error. 602 Fix: Recursively delete the affected directory from your working tree 603 and try the update again. 604
Indexes created Sun Oct 12 05:10:08 GMT 2025