UPDATING revision 1.230
11.230Stls$NetBSD: UPDATING,v 1.230 2011/11/19 22:51:18 tls 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.230Stls 191.230Stls20111119: 201.230Stls A problem with the datastructures used by the rndctl(8) 211.230Stls utility (pointers in datastructures in an array, making 32->64 221.230Stls bit compatibility very painful) has been fixed in a 231.230Stls non-backwards-compatible way. If you replace your kernel, 241.230Stls replace your rndctl executable too. 251.230Stls 261.229Sjym20111001: 271.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 281.229Sjym changed and their new version is not backward compatible with the old 291.229Sjym one. So ensure that all consumers of these functions (currently: 301.229Sjym quota2 code and its tests) are updated together with the new lib. 311.229Sjym 321.228Smrg20110817: 331.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 341.228Smrg DESTDIR for them should be deleted before updating. 351.228Smrg 361.227Sriastrad20110806: 371.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 381.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 391.227Sriastrad 401.226Smrg20110805: 411.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 421.226Smrg the tree to be cleaned. Best to delete both objdir and 431.226Smrg DESTDIR before running this update. So far, only the 441.226Smrg sparc64, mips and powerpc platforms have changed. 451.226Smrg 461.225Smatt20110803: 471.225Smatt The layout of external/public-domain/xz has changed. To do an 481.225Smatt update build you will have to remove the contents of the OBJDIR 491.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 501.225Smatt is now a directory. 511.225Smatt 521.223Sjoerg20110410: 531.224Sdholland The configuration of src/tools/gcc has changed. To do an 541.224Sdholland update build you have to clean both tools/binutils and 551.224Sdholland tools/gcc by hand. 561.223Sjoerg 571.222Splunky20110328: 581.222Splunky Building the Xorg binary was moved into a subdirectory to fix 591.222Splunky ordering issues with "make all". It may be necessary to remove 601.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 611.222Splunky if your update build fails, as the "Xorg" entry there is now a 621.222Splunky directory. 631.222Splunky 641.220Sjoerg20110121: 651.221Slukem Assembler files no longer use -traditional-cpp. This can break 661.220Sjoerg the build of individual parts of the tree. This is handled 671.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 681.220Sjoerg and re-run config(1) for any kernel configurations as needed. 691.218Sjoerg 701.217Sjruoho20101217: 711.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 721.217Sjruoho by default. It may be necessary to manually update passwd(5) and 731.217Sjruoho group(5) in order to make the program work with existing setups. 741.217Sjruoho 751.216Schristos20101125: 761.216Schristos The latest changes to setenv(3) dissallow setting environment 771.216Schristos variables with names that contain '='. Revision 1.18 of env.c 781.216Schristos assumed that this was allowed. Installing a new libc with an 791.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 801.216Schristos break which affects the autoconf tests for dependency finding, 811.216Schristos so building gcc will end up printing: 821.216Schristos checking dependency style of gcc... none 831.216Schristos configure: error: no usable dependency style found 841.216Schristos Fix it by rebuilding and re-installing env. 851.138Slukem 861.215Smrg20101119: 871.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 881.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 891.215Smrg have any build problems with xsrc, or problems with mismatched 901.215Smrg versions between xorg-server and drivers. 911.215Smrg 921.213Sjmmv20100604: 931.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 941.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 951.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 961.213Sjmmv trees by hand. 971.213Sjmmv 981.211Stnozaki20100522: 991.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 1001.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 1011.212Smrg build problems with xsrc. 1021.212Smrg 1031.212Smrg20100522: 1041.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 1051.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 1061.211Stnozaki 1071.210Schristos20100520: 1081.210Schristos The location of the xkb compiled descriptions has changed. Please 1091.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 1101.210Schristos 1111.209Snjoly20100222: 1121.209Snjoly The shared objects file extension has been changed from .so to 1131.209Snjoly .pico, in order to avoid conflicts with shared libraries names 1141.209Snjoly libXX.so. All now stale regular .so files can be removed from 1151.209Snjoly your object directories. 1161.209Snjoly 1171.208Sroy20100204: 1181.208Sroy The termcap database has been removed from the sources, 1191.208Sroy but has not been marked obsolete so it is not removed 1201.208Sroy from the system when upgrading. 1211.208Sroy As such, you will need to remove them from your object 1221.208Sroy and destination directories. 1231.208Sroy 1241.203Sdyoung20091101: 1251.205Sdholland After updating, it may be necessary to make the 'cleandir' 1261.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 1271.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 1281.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 1291.203Sdyoung 1301.202Smrg20091001: 1311.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 1321.206Sdholland before building a kernel, or the build fails on cpufunc.S. 1331.206Sdholland 1341.206Sdholland20091001: 1351.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 1361.202Smrg symlink, failing the build. Delete the link, and the subdir 1371.202Smrg it is in, and retry your build. 1381.202Smrg 1391.201Sdsl20090718: 1401.201Sdsl libc build changed so that strchr() provides the extra entry 1411.201Sdsl point for index(). Update build of libc.a (and libc_pic.a) 1421.201Sdsl may fail because the archive contains the unwanted index.o. 1431.201Sdsl (Similarly for strrchr() and rindex().) 1441.201Sdsl 1451.198Smrg20090709: 1461.198Smrg Native Xorg was upgraded again. Builds will probably fail again 1471.198Smrg without a clean objdir, at least for src/external/mit/xorg. 1481.198Smrg 1491.197Smrg20090616: 1501.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 1511.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 1521.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 1531.197Smrg subdirectory has been changed into a file, and this needs to 1541.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 1551.197Smrg 1561.195Sperry20090501: 1571.195Sperry Several new functions were added to string.h/libc, and this 1581.195Sperry can cause autoconf problems during the tool build for people 1591.195Sperry who fail to clean out their tools objects properly. If you 1601.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 1611.195Sperry failure during the tool build, clean out all your tools 1621.195Sperry objects and start again. 1631.195Sperry 1641.194Smrg20090325: 1651.194Smrg The i386 port was switched to i486 default toolchain. This requires 1661.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 1671.194Smrg 1681.192Sskrll20090126: 1691.207Smbalmer The __posix_fadvise50 system call changed assembly stub type. You 1701.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 1711.207Smbalmer to avoid using the old assembly stub. 1721.192Sskrll 1731.191Sjoerg20090202: 1741.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 1751.191Sjoerg detection. It is recommented to rebuild the cache with 1761.191Sjoerg ``pkg_admin rebuild''. 1771.191Sjoerg 1781.184Schristos20090110: 1791.184Schristos time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 1801.184Schristos 1. Make sure your kernel has COMPAT_50 in it. Build and install. 1811.188Schristos This is needed even in the MODULAR kernel because there is 1821.188Schristos conditionally compiled code in rtsock.c. 1831.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 1841.184Schristos before installing. 1851.184Schristos 3. If you don't use build.sh and you build directly to root, and 1861.187Sdholland your build breaks in the middle, don't despair. Make sure headers 1871.184Schristos are installed properly, and start building libraries first libc 1881.184Schristos and libutil, install them and then continue building all the 1891.184Schristos libraries in src/lib and src/gnu/lib and install them. Once 1901.184Schristos the new libraries are installed, you can restart the build. 1911.184Schristos 4. If you compile packages and you notice link time warnings, 1921.189Shubertf rebuild the required packages to update their shared libraries. 1931.189Shubertf Any package you rebuild will require rebuilding all the packages 1941.189Shubertf that depend on it. 1951.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 1961.186Schristos will be upgraded and it will not be backwards compatible. 1971.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 1981.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 1991.190Sapb for utmp. You are better off removing the old files after 2001.190Sapb upgrading. The automated clearing of /var/run during 2011.190Sapb boot, and the automated rotating of files in /var/log by 2021.190Sapb newsyslog(8), may mean that you do not have to remove the 2031.190Sapb files manually. 2041.190Sapb 7. The optional accounting file (/var/account/acct, see 2051.190Sapb accton(8)) has not been versioned, and will need to be 2061.190Sapb removed. The automatic rotation of the accounting file by 2071.190Sapb /etc/daily limits the bad consequences of failure to remove 2081.190Sapb the file. 2091.196Sdholland 8. Application software that writes time_t to binary files on 2101.196Sdholland disk will break or need attention. Most notably: if you are 2111.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 2121.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 2131.185Sjmcneill 2141.183Spgoyette20081219: 2151.183Spgoyette config(1) has been updated, and one of the files it creates - 2161.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 2171.183Spgoyette (done automatically by build.sh) and then you need to rerun 2181.183Spgoyette config on all kernel configuration files before rebuilding those 2191.183Spgoyette kernels. 2201.183Spgoyette 2211.181Scube20081205: 2221.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 2231.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 2241.181Scube set and will appear as extra files for MKX11=no update builds. 2251.178Slukem 2261.179Stsutsui20081122: 2271.182Stsutsui On i386, various kernel options(4) in GENERIC including 2281.180Swiz file systems have been disabled and moved into kernel modules. 2291.180Swiz Before trying a new GENERIC kernel, you have to prepare the 2301.179Stsutsui following files as well as a new GENERIC kernel: 2311.179Stsutsui 2321.179Stsutsui - build and install kernel modules from src/sys/modules 2331.179Stsutsui 2341.179Stsutsui - install the latest bootloader, which will load a module 2351.180Swiz for the file system from which the kernel is loaded automatically 2361.179Stsutsui 2371.180Swiz If you have to load your kernel from a file system which is not of 2381.180Swiz the same type as the root file system, you have to load the necessary 2391.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 2401.179Stsutsui 2411.178Slukem20080827: 2421.178Slukem If you built and installed a libc from sources between 2431.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 2441.178Slukem which results in false errors reported by lint(1). 2451.178Slukem Since this breaks the libc build itself, manual help is 2461.180Swiz needed -- lint must be disabled temporarily, e.g.: 2471.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 2481.178Slukem 2491.177Schristos20080813: 2501.177Schristos MKDEBUG build was broken because the .depend files did not know 2511.177Schristos about .go files. You need to remove all .depend files and rebuild. 2521.177Schristos 2531.200Sdholland20080802: 2541.200Sdholland A regression in binary compatibility for pthread_mutex_t has 2551.200Sdholland been fixed. Unfortunately, the price is breaking compatibility 2561.200Sdholland for -current. 2571.200Sdholland 2581.200Sdholland Threaded programs (using libpthread) and C++ programs (using 2591.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 2601.200Sdholland be recompiled. 2611.200Sdholland 2621.200Sdholland One way to find affected pkgsrc packages: 2631.200Sdholland 2641.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 2651.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 2661.200Sdholland 2671.175Ssimonb20080731: 2681.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 2691.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 2701.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 2711.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 2721.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 2731.176Ssimonb also requires the super block to be in the UFS2 format. You 2741.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 2751.175Ssimonb 2761.174Slukem20080721: 2771.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 2781.174Slukem isn't defined. 2791.174Slukem 2801.173Sfreza20080531: 2811.173Sfreza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 2821.173Sfreza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 2831.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 2841.173Sfreza won't work correctly. The following sequence of commands: 2851.173Sfreza 2861.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 2871.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 2881.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 2891.173Sfreza 2901.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 2911.173Sfreza 2921.172Slukem20080503: 2931.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 2941.172Slukem 2951.171She20080521: 2961.171She For a while, unprivileged UPDATE builds would fail to 2971.171She succeed at the checkflist stage, complaining that 2981.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 2991.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 3001.171She If you already hit this problem, update the .mk file, 3011.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 3021.171She 3031.174Slukem20080303: 3041.174Slukem Linker warnings are now fatal if $WARNS>0. 3051.174Slukem 3061.170Schristos20080126: 3071.170Schristos The posix_fadvise system call has been changed from an assembly 3081.170Schristos stub, to a c file that calls an assembly stub. You need to 3091.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 3101.170Schristos avoid using the old assembly stub. 3111.170Schristos 3121.168Sjoerg20071209: 3131.168Sjoerg The acpiec(4) driver has been split into two attachments. If you 3141.168Sjoerg get ACPI errors before the attachment, please update your kernel 3151.169Swiz configuration file appropriately or see GENERIC for more details. 3161.168Sjoerg 3171.166Sxtraeme20071115: 3181.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 3191.166Sxtraeme argument specified in the kernel configuration file is not valid 3201.166Sxtraeme anymore. The itesio(4) driver now uses the Super I/O address port 3211.166Sxtraeme rather than the EC address port. Please update your kernel 3221.167Swiz configuration file appropriately or see GENERIC for more details. 3231.166Sxtraeme 3241.165Sjmmv20071028: 3251.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 3261.165Sjmmv You need to update any custom kernel configuration file you have 3271.165Sjmmv to remove any references to pccons (which includes removing the 3281.165Sjmmv now useless XSERVER option) and replace them with the correct 3291.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 3301.165Sjmmv for more details. 3311.165Sjmmv 3321.164Sgdt20070913: 3331.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 3341.164Sgdt enumerate interfaces was fixed. The bug began to cause 3351.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 3361.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 3371.164Sgdt could not enumerate interfaces. (These are noted because 3381.164Sgdt normal kernel/userspace version matching hygiene is not 3391.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 3401.164Sgdt and userland are from after 20070913. 3411.164Sgdt 3421.163Sjoerg20070703: 3431.199Sdholland nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 3441.199Sdholland calls the target-specific strip program, and the logic to pass 3451.199Sdholland down STRIP from make has been removed. This requires a 3461.199Sdholland re-installation of tools. 3471.163Sjoerg 3481.161Sdsl20070422: 3491.161Sdsl The way OS emulations lookup filenames inside the emulation root 3501.161Sdsl has been changed. Rather than modify the pathname (and copy back 3511.161Sdsl to userspace) namei() and lookup() directly check the emulation 3521.161Sdsl root. One side effect is that absolute symlinks inside the emulated 3531.167Swiz root file system will be relative to that file system - unless they 3541.161Sdsl start /../ this is useful when the emulated root is a real install 3551.161Sdsl that has such links. 3561.161Sdsl This might affect symlinks that have been added to reference outside 3571.161Sdsl the emulated root. 3581.161Sdsl 3591.160Sjmcneill20070412: 3601.160Sjmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc 3611.160Sjmcneill instead. See the GENERIC32_IP3x kernel configuration for an 3621.160Sjmcneill example. 3631.160Sjmcneill 3641.159Sgdt20070319: 3651.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 3661.159Sgdt on many platforms due to incorrect flags settings. If you 3671.159Sgdt updated and built after about 20070315, do "nbmake-$arch 3681.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 3691.159Sgdt rebuild of object files that might have been built 3701.159Sgdt incorrectly, and ensure that you have at least 3711.159Sgdt src/lib/libc/Makefile 1.130. 3721.159Sgdt 3731.158Sdbj20070210: 3741.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 3751.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 3761.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 3771.158Sdbj will allow dependencies on those files to get get rebuilt 3781.158Sdbj 3791.157Sapb20070209: 3801.157Sapb The threading model was changed when the newlock2 branch 3811.157Sapb was merged to NetBSD-current. If you boot with a new 3821.157Sapb kernel (version 4.99.10), then you also need a new pthread 3831.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 3841.157Sapb an old kernel, then you need the old pthread library 3851.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 3861.157Sapb the pthread library in sync, old threaded applications should 3871.157Sapb continue to work with an old or new kernel. Note that named(8) 3881.157Sapb is the only threaded application in the base system. 3891.157Sapb 3901.154She20061214: 3911.154She Following the move of string_to_flags() and flags_to_string() 3921.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 3931.154She will need to do a "make cleandir" in 3941.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 3951.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 3961.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 3971.156She as the installation images in distrib/ 3981.154She in order to excise stale references to the old stat_flags.h header 3991.154She file in the ls sources -- stat_flags.h has been removed. 4001.154She 4011.152Schristos20061108: 4021.152Schristos The configure script used in the src/tools/gcc compiler has been 4031.152Schristos changed to indicate that our libc has ssp support built-in and 4041.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 4051.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 4061.152Schristos 4071.151Srpaulo20061009: 4081.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 4091.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 4101.151Srpaulo 4111.150Sbjh2120060814: 4121.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 4131.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 4141.150Sbjh21 kernel configuration for an example. X servers from the last 4151.150Sbjh21 few years should cope. 4161.150Sbjh21 4171.149Schristos20060703: 4181.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 4191.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 4201.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 4211.149Schristos 4221.148Sdogcow20060627: 4231.148Sdogcow socket(2) has changed, and its system call has been versioned. 4241.148Sdogcow For userlands with the old version of socket(2), make sure that 4251.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 4261.148Sdogcow errors will result. 4271.148Sdogcow 4281.1SabsHints for a more successful build: 4291.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4301.123Sjmc Use build.sh, but do not use its "expert mode": 4311.132Sjmmv This will automatically build the tools in the 4321.123Sjmc correct order, and it will keep the tools and the 4331.123Sjmc new build products from interfering with the running 4341.123Sjmc system. This will allow you to ignore most of the 4351.123Sjmc other advice in this file. 4361.2Smrg Build a new kernel first: 4371.2Smrg This makes sure that any new system calls or features 4381.2Smrg expected by the new userland will be present. This 4391.2Smrg helps to avoid critical errors when upgrading. 4401.1Sabs Use object directories: 4411.1Sabs This helps to keep stale object 4421.1Sabs files from polluting the build if a Makefile "forgets" 4431.1Sabs about one. It also makes it easier to clean up after 4441.1Sabs a build. It's also necessary if you want to use the 4451.1Sabs same source tree for multiple machines. 4461.123Sjmc To use object directories with build.sh: 4471.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 4481.123Sjmc To use object directories without using build.sh: 4491.1Sabs a) cd /usr/src ; make cleandir 4501.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 4511.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 4521.1Sabs d) cd /usr/src ; make build 4531.2Smrg Note that running "make obj" in a directory will create 4541.2Smrg in obj.$MACHINE directory. 4551.1Sabs Build to a DESTDIR: 4561.123Sjmc This helps to keep old installed files (especially libraries) 4571.123Sjmc from interfering with the new build. 4581.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 4591.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 4601.123Sjmc environment variable before running make build. It should be 4611.123Sjmc set to the pathname of an initially empty directory. 4621.123Sjmc Problems: if you do not use build.sh, you might need to 4631.123Sjmc update critical utilities without using DESTDIR since 4641.123Sjmc nothing is executed from what is installed in DESTDIR. 4651.123Sjmc (See critical utils, below.) 4661.1Sabs Build often: 4671.1Sabs This keeps critical utilities current enough to not choke 4681.1Sabs on any other part of the source tree that depends on up to 4691.123Sjmc date functionality. If you use build.sh, you should not have 4701.123Sjmc this problem. 4711.1Sabs 4721.1SabsWhat to do if things don't work: 4731.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4741.230StlsWhen things don't work there are usually a few things that commonly 4751.1Sabsshould be done. 4761.1Sabs 1) make includes 4771.1Sabs This should be done automatically by make build. 4781.1Sabs 2) cd share/mk && make install 4791.1Sabs Again, automatically done by make build. 4801.1Sabs 4811.1SabsFailsafe rebuild of a small part of the tree: 4821.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4831.1SabsTo make sure you rebuild something correctly you want to do 4841.1Sabssomething like the following: 4851.1Sabs 1) Make sure the includes and .mk files are up to date. 4861.1Sabs 2) Make sure any program used to build the particular 4871.1Sabs utility is up to date. (yacc, lex, etc...) 4881.1Sabs 3) cd ...path/to/util... 4891.1Sabs make cleandir 4901.1Sabs rm ...all obj directories... 4911.1Sabs make cleandir # yes, again 4921.1Sabs make obj 4931.1Sabs make depend && make 4941.1Sabs 4951.1SabsFailsafe rebuild of the entire tree: 4961.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4971.1SabsIf you really want to make sure the source tree is clean and 4981.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 4991.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 5001.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 5011.1Sabs 5021.1Sabs---cut here--- 5031.1Sabs#!/bin/sh 5041.1Sabs. /etc/mk.conf 5051.1Sabs 5061.58Slukemif [ -z $NETBSDSRCDIR ] ; then 5071.58Slukem NETBSDSRCDIR=/usr/src 5081.1Sabsfi 5091.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 5101.1Sabs echo Unable to find sources 5111.1Sabs exit 1 5121.1Sabsfi 5131.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 5141.1Sabs 5151.1Sabsif [ -z $BSDOBJDIR ] ; then 5161.1Sabs BSDOBJDIR=/usr/obj 5171.1Sabsfi 5181.1Sabsif [ -d $BSDOBJDIR ] ; then 5191.1Sabs rm -rf $BSDOBJDIR 5201.1Sabsfi 5211.1Sabs 5221.58Slukemcd $NETBSDSRCDIR && make cleandir 5231.1Sabs 5241.1Sabs---cut here--- 5251.1Sabs 5261.1SabsCritical utilities: 5271.1Sabs^^^^^^^^^^^^^^^^^^^ 5281.3Sitojun usr.bin/compile_et 5291.1Sabs usr.bin/make 5301.1Sabs usr.bin/yacc 5311.1Sabs usr.bin/lex 5321.11Slukem usr.bin/xlint 5331.142Sdrochner usr.bin/config 5341.1Sabs 5351.34SsimonbOther problems and possible solutions: 5361.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5371.1SabsSymptom:Complaints involving a Makefile. 5381.17SerhFix: Rebuild usr.bin/make: 5391.17Serh cd usr.bin/make && make && make install 5401.111Ssimonb Or, a failsafe method if that doesn't work: 5411.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 5421.17Serh 5431.1SabsFix: Make sure .mk files are up to date. 5441.1Sabs cd share/mk && make install 5451.2Smrg 5461.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 5471.142SdrochnerFix: Rebuild usr.bin/config 5481.1Sabs 5491.1SabsSymptom: 5501.1SabsFix: Rebuild usr.bin/yacc 5511.1Sabs 5521.1SabsSymptom: 5531.1SabsFix: Rebuild usr.bin/lex 5541.1Sabs 5551.1SabsSymptom: 5561.1SabsFix: rm /usr/lib/libbfd.a 5571.4Sitojun 5581.4SitojunSymptom:Obsolete intermediate files are used during compilation 5591.4SitojunFix: Try the following sequence of commands in the directory in question. 5601.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 5611.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 5621.4Sitojun may remain. The command tries to clean everything up) 5631.5Swiz 5641.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 5651.207Smbalmer pointer type 5661.5SwizFix: Rebuild and install usr.bin/menuc 5671.12Sitojun 5681.12SitojunSymptom:mklocale not found during build in share/locale/ctype 5691.12SitojunFix: Build and install usr.bin/mklocale 5701.13Sdogcow 5711.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 5721.13SdogcowFix: Rebuild and install lib/libc 5731.13Sdogcow 5741.142SdrochnerSymptom:usr.bin/config fails to build. 5751.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 5761.13Sdogcow 5771.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 5781.19ScgdFix: Rebuild and install lib/libc 5791.24Sabs 5801.24SabsSymptom:lint does not understand the '-X' option 5811.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 5821.223Sjoerg 5831.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 5841.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 5851.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 586