UPDATING revision 1.215
11.215Smrg$NetBSD: UPDATING,v 1.215 2010/11/23 06:49:29 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.215Smrg20101119: 201.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 211.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 221.215Smrg have any build problems with xsrc, or problems with mismatched 231.215Smrg versions between xorg-server and drivers. 241.215Smrg 251.213Sjmmv20100604: 261.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 271.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 281.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 291.213Sjmmv trees by hand. 301.213Sjmmv 311.211Stnozaki20100522: 321.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 331.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 341.212Smrg build problems with xsrc. 351.212Smrg 361.212Smrg20100522: 371.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 381.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 391.211Stnozaki 401.210Schristos20100520: 411.210Schristos The location of the xkb compiled descriptions has changed. Please 421.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 431.210Schristos 441.209Snjoly20100222: 451.209Snjoly The shared objects file extension has been changed from .so to 461.209Snjoly .pico, in order to avoid conflicts with shared libraries names 471.209Snjoly libXX.so. All now stale regular .so files can be removed from 481.209Snjoly your object directories. 491.209Snjoly 501.208Sroy20100204: 511.208Sroy The termcap database has been removed from the sources, 521.208Sroy but has not been marked obsolete so it is not removed 531.208Sroy from the system when upgrading. 541.208Sroy As such, you will need to remove them from your object 551.208Sroy and destination directories. 561.208Sroy 571.203Sdyoung20091101: 581.205Sdholland After updating, it may be necessary to make the 'cleandir' 591.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 601.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 611.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 621.203Sdyoung 631.202Smrg20091001: 641.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 651.206Sdholland before building a kernel, or the build fails on cpufunc.S. 661.206Sdholland 671.206Sdholland20091001: 681.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 691.202Smrg symlink, failing the build. Delete the link, and the subdir 701.202Smrg it is in, and retry your build. 711.202Smrg 721.201Sdsl20090718: 731.201Sdsl libc build changed so that strchr() provides the extra entry 741.201Sdsl point for index(). Update build of libc.a (and libc_pic.a) 751.201Sdsl may fail because the archive contains the unwanted index.o. 761.201Sdsl (Similarly for strrchr() and rindex().) 771.201Sdsl 781.198Smrg20090709: 791.198Smrg Native Xorg was upgraded again. Builds will probably fail again 801.198Smrg without a clean objdir, at least for src/external/mit/xorg. 811.198Smrg 821.197Smrg20090616: 831.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 841.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 851.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 861.197Smrg subdirectory has been changed into a file, and this needs to 871.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 881.197Smrg 891.195Sperry20090501: 901.195Sperry Several new functions were added to string.h/libc, and this 911.195Sperry can cause autoconf problems during the tool build for people 921.195Sperry who fail to clean out their tools objects properly. If you 931.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 941.195Sperry failure during the tool build, clean out all your tools 951.195Sperry objects and start again. 961.195Sperry 971.194Smrg20090325: 981.194Smrg The i386 port was switched to i486 default toolchain. This requires 991.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 1001.194Smrg 1011.192Sskrll20090126: 1021.207Smbalmer The __posix_fadvise50 system call changed assembly stub type. You 1031.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 1041.207Smbalmer to avoid using the old assembly stub. 1051.192Sskrll 1061.191Sjoerg20090202: 1071.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 1081.191Sjoerg detection. It is recommented to rebuild the cache with 1091.191Sjoerg ``pkg_admin rebuild''. 1101.191Sjoerg 1111.184Schristos20090110: 1121.184Schristos time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 1131.184Schristos 1. Make sure your kernel has COMPAT_50 in it. Build and install. 1141.188Schristos This is needed even in the MODULAR kernel because there is 1151.188Schristos conditionally compiled code in rtsock.c. 1161.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 1171.184Schristos before installing. 1181.184Schristos 3. If you don't use build.sh and you build directly to root, and 1191.187Sdholland your build breaks in the middle, don't despair. Make sure headers 1201.184Schristos are installed properly, and start building libraries first libc 1211.184Schristos and libutil, install them and then continue building all the 1221.184Schristos libraries in src/lib and src/gnu/lib and install them. Once 1231.184Schristos the new libraries are installed, you can restart the build. 1241.184Schristos 4. If you compile packages and you notice link time warnings, 1251.189Shubertf rebuild the required packages to update their shared libraries. 1261.189Shubertf Any package you rebuild will require rebuilding all the packages 1271.189Shubertf that depend on it. 1281.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 1291.186Schristos will be upgraded and it will not be backwards compatible. 1301.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 1311.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 1321.190Sapb for utmp. You are better off removing the old files after 1331.190Sapb upgrading. The automated clearing of /var/run during 1341.190Sapb boot, and the automated rotating of files in /var/log by 1351.190Sapb newsyslog(8), may mean that you do not have to remove the 1361.190Sapb files manually. 1371.190Sapb 7. The optional accounting file (/var/account/acct, see 1381.190Sapb accton(8)) has not been versioned, and will need to be 1391.190Sapb removed. The automatic rotation of the accounting file by 1401.190Sapb /etc/daily limits the bad consequences of failure to remove 1411.190Sapb the file. 1421.196Sdholland 8. Application software that writes time_t to binary files on 1431.196Sdholland disk will break or need attention. Most notably: if you are 1441.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 1451.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 1461.185Sjmcneill 1471.183Spgoyette20081219: 1481.183Spgoyette config(1) has been updated, and one of the files it creates - 1491.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 1501.183Spgoyette (done automatically by build.sh) and then you need to rerun 1511.183Spgoyette config on all kernel configuration files before rebuilding those 1521.183Spgoyette kernels. 1531.183Spgoyette 1541.181Scube20081205: 1551.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 1561.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 1571.181Scube set and will appear as extra files for MKX11=no update builds. 1581.178Slukem 1591.179Stsutsui20081122: 1601.182Stsutsui On i386, various kernel options(4) in GENERIC including 1611.180Swiz file systems have been disabled and moved into kernel modules. 1621.180Swiz Before trying a new GENERIC kernel, you have to prepare the 1631.179Stsutsui following files as well as a new GENERIC kernel: 1641.179Stsutsui 1651.179Stsutsui - build and install kernel modules from src/sys/modules 1661.179Stsutsui 1671.179Stsutsui - install the latest bootloader, which will load a module 1681.180Swiz for the file system from which the kernel is loaded automatically 1691.179Stsutsui 1701.180Swiz If you have to load your kernel from a file system which is not of 1711.180Swiz the same type as the root file system, you have to load the necessary 1721.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 1731.179Stsutsui 1741.178Slukem20080827: 1751.178Slukem If you built and installed a libc from sources between 1761.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 1771.178Slukem which results in false errors reported by lint(1). 1781.178Slukem Since this breaks the libc build itself, manual help is 1791.180Swiz needed -- lint must be disabled temporarily, e.g.: 1801.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 1811.178Slukem 1821.177Schristos20080813: 1831.177Schristos MKDEBUG build was broken because the .depend files did not know 1841.177Schristos about .go files. You need to remove all .depend files and rebuild. 1851.177Schristos 1861.200Sdholland20080802: 1871.200Sdholland A regression in binary compatibility for pthread_mutex_t has 1881.200Sdholland been fixed. Unfortunately, the price is breaking compatibility 1891.200Sdholland for -current. 1901.200Sdholland 1911.200Sdholland Threaded programs (using libpthread) and C++ programs (using 1921.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 1931.200Sdholland be recompiled. 1941.200Sdholland 1951.200Sdholland One way to find affected pkgsrc packages: 1961.200Sdholland 1971.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 1981.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 1991.200Sdholland 2001.175Ssimonb20080731: 2011.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 2021.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 2031.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 2041.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 2051.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 2061.176Ssimonb also requires the super block to be in the UFS2 format. You 2071.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 2081.175Ssimonb 2091.174Slukem20080721: 2101.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 2111.174Slukem isn't defined. 2121.174Slukem 2131.173Sfreza20080531: 2141.173Sfreza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 2151.173Sfreza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 2161.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 2171.173Sfreza won't work correctly. The following sequence of commands: 2181.173Sfreza 2191.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 2201.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 2211.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 2221.173Sfreza 2231.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 2241.173Sfreza 2251.172Slukem20080503: 2261.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 2271.172Slukem 2281.171She20080521: 2291.171She For a while, unprivileged UPDATE builds would fail to 2301.171She succeed at the checkflist stage, complaining that 2311.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 2321.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 2331.171She If you already hit this problem, update the .mk file, 2341.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 2351.171She 2361.174Slukem20080303: 2371.174Slukem Linker warnings are now fatal if $WARNS>0. 2381.174Slukem 2391.170Schristos20080126: 2401.170Schristos The posix_fadvise system call has been changed from an assembly 2411.170Schristos stub, to a c file that calls an assembly stub. You need to 2421.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 2431.170Schristos avoid using the old assembly stub. 2441.170Schristos 2451.168Sjoerg20071209: 2461.168Sjoerg The acpiec(4) driver has been split into two attachments. If you 2471.168Sjoerg get ACPI errors before the attachment, please update your kernel 2481.169Swiz configuration file appropriately or see GENERIC for more details. 2491.168Sjoerg 2501.166Sxtraeme20071115: 2511.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 2521.166Sxtraeme argument specified in the kernel configuration file is not valid 2531.166Sxtraeme anymore. The itesio(4) driver now uses the Super I/O address port 2541.166Sxtraeme rather than the EC address port. Please update your kernel 2551.167Swiz configuration file appropriately or see GENERIC for more details. 2561.166Sxtraeme 2571.165Sjmmv20071028: 2581.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 2591.165Sjmmv You need to update any custom kernel configuration file you have 2601.165Sjmmv to remove any references to pccons (which includes removing the 2611.165Sjmmv now useless XSERVER option) and replace them with the correct 2621.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 2631.165Sjmmv for more details. 2641.165Sjmmv 2651.164Sgdt20070913: 2661.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 2671.164Sgdt enumerate interfaces was fixed. The bug began to cause 2681.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 2691.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 2701.164Sgdt could not enumerate interfaces. (These are noted because 2711.164Sgdt normal kernel/userspace version matching hygiene is not 2721.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 2731.164Sgdt and userland are from after 20070913. 2741.164Sgdt 2751.163Sjoerg20070703: 2761.199Sdholland nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 2771.199Sdholland calls the target-specific strip program, and the logic to pass 2781.199Sdholland down STRIP from make has been removed. This requires a 2791.199Sdholland re-installation of tools. 2801.163Sjoerg 2811.161Sdsl20070422: 2821.161Sdsl The way OS emulations lookup filenames inside the emulation root 2831.161Sdsl has been changed. Rather than modify the pathname (and copy back 2841.161Sdsl to userspace) namei() and lookup() directly check the emulation 2851.161Sdsl root. One side effect is that absolute symlinks inside the emulated 2861.167Swiz root file system will be relative to that file system - unless they 2871.161Sdsl start /../ this is useful when the emulated root is a real install 2881.161Sdsl that has such links. 2891.161Sdsl This might affect symlinks that have been added to reference outside 2901.161Sdsl the emulated root. 2911.161Sdsl 2921.160Sjmcneill20070412: 2931.160Sjmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc 2941.160Sjmcneill instead. See the GENERIC32_IP3x kernel configuration for an 2951.160Sjmcneill example. 2961.160Sjmcneill 2971.159Sgdt20070319: 2981.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 2991.159Sgdt on many platforms due to incorrect flags settings. If you 3001.159Sgdt updated and built after about 20070315, do "nbmake-$arch 3011.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 3021.159Sgdt rebuild of object files that might have been built 3031.159Sgdt incorrectly, and ensure that you have at least 3041.159Sgdt src/lib/libc/Makefile 1.130. 3051.159Sgdt 3061.158Sdbj20070210: 3071.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 3081.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 3091.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 3101.158Sdbj will allow dependencies on those files to get get rebuilt 3111.158Sdbj 3121.157Sapb20070209: 3131.157Sapb The threading model was changed when the newlock2 branch 3141.157Sapb was merged to NetBSD-current. If you boot with a new 3151.157Sapb kernel (version 4.99.10), then you also need a new pthread 3161.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 3171.157Sapb an old kernel, then you need the old pthread library 3181.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 3191.157Sapb the pthread library in sync, old threaded applications should 3201.157Sapb continue to work with an old or new kernel. Note that named(8) 3211.157Sapb is the only threaded application in the base system. 3221.157Sapb 3231.154She20061214: 3241.154She Following the move of string_to_flags() and flags_to_string() 3251.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 3261.154She will need to do a "make cleandir" in 3271.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 3281.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 3291.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 3301.156She as the installation images in distrib/ 3311.154She in order to excise stale references to the old stat_flags.h header 3321.154She file in the ls sources -- stat_flags.h has been removed. 3331.154She 3341.152Schristos20061108: 3351.152Schristos The configure script used in the src/tools/gcc compiler has been 3361.152Schristos changed to indicate that our libc has ssp support built-in and 3371.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 3381.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 3391.152Schristos 3401.151Srpaulo20061009: 3411.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 3421.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 3431.151Srpaulo 3441.150Sbjh2120060814: 3451.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 3461.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 3471.150Sbjh21 kernel configuration for an example. X servers from the last 3481.150Sbjh21 few years should cope. 3491.150Sbjh21 3501.149Schristos20060703: 3511.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 3521.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 3531.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 3541.149Schristos 3551.148Sdogcow20060627: 3561.148Sdogcow socket(2) has changed, and its system call has been versioned. 3571.148Sdogcow For userlands with the old version of socket(2), make sure that 3581.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 3591.148Sdogcow errors will result. 3601.148Sdogcow 3611.1SabsHints for a more successful build: 3621.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3631.123Sjmc Use build.sh, but do not use its "expert mode": 3641.132Sjmmv This will automatically build the tools in the 3651.123Sjmc correct order, and it will keep the tools and the 3661.123Sjmc new build products from interfering with the running 3671.123Sjmc system. This will allow you to ignore most of the 3681.123Sjmc other advice in this file. 3691.2Smrg Build a new kernel first: 3701.2Smrg This makes sure that any new system calls or features 3711.2Smrg expected by the new userland will be present. This 3721.2Smrg helps to avoid critical errors when upgrading. 3731.1Sabs Use object directories: 3741.1Sabs This helps to keep stale object 3751.1Sabs files from polluting the build if a Makefile "forgets" 3761.1Sabs about one. It also makes it easier to clean up after 3771.1Sabs a build. It's also necessary if you want to use the 3781.1Sabs same source tree for multiple machines. 3791.123Sjmc To use object directories with build.sh: 3801.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 3811.123Sjmc To use object directories without using build.sh: 3821.1Sabs a) cd /usr/src ; make cleandir 3831.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 3841.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 3851.1Sabs d) cd /usr/src ; make build 3861.2Smrg Note that running "make obj" in a directory will create 3871.2Smrg in obj.$MACHINE directory. 3881.1Sabs Build to a DESTDIR: 3891.123Sjmc This helps to keep old installed files (especially libraries) 3901.123Sjmc from interfering with the new build. 3911.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 3921.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 3931.123Sjmc environment variable before running make build. It should be 3941.123Sjmc set to the pathname of an initially empty directory. 3951.123Sjmc Problems: if you do not use build.sh, you might need to 3961.123Sjmc update critical utilities without using DESTDIR since 3971.123Sjmc nothing is executed from what is installed in DESTDIR. 3981.123Sjmc (See critical utils, below.) 3991.1Sabs Build often: 4001.1Sabs This keeps critical utilities current enough to not choke 4011.1Sabs on any other part of the source tree that depends on up to 4021.123Sjmc date functionality. If you use build.sh, you should not have 4031.123Sjmc this problem. 4041.1Sabs 4051.1SabsWhat to do if things don't work: 4061.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4071.1SabsWhen things don't work there is usually a few things that commonly 4081.1Sabsshould be done. 4091.1Sabs 1) make includes 4101.1Sabs This should be done automatically by make build. 4111.1Sabs 2) cd share/mk && make install 4121.1Sabs Again, automatically done by make build. 4131.1Sabs 4141.1SabsFailsafe rebuild of a small part of the tree: 4151.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4161.1SabsTo make sure you rebuild something correctly you want to do 4171.1Sabssomething like the following: 4181.1Sabs 1) Make sure the includes and .mk files are up to date. 4191.1Sabs 2) Make sure any program used to build the particular 4201.1Sabs utility is up to date. (yacc, lex, etc...) 4211.1Sabs 3) cd ...path/to/util... 4221.1Sabs make cleandir 4231.1Sabs rm ...all obj directories... 4241.1Sabs make cleandir # yes, again 4251.1Sabs make obj 4261.1Sabs make depend && make 4271.1Sabs 4281.1SabsFailsafe rebuild of the entire tree: 4291.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4301.1SabsIf you really want to make sure the source tree is clean and 4311.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 4321.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 4331.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 4341.1Sabs 4351.1Sabs---cut here--- 4361.1Sabs#!/bin/sh 4371.1Sabs. /etc/mk.conf 4381.1Sabs 4391.58Slukemif [ -z $NETBSDSRCDIR ] ; then 4401.58Slukem NETBSDSRCDIR=/usr/src 4411.1Sabsfi 4421.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 4431.1Sabs echo Unable to find sources 4441.1Sabs exit 1 4451.1Sabsfi 4461.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 4471.1Sabs 4481.1Sabsif [ -z $BSDOBJDIR ] ; then 4491.1Sabs BSDOBJDIR=/usr/obj 4501.1Sabsfi 4511.1Sabsif [ -d $BSDOBJDIR ] ; then 4521.1Sabs rm -rf $BSDOBJDIR 4531.1Sabsfi 4541.1Sabs 4551.58Slukemcd $NETBSDSRCDIR && make cleandir 4561.1Sabs 4571.1Sabs---cut here--- 4581.1Sabs 4591.1SabsCritical utilities: 4601.1Sabs^^^^^^^^^^^^^^^^^^^ 4611.3Sitojun usr.bin/compile_et 4621.1Sabs usr.bin/make 4631.1Sabs usr.bin/yacc 4641.1Sabs usr.bin/lex 4651.11Slukem usr.bin/xlint 4661.142Sdrochner usr.bin/config 4671.1Sabs 4681.34SsimonbOther problems and possible solutions: 4691.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4701.1SabsSymptom:Complaints involving a Makefile. 4711.17SerhFix: Rebuild usr.bin/make: 4721.17Serh cd usr.bin/make && make && make install 4731.111Ssimonb Or, a failsafe method if that doesn't work: 4741.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 4751.17Serh 4761.1SabsFix: Make sure .mk files are up to date. 4771.1Sabs cd share/mk && make install 4781.2Smrg 4791.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 4801.142SdrochnerFix: Rebuild usr.bin/config 4811.1Sabs 4821.1SabsSymptom: 4831.1SabsFix: Rebuild usr.bin/yacc 4841.1Sabs 4851.1SabsSymptom: 4861.1SabsFix: Rebuild usr.bin/lex 4871.1Sabs 4881.1SabsSymptom: 4891.1SabsFix: rm /usr/lib/libbfd.a 4901.4Sitojun 4911.4SitojunSymptom:Obsolete intermediate files are used during compilation 4921.4SitojunFix: Try the following sequence of commands in the directory in question. 4931.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 4941.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 4951.4Sitojun may remain. The command tries to clean everything up) 4961.5Swiz 4971.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 4981.207Smbalmer pointer type 4991.5SwizFix: Rebuild and install usr.bin/menuc 5001.12Sitojun 5011.12SitojunSymptom:mklocale not found during build in share/locale/ctype 5021.12SitojunFix: Build and install usr.bin/mklocale 5031.13Sdogcow 5041.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 5051.13SdogcowFix: Rebuild and install lib/libc 5061.13Sdogcow 5071.142SdrochnerSymptom:usr.bin/config fails to build. 5081.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 5091.13Sdogcow 5101.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 5111.19ScgdFix: Rebuild and install lib/libc 5121.24Sabs 5131.24SabsSymptom:lint does not understand the '-X' option 5141.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 515