UPDATING revision 1.265
11.265Saymeric$NetBSD: UPDATING,v 1.265 2016/02/29 22:49:11 aymeric 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.265Saymeric20160229: 231.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 241.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 251.265Saymeric non-NetBSD hosts if linked with stale object files produced 261.265Saymeric while they included a non-NetBSD regex.h. 271.265Saymeric In any case, you should "make cleandir" at least these tools 281.265Saymeric before updating your toolchain. 291.265Saymeric 301.264Smartin20160125: 311.264Smartin Dtrace has been enabled by default on some architectures. 321.264Smartin When doing an update build, make sure to clean the etc/mtree 331.264Smartin object directory before starting the build - otherwise the 341.264Smartin needed directories in destdir will not be created. 351.264Smartin An easy way to do this is: 361.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 371.264Smartin 381.263Sdholland20150818: 391.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 401.263Sdholland again. 411.263Sdholland 421.262Schristos20150413: 431.262Schristos New acpica requires "make cleandir" and reinstalling yacc 441.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 451.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 461.262Schristos 471.261Smartin20150404: 481.261Smartin Lint changes require a full rebuild of the tool, so make 491.261Smartin sure to build without -u option to build.sh, or manually 501.261Smartin do a make cleandir in src/tools/lint1 and 511.261Smartin src/usr.bin/xlint. 521.261Smartin 531.260Sskrll20150310: 541.260Sskrll Improvements to openssl for arm mean that update builds of 551.260Sskrll the openssl libraries will fail. A make cleandir in 561.260Sskrll external/bsd/openssl/lib is needed 571.260Sskrll 581.258Smartin20141026: 591.259Smsaitoh A mishap during the import of pppd may cause your corruption 601.258Smartin in your cvs directory if you happened to do a cvs update 611.258Smartin during a short period of time. To fix, just remove the 621.258Smartin directory src/external/bsd/ppp/dist/pppd completely 631.258Smartin and let cvs restore it on next update. 641.258Smartin 651.256Sapb20140721: 661.256Sapb The src/external/mit/lua/src directory was accidentally created 671.256Sapb and then deleted in the CVS repository. If you get errors like 681.256Sapb 691.256Sapb cvs [update aborted]: cannot open directory 701.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 711.256Sapb 721.256Sapb then delete your local copy of that directory tree and try again. 731.256Sapb 741.255Sjoerg20140530: 751.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 761.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 771.255Sjoerg 781.251Smartin20140131: 791.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 801.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 811.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 821.251Smartin 831.250Schristos20131227: 841.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 851.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 861.250Schristos mode7 in your config file. Make sure you put the necessary restrict 871.250Schristos statements to avoid being exposed. 881.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 891.250Schristos to make clean in libc 901.250Schristos 911.249Smrg20131129: 921.249Smrg The GMP sources were updated, and builds will likely fail without 931.249Smrg cleaning their build trees for both tools and in-tree, like below. 941.249Smrg 951.248Smrg20131128: 961.248Smrg The MPC and MPFR sources were updated, and builds may require their 971.248Smrg tools and in-tree directories cleaned for successful updates. 981.248Smrg 991.246Smartin20130605: 1001.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 1011.247Sspz to IPSEC (and the older IPSEC version removed). 1021.247Sspz 1031.247Sspz20130605: 1041.246Smartin Previous freetype installations eroneously installed private 1051.246Smartin header files. If you are building against a non-empty $DESTDIR, 1061.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 1071.246Smartin 1081.245Smrg20130531: 1091.245Smrg The xdm update may cause build failure due to xdm.man being 1101.245Smrg in the obj tree. Make sure to ensure any like this: 1111.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 1121.245Smrg is fixed by deleting the xdm.man in the obj tree. 1131.245Smrg 1141.244Smrg20130530: 1151.244Smrg Updates of many xsrc packages will leave old .pc files around. 1161.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 1171.244Smrg 1181.242Schristos20130301: 1191.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 1201.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 1211.242Schristos 1221.238Sdholland20120726: 1231.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 1241.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 1251.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 1261.241Swiz some cases may succeed and install broken OpenSSL libraries that 1271.240Sdholland cause third-party software to link incorrectly and/or crash. 1281.238Sdholland 1291.237Swiz20120507: 1301.241Swiz The database schema for makemandb was changed. You will 1311.237Swiz need to update the database using 'makemandb -f' or wait 1321.237Swiz for the next weekly run to fix it. 1331.237Swiz 1341.236Sbsh20120319: 1351.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 1361.236Sbsh size of db_symtab automatically. You need to update dbsym in 1371.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 1381.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 1391.236Sbsh mk.conf. 1401.236Sbsh 1411.235Sjoerg20120216: 1421.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 1431.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 1441.239Sdholland and 20120216, daily and weekly could have created an unreadable 1451.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 1461.235Sjoerg the next run of weekly will fix it. 1471.233Sjoerg 1481.232Schristos20111227: 1491.232Schristos If you built between 20111225 and 20111227 you need to remove 1501.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 1511.232Schristos bump has been reverted. 1521.232Schristos 1531.231Stls20111125: 1541.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 1551.231Stls means it should no longer be explicitly listed in kernel 1561.231Stls configuration files. The line "pseudo-device rnd" should be 1571.231Stls removed from any custom kernel config files users may have. 1581.231Stls 1591.230Stls20111119: 1601.230Stls A problem with the datastructures used by the rndctl(8) 1611.230Stls utility (pointers in datastructures in an array, making 32->64 1621.230Stls bit compatibility very painful) has been fixed in a 1631.230Stls non-backwards-compatible way. If you replace your kernel, 1641.230Stls replace your rndctl executable too. 1651.241Swiz 1661.229Sjym20111001: 1671.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 1681.229Sjym changed and their new version is not backward compatible with the old 1691.241Swiz one. So ensure that all consumers of these functions (currently: 1701.229Sjym quota2 code and its tests) are updated together with the new lib. 1711.229Sjym 1721.228Smrg20110817: 1731.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 1741.228Smrg DESTDIR for them should be deleted before updating. 1751.228Smrg 1761.227Sriastrad20110806: 1771.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 1781.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 1791.227Sriastrad 1801.226Smrg20110805: 1811.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 1821.226Smrg the tree to be cleaned. Best to delete both objdir and 1831.226Smrg DESTDIR before running this update. So far, only the 1841.226Smrg sparc64, mips and powerpc platforms have changed. 1851.226Smrg 1861.225Smatt20110803: 1871.241Swiz The layout of external/public-domain/xz has changed. To do an 1881.225Smatt update build you will have to remove the contents of the OBJDIR 1891.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 1901.225Smatt is now a directory. 1911.225Smatt 1921.223Sjoerg20110410: 1931.241Swiz The configuration of src/tools/gcc has changed. To do an 1941.224Sdholland update build you have to clean both tools/binutils and 1951.224Sdholland tools/gcc by hand. 1961.223Sjoerg 1971.222Splunky20110328: 1981.222Splunky Building the Xorg binary was moved into a subdirectory to fix 1991.241Swiz ordering issues with "make all". It may be necessary to remove 2001.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 2011.222Splunky if your update build fails, as the "Xorg" entry there is now a 2021.222Splunky directory. 2031.222Splunky 2041.220Sjoerg20110121: 2051.221Slukem Assembler files no longer use -traditional-cpp. This can break 2061.220Sjoerg the build of individual parts of the tree. This is handled 2071.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 2081.220Sjoerg and re-run config(1) for any kernel configurations as needed. 2091.218Sjoerg 2101.217Sjruoho20101217: 2111.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 2121.241Swiz by default. It may be necessary to manually update passwd(5) and 2131.217Sjruoho group(5) in order to make the program work with existing setups. 2141.217Sjruoho 2151.216Schristos20101125: 2161.216Schristos The latest changes to setenv(3) dissallow setting environment 2171.241Swiz variables with names that contain '='. Revision 1.18 of env.c 2181.241Swiz assumed that this was allowed. Installing a new libc with an 2191.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 2201.216Schristos break which affects the autoconf tests for dependency finding, 2211.216Schristos so building gcc will end up printing: 2221.216Schristos checking dependency style of gcc... none 2231.216Schristos configure: error: no usable dependency style found 2241.216Schristos Fix it by rebuilding and re-installing env. 2251.138Slukem 2261.215Smrg20101119: 2271.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 2281.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 2291.215Smrg have any build problems with xsrc, or problems with mismatched 2301.215Smrg versions between xorg-server and drivers. 2311.215Smrg 2321.213Sjmmv20100604: 2331.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 2341.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 2351.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 2361.213Sjmmv trees by hand. 2371.213Sjmmv 2381.211Stnozaki20100522: 2391.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 2401.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 2411.212Smrg build problems with xsrc. 2421.212Smrg 2431.212Smrg20100522: 2441.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 2451.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 2461.211Stnozaki 2471.210Schristos20100520: 2481.241Swiz The location of the xkb compiled descriptions has changed. Please 2491.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 2501.210Schristos 2511.209Snjoly20100222: 2521.209Snjoly The shared objects file extension has been changed from .so to 2531.209Snjoly .pico, in order to avoid conflicts with shared libraries names 2541.209Snjoly libXX.so. All now stale regular .so files can be removed from 2551.209Snjoly your object directories. 2561.209Snjoly 2571.208Sroy20100204: 2581.208Sroy The termcap database has been removed from the sources, 2591.208Sroy but has not been marked obsolete so it is not removed 2601.208Sroy from the system when upgrading. 2611.208Sroy As such, you will need to remove them from your object 2621.208Sroy and destination directories. 2631.208Sroy 2641.203Sdyoung20091101: 2651.205Sdholland After updating, it may be necessary to make the 'cleandir' 2661.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 2671.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 2681.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 2691.203Sdyoung 2701.202Smrg20091001: 2711.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 2721.206Sdholland before building a kernel, or the build fails on cpufunc.S. 2731.206Sdholland 2741.206Sdholland20091001: 2751.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 2761.202Smrg symlink, failing the build. Delete the link, and the subdir 2771.202Smrg it is in, and retry your build. 2781.202Smrg 2791.201Sdsl20090718: 2801.201Sdsl libc build changed so that strchr() provides the extra entry 2811.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 2821.201Sdsl may fail because the archive contains the unwanted index.o. 2831.201Sdsl (Similarly for strrchr() and rindex().) 2841.201Sdsl 2851.198Smrg20090709: 2861.198Smrg Native Xorg was upgraded again. Builds will probably fail again 2871.198Smrg without a clean objdir, at least for src/external/mit/xorg. 2881.198Smrg 2891.197Smrg20090616: 2901.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 2911.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 2921.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 2931.197Smrg subdirectory has been changed into a file, and this needs to 2941.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 2951.197Smrg 2961.195Sperry20090501: 2971.195Sperry Several new functions were added to string.h/libc, and this 2981.195Sperry can cause autoconf problems during the tool build for people 2991.241Swiz who fail to clean out their tools objects properly. If you 3001.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 3011.195Sperry failure during the tool build, clean out all your tools 3021.195Sperry objects and start again. 3031.195Sperry 3041.194Smrg20090325: 3051.194Smrg The i386 port was switched to i486 default toolchain. This requires 3061.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 3071.194Smrg 3081.192Sskrll20090126: 3091.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 3101.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 3111.207Smbalmer to avoid using the old assembly stub. 3121.192Sskrll 3131.191Sjoerg20090202: 3141.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 3151.191Sjoerg detection. It is recommented to rebuild the cache with 3161.191Sjoerg ``pkg_admin rebuild''. 3171.191Sjoerg 3181.184Schristos20090110: 3191.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 3201.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 3211.188Schristos This is needed even in the MODULAR kernel because there is 3221.188Schristos conditionally compiled code in rtsock.c. 3231.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 3241.184Schristos before installing. 3251.184Schristos 3. If you don't use build.sh and you build directly to root, and 3261.241Swiz your build breaks in the middle, don't despair. Make sure headers 3271.184Schristos are installed properly, and start building libraries first libc 3281.184Schristos and libutil, install them and then continue building all the 3291.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 3301.184Schristos the new libraries are installed, you can restart the build. 3311.184Schristos 4. If you compile packages and you notice link time warnings, 3321.189Shubertf rebuild the required packages to update their shared libraries. 3331.189Shubertf Any package you rebuild will require rebuilding all the packages 3341.189Shubertf that depend on it. 3351.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 3361.186Schristos will be upgraded and it will not be backwards compatible. 3371.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 3381.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 3391.241Swiz for utmp. You are better off removing the old files after 3401.190Sapb upgrading. The automated clearing of /var/run during 3411.190Sapb boot, and the automated rotating of files in /var/log by 3421.190Sapb newsyslog(8), may mean that you do not have to remove the 3431.190Sapb files manually. 3441.190Sapb 7. The optional accounting file (/var/account/acct, see 3451.190Sapb accton(8)) has not been versioned, and will need to be 3461.190Sapb removed. The automatic rotation of the accounting file by 3471.190Sapb /etc/daily limits the bad consequences of failure to remove 3481.190Sapb the file. 3491.196Sdholland 8. Application software that writes time_t to binary files on 3501.241Swiz disk will break or need attention. Most notably: if you are 3511.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 3521.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 3531.185Sjmcneill 3541.183Spgoyette20081219: 3551.183Spgoyette config(1) has been updated, and one of the files it creates - 3561.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 3571.183Spgoyette (done automatically by build.sh) and then you need to rerun 3581.183Spgoyette config on all kernel configuration files before rebuilding those 3591.183Spgoyette kernels. 3601.183Spgoyette 3611.181Scube20081205: 3621.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 3631.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 3641.181Scube set and will appear as extra files for MKX11=no update builds. 3651.178Slukem 3661.179Stsutsui20081122: 3671.182Stsutsui On i386, various kernel options(4) in GENERIC including 3681.180Swiz file systems have been disabled and moved into kernel modules. 3691.180Swiz Before trying a new GENERIC kernel, you have to prepare the 3701.179Stsutsui following files as well as a new GENERIC kernel: 3711.179Stsutsui 3721.179Stsutsui - build and install kernel modules from src/sys/modules 3731.179Stsutsui 3741.179Stsutsui - install the latest bootloader, which will load a module 3751.180Swiz for the file system from which the kernel is loaded automatically 3761.179Stsutsui 3771.180Swiz If you have to load your kernel from a file system which is not of 3781.180Swiz the same type as the root file system, you have to load the necessary 3791.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 3801.179Stsutsui 3811.178Slukem20080827: 3821.178Slukem If you built and installed a libc from sources between 3831.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 3841.178Slukem which results in false errors reported by lint(1). 3851.178Slukem Since this breaks the libc build itself, manual help is 3861.180Swiz needed -- lint must be disabled temporarily, e.g.: 3871.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 3881.178Slukem 3891.177Schristos20080813: 3901.177Schristos MKDEBUG build was broken because the .depend files did not know 3911.241Swiz about .go files. You need to remove all .depend files and rebuild. 3921.177Schristos 3931.200Sdholland20080802: 3941.200Sdholland A regression in binary compatibility for pthread_mutex_t has 3951.241Swiz been fixed. Unfortunately, the price is breaking compatibility 3961.200Sdholland for -current. 3971.200Sdholland 3981.200Sdholland Threaded programs (using libpthread) and C++ programs (using 3991.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 4001.200Sdholland be recompiled. 4011.200Sdholland 4021.200Sdholland One way to find affected pkgsrc packages: 4031.200Sdholland 4041.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 4051.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 4061.200Sdholland 4071.175Ssimonb20080731: 4081.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 4091.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 4101.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 4111.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 4121.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 4131.176Ssimonb also requires the super block to be in the UFS2 format. You 4141.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 4151.175Ssimonb 4161.174Slukem20080721: 4171.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 4181.174Slukem isn't defined. 4191.174Slukem 4201.173Sfreza20080531: 4211.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 4221.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 4231.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 4241.241Swiz won't work correctly. The following sequence of commands: 4251.173Sfreza 4261.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 4271.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 4281.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 4291.173Sfreza 4301.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 4311.173Sfreza 4321.172Slukem20080503: 4331.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 4341.172Slukem 4351.171She20080521: 4361.171She For a while, unprivileged UPDATE builds would fail to 4371.171She succeed at the checkflist stage, complaining that 4381.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 4391.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 4401.171She If you already hit this problem, update the .mk file, 4411.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 4421.171She 4431.174Slukem20080303: 4441.174Slukem Linker warnings are now fatal if $WARNS>0. 4451.174Slukem 4461.170Schristos20080126: 4471.170Schristos The posix_fadvise system call has been changed from an assembly 4481.241Swiz stub, to a c file that calls an assembly stub. You need to 4491.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 4501.170Schristos avoid using the old assembly stub. 4511.170Schristos 4521.168Sjoerg20071209: 4531.241Swiz The acpiec(4) driver has been split into two attachments. If you 4541.168Sjoerg get ACPI errors before the attachment, please update your kernel 4551.169Swiz configuration file appropriately or see GENERIC for more details. 4561.168Sjoerg 4571.166Sxtraeme20071115: 4581.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 4591.166Sxtraeme argument specified in the kernel configuration file is not valid 4601.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 4611.241Swiz rather than the EC address port. Please update your kernel 4621.167Swiz configuration file appropriately or see GENERIC for more details. 4631.166Sxtraeme 4641.165Sjmmv20071028: 4651.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 4661.165Sjmmv You need to update any custom kernel configuration file you have 4671.165Sjmmv to remove any references to pccons (which includes removing the 4681.165Sjmmv now useless XSERVER option) and replace them with the correct 4691.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 4701.165Sjmmv for more details. 4711.165Sjmmv 4721.164Sgdt20070913: 4731.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 4741.164Sgdt enumerate interfaces was fixed. The bug began to cause 4751.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 4761.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 4771.164Sgdt could not enumerate interfaces. (These are noted because 4781.164Sgdt normal kernel/userspace version matching hygiene is not 4791.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 4801.164Sgdt and userland are from after 20070913. 4811.164Sgdt 4821.163Sjoerg20070703: 4831.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 4841.199Sdholland calls the target-specific strip program, and the logic to pass 4851.199Sdholland down STRIP from make has been removed. This requires a 4861.199Sdholland re-installation of tools. 4871.163Sjoerg 4881.161Sdsl20070422: 4891.161Sdsl The way OS emulations lookup filenames inside the emulation root 4901.161Sdsl has been changed. Rather than modify the pathname (and copy back 4911.161Sdsl to userspace) namei() and lookup() directly check the emulation 4921.241Swiz root. One side effect is that absolute symlinks inside the emulated 4931.167Swiz root file system will be relative to that file system - unless they 4941.161Sdsl start /../ this is useful when the emulated root is a real install 4951.161Sdsl that has such links. 4961.161Sdsl This might affect symlinks that have been added to reference outside 4971.161Sdsl the emulated root. 4981.161Sdsl 4991.160Sjmcneill20070412: 5001.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 5011.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 5021.160Sjmcneill example. 5031.160Sjmcneill 5041.159Sgdt20070319: 5051.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 5061.159Sgdt on many platforms due to incorrect flags settings. If you 5071.159Sgdt updated and built after about 20070315, do "nbmake-$arch 5081.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 5091.159Sgdt rebuild of object files that might have been built 5101.159Sgdt incorrectly, and ensure that you have at least 5111.159Sgdt src/lib/libc/Makefile 1.130. 5121.159Sgdt 5131.241Swiz20070210: 5141.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 5151.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 5161.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 5171.158Sdbj will allow dependencies on those files to get get rebuilt 5181.158Sdbj 5191.157Sapb20070209: 5201.157Sapb The threading model was changed when the newlock2 branch 5211.157Sapb was merged to NetBSD-current. If you boot with a new 5221.157Sapb kernel (version 4.99.10), then you also need a new pthread 5231.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 5241.157Sapb an old kernel, then you need the old pthread library 5251.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 5261.157Sapb the pthread library in sync, old threaded applications should 5271.157Sapb continue to work with an old or new kernel. Note that named(8) 5281.157Sapb is the only threaded application in the base system. 5291.157Sapb 5301.154She20061214: 5311.154She Following the move of string_to_flags() and flags_to_string() 5321.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 5331.154She will need to do a "make cleandir" in 5341.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 5351.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 5361.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 5371.156She as the installation images in distrib/ 5381.154She in order to excise stale references to the old stat_flags.h header 5391.154She file in the ls sources -- stat_flags.h has been removed. 5401.154She 5411.152Schristos20061108: 5421.152Schristos The configure script used in the src/tools/gcc compiler has been 5431.152Schristos changed to indicate that our libc has ssp support built-in and 5441.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 5451.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 5461.152Schristos 5471.151Srpaulo20061009: 5481.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 5491.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 5501.151Srpaulo 5511.150Sbjh2120060814: 5521.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 5531.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 5541.150Sbjh21 kernel configuration for an example. X servers from the last 5551.150Sbjh21 few years should cope. 5561.150Sbjh21 5571.149Schristos20060703: 5581.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 5591.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 5601.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 5611.149Schristos 5621.148Sdogcow20060627: 5631.148Sdogcow socket(2) has changed, and its system call has been versioned. 5641.148Sdogcow For userlands with the old version of socket(2), make sure that 5651.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 5661.148Sdogcow errors will result. 5671.148Sdogcow 5681.1SabsHints for a more successful build: 5691.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 5701.123Sjmc Use build.sh, but do not use its "expert mode": 5711.132Sjmmv This will automatically build the tools in the 5721.123Sjmc correct order, and it will keep the tools and the 5731.123Sjmc new build products from interfering with the running 5741.123Sjmc system. This will allow you to ignore most of the 5751.123Sjmc other advice in this file. 5761.2Smrg Build a new kernel first: 5771.2Smrg This makes sure that any new system calls or features 5781.2Smrg expected by the new userland will be present. This 5791.2Smrg helps to avoid critical errors when upgrading. 5801.1Sabs Use object directories: 5811.1Sabs This helps to keep stale object 5821.1Sabs files from polluting the build if a Makefile "forgets" 5831.1Sabs about one. It also makes it easier to clean up after 5841.1Sabs a build. It's also necessary if you want to use the 5851.1Sabs same source tree for multiple machines. 5861.123Sjmc To use object directories with build.sh: 5871.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 5881.123Sjmc To use object directories without using build.sh: 5891.1Sabs a) cd /usr/src ; make cleandir 5901.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 5911.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 5921.1Sabs d) cd /usr/src ; make build 5931.2Smrg Note that running "make obj" in a directory will create 5941.2Smrg in obj.$MACHINE directory. 5951.1Sabs Build to a DESTDIR: 5961.123Sjmc This helps to keep old installed files (especially libraries) 5971.123Sjmc from interfering with the new build. 5981.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 5991.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 6001.123Sjmc environment variable before running make build. It should be 6011.123Sjmc set to the pathname of an initially empty directory. 6021.123Sjmc Problems: if you do not use build.sh, you might need to 6031.123Sjmc update critical utilities without using DESTDIR since 6041.123Sjmc nothing is executed from what is installed in DESTDIR. 6051.123Sjmc (See critical utils, below.) 6061.1Sabs Build often: 6071.1Sabs This keeps critical utilities current enough to not choke 6081.1Sabs on any other part of the source tree that depends on up to 6091.123Sjmc date functionality. If you use build.sh, you should not have 6101.123Sjmc this problem. 6111.241Swiz 6121.1SabsWhat to do if things don't work: 6131.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6141.230StlsWhen things don't work there are usually a few things that commonly 6151.1Sabsshould be done. 6161.1Sabs 1) make includes 6171.1Sabs This should be done automatically by make build. 6181.1Sabs 2) cd share/mk && make install 6191.1Sabs Again, automatically done by make build. 6201.1Sabs 6211.1SabsFailsafe rebuild of a small part of the tree: 6221.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6231.1SabsTo make sure you rebuild something correctly you want to do 6241.1Sabssomething like the following: 6251.1Sabs 1) Make sure the includes and .mk files are up to date. 6261.1Sabs 2) Make sure any program used to build the particular 6271.1Sabs utility is up to date. (yacc, lex, etc...) 6281.1Sabs 3) cd ...path/to/util... 6291.1Sabs make cleandir 6301.1Sabs rm ...all obj directories... 6311.1Sabs make cleandir # yes, again 6321.1Sabs make obj 6331.1Sabs make depend && make 6341.1Sabs 6351.1SabsFailsafe rebuild of the entire tree: 6361.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6371.1SabsIf you really want to make sure the source tree is clean and 6381.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 6391.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 6401.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 6411.1Sabs 6421.1Sabs---cut here--- 6431.1Sabs#!/bin/sh 6441.1Sabs. /etc/mk.conf 6451.1Sabs 6461.58Slukemif [ -z $NETBSDSRCDIR ] ; then 6471.58Slukem NETBSDSRCDIR=/usr/src 6481.1Sabsfi 6491.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 6501.1Sabs echo Unable to find sources 6511.1Sabs exit 1 6521.1Sabsfi 6531.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 6541.1Sabs 6551.1Sabsif [ -z $BSDOBJDIR ] ; then 6561.1Sabs BSDOBJDIR=/usr/obj 6571.1Sabsfi 6581.1Sabsif [ -d $BSDOBJDIR ] ; then 6591.1Sabs rm -rf $BSDOBJDIR 6601.1Sabsfi 6611.1Sabs 6621.58Slukemcd $NETBSDSRCDIR && make cleandir 6631.1Sabs 6641.1Sabs---cut here--- 6651.1Sabs 6661.1SabsCritical utilities: 6671.1Sabs^^^^^^^^^^^^^^^^^^^ 6681.3Sitojun usr.bin/compile_et 6691.1Sabs usr.bin/make 6701.1Sabs usr.bin/yacc 6711.1Sabs usr.bin/lex 6721.11Slukem usr.bin/xlint 6731.142Sdrochner usr.bin/config 6741.1Sabs 6751.34SsimonbOther problems and possible solutions: 6761.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6771.1SabsSymptom:Complaints involving a Makefile. 6781.17SerhFix: Rebuild usr.bin/make: 6791.17Serh cd usr.bin/make && make && make install 6801.111Ssimonb Or, a failsafe method if that doesn't work: 6811.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 6821.17Serh 6831.1SabsFix: Make sure .mk files are up to date. 6841.1Sabs cd share/mk && make install 6851.2Smrg 6861.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 6871.142SdrochnerFix: Rebuild usr.bin/config 6881.1Sabs 6891.1SabsSymptom: 6901.1SabsFix: Rebuild usr.bin/yacc 6911.1Sabs 6921.1SabsSymptom: 6931.1SabsFix: Rebuild usr.bin/lex 6941.1Sabs 6951.1SabsSymptom: 6961.1SabsFix: rm /usr/lib/libbfd.a 6971.4Sitojun 6981.4SitojunSymptom:Obsolete intermediate files are used during compilation 6991.4SitojunFix: Try the following sequence of commands in the directory in question. 7001.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 7011.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 7021.4Sitojun may remain. The command tries to clean everything up) 7031.5Swiz 7041.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 7051.207Smbalmer pointer type 7061.5SwizFix: Rebuild and install usr.bin/menuc 7071.12Sitojun 7081.12SitojunSymptom:mklocale not found during build in share/locale/ctype 7091.12SitojunFix: Build and install usr.bin/mklocale 7101.13Sdogcow 7111.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 7121.13SdogcowFix: Rebuild and install lib/libc 7131.13Sdogcow 7141.142SdrochnerSymptom:usr.bin/config fails to build. 7151.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 7161.13Sdogcow 7171.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 7181.19ScgdFix: Rebuild and install lib/libc 7191.24Sabs 7201.24SabsSymptom:lint does not understand the '-X' option 7211.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 7221.223Sjoerg 7231.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 7241.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 7251.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 7261.257Sapb 7271.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 7281.257Sapb No such file or directory. 7291.257SapbCause: If a directory is created by mistake, then it is sometimes 7301.257Sapb deleted from the CVS repository using administrative commands 7311.257Sapb that bypass the normal cvs access controls. If your cvs working tree 7321.257Sapb contains references to a directory that has been deleted on the 7331.257Sapb server in this way, then "cvs update" reports this error. 7341.257SapbFix: Recursively delete the affected directory from your working tree 7351.257Sapb and try the update again. 736