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