UPDATING revision 1.263
11.263Sdholland$NetBSD: UPDATING,v 1.263 2015/09/19 18:31:41 dholland 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.257SapbSections are marked with "^^^^^". After the section on "Recent changes" 151.257Sapbare several sections containing more general information. 161.257Sapb 171.123SjmcSee also: BUILDING, build.sh, Makefile. 181.1Sabs 191.1SabsRecent changes: 201.1Sabs^^^^^^^^^^^^^^^ 211.230Stls 221.263Sdholland20150818: 231.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 241.263Sdholland again. 251.263Sdholland 261.262Schristos20150413: 271.262Schristos New acpica requires "make cleandir" and reinstalling yacc 281.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 291.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 301.262Schristos 311.261Smartin20150404: 321.261Smartin Lint changes require a full rebuild of the tool, so make 331.261Smartin sure to build without -u option to build.sh, or manually 341.261Smartin do a make cleandir in src/tools/lint1 and 351.261Smartin src/usr.bin/xlint. 361.261Smartin 371.260Sskrll20150310: 381.260Sskrll Improvements to openssl for arm mean that update builds of 391.260Sskrll the openssl libraries will fail. A make cleandir in 401.260Sskrll external/bsd/openssl/lib is needed 411.260Sskrll 421.258Smartin20141026: 431.259Smsaitoh A mishap during the import of pppd may cause your corruption 441.258Smartin in your cvs directory if you happened to do a cvs update 451.258Smartin during a short period of time. To fix, just remove the 461.258Smartin directory src/external/bsd/ppp/dist/pppd completely 471.258Smartin and let cvs restore it on next update. 481.258Smartin 491.256Sapb20140721: 501.256Sapb The src/external/mit/lua/src directory was accidentally created 511.256Sapb and then deleted in the CVS repository. If you get errors like 521.256Sapb 531.256Sapb cvs [update aborted]: cannot open directory 541.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 551.256Sapb 561.256Sapb then delete your local copy of that directory tree and try again. 571.256Sapb 581.255Sjoerg20140530: 591.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 601.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 611.255Sjoerg 621.251Smartin20140131: 631.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 641.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 651.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 661.251Smartin 671.250Schristos20131227: 681.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 691.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 701.250Schristos mode7 in your config file. Make sure you put the necessary restrict 711.250Schristos statements to avoid being exposed. 721.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 731.250Schristos to make clean in libc 741.250Schristos 751.249Smrg20131129: 761.249Smrg The GMP sources were updated, and builds will likely fail without 771.249Smrg cleaning their build trees for both tools and in-tree, like below. 781.249Smrg 791.248Smrg20131128: 801.248Smrg The MPC and MPFR sources were updated, and builds may require their 811.248Smrg tools and in-tree directories cleaned for successful updates. 821.248Smrg 831.246Smartin20130605: 841.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 851.247Sspz to IPSEC (and the older IPSEC version removed). 861.247Sspz 871.247Sspz20130605: 881.246Smartin Previous freetype installations eroneously installed private 891.246Smartin header files. If you are building against a non-empty $DESTDIR, 901.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 911.246Smartin 921.245Smrg20130531: 931.245Smrg The xdm update may cause build failure due to xdm.man being 941.245Smrg in the obj tree. Make sure to ensure any like this: 951.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 961.245Smrg is fixed by deleting the xdm.man in the obj tree. 971.245Smrg 981.244Smrg20130530: 991.244Smrg Updates of many xsrc packages will leave old .pc files around. 1001.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 1011.244Smrg 1021.242Schristos20130301: 1031.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 1041.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 1051.242Schristos 1061.238Sdholland20120726: 1071.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 1081.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 1091.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 1101.241Swiz some cases may succeed and install broken OpenSSL libraries that 1111.240Sdholland cause third-party software to link incorrectly and/or crash. 1121.238Sdholland 1131.237Swiz20120507: 1141.241Swiz The database schema for makemandb was changed. You will 1151.237Swiz need to update the database using 'makemandb -f' or wait 1161.237Swiz for the next weekly run to fix it. 1171.237Swiz 1181.236Sbsh20120319: 1191.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 1201.236Sbsh size of db_symtab automatically. You need to update dbsym in 1211.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 1221.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 1231.236Sbsh mk.conf. 1241.236Sbsh 1251.235Sjoerg20120216: 1261.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 1271.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 1281.239Sdholland and 20120216, daily and weekly could have created an unreadable 1291.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 1301.235Sjoerg the next run of weekly will fix it. 1311.233Sjoerg 1321.232Schristos20111227: 1331.232Schristos If you built between 20111225 and 20111227 you need to remove 1341.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 1351.232Schristos bump has been reverted. 1361.232Schristos 1371.231Stls20111125: 1381.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 1391.231Stls means it should no longer be explicitly listed in kernel 1401.231Stls configuration files. The line "pseudo-device rnd" should be 1411.231Stls removed from any custom kernel config files users may have. 1421.231Stls 1431.230Stls20111119: 1441.230Stls A problem with the datastructures used by the rndctl(8) 1451.230Stls utility (pointers in datastructures in an array, making 32->64 1461.230Stls bit compatibility very painful) has been fixed in a 1471.230Stls non-backwards-compatible way. If you replace your kernel, 1481.230Stls replace your rndctl executable too. 1491.241Swiz 1501.229Sjym20111001: 1511.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 1521.229Sjym changed and their new version is not backward compatible with the old 1531.241Swiz one. So ensure that all consumers of these functions (currently: 1541.229Sjym quota2 code and its tests) are updated together with the new lib. 1551.229Sjym 1561.228Smrg20110817: 1571.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 1581.228Smrg DESTDIR for them should be deleted before updating. 1591.228Smrg 1601.227Sriastrad20110806: 1611.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 1621.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 1631.227Sriastrad 1641.226Smrg20110805: 1651.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 1661.226Smrg the tree to be cleaned. Best to delete both objdir and 1671.226Smrg DESTDIR before running this update. So far, only the 1681.226Smrg sparc64, mips and powerpc platforms have changed. 1691.226Smrg 1701.225Smatt20110803: 1711.241Swiz The layout of external/public-domain/xz has changed. To do an 1721.225Smatt update build you will have to remove the contents of the OBJDIR 1731.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 1741.225Smatt is now a directory. 1751.225Smatt 1761.223Sjoerg20110410: 1771.241Swiz The configuration of src/tools/gcc has changed. To do an 1781.224Sdholland update build you have to clean both tools/binutils and 1791.224Sdholland tools/gcc by hand. 1801.223Sjoerg 1811.222Splunky20110328: 1821.222Splunky Building the Xorg binary was moved into a subdirectory to fix 1831.241Swiz ordering issues with "make all". It may be necessary to remove 1841.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 1851.222Splunky if your update build fails, as the "Xorg" entry there is now a 1861.222Splunky directory. 1871.222Splunky 1881.220Sjoerg20110121: 1891.221Slukem Assembler files no longer use -traditional-cpp. This can break 1901.220Sjoerg the build of individual parts of the tree. This is handled 1911.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 1921.220Sjoerg and re-run config(1) for any kernel configurations as needed. 1931.218Sjoerg 1941.217Sjruoho20101217: 1951.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 1961.241Swiz by default. It may be necessary to manually update passwd(5) and 1971.217Sjruoho group(5) in order to make the program work with existing setups. 1981.217Sjruoho 1991.216Schristos20101125: 2001.216Schristos The latest changes to setenv(3) dissallow setting environment 2011.241Swiz variables with names that contain '='. Revision 1.18 of env.c 2021.241Swiz assumed that this was allowed. Installing a new libc with an 2031.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 2041.216Schristos break which affects the autoconf tests for dependency finding, 2051.216Schristos so building gcc will end up printing: 2061.216Schristos checking dependency style of gcc... none 2071.216Schristos configure: error: no usable dependency style found 2081.216Schristos Fix it by rebuilding and re-installing env. 2091.138Slukem 2101.215Smrg20101119: 2111.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 2121.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 2131.215Smrg have any build problems with xsrc, or problems with mismatched 2141.215Smrg versions between xorg-server and drivers. 2151.215Smrg 2161.213Sjmmv20100604: 2171.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 2181.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 2191.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 2201.213Sjmmv trees by hand. 2211.213Sjmmv 2221.211Stnozaki20100522: 2231.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 2241.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 2251.212Smrg build problems with xsrc. 2261.212Smrg 2271.212Smrg20100522: 2281.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 2291.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 2301.211Stnozaki 2311.210Schristos20100520: 2321.241Swiz The location of the xkb compiled descriptions has changed. Please 2331.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 2341.210Schristos 2351.209Snjoly20100222: 2361.209Snjoly The shared objects file extension has been changed from .so to 2371.209Snjoly .pico, in order to avoid conflicts with shared libraries names 2381.209Snjoly libXX.so. All now stale regular .so files can be removed from 2391.209Snjoly your object directories. 2401.209Snjoly 2411.208Sroy20100204: 2421.208Sroy The termcap database has been removed from the sources, 2431.208Sroy but has not been marked obsolete so it is not removed 2441.208Sroy from the system when upgrading. 2451.208Sroy As such, you will need to remove them from your object 2461.208Sroy and destination directories. 2471.208Sroy 2481.203Sdyoung20091101: 2491.205Sdholland After updating, it may be necessary to make the 'cleandir' 2501.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 2511.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 2521.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 2531.203Sdyoung 2541.202Smrg20091001: 2551.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 2561.206Sdholland before building a kernel, or the build fails on cpufunc.S. 2571.206Sdholland 2581.206Sdholland20091001: 2591.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 2601.202Smrg symlink, failing the build. Delete the link, and the subdir 2611.202Smrg it is in, and retry your build. 2621.202Smrg 2631.201Sdsl20090718: 2641.201Sdsl libc build changed so that strchr() provides the extra entry 2651.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 2661.201Sdsl may fail because the archive contains the unwanted index.o. 2671.201Sdsl (Similarly for strrchr() and rindex().) 2681.201Sdsl 2691.198Smrg20090709: 2701.198Smrg Native Xorg was upgraded again. Builds will probably fail again 2711.198Smrg without a clean objdir, at least for src/external/mit/xorg. 2721.198Smrg 2731.197Smrg20090616: 2741.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 2751.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 2761.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 2771.197Smrg subdirectory has been changed into a file, and this needs to 2781.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 2791.197Smrg 2801.195Sperry20090501: 2811.195Sperry Several new functions were added to string.h/libc, and this 2821.195Sperry can cause autoconf problems during the tool build for people 2831.241Swiz who fail to clean out their tools objects properly. If you 2841.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 2851.195Sperry failure during the tool build, clean out all your tools 2861.195Sperry objects and start again. 2871.195Sperry 2881.194Smrg20090325: 2891.194Smrg The i386 port was switched to i486 default toolchain. This requires 2901.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 2911.194Smrg 2921.192Sskrll20090126: 2931.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 2941.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 2951.207Smbalmer to avoid using the old assembly stub. 2961.192Sskrll 2971.191Sjoerg20090202: 2981.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 2991.191Sjoerg detection. It is recommented to rebuild the cache with 3001.191Sjoerg ``pkg_admin rebuild''. 3011.191Sjoerg 3021.184Schristos20090110: 3031.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 3041.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 3051.188Schristos This is needed even in the MODULAR kernel because there is 3061.188Schristos conditionally compiled code in rtsock.c. 3071.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 3081.184Schristos before installing. 3091.184Schristos 3. If you don't use build.sh and you build directly to root, and 3101.241Swiz your build breaks in the middle, don't despair. Make sure headers 3111.184Schristos are installed properly, and start building libraries first libc 3121.184Schristos and libutil, install them and then continue building all the 3131.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 3141.184Schristos the new libraries are installed, you can restart the build. 3151.184Schristos 4. If you compile packages and you notice link time warnings, 3161.189Shubertf rebuild the required packages to update their shared libraries. 3171.189Shubertf Any package you rebuild will require rebuilding all the packages 3181.189Shubertf that depend on it. 3191.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 3201.186Schristos will be upgraded and it will not be backwards compatible. 3211.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 3221.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 3231.241Swiz for utmp. You are better off removing the old files after 3241.190Sapb upgrading. The automated clearing of /var/run during 3251.190Sapb boot, and the automated rotating of files in /var/log by 3261.190Sapb newsyslog(8), may mean that you do not have to remove the 3271.190Sapb files manually. 3281.190Sapb 7. The optional accounting file (/var/account/acct, see 3291.190Sapb accton(8)) has not been versioned, and will need to be 3301.190Sapb removed. The automatic rotation of the accounting file by 3311.190Sapb /etc/daily limits the bad consequences of failure to remove 3321.190Sapb the file. 3331.196Sdholland 8. Application software that writes time_t to binary files on 3341.241Swiz disk will break or need attention. Most notably: if you are 3351.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 3361.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 3371.185Sjmcneill 3381.183Spgoyette20081219: 3391.183Spgoyette config(1) has been updated, and one of the files it creates - 3401.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 3411.183Spgoyette (done automatically by build.sh) and then you need to rerun 3421.183Spgoyette config on all kernel configuration files before rebuilding those 3431.183Spgoyette kernels. 3441.183Spgoyette 3451.181Scube20081205: 3461.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 3471.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 3481.181Scube set and will appear as extra files for MKX11=no update builds. 3491.178Slukem 3501.179Stsutsui20081122: 3511.182Stsutsui On i386, various kernel options(4) in GENERIC including 3521.180Swiz file systems have been disabled and moved into kernel modules. 3531.180Swiz Before trying a new GENERIC kernel, you have to prepare the 3541.179Stsutsui following files as well as a new GENERIC kernel: 3551.179Stsutsui 3561.179Stsutsui - build and install kernel modules from src/sys/modules 3571.179Stsutsui 3581.179Stsutsui - install the latest bootloader, which will load a module 3591.180Swiz for the file system from which the kernel is loaded automatically 3601.179Stsutsui 3611.180Swiz If you have to load your kernel from a file system which is not of 3621.180Swiz the same type as the root file system, you have to load the necessary 3631.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 3641.179Stsutsui 3651.178Slukem20080827: 3661.178Slukem If you built and installed a libc from sources between 3671.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 3681.178Slukem which results in false errors reported by lint(1). 3691.178Slukem Since this breaks the libc build itself, manual help is 3701.180Swiz needed -- lint must be disabled temporarily, e.g.: 3711.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 3721.178Slukem 3731.177Schristos20080813: 3741.177Schristos MKDEBUG build was broken because the .depend files did not know 3751.241Swiz about .go files. You need to remove all .depend files and rebuild. 3761.177Schristos 3771.200Sdholland20080802: 3781.200Sdholland A regression in binary compatibility for pthread_mutex_t has 3791.241Swiz been fixed. Unfortunately, the price is breaking compatibility 3801.200Sdholland for -current. 3811.200Sdholland 3821.200Sdholland Threaded programs (using libpthread) and C++ programs (using 3831.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 3841.200Sdholland be recompiled. 3851.200Sdholland 3861.200Sdholland One way to find affected pkgsrc packages: 3871.200Sdholland 3881.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 3891.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 3901.200Sdholland 3911.175Ssimonb20080731: 3921.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 3931.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 3941.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 3951.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 3961.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 3971.176Ssimonb also requires the super block to be in the UFS2 format. You 3981.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 3991.175Ssimonb 4001.174Slukem20080721: 4011.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 4021.174Slukem isn't defined. 4031.174Slukem 4041.173Sfreza20080531: 4051.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 4061.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 4071.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 4081.241Swiz won't work correctly. The following sequence of commands: 4091.173Sfreza 4101.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 4111.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 4121.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 4131.173Sfreza 4141.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 4151.173Sfreza 4161.172Slukem20080503: 4171.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 4181.172Slukem 4191.171She20080521: 4201.171She For a while, unprivileged UPDATE builds would fail to 4211.171She succeed at the checkflist stage, complaining that 4221.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 4231.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 4241.171She If you already hit this problem, update the .mk file, 4251.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 4261.171She 4271.174Slukem20080303: 4281.174Slukem Linker warnings are now fatal if $WARNS>0. 4291.174Slukem 4301.170Schristos20080126: 4311.170Schristos The posix_fadvise system call has been changed from an assembly 4321.241Swiz stub, to a c file that calls an assembly stub. You need to 4331.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 4341.170Schristos avoid using the old assembly stub. 4351.170Schristos 4361.168Sjoerg20071209: 4371.241Swiz The acpiec(4) driver has been split into two attachments. If you 4381.168Sjoerg get ACPI errors before the attachment, please update your kernel 4391.169Swiz configuration file appropriately or see GENERIC for more details. 4401.168Sjoerg 4411.166Sxtraeme20071115: 4421.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 4431.166Sxtraeme argument specified in the kernel configuration file is not valid 4441.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 4451.241Swiz rather than the EC address port. Please update your kernel 4461.167Swiz configuration file appropriately or see GENERIC for more details. 4471.166Sxtraeme 4481.165Sjmmv20071028: 4491.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 4501.165Sjmmv You need to update any custom kernel configuration file you have 4511.165Sjmmv to remove any references to pccons (which includes removing the 4521.165Sjmmv now useless XSERVER option) and replace them with the correct 4531.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 4541.165Sjmmv for more details. 4551.165Sjmmv 4561.164Sgdt20070913: 4571.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 4581.164Sgdt enumerate interfaces was fixed. The bug began to cause 4591.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 4601.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 4611.164Sgdt could not enumerate interfaces. (These are noted because 4621.164Sgdt normal kernel/userspace version matching hygiene is not 4631.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 4641.164Sgdt and userland are from after 20070913. 4651.164Sgdt 4661.163Sjoerg20070703: 4671.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 4681.199Sdholland calls the target-specific strip program, and the logic to pass 4691.199Sdholland down STRIP from make has been removed. This requires a 4701.199Sdholland re-installation of tools. 4711.163Sjoerg 4721.161Sdsl20070422: 4731.161Sdsl The way OS emulations lookup filenames inside the emulation root 4741.161Sdsl has been changed. Rather than modify the pathname (and copy back 4751.161Sdsl to userspace) namei() and lookup() directly check the emulation 4761.241Swiz root. One side effect is that absolute symlinks inside the emulated 4771.167Swiz root file system will be relative to that file system - unless they 4781.161Sdsl start /../ this is useful when the emulated root is a real install 4791.161Sdsl that has such links. 4801.161Sdsl This might affect symlinks that have been added to reference outside 4811.161Sdsl the emulated root. 4821.161Sdsl 4831.160Sjmcneill20070412: 4841.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 4851.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 4861.160Sjmcneill example. 4871.160Sjmcneill 4881.159Sgdt20070319: 4891.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 4901.159Sgdt on many platforms due to incorrect flags settings. If you 4911.159Sgdt updated and built after about 20070315, do "nbmake-$arch 4921.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 4931.159Sgdt rebuild of object files that might have been built 4941.159Sgdt incorrectly, and ensure that you have at least 4951.159Sgdt src/lib/libc/Makefile 1.130. 4961.159Sgdt 4971.241Swiz20070210: 4981.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 4991.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 5001.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 5011.158Sdbj will allow dependencies on those files to get get rebuilt 5021.158Sdbj 5031.157Sapb20070209: 5041.157Sapb The threading model was changed when the newlock2 branch 5051.157Sapb was merged to NetBSD-current. If you boot with a new 5061.157Sapb kernel (version 4.99.10), then you also need a new pthread 5071.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 5081.157Sapb an old kernel, then you need the old pthread library 5091.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 5101.157Sapb the pthread library in sync, old threaded applications should 5111.157Sapb continue to work with an old or new kernel. Note that named(8) 5121.157Sapb is the only threaded application in the base system. 5131.157Sapb 5141.154She20061214: 5151.154She Following the move of string_to_flags() and flags_to_string() 5161.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 5171.154She will need to do a "make cleandir" in 5181.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 5191.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 5201.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 5211.156She as the installation images in distrib/ 5221.154She in order to excise stale references to the old stat_flags.h header 5231.154She file in the ls sources -- stat_flags.h has been removed. 5241.154She 5251.152Schristos20061108: 5261.152Schristos The configure script used in the src/tools/gcc compiler has been 5271.152Schristos changed to indicate that our libc has ssp support built-in and 5281.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 5291.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 5301.152Schristos 5311.151Srpaulo20061009: 5321.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 5331.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 5341.151Srpaulo 5351.150Sbjh2120060814: 5361.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 5371.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 5381.150Sbjh21 kernel configuration for an example. X servers from the last 5391.150Sbjh21 few years should cope. 5401.150Sbjh21 5411.149Schristos20060703: 5421.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 5431.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 5441.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 5451.149Schristos 5461.148Sdogcow20060627: 5471.148Sdogcow socket(2) has changed, and its system call has been versioned. 5481.148Sdogcow For userlands with the old version of socket(2), make sure that 5491.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 5501.148Sdogcow errors will result. 5511.148Sdogcow 5521.1SabsHints for a more successful build: 5531.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5541.123Sjmc Use build.sh, but do not use its "expert mode": 5551.132Sjmmv This will automatically build the tools in the 5561.123Sjmc correct order, and it will keep the tools and the 5571.123Sjmc new build products from interfering with the running 5581.123Sjmc system. This will allow you to ignore most of the 5591.123Sjmc other advice in this file. 5601.2Smrg Build a new kernel first: 5611.2Smrg This makes sure that any new system calls or features 5621.2Smrg expected by the new userland will be present. This 5631.2Smrg helps to avoid critical errors when upgrading. 5641.1Sabs Use object directories: 5651.1Sabs This helps to keep stale object 5661.1Sabs files from polluting the build if a Makefile "forgets" 5671.1Sabs about one. It also makes it easier to clean up after 5681.1Sabs a build. It's also necessary if you want to use the 5691.1Sabs same source tree for multiple machines. 5701.123Sjmc To use object directories with build.sh: 5711.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 5721.123Sjmc To use object directories without using build.sh: 5731.1Sabs a) cd /usr/src ; make cleandir 5741.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 5751.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 5761.1Sabs d) cd /usr/src ; make build 5771.2Smrg Note that running "make obj" in a directory will create 5781.2Smrg in obj.$MACHINE directory. 5791.1Sabs Build to a DESTDIR: 5801.123Sjmc This helps to keep old installed files (especially libraries) 5811.123Sjmc from interfering with the new build. 5821.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 5831.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 5841.123Sjmc environment variable before running make build. It should be 5851.123Sjmc set to the pathname of an initially empty directory. 5861.123Sjmc Problems: if you do not use build.sh, you might need to 5871.123Sjmc update critical utilities without using DESTDIR since 5881.123Sjmc nothing is executed from what is installed in DESTDIR. 5891.123Sjmc (See critical utils, below.) 5901.1Sabs Build often: 5911.1Sabs This keeps critical utilities current enough to not choke 5921.1Sabs on any other part of the source tree that depends on up to 5931.123Sjmc date functionality. If you use build.sh, you should not have 5941.123Sjmc this problem. 5951.241Swiz 5961.1SabsWhat to do if things don't work: 5971.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5981.230StlsWhen things don't work there are usually a few things that commonly 5991.1Sabsshould be done. 6001.1Sabs 1) make includes 6011.1Sabs This should be done automatically by make build. 6021.1Sabs 2) cd share/mk && make install 6031.1Sabs Again, automatically done by make build. 6041.1Sabs 6051.1SabsFailsafe rebuild of a small part of the tree: 6061.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6071.1SabsTo make sure you rebuild something correctly you want to do 6081.1Sabssomething like the following: 6091.1Sabs 1) Make sure the includes and .mk files are up to date. 6101.1Sabs 2) Make sure any program used to build the particular 6111.1Sabs utility is up to date. (yacc, lex, etc...) 6121.1Sabs 3) cd ...path/to/util... 6131.1Sabs make cleandir 6141.1Sabs rm ...all obj directories... 6151.1Sabs make cleandir # yes, again 6161.1Sabs make obj 6171.1Sabs make depend && make 6181.1Sabs 6191.1SabsFailsafe rebuild of the entire tree: 6201.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6211.1SabsIf you really want to make sure the source tree is clean and 6221.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 6231.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 6241.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 6251.1Sabs 6261.1Sabs---cut here--- 6271.1Sabs#!/bin/sh 6281.1Sabs. /etc/mk.conf 6291.1Sabs 6301.58Slukemif [ -z $NETBSDSRCDIR ] ; then 6311.58Slukem NETBSDSRCDIR=/usr/src 6321.1Sabsfi 6331.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 6341.1Sabs echo Unable to find sources 6351.1Sabs exit 1 6361.1Sabsfi 6371.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 6381.1Sabs 6391.1Sabsif [ -z $BSDOBJDIR ] ; then 6401.1Sabs BSDOBJDIR=/usr/obj 6411.1Sabsfi 6421.1Sabsif [ -d $BSDOBJDIR ] ; then 6431.1Sabs rm -rf $BSDOBJDIR 6441.1Sabsfi 6451.1Sabs 6461.58Slukemcd $NETBSDSRCDIR && make cleandir 6471.1Sabs 6481.1Sabs---cut here--- 6491.1Sabs 6501.1SabsCritical utilities: 6511.1Sabs^^^^^^^^^^^^^^^^^^^ 6521.3Sitojun usr.bin/compile_et 6531.1Sabs usr.bin/make 6541.1Sabs usr.bin/yacc 6551.1Sabs usr.bin/lex 6561.11Slukem usr.bin/xlint 6571.142Sdrochner usr.bin/config 6581.1Sabs 6591.34SsimonbOther problems and possible solutions: 6601.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6611.1SabsSymptom:Complaints involving a Makefile. 6621.17SerhFix: Rebuild usr.bin/make: 6631.17Serh cd usr.bin/make && make && make install 6641.111Ssimonb Or, a failsafe method if that doesn't work: 6651.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 6661.17Serh 6671.1SabsFix: Make sure .mk files are up to date. 6681.1Sabs cd share/mk && make install 6691.2Smrg 6701.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 6711.142SdrochnerFix: Rebuild usr.bin/config 6721.1Sabs 6731.1SabsSymptom: 6741.1SabsFix: Rebuild usr.bin/yacc 6751.1Sabs 6761.1SabsSymptom: 6771.1SabsFix: Rebuild usr.bin/lex 6781.1Sabs 6791.1SabsSymptom: 6801.1SabsFix: rm /usr/lib/libbfd.a 6811.4Sitojun 6821.4SitojunSymptom:Obsolete intermediate files are used during compilation 6831.4SitojunFix: Try the following sequence of commands in the directory in question. 6841.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 6851.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 6861.4Sitojun may remain. The command tries to clean everything up) 6871.5Swiz 6881.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 6891.207Smbalmer pointer type 6901.5SwizFix: Rebuild and install usr.bin/menuc 6911.12Sitojun 6921.12SitojunSymptom:mklocale not found during build in share/locale/ctype 6931.12SitojunFix: Build and install usr.bin/mklocale 6941.13Sdogcow 6951.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 6961.13SdogcowFix: Rebuild and install lib/libc 6971.13Sdogcow 6981.142SdrochnerSymptom:usr.bin/config fails to build. 6991.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 7001.13Sdogcow 7011.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 7021.19ScgdFix: Rebuild and install lib/libc 7031.24Sabs 7041.24SabsSymptom:lint does not understand the '-X' option 7051.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 7061.223Sjoerg 7071.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 7081.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 7091.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 7101.257Sapb 7111.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 7121.257Sapb No such file or directory. 7131.257SapbCause: If a directory is created by mistake, then it is sometimes 7141.257Sapb deleted from the CVS repository using administrative commands 7151.257Sapb that bypass the normal cvs access controls. If your cvs working tree 7161.257Sapb contains references to a directory that has been deleted on the 7171.257Sapb server in this way, then "cvs update" reports this error. 7181.257SapbFix: Recursively delete the affected directory from your working tree 7191.257Sapb and try the update again. 720