UPDATING revision 1.198
11.198Smrg$NetBSD: UPDATING,v 1.198 2009/07/09 07:31:54 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.198Smrg20090709: 201.198Smrg Native Xorg was upgraded again. Builds will probably fail again 211.198Smrg without a clean objdir, at least for src/external/mit/xorg. 221.198Smrg 231.197Smrg20090616: 241.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 251.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 261.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 271.197Smrg subdirectory has been changed into a file, and this needs to 281.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 291.197Smrg 301.195Sperry20090501: 311.195Sperry Several new functions were added to string.h/libc, and this 321.195Sperry can cause autoconf problems during the tool build for people 331.195Sperry who fail to clean out their tools objects properly. If you 341.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 351.195Sperry failure during the tool build, clean out all your tools 361.195Sperry objects and start again. 371.195Sperry 381.194Smrg20090325: 391.194Smrg The i386 port was switched to i486 default toolchain. This requires 401.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 411.194Smrg 421.192Sskrll20090126: 431.193Sskrll The __posix_fadvise50 system call changed assembly stub type. You need to 441.193Sskrll 'rm -f __posix_fadvise50.*' in the libc build directory to avoid using 451.192Sskrll the old assembly stub. 461.192Sskrll 471.191Sjoerg20090202: 481.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 491.191Sjoerg detection. It is recommented to rebuild the cache with 501.191Sjoerg ``pkg_admin rebuild''. 511.191Sjoerg 521.184Schristos20090110: 531.184Schristos time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 541.184Schristos 1. Make sure your kernel has COMPAT_50 in it. Build and install. 551.188Schristos This is needed even in the MODULAR kernel because there is 561.188Schristos conditionally compiled code in rtsock.c. 571.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 581.184Schristos before installing. 591.184Schristos 3. If you don't use build.sh and you build directly to root, and 601.187Sdholland your build breaks in the middle, don't despair. Make sure headers 611.184Schristos are installed properly, and start building libraries first libc 621.184Schristos and libutil, install them and then continue building all the 631.184Schristos libraries in src/lib and src/gnu/lib and install them. Once 641.184Schristos the new libraries are installed, you can restart the build. 651.184Schristos 4. If you compile packages and you notice link time warnings, 661.189Shubertf rebuild the required packages to update their shared libraries. 671.189Shubertf Any package you rebuild will require rebuilding all the packages 681.189Shubertf that depend on it. 691.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 701.186Schristos will be upgraded and it will not be backwards compatible. 711.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 721.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 731.190Sapb for utmp. You are better off removing the old files after 741.190Sapb upgrading. The automated clearing of /var/run during 751.190Sapb boot, and the automated rotating of files in /var/log by 761.190Sapb newsyslog(8), may mean that you do not have to remove the 771.190Sapb files manually. 781.190Sapb 7. The optional accounting file (/var/account/acct, see 791.190Sapb accton(8)) has not been versioned, and will need to be 801.190Sapb removed. The automatic rotation of the accounting file by 811.190Sapb /etc/daily limits the bad consequences of failure to remove 821.190Sapb the file. 831.196Sdholland 8. Application software that writes time_t to binary files on 841.196Sdholland disk will break or need attention. Most notably: if you are 851.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 861.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 871.185Sjmcneill 881.183Spgoyette20081219: 891.183Spgoyette config(1) has been updated, and one of the files it creates - 901.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 911.183Spgoyette (done automatically by build.sh) and then you need to rerun 921.183Spgoyette config on all kernel configuration files before rebuilding those 931.183Spgoyette kernels. 941.183Spgoyette 951.181Scube20081205: 961.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 971.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 981.181Scube set and will appear as extra files for MKX11=no update builds. 991.178Slukem 1001.179Stsutsui20081122: 1011.182Stsutsui On i386, various kernel options(4) in GENERIC including 1021.180Swiz file systems have been disabled and moved into kernel modules. 1031.180Swiz Before trying a new GENERIC kernel, you have to prepare the 1041.179Stsutsui following files as well as a new GENERIC kernel: 1051.179Stsutsui 1061.179Stsutsui - build and install kernel modules from src/sys/modules 1071.179Stsutsui 1081.179Stsutsui - install the latest bootloader, which will load a module 1091.180Swiz for the file system from which the kernel is loaded automatically 1101.179Stsutsui 1111.180Swiz If you have to load your kernel from a file system which is not of 1121.180Swiz the same type as the root file system, you have to load the necessary 1131.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 1141.179Stsutsui 1151.178Slukem20080827: 1161.178Slukem If you built and installed a libc from sources between 1171.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 1181.178Slukem which results in false errors reported by lint(1). 1191.178Slukem Since this breaks the libc build itself, manual help is 1201.180Swiz needed -- lint must be disabled temporarily, e.g.: 1211.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 1221.178Slukem 1231.177Schristos20080813: 1241.177Schristos MKDEBUG build was broken because the .depend files did not know 1251.177Schristos about .go files. You need to remove all .depend files and rebuild. 1261.177Schristos 1271.175Ssimonb20080731: 1281.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 1291.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 1301.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 1311.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 1321.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 1331.176Ssimonb also requires the super block to be in the UFS2 format. You 1341.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 1351.175Ssimonb 1361.174Slukem20080721: 1371.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 1381.174Slukem isn't defined. 1391.174Slukem 1401.173Sfreza20080531: 1411.173Sfreza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 1421.173Sfreza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 1431.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 1441.173Sfreza won't work correctly. The following sequence of commands: 1451.173Sfreza 1461.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 1471.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 1481.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 1491.173Sfreza 1501.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 1511.173Sfreza 1521.172Slukem20080503: 1531.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 1541.172Slukem 1551.171She20080521: 1561.171She For a while, unprivileged UPDATE builds would fail to 1571.171She succeed at the checkflist stage, complaining that 1581.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 1591.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 1601.171She If you already hit this problem, update the .mk file, 1611.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 1621.171She 1631.174Slukem20080303: 1641.174Slukem Linker warnings are now fatal if $WARNS>0. 1651.174Slukem 1661.170Schristos20080126: 1671.170Schristos The posix_fadvise system call has been changed from an assembly 1681.170Schristos stub, to a c file that calls an assembly stub. You need to 1691.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 1701.170Schristos avoid using the old assembly stub. 1711.170Schristos 1721.168Sjoerg20071209: 1731.168Sjoerg The acpiec(4) driver has been split into two attachments. If you 1741.168Sjoerg get ACPI errors before the attachment, please update your kernel 1751.169Swiz configuration file appropriately or see GENERIC for more details. 1761.168Sjoerg 1771.166Sxtraeme20071115: 1781.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 1791.166Sxtraeme argument specified in the kernel configuration file is not valid 1801.166Sxtraeme anymore. The itesio(4) driver now uses the Super I/O address port 1811.166Sxtraeme rather than the EC address port. Please update your kernel 1821.167Swiz configuration file appropriately or see GENERIC for more details. 1831.166Sxtraeme 1841.165Sjmmv20071028: 1851.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 1861.165Sjmmv You need to update any custom kernel configuration file you have 1871.165Sjmmv to remove any references to pccons (which includes removing the 1881.165Sjmmv now useless XSERVER option) and replace them with the correct 1891.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 1901.165Sjmmv for more details. 1911.165Sjmmv 1921.164Sgdt20070913: 1931.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 1941.164Sgdt enumerate interfaces was fixed. The bug began to cause 1951.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 1961.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 1971.164Sgdt could not enumerate interfaces. (These are noted because 1981.164Sgdt normal kernel/userspace version matching hygiene is not 1991.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 2001.164Sgdt and userland are from after 20070913. 2011.164Sgdt 2021.163Sjoerg20070703: 2031.163Sjoerg nbinstall has been renamed as it calls the target specific and 2041.163Sjoerg the logic to pass down STRIP from mk been removed. This forces 2051.163Sjoerg a re-installation of tools. 2061.163Sjoerg 2071.161Sdsl20070422: 2081.161Sdsl The way OS emulations lookup filenames inside the emulation root 2091.161Sdsl has been changed. Rather than modify the pathname (and copy back 2101.161Sdsl to userspace) namei() and lookup() directly check the emulation 2111.161Sdsl root. One side effect is that absolute symlinks inside the emulated 2121.167Swiz root file system will be relative to that file system - unless they 2131.161Sdsl start /../ this is useful when the emulated root is a real install 2141.161Sdsl that has such links. 2151.161Sdsl This might affect symlinks that have been added to reference outside 2161.161Sdsl the emulated root. 2171.161Sdsl 2181.160Sjmcneill20070412: 2191.160Sjmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc 2201.160Sjmcneill instead. See the GENERIC32_IP3x kernel configuration for an 2211.160Sjmcneill example. 2221.160Sjmcneill 2231.159Sgdt20070319: 2241.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 2251.159Sgdt on many platforms due to incorrect flags settings. If you 2261.159Sgdt updated and built after about 20070315, do "nbmake-$arch 2271.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 2281.159Sgdt rebuild of object files that might have been built 2291.159Sgdt incorrectly, and ensure that you have at least 2301.159Sgdt src/lib/libc/Makefile 1.130. 2311.159Sgdt 2321.158Sdbj20070210: 2331.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 2341.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 2351.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 2361.158Sdbj will allow dependencies on those files to get get rebuilt 2371.158Sdbj 2381.157Sapb20070209: 2391.157Sapb The threading model was changed when the newlock2 branch 2401.157Sapb was merged to NetBSD-current. If you boot with a new 2411.157Sapb kernel (version 4.99.10), then you also need a new pthread 2421.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 2431.157Sapb an old kernel, then you need the old pthread library 2441.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 2451.157Sapb the pthread library in sync, old threaded applications should 2461.157Sapb continue to work with an old or new kernel. Note that named(8) 2471.157Sapb is the only threaded application in the base system. 2481.157Sapb 2491.154She20061214: 2501.154She Following the move of string_to_flags() and flags_to_string() 2511.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 2521.154She will need to do a "make cleandir" in 2531.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 2541.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 2551.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 2561.156She as the installation images in distrib/ 2571.154She in order to excise stale references to the old stat_flags.h header 2581.154She file in the ls sources -- stat_flags.h has been removed. 2591.154She 2601.152Schristos20061108: 2611.152Schristos The configure script used in the src/tools/gcc compiler has been 2621.152Schristos changed to indicate that our libc has ssp support built-in and 2631.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 2641.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 2651.152Schristos 2661.151Srpaulo20061009: 2671.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 2681.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 2691.151Srpaulo 2701.150Sbjh2120060814: 2711.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 2721.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 2731.150Sbjh21 kernel configuration for an example. X servers from the last 2741.150Sbjh21 few years should cope. 2751.150Sbjh21 2761.149Schristos20060703: 2771.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 2781.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 2791.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 2801.149Schristos 2811.148Sdogcow20060627: 2821.148Sdogcow socket(2) has changed, and its system call has been versioned. 2831.148Sdogcow For userlands with the old version of socket(2), make sure that 2841.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 2851.148Sdogcow errors will result. 2861.148Sdogcow 2871.1SabsHints for a more successful build: 2881.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2891.123Sjmc Use build.sh, but do not use its "expert mode": 2901.132Sjmmv This will automatically build the tools in the 2911.123Sjmc correct order, and it will keep the tools and the 2921.123Sjmc new build products from interfering with the running 2931.123Sjmc system. This will allow you to ignore most of the 2941.123Sjmc other advice in this file. 2951.2Smrg Build a new kernel first: 2961.2Smrg This makes sure that any new system calls or features 2971.2Smrg expected by the new userland will be present. This 2981.2Smrg helps to avoid critical errors when upgrading. 2991.1Sabs Use object directories: 3001.1Sabs This helps to keep stale object 3011.1Sabs files from polluting the build if a Makefile "forgets" 3021.1Sabs about one. It also makes it easier to clean up after 3031.1Sabs a build. It's also necessary if you want to use the 3041.1Sabs same source tree for multiple machines. 3051.123Sjmc To use object directories with build.sh: 3061.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 3071.123Sjmc To use object directories without using build.sh: 3081.1Sabs a) cd /usr/src ; make cleandir 3091.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 3101.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 3111.1Sabs d) cd /usr/src ; make build 3121.2Smrg Note that running "make obj" in a directory will create 3131.2Smrg in obj.$MACHINE directory. 3141.1Sabs Build to a DESTDIR: 3151.123Sjmc This helps to keep old installed files (especially libraries) 3161.123Sjmc from interfering with the new build. 3171.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 3181.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 3191.123Sjmc environment variable before running make build. It should be 3201.123Sjmc set to the pathname of an initially empty directory. 3211.123Sjmc Problems: if you do not use build.sh, you might need to 3221.123Sjmc update critical utilities without using DESTDIR since 3231.123Sjmc nothing is executed from what is installed in DESTDIR. 3241.123Sjmc (See critical utils, below.) 3251.1Sabs Build often: 3261.1Sabs This keeps critical utilities current enough to not choke 3271.1Sabs on any other part of the source tree that depends on up to 3281.123Sjmc date functionality. If you use build.sh, you should not have 3291.123Sjmc this problem. 3301.1Sabs 3311.1SabsWhat to do if things don't work: 3321.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3331.1SabsWhen things don't work there is usually a few things that commonly 3341.1Sabsshould be done. 3351.1Sabs 1) make includes 3361.1Sabs This should be done automatically by make build. 3371.1Sabs 2) cd share/mk && make install 3381.1Sabs Again, automatically done by make build. 3391.1Sabs 3401.1SabsFailsafe rebuild of a small part of the tree: 3411.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3421.1SabsTo make sure you rebuild something correctly you want to do 3431.1Sabssomething like the following: 3441.1Sabs 1) Make sure the includes and .mk files are up to date. 3451.1Sabs 2) Make sure any program used to build the particular 3461.1Sabs utility is up to date. (yacc, lex, etc...) 3471.1Sabs 3) cd ...path/to/util... 3481.1Sabs make cleandir 3491.1Sabs rm ...all obj directories... 3501.1Sabs make cleandir # yes, again 3511.1Sabs make obj 3521.1Sabs make depend && make 3531.1Sabs 3541.1SabsFailsafe rebuild of the entire tree: 3551.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3561.1SabsIf you really want to make sure the source tree is clean and 3571.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 3581.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 3591.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 3601.1Sabs 3611.1Sabs---cut here--- 3621.1Sabs#!/bin/sh 3631.1Sabs. /etc/mk.conf 3641.1Sabs 3651.58Slukemif [ -z $NETBSDSRCDIR ] ; then 3661.58Slukem NETBSDSRCDIR=/usr/src 3671.1Sabsfi 3681.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 3691.1Sabs echo Unable to find sources 3701.1Sabs exit 1 3711.1Sabsfi 3721.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 3731.1Sabs 3741.1Sabsif [ -z $BSDOBJDIR ] ; then 3751.1Sabs BSDOBJDIR=/usr/obj 3761.1Sabsfi 3771.1Sabsif [ -d $BSDOBJDIR ] ; then 3781.1Sabs rm -rf $BSDOBJDIR 3791.1Sabsfi 3801.1Sabs 3811.58Slukemcd $NETBSDSRCDIR && make cleandir 3821.1Sabs 3831.1Sabs---cut here--- 3841.1Sabs 3851.1SabsCritical utilities: 3861.1Sabs^^^^^^^^^^^^^^^^^^^ 3871.3Sitojun usr.bin/compile_et 3881.1Sabs usr.bin/make 3891.1Sabs usr.bin/yacc 3901.1Sabs usr.bin/lex 3911.11Slukem usr.bin/xlint 3921.142Sdrochner usr.bin/config 3931.1Sabs 3941.34SsimonbOther problems and possible solutions: 3951.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3961.1SabsSymptom:Complaints involving a Makefile. 3971.17SerhFix: Rebuild usr.bin/make: 3981.17Serh cd usr.bin/make && make && make install 3991.111Ssimonb Or, a failsafe method if that doesn't work: 4001.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 4011.17Serh 4021.1SabsFix: Make sure .mk files are up to date. 4031.1Sabs cd share/mk && make install 4041.2Smrg 4051.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 4061.142SdrochnerFix: Rebuild usr.bin/config 4071.1Sabs 4081.1SabsSymptom: 4091.1SabsFix: Rebuild usr.bin/yacc 4101.1Sabs 4111.1SabsSymptom: 4121.1SabsFix: Rebuild usr.bin/lex 4131.1Sabs 4141.1SabsSymptom: 4151.1SabsFix: rm /usr/lib/libbfd.a 4161.4Sitojun 4171.4SitojunSymptom:Obsolete intermediate files are used during compilation 4181.4SitojunFix: Try the following sequence of commands in the directory in question. 4191.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 4201.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 4211.4Sitojun may remain. The command tries to clean everything up) 4221.5Swiz 4231.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 4241.5SwizFix: Rebuild and install usr.bin/menuc 4251.12Sitojun 4261.12SitojunSymptom:mklocale not found during build in share/locale/ctype 4271.12SitojunFix: Build and install usr.bin/mklocale 4281.13Sdogcow 4291.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 4301.13SdogcowFix: Rebuild and install lib/libc 4311.13Sdogcow 4321.142SdrochnerSymptom:usr.bin/config fails to build. 4331.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 4341.13Sdogcow 4351.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 4361.19ScgdFix: Rebuild and install lib/libc 4371.24Sabs 4381.24SabsSymptom:lint does not understand the '-X' option 4391.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 440