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