UPDATING revision 1.237
11.237Swiz$NetBSD: UPDATING,v 1.237 2012/05/07 11:20:24 wiz 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.237Swiz20120507: 201.237Swiz The database schema for makemandb was changed. You will 211.237Swiz need to update the database using 'makemandb -f' or wait 221.237Swiz for the next weekly run to fix it. 231.237Swiz 241.236Sbsh20120319: 251.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 261.236Sbsh size of db_symtab automatically. You need to update dbsym in 271.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 281.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 291.236Sbsh mk.conf. 301.236Sbsh 311.235Sjoerg20120216: 321.234Sspz Default for MKCATPAGES changed to NO. Update builds will fail 331.235Sjoerg unless DESTDIR is cleaned manually. If you built between 20120207 341.235Sjoerg and 20120216, daily and weekly could have created an unreable 351.235Sjoerg /var/db/man.db index for apropos. Running makemandb -f or 361.235Sjoerg the next run of weekly will fix it. 371.233Sjoerg 381.232Schristos20111227: 391.232Schristos If you built between 20111225 and 20111227 you need to remove 401.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 411.232Schristos bump has been reverted. 421.232Schristos 431.231Stls20111125: 441.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 451.231Stls means it should no longer be explicitly listed in kernel 461.231Stls configuration files. The line "pseudo-device rnd" should be 471.231Stls removed from any custom kernel config files users may have. 481.231Stls 491.230Stls20111119: 501.230Stls A problem with the datastructures used by the rndctl(8) 511.230Stls utility (pointers in datastructures in an array, making 32->64 521.230Stls bit compatibility very painful) has been fixed in a 531.230Stls non-backwards-compatible way. If you replace your kernel, 541.230Stls replace your rndctl executable too. 551.230Stls 561.229Sjym20111001: 571.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 581.229Sjym changed and their new version is not backward compatible with the old 591.229Sjym one. So ensure that all consumers of these functions (currently: 601.229Sjym quota2 code and its tests) are updated together with the new lib. 611.229Sjym 621.228Smrg20110817: 631.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 641.228Smrg DESTDIR for them should be deleted before updating. 651.228Smrg 661.227Sriastrad20110806: 671.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 681.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 691.227Sriastrad 701.226Smrg20110805: 711.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 721.226Smrg the tree to be cleaned. Best to delete both objdir and 731.226Smrg DESTDIR before running this update. So far, only the 741.226Smrg sparc64, mips and powerpc platforms have changed. 751.226Smrg 761.225Smatt20110803: 771.225Smatt The layout of external/public-domain/xz has changed. To do an 781.225Smatt update build you will have to remove the contents of the OBJDIR 791.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 801.225Smatt is now a directory. 811.225Smatt 821.223Sjoerg20110410: 831.224Sdholland The configuration of src/tools/gcc has changed. To do an 841.224Sdholland update build you have to clean both tools/binutils and 851.224Sdholland tools/gcc by hand. 861.223Sjoerg 871.222Splunky20110328: 881.222Splunky Building the Xorg binary was moved into a subdirectory to fix 891.222Splunky ordering issues with "make all". It may be necessary to remove 901.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 911.222Splunky if your update build fails, as the "Xorg" entry there is now a 921.222Splunky directory. 931.222Splunky 941.220Sjoerg20110121: 951.221Slukem Assembler files no longer use -traditional-cpp. This can break 961.220Sjoerg the build of individual parts of the tree. This is handled 971.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 981.220Sjoerg and re-run config(1) for any kernel configurations as needed. 991.218Sjoerg 1001.217Sjruoho20101217: 1011.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 1021.217Sjruoho by default. It may be necessary to manually update passwd(5) and 1031.217Sjruoho group(5) in order to make the program work with existing setups. 1041.217Sjruoho 1051.216Schristos20101125: 1061.216Schristos The latest changes to setenv(3) dissallow setting environment 1071.216Schristos variables with names that contain '='. Revision 1.18 of env.c 1081.216Schristos assumed that this was allowed. Installing a new libc with an 1091.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 1101.216Schristos break which affects the autoconf tests for dependency finding, 1111.216Schristos so building gcc will end up printing: 1121.216Schristos checking dependency style of gcc... none 1131.216Schristos configure: error: no usable dependency style found 1141.216Schristos Fix it by rebuilding and re-installing env. 1151.138Slukem 1161.215Smrg20101119: 1171.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 1181.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 1191.215Smrg have any build problems with xsrc, or problems with mismatched 1201.215Smrg versions between xorg-server and drivers. 1211.215Smrg 1221.213Sjmmv20100604: 1231.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 1241.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 1251.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 1261.213Sjmmv trees by hand. 1271.213Sjmmv 1281.211Stnozaki20100522: 1291.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 1301.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 1311.212Smrg build problems with xsrc. 1321.212Smrg 1331.212Smrg20100522: 1341.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 1351.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 1361.211Stnozaki 1371.210Schristos20100520: 1381.210Schristos The location of the xkb compiled descriptions has changed. Please 1391.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 1401.210Schristos 1411.209Snjoly20100222: 1421.209Snjoly The shared objects file extension has been changed from .so to 1431.209Snjoly .pico, in order to avoid conflicts with shared libraries names 1441.209Snjoly libXX.so. All now stale regular .so files can be removed from 1451.209Snjoly your object directories. 1461.209Snjoly 1471.208Sroy20100204: 1481.208Sroy The termcap database has been removed from the sources, 1491.208Sroy but has not been marked obsolete so it is not removed 1501.208Sroy from the system when upgrading. 1511.208Sroy As such, you will need to remove them from your object 1521.208Sroy and destination directories. 1531.208Sroy 1541.203Sdyoung20091101: 1551.205Sdholland After updating, it may be necessary to make the 'cleandir' 1561.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 1571.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 1581.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 1591.203Sdyoung 1601.202Smrg20091001: 1611.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 1621.206Sdholland before building a kernel, or the build fails on cpufunc.S. 1631.206Sdholland 1641.206Sdholland20091001: 1651.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 1661.202Smrg symlink, failing the build. Delete the link, and the subdir 1671.202Smrg it is in, and retry your build. 1681.202Smrg 1691.201Sdsl20090718: 1701.201Sdsl libc build changed so that strchr() provides the extra entry 1711.201Sdsl point for index(). Update build of libc.a (and libc_pic.a) 1721.201Sdsl may fail because the archive contains the unwanted index.o. 1731.201Sdsl (Similarly for strrchr() and rindex().) 1741.201Sdsl 1751.198Smrg20090709: 1761.198Smrg Native Xorg was upgraded again. Builds will probably fail again 1771.198Smrg without a clean objdir, at least for src/external/mit/xorg. 1781.198Smrg 1791.197Smrg20090616: 1801.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 1811.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 1821.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 1831.197Smrg subdirectory has been changed into a file, and this needs to 1841.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 1851.197Smrg 1861.195Sperry20090501: 1871.195Sperry Several new functions were added to string.h/libc, and this 1881.195Sperry can cause autoconf problems during the tool build for people 1891.195Sperry who fail to clean out their tools objects properly. If you 1901.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 1911.195Sperry failure during the tool build, clean out all your tools 1921.195Sperry objects and start again. 1931.195Sperry 1941.194Smrg20090325: 1951.194Smrg The i386 port was switched to i486 default toolchain. This requires 1961.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 1971.194Smrg 1981.192Sskrll20090126: 1991.207Smbalmer The __posix_fadvise50 system call changed assembly stub type. You 2001.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 2011.207Smbalmer to avoid using the old assembly stub. 2021.192Sskrll 2031.191Sjoerg20090202: 2041.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 2051.191Sjoerg detection. It is recommented to rebuild the cache with 2061.191Sjoerg ``pkg_admin rebuild''. 2071.191Sjoerg 2081.184Schristos20090110: 2091.184Schristos time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 2101.184Schristos 1. Make sure your kernel has COMPAT_50 in it. Build and install. 2111.188Schristos This is needed even in the MODULAR kernel because there is 2121.188Schristos conditionally compiled code in rtsock.c. 2131.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 2141.184Schristos before installing. 2151.184Schristos 3. If you don't use build.sh and you build directly to root, and 2161.187Sdholland your build breaks in the middle, don't despair. Make sure headers 2171.184Schristos are installed properly, and start building libraries first libc 2181.184Schristos and libutil, install them and then continue building all the 2191.184Schristos libraries in src/lib and src/gnu/lib and install them. Once 2201.184Schristos the new libraries are installed, you can restart the build. 2211.184Schristos 4. If you compile packages and you notice link time warnings, 2221.189Shubertf rebuild the required packages to update their shared libraries. 2231.189Shubertf Any package you rebuild will require rebuilding all the packages 2241.189Shubertf that depend on it. 2251.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 2261.186Schristos will be upgraded and it will not be backwards compatible. 2271.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 2281.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 2291.190Sapb for utmp. You are better off removing the old files after 2301.190Sapb upgrading. The automated clearing of /var/run during 2311.190Sapb boot, and the automated rotating of files in /var/log by 2321.190Sapb newsyslog(8), may mean that you do not have to remove the 2331.190Sapb files manually. 2341.190Sapb 7. The optional accounting file (/var/account/acct, see 2351.190Sapb accton(8)) has not been versioned, and will need to be 2361.190Sapb removed. The automatic rotation of the accounting file by 2371.190Sapb /etc/daily limits the bad consequences of failure to remove 2381.190Sapb the file. 2391.196Sdholland 8. Application software that writes time_t to binary files on 2401.196Sdholland disk will break or need attention. Most notably: if you are 2411.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 2421.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 2431.185Sjmcneill 2441.183Spgoyette20081219: 2451.183Spgoyette config(1) has been updated, and one of the files it creates - 2461.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 2471.183Spgoyette (done automatically by build.sh) and then you need to rerun 2481.183Spgoyette config on all kernel configuration files before rebuilding those 2491.183Spgoyette kernels. 2501.183Spgoyette 2511.181Scube20081205: 2521.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 2531.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 2541.181Scube set and will appear as extra files for MKX11=no update builds. 2551.178Slukem 2561.179Stsutsui20081122: 2571.182Stsutsui On i386, various kernel options(4) in GENERIC including 2581.180Swiz file systems have been disabled and moved into kernel modules. 2591.180Swiz Before trying a new GENERIC kernel, you have to prepare the 2601.179Stsutsui following files as well as a new GENERIC kernel: 2611.179Stsutsui 2621.179Stsutsui - build and install kernel modules from src/sys/modules 2631.179Stsutsui 2641.179Stsutsui - install the latest bootloader, which will load a module 2651.180Swiz for the file system from which the kernel is loaded automatically 2661.179Stsutsui 2671.180Swiz If you have to load your kernel from a file system which is not of 2681.180Swiz the same type as the root file system, you have to load the necessary 2691.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 2701.179Stsutsui 2711.178Slukem20080827: 2721.178Slukem If you built and installed a libc from sources between 2731.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 2741.178Slukem which results in false errors reported by lint(1). 2751.178Slukem Since this breaks the libc build itself, manual help is 2761.180Swiz needed -- lint must be disabled temporarily, e.g.: 2771.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 2781.178Slukem 2791.177Schristos20080813: 2801.177Schristos MKDEBUG build was broken because the .depend files did not know 2811.177Schristos about .go files. You need to remove all .depend files and rebuild. 2821.177Schristos 2831.200Sdholland20080802: 2841.200Sdholland A regression in binary compatibility for pthread_mutex_t has 2851.200Sdholland been fixed. Unfortunately, the price is breaking compatibility 2861.200Sdholland for -current. 2871.200Sdholland 2881.200Sdholland Threaded programs (using libpthread) and C++ programs (using 2891.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 2901.200Sdholland be recompiled. 2911.200Sdholland 2921.200Sdholland One way to find affected pkgsrc packages: 2931.200Sdholland 2941.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 2951.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 2961.200Sdholland 2971.175Ssimonb20080731: 2981.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 2991.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 3001.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 3011.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 3021.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 3031.176Ssimonb also requires the super block to be in the UFS2 format. You 3041.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 3051.175Ssimonb 3061.174Slukem20080721: 3071.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 3081.174Slukem isn't defined. 3091.174Slukem 3101.173Sfreza20080531: 3111.173Sfreza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 3121.173Sfreza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 3131.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 3141.173Sfreza won't work correctly. The following sequence of commands: 3151.173Sfreza 3161.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 3171.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 3181.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 3191.173Sfreza 3201.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 3211.173Sfreza 3221.172Slukem20080503: 3231.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 3241.172Slukem 3251.171She20080521: 3261.171She For a while, unprivileged UPDATE builds would fail to 3271.171She succeed at the checkflist stage, complaining that 3281.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 3291.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 3301.171She If you already hit this problem, update the .mk file, 3311.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 3321.171She 3331.174Slukem20080303: 3341.174Slukem Linker warnings are now fatal if $WARNS>0. 3351.174Slukem 3361.170Schristos20080126: 3371.170Schristos The posix_fadvise system call has been changed from an assembly 3381.170Schristos stub, to a c file that calls an assembly stub. You need to 3391.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 3401.170Schristos avoid using the old assembly stub. 3411.170Schristos 3421.168Sjoerg20071209: 3431.168Sjoerg The acpiec(4) driver has been split into two attachments. If you 3441.168Sjoerg get ACPI errors before the attachment, please update your kernel 3451.169Swiz configuration file appropriately or see GENERIC for more details. 3461.168Sjoerg 3471.166Sxtraeme20071115: 3481.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 3491.166Sxtraeme argument specified in the kernel configuration file is not valid 3501.166Sxtraeme anymore. The itesio(4) driver now uses the Super I/O address port 3511.166Sxtraeme rather than the EC address port. Please update your kernel 3521.167Swiz configuration file appropriately or see GENERIC for more details. 3531.166Sxtraeme 3541.165Sjmmv20071028: 3551.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 3561.165Sjmmv You need to update any custom kernel configuration file you have 3571.165Sjmmv to remove any references to pccons (which includes removing the 3581.165Sjmmv now useless XSERVER option) and replace them with the correct 3591.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 3601.165Sjmmv for more details. 3611.165Sjmmv 3621.164Sgdt20070913: 3631.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 3641.164Sgdt enumerate interfaces was fixed. The bug began to cause 3651.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 3661.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 3671.164Sgdt could not enumerate interfaces. (These are noted because 3681.164Sgdt normal kernel/userspace version matching hygiene is not 3691.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 3701.164Sgdt and userland are from after 20070913. 3711.164Sgdt 3721.163Sjoerg20070703: 3731.199Sdholland nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 3741.199Sdholland calls the target-specific strip program, and the logic to pass 3751.199Sdholland down STRIP from make has been removed. This requires a 3761.199Sdholland re-installation of tools. 3771.163Sjoerg 3781.161Sdsl20070422: 3791.161Sdsl The way OS emulations lookup filenames inside the emulation root 3801.161Sdsl has been changed. Rather than modify the pathname (and copy back 3811.161Sdsl to userspace) namei() and lookup() directly check the emulation 3821.161Sdsl root. One side effect is that absolute symlinks inside the emulated 3831.167Swiz root file system will be relative to that file system - unless they 3841.161Sdsl start /../ this is useful when the emulated root is a real install 3851.161Sdsl that has such links. 3861.161Sdsl This might affect symlinks that have been added to reference outside 3871.161Sdsl the emulated root. 3881.161Sdsl 3891.160Sjmcneill20070412: 3901.160Sjmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc 3911.160Sjmcneill instead. See the GENERIC32_IP3x kernel configuration for an 3921.160Sjmcneill example. 3931.160Sjmcneill 3941.159Sgdt20070319: 3951.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 3961.159Sgdt on many platforms due to incorrect flags settings. If you 3971.159Sgdt updated and built after about 20070315, do "nbmake-$arch 3981.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 3991.159Sgdt rebuild of object files that might have been built 4001.159Sgdt incorrectly, and ensure that you have at least 4011.159Sgdt src/lib/libc/Makefile 1.130. 4021.159Sgdt 4031.158Sdbj20070210: 4041.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 4051.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 4061.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 4071.158Sdbj will allow dependencies on those files to get get rebuilt 4081.158Sdbj 4091.157Sapb20070209: 4101.157Sapb The threading model was changed when the newlock2 branch 4111.157Sapb was merged to NetBSD-current. If you boot with a new 4121.157Sapb kernel (version 4.99.10), then you also need a new pthread 4131.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 4141.157Sapb an old kernel, then you need the old pthread library 4151.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 4161.157Sapb the pthread library in sync, old threaded applications should 4171.157Sapb continue to work with an old or new kernel. Note that named(8) 4181.157Sapb is the only threaded application in the base system. 4191.157Sapb 4201.154She20061214: 4211.154She Following the move of string_to_flags() and flags_to_string() 4221.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 4231.154She will need to do a "make cleandir" in 4241.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 4251.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 4261.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 4271.156She as the installation images in distrib/ 4281.154She in order to excise stale references to the old stat_flags.h header 4291.154She file in the ls sources -- stat_flags.h has been removed. 4301.154She 4311.152Schristos20061108: 4321.152Schristos The configure script used in the src/tools/gcc compiler has been 4331.152Schristos changed to indicate that our libc has ssp support built-in and 4341.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 4351.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 4361.152Schristos 4371.151Srpaulo20061009: 4381.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 4391.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 4401.151Srpaulo 4411.150Sbjh2120060814: 4421.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 4431.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 4441.150Sbjh21 kernel configuration for an example. X servers from the last 4451.150Sbjh21 few years should cope. 4461.150Sbjh21 4471.149Schristos20060703: 4481.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 4491.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 4501.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 4511.149Schristos 4521.148Sdogcow20060627: 4531.148Sdogcow socket(2) has changed, and its system call has been versioned. 4541.148Sdogcow For userlands with the old version of socket(2), make sure that 4551.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 4561.148Sdogcow errors will result. 4571.148Sdogcow 4581.1SabsHints for a more successful build: 4591.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 4601.123Sjmc Use build.sh, but do not use its "expert mode": 4611.132Sjmmv This will automatically build the tools in the 4621.123Sjmc correct order, and it will keep the tools and the 4631.123Sjmc new build products from interfering with the running 4641.123Sjmc system. This will allow you to ignore most of the 4651.123Sjmc other advice in this file. 4661.2Smrg Build a new kernel first: 4671.2Smrg This makes sure that any new system calls or features 4681.2Smrg expected by the new userland will be present. This 4691.2Smrg helps to avoid critical errors when upgrading. 4701.1Sabs Use object directories: 4711.1Sabs This helps to keep stale object 4721.1Sabs files from polluting the build if a Makefile "forgets" 4731.1Sabs about one. It also makes it easier to clean up after 4741.1Sabs a build. It's also necessary if you want to use the 4751.1Sabs same source tree for multiple machines. 4761.123Sjmc To use object directories with build.sh: 4771.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 4781.123Sjmc To use object directories without using build.sh: 4791.1Sabs a) cd /usr/src ; make cleandir 4801.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 4811.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 4821.1Sabs d) cd /usr/src ; make build 4831.2Smrg Note that running "make obj" in a directory will create 4841.2Smrg in obj.$MACHINE directory. 4851.1Sabs Build to a DESTDIR: 4861.123Sjmc This helps to keep old installed files (especially libraries) 4871.123Sjmc from interfering with the new build. 4881.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 4891.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 4901.123Sjmc environment variable before running make build. It should be 4911.123Sjmc set to the pathname of an initially empty directory. 4921.123Sjmc Problems: if you do not use build.sh, you might need to 4931.123Sjmc update critical utilities without using DESTDIR since 4941.123Sjmc nothing is executed from what is installed in DESTDIR. 4951.123Sjmc (See critical utils, below.) 4961.1Sabs Build often: 4971.1Sabs This keeps critical utilities current enough to not choke 4981.1Sabs on any other part of the source tree that depends on up to 4991.123Sjmc date functionality. If you use build.sh, you should not have 5001.123Sjmc this problem. 5011.1Sabs 5021.1SabsWhat to do if things don't work: 5031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5041.230StlsWhen things don't work there are usually a few things that commonly 5051.1Sabsshould be done. 5061.1Sabs 1) make includes 5071.1Sabs This should be done automatically by make build. 5081.1Sabs 2) cd share/mk && make install 5091.1Sabs Again, automatically done by make build. 5101.1Sabs 5111.1SabsFailsafe rebuild of a small part of the tree: 5121.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5131.1SabsTo make sure you rebuild something correctly you want to do 5141.1Sabssomething like the following: 5151.1Sabs 1) Make sure the includes and .mk files are up to date. 5161.1Sabs 2) Make sure any program used to build the particular 5171.1Sabs utility is up to date. (yacc, lex, etc...) 5181.1Sabs 3) cd ...path/to/util... 5191.1Sabs make cleandir 5201.1Sabs rm ...all obj directories... 5211.1Sabs make cleandir # yes, again 5221.1Sabs make obj 5231.1Sabs make depend && make 5241.1Sabs 5251.1SabsFailsafe rebuild of the entire tree: 5261.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5271.1SabsIf you really want to make sure the source tree is clean and 5281.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 5291.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 5301.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 5311.1Sabs 5321.1Sabs---cut here--- 5331.1Sabs#!/bin/sh 5341.1Sabs. /etc/mk.conf 5351.1Sabs 5361.58Slukemif [ -z $NETBSDSRCDIR ] ; then 5371.58Slukem NETBSDSRCDIR=/usr/src 5381.1Sabsfi 5391.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 5401.1Sabs echo Unable to find sources 5411.1Sabs exit 1 5421.1Sabsfi 5431.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 5441.1Sabs 5451.1Sabsif [ -z $BSDOBJDIR ] ; then 5461.1Sabs BSDOBJDIR=/usr/obj 5471.1Sabsfi 5481.1Sabsif [ -d $BSDOBJDIR ] ; then 5491.1Sabs rm -rf $BSDOBJDIR 5501.1Sabsfi 5511.1Sabs 5521.58Slukemcd $NETBSDSRCDIR && make cleandir 5531.1Sabs 5541.1Sabs---cut here--- 5551.1Sabs 5561.1SabsCritical utilities: 5571.1Sabs^^^^^^^^^^^^^^^^^^^ 5581.3Sitojun usr.bin/compile_et 5591.1Sabs usr.bin/make 5601.1Sabs usr.bin/yacc 5611.1Sabs usr.bin/lex 5621.11Slukem usr.bin/xlint 5631.142Sdrochner usr.bin/config 5641.1Sabs 5651.34SsimonbOther problems and possible solutions: 5661.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5671.1SabsSymptom:Complaints involving a Makefile. 5681.17SerhFix: Rebuild usr.bin/make: 5691.17Serh cd usr.bin/make && make && make install 5701.111Ssimonb Or, a failsafe method if that doesn't work: 5711.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 5721.17Serh 5731.1SabsFix: Make sure .mk files are up to date. 5741.1Sabs cd share/mk && make install 5751.2Smrg 5761.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 5771.142SdrochnerFix: Rebuild usr.bin/config 5781.1Sabs 5791.1SabsSymptom: 5801.1SabsFix: Rebuild usr.bin/yacc 5811.1Sabs 5821.1SabsSymptom: 5831.1SabsFix: Rebuild usr.bin/lex 5841.1Sabs 5851.1SabsSymptom: 5861.1SabsFix: rm /usr/lib/libbfd.a 5871.4Sitojun 5881.4SitojunSymptom:Obsolete intermediate files are used during compilation 5891.4SitojunFix: Try the following sequence of commands in the directory in question. 5901.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 5911.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 5921.4Sitojun may remain. The command tries to clean everything up) 5931.5Swiz 5941.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 5951.207Smbalmer pointer type 5961.5SwizFix: Rebuild and install usr.bin/menuc 5971.12Sitojun 5981.12SitojunSymptom:mklocale not found during build in share/locale/ctype 5991.12SitojunFix: Build and install usr.bin/mklocale 6001.13Sdogcow 6011.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 6021.13SdogcowFix: Rebuild and install lib/libc 6031.13Sdogcow 6041.142SdrochnerSymptom:usr.bin/config fails to build. 6051.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 6061.13Sdogcow 6071.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 6081.19ScgdFix: Rebuild and install lib/libc 6091.24Sabs 6101.24SabsSymptom:lint does not understand the '-X' option 6111.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 6121.223Sjoerg 6131.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 6141.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 6151.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 616