UPDATING revision 1.202
11.202Smrg$NetBSD: UPDATING,v 1.202 2009/10/02 03:13:23 mrg Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.123SjmcSee also: BUILDING, build.sh, Makefile. 151.1Sabs 161.1SabsRecent changes: 171.1Sabs^^^^^^^^^^^^^^^ 181.138Slukem 191.202Smrg20091001: 201.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 211.202Smrg symlink, failing the build. Delete the link, and the subdir 221.202Smrg it is in, and retry your build. 231.202Smrg 241.201Sdsl20090718: 251.201Sdsl libc build changed so that strchr() provides the extra entry 261.201Sdsl point for index(). Update build of libc.a (and libc_pic.a) 271.201Sdsl may fail because the archive contains the unwanted index.o. 281.201Sdsl (Similarly for strrchr() and rindex().) 291.201Sdsl 301.198Smrg20090709: 311.198Smrg Native Xorg was upgraded again. Builds will probably fail again 321.198Smrg without a clean objdir, at least for src/external/mit/xorg. 331.198Smrg 341.197Smrg20090616: 351.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 361.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 371.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 381.197Smrg subdirectory has been changed into a file, and this needs to 391.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 401.197Smrg 411.195Sperry20090501: 421.195Sperry Several new functions were added to string.h/libc, and this 431.195Sperry can cause autoconf problems during the tool build for people 441.195Sperry who fail to clean out their tools objects properly. If you 451.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 461.195Sperry failure during the tool build, clean out all your tools 471.195Sperry objects and start again. 481.195Sperry 491.194Smrg20090325: 501.194Smrg The i386 port was switched to i486 default toolchain. This requires 511.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 521.194Smrg 531.192Sskrll20090126: 541.193Sskrll The __posix_fadvise50 system call changed assembly stub type. You need to 551.193Sskrll 'rm -f __posix_fadvise50.*' in the libc build directory to avoid using 561.192Sskrll the old assembly stub. 571.192Sskrll 581.191Sjoerg20090202: 591.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 601.191Sjoerg detection. It is recommented to rebuild the cache with 611.191Sjoerg ``pkg_admin rebuild''. 621.191Sjoerg 631.184Schristos20090110: 641.184Schristos time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 651.184Schristos 1. Make sure your kernel has COMPAT_50 in it. Build and install. 661.188Schristos This is needed even in the MODULAR kernel because there is 671.188Schristos conditionally compiled code in rtsock.c. 681.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 691.184Schristos before installing. 701.184Schristos 3. If you don't use build.sh and you build directly to root, and 711.187Sdholland your build breaks in the middle, don't despair. Make sure headers 721.184Schristos are installed properly, and start building libraries first libc 731.184Schristos and libutil, install them and then continue building all the 741.184Schristos libraries in src/lib and src/gnu/lib and install them. Once 751.184Schristos the new libraries are installed, you can restart the build. 761.184Schristos 4. If you compile packages and you notice link time warnings, 771.189Shubertf rebuild the required packages to update their shared libraries. 781.189Shubertf Any package you rebuild will require rebuilding all the packages 791.189Shubertf that depend on it. 801.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 811.186Schristos will be upgraded and it will not be backwards compatible. 821.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 831.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 841.190Sapb for utmp. You are better off removing the old files after 851.190Sapb upgrading. The automated clearing of /var/run during 861.190Sapb boot, and the automated rotating of files in /var/log by 871.190Sapb newsyslog(8), may mean that you do not have to remove the 881.190Sapb files manually. 891.190Sapb 7. The optional accounting file (/var/account/acct, see 901.190Sapb accton(8)) has not been versioned, and will need to be 911.190Sapb removed. The automatic rotation of the accounting file by 921.190Sapb /etc/daily limits the bad consequences of failure to remove 931.190Sapb the file. 941.196Sdholland 8. Application software that writes time_t to binary files on 951.196Sdholland disk will break or need attention. Most notably: if you are 961.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 971.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 981.185Sjmcneill 991.183Spgoyette20081219: 1001.183Spgoyette config(1) has been updated, and one of the files it creates - 1011.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 1021.183Spgoyette (done automatically by build.sh) and then you need to rerun 1031.183Spgoyette config on all kernel configuration files before rebuilding those 1041.183Spgoyette kernels. 1051.183Spgoyette 1061.181Scube20081205: 1071.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 1081.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 1091.181Scube set and will appear as extra files for MKX11=no update builds. 1101.178Slukem 1111.179Stsutsui20081122: 1121.182Stsutsui On i386, various kernel options(4) in GENERIC including 1131.180Swiz file systems have been disabled and moved into kernel modules. 1141.180Swiz Before trying a new GENERIC kernel, you have to prepare the 1151.179Stsutsui following files as well as a new GENERIC kernel: 1161.179Stsutsui 1171.179Stsutsui - build and install kernel modules from src/sys/modules 1181.179Stsutsui 1191.179Stsutsui - install the latest bootloader, which will load a module 1201.180Swiz for the file system from which the kernel is loaded automatically 1211.179Stsutsui 1221.180Swiz If you have to load your kernel from a file system which is not of 1231.180Swiz the same type as the root file system, you have to load the necessary 1241.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 1251.179Stsutsui 1261.178Slukem20080827: 1271.178Slukem If you built and installed a libc from sources between 1281.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 1291.178Slukem which results in false errors reported by lint(1). 1301.178Slukem Since this breaks the libc build itself, manual help is 1311.180Swiz needed -- lint must be disabled temporarily, e.g.: 1321.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 1331.178Slukem 1341.177Schristos20080813: 1351.177Schristos MKDEBUG build was broken because the .depend files did not know 1361.177Schristos about .go files. You need to remove all .depend files and rebuild. 1371.177Schristos 1381.200Sdholland20080802: 1391.200Sdholland A regression in binary compatibility for pthread_mutex_t has 1401.200Sdholland been fixed. Unfortunately, the price is breaking compatibility 1411.200Sdholland for -current. 1421.200Sdholland 1431.200Sdholland Threaded programs (using libpthread) and C++ programs (using 1441.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 1451.200Sdholland be recompiled. 1461.200Sdholland 1471.200Sdholland One way to find affected pkgsrc packages: 1481.200Sdholland 1491.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 1501.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 1511.200Sdholland 1521.175Ssimonb20080731: 1531.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 1541.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 1551.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 1561.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 1571.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 1581.176Ssimonb also requires the super block to be in the UFS2 format. You 1591.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 1601.175Ssimonb 1611.174Slukem20080721: 1621.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 1631.174Slukem isn't defined. 1641.174Slukem 1651.173Sfreza20080531: 1661.173Sfreza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 1671.173Sfreza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 1681.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 1691.173Sfreza won't work correctly. The following sequence of commands: 1701.173Sfreza 1711.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 1721.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 1731.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 1741.173Sfreza 1751.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 1761.173Sfreza 1771.172Slukem20080503: 1781.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 1791.172Slukem 1801.171She20080521: 1811.171She For a while, unprivileged UPDATE builds would fail to 1821.171She succeed at the checkflist stage, complaining that 1831.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 1841.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 1851.171She If you already hit this problem, update the .mk file, 1861.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 1871.171She 1881.174Slukem20080303: 1891.174Slukem Linker warnings are now fatal if $WARNS>0. 1901.174Slukem 1911.170Schristos20080126: 1921.170Schristos The posix_fadvise system call has been changed from an assembly 1931.170Schristos stub, to a c file that calls an assembly stub. You need to 1941.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 1951.170Schristos avoid using the old assembly stub. 1961.170Schristos 1971.168Sjoerg20071209: 1981.168Sjoerg The acpiec(4) driver has been split into two attachments. If you 1991.168Sjoerg get ACPI errors before the attachment, please update your kernel 2001.169Swiz configuration file appropriately or see GENERIC for more details. 2011.168Sjoerg 2021.166Sxtraeme20071115: 2031.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 2041.166Sxtraeme argument specified in the kernel configuration file is not valid 2051.166Sxtraeme anymore. The itesio(4) driver now uses the Super I/O address port 2061.166Sxtraeme rather than the EC address port. Please update your kernel 2071.167Swiz configuration file appropriately or see GENERIC for more details. 2081.166Sxtraeme 2091.165Sjmmv20071028: 2101.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 2111.165Sjmmv You need to update any custom kernel configuration file you have 2121.165Sjmmv to remove any references to pccons (which includes removing the 2131.165Sjmmv now useless XSERVER option) and replace them with the correct 2141.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 2151.165Sjmmv for more details. 2161.165Sjmmv 2171.164Sgdt20070913: 2181.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 2191.164Sgdt enumerate interfaces was fixed. The bug began to cause 2201.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 2211.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 2221.164Sgdt could not enumerate interfaces. (These are noted because 2231.164Sgdt normal kernel/userspace version matching hygiene is not 2241.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 2251.164Sgdt and userland are from after 20070913. 2261.164Sgdt 2271.163Sjoerg20070703: 2281.199Sdholland nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 2291.199Sdholland calls the target-specific strip program, and the logic to pass 2301.199Sdholland down STRIP from make has been removed. This requires a 2311.199Sdholland re-installation of tools. 2321.163Sjoerg 2331.161Sdsl20070422: 2341.161Sdsl The way OS emulations lookup filenames inside the emulation root 2351.161Sdsl has been changed. Rather than modify the pathname (and copy back 2361.161Sdsl to userspace) namei() and lookup() directly check the emulation 2371.161Sdsl root. One side effect is that absolute symlinks inside the emulated 2381.167Swiz root file system will be relative to that file system - unless they 2391.161Sdsl start /../ this is useful when the emulated root is a real install 2401.161Sdsl that has such links. 2411.161Sdsl This might affect symlinks that have been added to reference outside 2421.161Sdsl the emulated root. 2431.161Sdsl 2441.160Sjmcneill20070412: 2451.160Sjmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc 2461.160Sjmcneill instead. See the GENERIC32_IP3x kernel configuration for an 2471.160Sjmcneill example. 2481.160Sjmcneill 2491.159Sgdt20070319: 2501.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 2511.159Sgdt on many platforms due to incorrect flags settings. If you 2521.159Sgdt updated and built after about 20070315, do "nbmake-$arch 2531.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 2541.159Sgdt rebuild of object files that might have been built 2551.159Sgdt incorrectly, and ensure that you have at least 2561.159Sgdt src/lib/libc/Makefile 1.130. 2571.159Sgdt 2581.158Sdbj20070210: 2591.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 2601.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 2611.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 2621.158Sdbj will allow dependencies on those files to get get rebuilt 2631.158Sdbj 2641.157Sapb20070209: 2651.157Sapb The threading model was changed when the newlock2 branch 2661.157Sapb was merged to NetBSD-current. If you boot with a new 2671.157Sapb kernel (version 4.99.10), then you also need a new pthread 2681.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 2691.157Sapb an old kernel, then you need the old pthread library 2701.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 2711.157Sapb the pthread library in sync, old threaded applications should 2721.157Sapb continue to work with an old or new kernel. Note that named(8) 2731.157Sapb is the only threaded application in the base system. 2741.157Sapb 2751.154She20061214: 2761.154She Following the move of string_to_flags() and flags_to_string() 2771.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 2781.154She will need to do a "make cleandir" in 2791.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 2801.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 2811.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 2821.156She as the installation images in distrib/ 2831.154She in order to excise stale references to the old stat_flags.h header 2841.154She file in the ls sources -- stat_flags.h has been removed. 2851.154She 2861.152Schristos20061108: 2871.152Schristos The configure script used in the src/tools/gcc compiler has been 2881.152Schristos changed to indicate that our libc has ssp support built-in and 2891.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 2901.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 2911.152Schristos 2921.151Srpaulo20061009: 2931.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 2941.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 2951.151Srpaulo 2961.150Sbjh2120060814: 2971.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 2981.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 2991.150Sbjh21 kernel configuration for an example. X servers from the last 3001.150Sbjh21 few years should cope. 3011.150Sbjh21 3021.149Schristos20060703: 3031.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 3041.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 3051.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 3061.149Schristos 3071.148Sdogcow20060627: 3081.148Sdogcow socket(2) has changed, and its system call has been versioned. 3091.148Sdogcow For userlands with the old version of socket(2), make sure that 3101.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 3111.148Sdogcow errors will result. 3121.148Sdogcow 3131.1SabsHints for a more successful build: 3141.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3151.123Sjmc Use build.sh, but do not use its "expert mode": 3161.132Sjmmv This will automatically build the tools in the 3171.123Sjmc correct order, and it will keep the tools and the 3181.123Sjmc new build products from interfering with the running 3191.123Sjmc system. This will allow you to ignore most of the 3201.123Sjmc other advice in this file. 3211.2Smrg Build a new kernel first: 3221.2Smrg This makes sure that any new system calls or features 3231.2Smrg expected by the new userland will be present. This 3241.2Smrg helps to avoid critical errors when upgrading. 3251.1Sabs Use object directories: 3261.1Sabs This helps to keep stale object 3271.1Sabs files from polluting the build if a Makefile "forgets" 3281.1Sabs about one. It also makes it easier to clean up after 3291.1Sabs a build. It's also necessary if you want to use the 3301.1Sabs same source tree for multiple machines. 3311.123Sjmc To use object directories with build.sh: 3321.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 3331.123Sjmc To use object directories without using build.sh: 3341.1Sabs a) cd /usr/src ; make cleandir 3351.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 3361.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 3371.1Sabs d) cd /usr/src ; make build 3381.2Smrg Note that running "make obj" in a directory will create 3391.2Smrg in obj.$MACHINE directory. 3401.1Sabs Build to a DESTDIR: 3411.123Sjmc This helps to keep old installed files (especially libraries) 3421.123Sjmc from interfering with the new build. 3431.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 3441.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 3451.123Sjmc environment variable before running make build. It should be 3461.123Sjmc set to the pathname of an initially empty directory. 3471.123Sjmc Problems: if you do not use build.sh, you might need to 3481.123Sjmc update critical utilities without using DESTDIR since 3491.123Sjmc nothing is executed from what is installed in DESTDIR. 3501.123Sjmc (See critical utils, below.) 3511.1Sabs Build often: 3521.1Sabs This keeps critical utilities current enough to not choke 3531.1Sabs on any other part of the source tree that depends on up to 3541.123Sjmc date functionality. If you use build.sh, you should not have 3551.123Sjmc this problem. 3561.1Sabs 3571.1SabsWhat to do if things don't work: 3581.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3591.1SabsWhen things don't work there is usually a few things that commonly 3601.1Sabsshould be done. 3611.1Sabs 1) make includes 3621.1Sabs This should be done automatically by make build. 3631.1Sabs 2) cd share/mk && make install 3641.1Sabs Again, automatically done by make build. 3651.1Sabs 3661.1SabsFailsafe rebuild of a small part of the tree: 3671.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3681.1SabsTo make sure you rebuild something correctly you want to do 3691.1Sabssomething like the following: 3701.1Sabs 1) Make sure the includes and .mk files are up to date. 3711.1Sabs 2) Make sure any program used to build the particular 3721.1Sabs utility is up to date. (yacc, lex, etc...) 3731.1Sabs 3) cd ...path/to/util... 3741.1Sabs make cleandir 3751.1Sabs rm ...all obj directories... 3761.1Sabs make cleandir # yes, again 3771.1Sabs make obj 3781.1Sabs make depend && make 3791.1Sabs 3801.1SabsFailsafe rebuild of the entire tree: 3811.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3821.1SabsIf you really want to make sure the source tree is clean and 3831.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 3841.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 3851.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 3861.1Sabs 3871.1Sabs---cut here--- 3881.1Sabs#!/bin/sh 3891.1Sabs. /etc/mk.conf 3901.1Sabs 3911.58Slukemif [ -z $NETBSDSRCDIR ] ; then 3921.58Slukem NETBSDSRCDIR=/usr/src 3931.1Sabsfi 3941.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 3951.1Sabs echo Unable to find sources 3961.1Sabs exit 1 3971.1Sabsfi 3981.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 3991.1Sabs 4001.1Sabsif [ -z $BSDOBJDIR ] ; then 4011.1Sabs BSDOBJDIR=/usr/obj 4021.1Sabsfi 4031.1Sabsif [ -d $BSDOBJDIR ] ; then 4041.1Sabs rm -rf $BSDOBJDIR 4051.1Sabsfi 4061.1Sabs 4071.58Slukemcd $NETBSDSRCDIR && make cleandir 4081.1Sabs 4091.1Sabs---cut here--- 4101.1Sabs 4111.1SabsCritical utilities: 4121.1Sabs^^^^^^^^^^^^^^^^^^^ 4131.3Sitojun usr.bin/compile_et 4141.1Sabs usr.bin/make 4151.1Sabs usr.bin/yacc 4161.1Sabs usr.bin/lex 4171.11Slukem usr.bin/xlint 4181.142Sdrochner usr.bin/config 4191.1Sabs 4201.34SsimonbOther problems and possible solutions: 4211.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4221.1SabsSymptom:Complaints involving a Makefile. 4231.17SerhFix: Rebuild usr.bin/make: 4241.17Serh cd usr.bin/make && make && make install 4251.111Ssimonb Or, a failsafe method if that doesn't work: 4261.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 4271.17Serh 4281.1SabsFix: Make sure .mk files are up to date. 4291.1Sabs cd share/mk && make install 4301.2Smrg 4311.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 4321.142SdrochnerFix: Rebuild usr.bin/config 4331.1Sabs 4341.1SabsSymptom: 4351.1SabsFix: Rebuild usr.bin/yacc 4361.1Sabs 4371.1SabsSymptom: 4381.1SabsFix: Rebuild usr.bin/lex 4391.1Sabs 4401.1SabsSymptom: 4411.1SabsFix: rm /usr/lib/libbfd.a 4421.4Sitojun 4431.4SitojunSymptom:Obsolete intermediate files are used during compilation 4441.4SitojunFix: Try the following sequence of commands in the directory in question. 4451.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 4461.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 4471.4Sitojun may remain. The command tries to clean everything up) 4481.5Swiz 4491.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 4501.5SwizFix: Rebuild and install usr.bin/menuc 4511.12Sitojun 4521.12SitojunSymptom:mklocale not found during build in share/locale/ctype 4531.12SitojunFix: Build and install usr.bin/mklocale 4541.13Sdogcow 4551.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 4561.13SdogcowFix: Rebuild and install lib/libc 4571.13Sdogcow 4581.142SdrochnerSymptom:usr.bin/config fails to build. 4591.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 4601.13Sdogcow 4611.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 4621.19ScgdFix: Rebuild and install lib/libc 4631.24Sabs 4641.24SabsSymptom:lint does not understand the '-X' option 4651.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 466