UPDATING revision 1.277
11.277Smartin$NetBSD: UPDATING,v 1.277 2017/01/05 05:40:46 martin 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.277Smartin20170104: 231.277Smartin xinput build options have changed. 241.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 251.277Smartin if you build.sh -u 261.277Smartin 271.276Smartin20170103: 281.276Smartin a new version of flex has been imported. 291.276Smartin Remove the file from obj (external/bsd/flex) 301.276Smartin if you build.sh -u 311.276Smartin 321.275Sspz20161014: 331.275Sspz a new version of OpenSSL has been imported. 341.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 351.275Sspz if you build.sh -u 361.275Sspz 371.274Smartin20161009: 381.274Smartin a new version of dhcpcd has been imported with slightly changed 391.274Smartin build infrastructure. When doing a build.sh -u this requires 401.274Smartin pruning the external/bsd/dhcpcd objdir. 411.274Smartin 421.273Smrg20160914: 431.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 441.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 451.273Smrg and a clean objdir. 461.273Smrg 471.272Sdholland20160527: 481.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 491.272Sdholland been enabled. (see the amd64 entry two down for further info) 501.272Sdholland 511.270Schristos20160418: 521.270Schristos libedit needs manual removal of all autogenerated files since 531.271Schristos some of them are not autogenerated anymore. Remember that there 541.271Schristos might be two copies of libedit if your platform builds "compat". 551.270Schristos 561.268Sriastrad20160410: 571.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 581.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 591.268Sriastrad executables, means all code, including executables and not just 601.268Sriastrad shared libraries, is position-independent and hence able to be 611.268Sriastrad relocated by ASLR, address space layout randomization. 621.268Sriastrad 631.268Sriastrad The change was made in Makefile variables for compiler and 641.268Sriastrad linker flags, for which make(1) does not record dependencies, 651.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 661.268Sriastrad 671.268Sriastrad Partial rebuilds with some modified source files will likely 681.268Sriastrad fail when linking executables, since the linker refuses to mix 691.268Sriastrad position-independent code with position-dependent code in 701.268Sriastrad position-independent executables: 711.268Sriastrad 721.268Sriastrad .../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC 731.268Sriastrad 741.267Smrg20160401: 751.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 761.269Sdholland Some people have found that cleandir is not sufficient, so if 771.269Sdholland in doubt delete the entire object directory tree for gcc. 781.267Smrg 791.266Saymeric20160306: 801.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 811.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 821.265Saymeric non-NetBSD hosts if linked with stale object files produced 831.265Saymeric while they included a non-NetBSD regex.h. 841.265Saymeric In any case, you should "make cleandir" at least these tools 851.265Saymeric before updating your toolchain. 861.265Saymeric 871.264Smartin20160125: 881.264Smartin Dtrace has been enabled by default on some architectures. 891.264Smartin When doing an update build, make sure to clean the etc/mtree 901.264Smartin object directory before starting the build - otherwise the 911.264Smartin needed directories in destdir will not be created. 921.264Smartin An easy way to do this is: 931.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 941.264Smartin 951.263Sdholland20150818: 961.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 971.263Sdholland again. 981.263Sdholland 991.262Schristos20150413: 1001.262Schristos New acpica requires "make cleandir" and reinstalling yacc 1011.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 1021.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 1031.262Schristos 1041.261Smartin20150404: 1051.261Smartin Lint changes require a full rebuild of the tool, so make 1061.261Smartin sure to build without -u option to build.sh, or manually 1071.261Smartin do a make cleandir in src/tools/lint1 and 1081.261Smartin src/usr.bin/xlint. 1091.261Smartin 1101.260Sskrll20150310: 1111.260Sskrll Improvements to openssl for arm mean that update builds of 1121.260Sskrll the openssl libraries will fail. A make cleandir in 1131.260Sskrll external/bsd/openssl/lib is needed 1141.260Sskrll 1151.258Smartin20141026: 1161.259Smsaitoh A mishap during the import of pppd may cause your corruption 1171.258Smartin in your cvs directory if you happened to do a cvs update 1181.258Smartin during a short period of time. To fix, just remove the 1191.258Smartin directory src/external/bsd/ppp/dist/pppd completely 1201.258Smartin and let cvs restore it on next update. 1211.258Smartin 1221.256Sapb20140721: 1231.256Sapb The src/external/mit/lua/src directory was accidentally created 1241.256Sapb and then deleted in the CVS repository. If you get errors like 1251.256Sapb 1261.256Sapb cvs [update aborted]: cannot open directory 1271.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 1281.256Sapb 1291.256Sapb then delete your local copy of that directory tree and try again. 1301.256Sapb 1311.255Sjoerg20140530: 1321.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 1331.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 1341.255Sjoerg 1351.251Smartin20140131: 1361.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 1371.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 1381.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 1391.251Smartin 1401.250Schristos20131227: 1411.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 1421.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 1431.250Schristos mode7 in your config file. Make sure you put the necessary restrict 1441.250Schristos statements to avoid being exposed. 1451.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 1461.250Schristos to make clean in libc 1471.250Schristos 1481.249Smrg20131129: 1491.249Smrg The GMP sources were updated, and builds will likely fail without 1501.249Smrg cleaning their build trees for both tools and in-tree, like below. 1511.249Smrg 1521.248Smrg20131128: 1531.248Smrg The MPC and MPFR sources were updated, and builds may require their 1541.248Smrg tools and in-tree directories cleaned for successful updates. 1551.248Smrg 1561.246Smartin20130605: 1571.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 1581.247Sspz to IPSEC (and the older IPSEC version removed). 1591.247Sspz 1601.247Sspz20130605: 1611.246Smartin Previous freetype installations eroneously installed private 1621.246Smartin header files. If you are building against a non-empty $DESTDIR, 1631.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 1641.246Smartin 1651.245Smrg20130531: 1661.245Smrg The xdm update may cause build failure due to xdm.man being 1671.245Smrg in the obj tree. Make sure to ensure any like this: 1681.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 1691.245Smrg is fixed by deleting the xdm.man in the obj tree. 1701.245Smrg 1711.244Smrg20130530: 1721.244Smrg Updates of many xsrc packages will leave old .pc files around. 1731.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 1741.244Smrg 1751.242Schristos20130301: 1761.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 1771.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 1781.242Schristos 1791.238Sdholland20120726: 1801.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 1811.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 1821.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 1831.241Swiz some cases may succeed and install broken OpenSSL libraries that 1841.240Sdholland cause third-party software to link incorrectly and/or crash. 1851.238Sdholland 1861.237Swiz20120507: 1871.241Swiz The database schema for makemandb was changed. You will 1881.237Swiz need to update the database using 'makemandb -f' or wait 1891.237Swiz for the next weekly run to fix it. 1901.237Swiz 1911.236Sbsh20120319: 1921.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 1931.236Sbsh size of db_symtab automatically. You need to update dbsym in 1941.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 1951.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 1961.236Sbsh mk.conf. 1971.236Sbsh 1981.235Sjoerg20120216: 1991.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 2001.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 2011.239Sdholland and 20120216, daily and weekly could have created an unreadable 2021.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 2031.235Sjoerg the next run of weekly will fix it. 2041.233Sjoerg 2051.232Schristos20111227: 2061.232Schristos If you built between 20111225 and 20111227 you need to remove 2071.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 2081.232Schristos bump has been reverted. 2091.232Schristos 2101.231Stls20111125: 2111.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 2121.231Stls means it should no longer be explicitly listed in kernel 2131.231Stls configuration files. The line "pseudo-device rnd" should be 2141.231Stls removed from any custom kernel config files users may have. 2151.231Stls 2161.230Stls20111119: 2171.230Stls A problem with the datastructures used by the rndctl(8) 2181.230Stls utility (pointers in datastructures in an array, making 32->64 2191.230Stls bit compatibility very painful) has been fixed in a 2201.230Stls non-backwards-compatible way. If you replace your kernel, 2211.230Stls replace your rndctl executable too. 2221.241Swiz 2231.229Sjym20111001: 2241.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 2251.229Sjym changed and their new version is not backward compatible with the old 2261.241Swiz one. So ensure that all consumers of these functions (currently: 2271.229Sjym quota2 code and its tests) are updated together with the new lib. 2281.229Sjym 2291.228Smrg20110817: 2301.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 2311.228Smrg DESTDIR for them should be deleted before updating. 2321.228Smrg 2331.227Sriastrad20110806: 2341.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 2351.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 2361.227Sriastrad 2371.226Smrg20110805: 2381.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 2391.226Smrg the tree to be cleaned. Best to delete both objdir and 2401.226Smrg DESTDIR before running this update. So far, only the 2411.226Smrg sparc64, mips and powerpc platforms have changed. 2421.226Smrg 2431.225Smatt20110803: 2441.241Swiz The layout of external/public-domain/xz has changed. To do an 2451.225Smatt update build you will have to remove the contents of the OBJDIR 2461.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 2471.225Smatt is now a directory. 2481.225Smatt 2491.223Sjoerg20110410: 2501.241Swiz The configuration of src/tools/gcc has changed. To do an 2511.224Sdholland update build you have to clean both tools/binutils and 2521.224Sdholland tools/gcc by hand. 2531.223Sjoerg 2541.222Splunky20110328: 2551.222Splunky Building the Xorg binary was moved into a subdirectory to fix 2561.241Swiz ordering issues with "make all". It may be necessary to remove 2571.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 2581.222Splunky if your update build fails, as the "Xorg" entry there is now a 2591.222Splunky directory. 2601.222Splunky 2611.220Sjoerg20110121: 2621.221Slukem Assembler files no longer use -traditional-cpp. This can break 2631.220Sjoerg the build of individual parts of the tree. This is handled 2641.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 2651.220Sjoerg and re-run config(1) for any kernel configurations as needed. 2661.218Sjoerg 2671.217Sjruoho20101217: 2681.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 2691.241Swiz by default. It may be necessary to manually update passwd(5) and 2701.217Sjruoho group(5) in order to make the program work with existing setups. 2711.217Sjruoho 2721.216Schristos20101125: 2731.216Schristos The latest changes to setenv(3) dissallow setting environment 2741.241Swiz variables with names that contain '='. Revision 1.18 of env.c 2751.241Swiz assumed that this was allowed. Installing a new libc with an 2761.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 2771.216Schristos break which affects the autoconf tests for dependency finding, 2781.216Schristos so building gcc will end up printing: 2791.216Schristos checking dependency style of gcc... none 2801.216Schristos configure: error: no usable dependency style found 2811.216Schristos Fix it by rebuilding and re-installing env. 2821.138Slukem 2831.215Smrg20101119: 2841.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 2851.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 2861.215Smrg have any build problems with xsrc, or problems with mismatched 2871.215Smrg versions between xorg-server and drivers. 2881.215Smrg 2891.213Sjmmv20100604: 2901.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 2911.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 2921.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 2931.213Sjmmv trees by hand. 2941.213Sjmmv 2951.211Stnozaki20100522: 2961.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 2971.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 2981.212Smrg build problems with xsrc. 2991.212Smrg 3001.212Smrg20100522: 3011.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 3021.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 3031.211Stnozaki 3041.210Schristos20100520: 3051.241Swiz The location of the xkb compiled descriptions has changed. Please 3061.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 3071.210Schristos 3081.209Snjoly20100222: 3091.209Snjoly The shared objects file extension has been changed from .so to 3101.209Snjoly .pico, in order to avoid conflicts with shared libraries names 3111.209Snjoly libXX.so. All now stale regular .so files can be removed from 3121.209Snjoly your object directories. 3131.209Snjoly 3141.208Sroy20100204: 3151.208Sroy The termcap database has been removed from the sources, 3161.208Sroy but has not been marked obsolete so it is not removed 3171.208Sroy from the system when upgrading. 3181.208Sroy As such, you will need to remove them from your object 3191.208Sroy and destination directories. 3201.208Sroy 3211.203Sdyoung20091101: 3221.205Sdholland After updating, it may be necessary to make the 'cleandir' 3231.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 3241.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 3251.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 3261.203Sdyoung 3271.202Smrg20091001: 3281.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 3291.206Sdholland before building a kernel, or the build fails on cpufunc.S. 3301.206Sdholland 3311.206Sdholland20091001: 3321.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 3331.202Smrg symlink, failing the build. Delete the link, and the subdir 3341.202Smrg it is in, and retry your build. 3351.202Smrg 3361.201Sdsl20090718: 3371.201Sdsl libc build changed so that strchr() provides the extra entry 3381.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 3391.201Sdsl may fail because the archive contains the unwanted index.o. 3401.201Sdsl (Similarly for strrchr() and rindex().) 3411.201Sdsl 3421.198Smrg20090709: 3431.198Smrg Native Xorg was upgraded again. Builds will probably fail again 3441.198Smrg without a clean objdir, at least for src/external/mit/xorg. 3451.198Smrg 3461.197Smrg20090616: 3471.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 3481.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 3491.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 3501.197Smrg subdirectory has been changed into a file, and this needs to 3511.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 3521.197Smrg 3531.195Sperry20090501: 3541.195Sperry Several new functions were added to string.h/libc, and this 3551.195Sperry can cause autoconf problems during the tool build for people 3561.241Swiz who fail to clean out their tools objects properly. If you 3571.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 3581.195Sperry failure during the tool build, clean out all your tools 3591.195Sperry objects and start again. 3601.195Sperry 3611.194Smrg20090325: 3621.194Smrg The i386 port was switched to i486 default toolchain. This requires 3631.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 3641.194Smrg 3651.192Sskrll20090126: 3661.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 3671.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 3681.207Smbalmer to avoid using the old assembly stub. 3691.192Sskrll 3701.191Sjoerg20090202: 3711.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 3721.191Sjoerg detection. It is recommented to rebuild the cache with 3731.191Sjoerg ``pkg_admin rebuild''. 3741.191Sjoerg 3751.184Schristos20090110: 3761.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 3771.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 3781.188Schristos This is needed even in the MODULAR kernel because there is 3791.188Schristos conditionally compiled code in rtsock.c. 3801.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 3811.184Schristos before installing. 3821.184Schristos 3. If you don't use build.sh and you build directly to root, and 3831.241Swiz your build breaks in the middle, don't despair. Make sure headers 3841.184Schristos are installed properly, and start building libraries first libc 3851.184Schristos and libutil, install them and then continue building all the 3861.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 3871.184Schristos the new libraries are installed, you can restart the build. 3881.184Schristos 4. If you compile packages and you notice link time warnings, 3891.189Shubertf rebuild the required packages to update their shared libraries. 3901.189Shubertf Any package you rebuild will require rebuilding all the packages 3911.189Shubertf that depend on it. 3921.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 3931.186Schristos will be upgraded and it will not be backwards compatible. 3941.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 3951.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 3961.241Swiz for utmp. You are better off removing the old files after 3971.190Sapb upgrading. The automated clearing of /var/run during 3981.190Sapb boot, and the automated rotating of files in /var/log by 3991.190Sapb newsyslog(8), may mean that you do not have to remove the 4001.190Sapb files manually. 4011.190Sapb 7. The optional accounting file (/var/account/acct, see 4021.190Sapb accton(8)) has not been versioned, and will need to be 4031.190Sapb removed. The automatic rotation of the accounting file by 4041.190Sapb /etc/daily limits the bad consequences of failure to remove 4051.190Sapb the file. 4061.196Sdholland 8. Application software that writes time_t to binary files on 4071.241Swiz disk will break or need attention. Most notably: if you are 4081.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 4091.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 4101.185Sjmcneill 4111.183Spgoyette20081219: 4121.183Spgoyette config(1) has been updated, and one of the files it creates - 4131.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 4141.183Spgoyette (done automatically by build.sh) and then you need to rerun 4151.183Spgoyette config on all kernel configuration files before rebuilding those 4161.183Spgoyette kernels. 4171.183Spgoyette 4181.181Scube20081205: 4191.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 4201.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 4211.181Scube set and will appear as extra files for MKX11=no update builds. 4221.178Slukem 4231.179Stsutsui20081122: 4241.182Stsutsui On i386, various kernel options(4) in GENERIC including 4251.180Swiz file systems have been disabled and moved into kernel modules. 4261.180Swiz Before trying a new GENERIC kernel, you have to prepare the 4271.179Stsutsui following files as well as a new GENERIC kernel: 4281.179Stsutsui 4291.179Stsutsui - build and install kernel modules from src/sys/modules 4301.179Stsutsui 4311.179Stsutsui - install the latest bootloader, which will load a module 4321.180Swiz for the file system from which the kernel is loaded automatically 4331.179Stsutsui 4341.180Swiz If you have to load your kernel from a file system which is not of 4351.180Swiz the same type as the root file system, you have to load the necessary 4361.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 4371.179Stsutsui 4381.178Slukem20080827: 4391.178Slukem If you built and installed a libc from sources between 4401.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 4411.178Slukem which results in false errors reported by lint(1). 4421.178Slukem Since this breaks the libc build itself, manual help is 4431.180Swiz needed -- lint must be disabled temporarily, e.g.: 4441.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 4451.178Slukem 4461.177Schristos20080813: 4471.177Schristos MKDEBUG build was broken because the .depend files did not know 4481.241Swiz about .go files. You need to remove all .depend files and rebuild. 4491.177Schristos 4501.200Sdholland20080802: 4511.200Sdholland A regression in binary compatibility for pthread_mutex_t has 4521.241Swiz been fixed. Unfortunately, the price is breaking compatibility 4531.200Sdholland for -current. 4541.200Sdholland 4551.200Sdholland Threaded programs (using libpthread) and C++ programs (using 4561.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 4571.200Sdholland be recompiled. 4581.200Sdholland 4591.200Sdholland One way to find affected pkgsrc packages: 4601.200Sdholland 4611.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 4621.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 4631.200Sdholland 4641.175Ssimonb20080731: 4651.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 4661.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 4671.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 4681.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 4691.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 4701.176Ssimonb also requires the super block to be in the UFS2 format. You 4711.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 4721.175Ssimonb 4731.174Slukem20080721: 4741.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 4751.174Slukem isn't defined. 4761.174Slukem 4771.173Sfreza20080531: 4781.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 4791.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 4801.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 4811.241Swiz won't work correctly. The following sequence of commands: 4821.173Sfreza 4831.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 4841.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 4851.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 4861.173Sfreza 4871.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 4881.173Sfreza 4891.172Slukem20080503: 4901.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 4911.172Slukem 4921.171She20080521: 4931.171She For a while, unprivileged UPDATE builds would fail to 4941.171She succeed at the checkflist stage, complaining that 4951.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 4961.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 4971.171She If you already hit this problem, update the .mk file, 4981.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 4991.171She 5001.174Slukem20080303: 5011.174Slukem Linker warnings are now fatal if $WARNS>0. 5021.174Slukem 5031.170Schristos20080126: 5041.170Schristos The posix_fadvise system call has been changed from an assembly 5051.241Swiz stub, to a c file that calls an assembly stub. You need to 5061.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 5071.170Schristos avoid using the old assembly stub. 5081.170Schristos 5091.168Sjoerg20071209: 5101.241Swiz The acpiec(4) driver has been split into two attachments. If you 5111.168Sjoerg get ACPI errors before the attachment, please update your kernel 5121.169Swiz configuration file appropriately or see GENERIC for more details. 5131.168Sjoerg 5141.166Sxtraeme20071115: 5151.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 5161.166Sxtraeme argument specified in the kernel configuration file is not valid 5171.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 5181.241Swiz rather than the EC address port. Please update your kernel 5191.167Swiz configuration file appropriately or see GENERIC for more details. 5201.166Sxtraeme 5211.165Sjmmv20071028: 5221.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 5231.165Sjmmv You need to update any custom kernel configuration file you have 5241.165Sjmmv to remove any references to pccons (which includes removing the 5251.165Sjmmv now useless XSERVER option) and replace them with the correct 5261.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 5271.165Sjmmv for more details. 5281.165Sjmmv 5291.164Sgdt20070913: 5301.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 5311.164Sgdt enumerate interfaces was fixed. The bug began to cause 5321.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 5331.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 5341.164Sgdt could not enumerate interfaces. (These are noted because 5351.164Sgdt normal kernel/userspace version matching hygiene is not 5361.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 5371.164Sgdt and userland are from after 20070913. 5381.164Sgdt 5391.163Sjoerg20070703: 5401.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 5411.199Sdholland calls the target-specific strip program, and the logic to pass 5421.199Sdholland down STRIP from make has been removed. This requires a 5431.199Sdholland re-installation of tools. 5441.163Sjoerg 5451.161Sdsl20070422: 5461.161Sdsl The way OS emulations lookup filenames inside the emulation root 5471.161Sdsl has been changed. Rather than modify the pathname (and copy back 5481.161Sdsl to userspace) namei() and lookup() directly check the emulation 5491.241Swiz root. One side effect is that absolute symlinks inside the emulated 5501.167Swiz root file system will be relative to that file system - unless they 5511.161Sdsl start /../ this is useful when the emulated root is a real install 5521.161Sdsl that has such links. 5531.161Sdsl This might affect symlinks that have been added to reference outside 5541.161Sdsl the emulated root. 5551.161Sdsl 5561.160Sjmcneill20070412: 5571.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 5581.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 5591.160Sjmcneill example. 5601.160Sjmcneill 5611.159Sgdt20070319: 5621.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 5631.159Sgdt on many platforms due to incorrect flags settings. If you 5641.159Sgdt updated and built after about 20070315, do "nbmake-$arch 5651.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 5661.159Sgdt rebuild of object files that might have been built 5671.159Sgdt incorrectly, and ensure that you have at least 5681.159Sgdt src/lib/libc/Makefile 1.130. 5691.159Sgdt 5701.241Swiz20070210: 5711.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 5721.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 5731.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 5741.158Sdbj will allow dependencies on those files to get get rebuilt 5751.158Sdbj 5761.157Sapb20070209: 5771.157Sapb The threading model was changed when the newlock2 branch 5781.157Sapb was merged to NetBSD-current. If you boot with a new 5791.157Sapb kernel (version 4.99.10), then you also need a new pthread 5801.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 5811.157Sapb an old kernel, then you need the old pthread library 5821.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 5831.157Sapb the pthread library in sync, old threaded applications should 5841.157Sapb continue to work with an old or new kernel. Note that named(8) 5851.157Sapb is the only threaded application in the base system. 5861.157Sapb 5871.154She20061214: 5881.154She Following the move of string_to_flags() and flags_to_string() 5891.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 5901.154She will need to do a "make cleandir" in 5911.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 5921.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 5931.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 5941.156She as the installation images in distrib/ 5951.154She in order to excise stale references to the old stat_flags.h header 5961.154She file in the ls sources -- stat_flags.h has been removed. 5971.154She 5981.152Schristos20061108: 5991.152Schristos The configure script used in the src/tools/gcc compiler has been 6001.152Schristos changed to indicate that our libc has ssp support built-in and 6011.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 6021.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 6031.152Schristos 6041.151Srpaulo20061009: 6051.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 6061.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 6071.151Srpaulo 6081.150Sbjh2120060814: 6091.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 6101.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 6111.150Sbjh21 kernel configuration for an example. X servers from the last 6121.150Sbjh21 few years should cope. 6131.150Sbjh21 6141.149Schristos20060703: 6151.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 6161.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 6171.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 6181.149Schristos 6191.148Sdogcow20060627: 6201.148Sdogcow socket(2) has changed, and its system call has been versioned. 6211.148Sdogcow For userlands with the old version of socket(2), make sure that 6221.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 6231.148Sdogcow errors will result. 6241.148Sdogcow 6251.1SabsHints for a more successful build: 6261.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6271.123Sjmc Use build.sh, but do not use its "expert mode": 6281.132Sjmmv This will automatically build the tools in the 6291.123Sjmc correct order, and it will keep the tools and the 6301.123Sjmc new build products from interfering with the running 6311.123Sjmc system. This will allow you to ignore most of the 6321.123Sjmc other advice in this file. 6331.2Smrg Build a new kernel first: 6341.2Smrg This makes sure that any new system calls or features 6351.2Smrg expected by the new userland will be present. This 6361.2Smrg helps to avoid critical errors when upgrading. 6371.1Sabs Use object directories: 6381.1Sabs This helps to keep stale object 6391.1Sabs files from polluting the build if a Makefile "forgets" 6401.1Sabs about one. It also makes it easier to clean up after 6411.1Sabs a build. It's also necessary if you want to use the 6421.1Sabs same source tree for multiple machines. 6431.123Sjmc To use object directories with build.sh: 6441.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 6451.123Sjmc To use object directories without using build.sh: 6461.1Sabs a) cd /usr/src ; make cleandir 6471.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 6481.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 6491.1Sabs d) cd /usr/src ; make build 6501.2Smrg Note that running "make obj" in a directory will create 6511.2Smrg in obj.$MACHINE directory. 6521.1Sabs Build to a DESTDIR: 6531.123Sjmc This helps to keep old installed files (especially libraries) 6541.123Sjmc from interfering with the new build. 6551.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 6561.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 6571.123Sjmc environment variable before running make build. It should be 6581.123Sjmc set to the pathname of an initially empty directory. 6591.123Sjmc Problems: if you do not use build.sh, you might need to 6601.123Sjmc update critical utilities without using DESTDIR since 6611.123Sjmc nothing is executed from what is installed in DESTDIR. 6621.123Sjmc (See critical utils, below.) 6631.1Sabs Build often: 6641.1Sabs This keeps critical utilities current enough to not choke 6651.1Sabs on any other part of the source tree that depends on up to 6661.123Sjmc date functionality. If you use build.sh, you should not have 6671.123Sjmc this problem. 6681.241Swiz 6691.1SabsWhat to do if things don't work: 6701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6711.230StlsWhen things don't work there are usually a few things that commonly 6721.1Sabsshould be done. 6731.1Sabs 1) make includes 6741.1Sabs This should be done automatically by make build. 6751.1Sabs 2) cd share/mk && make install 6761.1Sabs Again, automatically done by make build. 6771.1Sabs 6781.1SabsFailsafe rebuild of a small part of the tree: 6791.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6801.1SabsTo make sure you rebuild something correctly you want to do 6811.1Sabssomething like the following: 6821.1Sabs 1) Make sure the includes and .mk files are up to date. 6831.1Sabs 2) Make sure any program used to build the particular 6841.1Sabs utility is up to date. (yacc, lex, etc...) 6851.1Sabs 3) cd ...path/to/util... 6861.1Sabs make cleandir 6871.1Sabs rm ...all obj directories... 6881.1Sabs make cleandir # yes, again 6891.1Sabs make obj 6901.1Sabs make depend && make 6911.1Sabs 6921.1SabsFailsafe rebuild of the entire tree: 6931.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6941.1SabsIf you really want to make sure the source tree is clean and 6951.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 6961.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 6971.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 6981.1Sabs 6991.1Sabs---cut here--- 7001.1Sabs#!/bin/sh 7011.1Sabs. /etc/mk.conf 7021.1Sabs 7031.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7041.58Slukem NETBSDSRCDIR=/usr/src 7051.1Sabsfi 7061.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7071.1Sabs echo Unable to find sources 7081.1Sabs exit 1 7091.1Sabsfi 7101.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 7111.1Sabs 7121.1Sabsif [ -z $BSDOBJDIR ] ; then 7131.1Sabs BSDOBJDIR=/usr/obj 7141.1Sabsfi 7151.1Sabsif [ -d $BSDOBJDIR ] ; then 7161.1Sabs rm -rf $BSDOBJDIR 7171.1Sabsfi 7181.1Sabs 7191.58Slukemcd $NETBSDSRCDIR && make cleandir 7201.1Sabs 7211.1Sabs---cut here--- 7221.1Sabs 7231.1SabsCritical utilities: 7241.1Sabs^^^^^^^^^^^^^^^^^^^ 7251.3Sitojun usr.bin/compile_et 7261.1Sabs usr.bin/make 7271.1Sabs usr.bin/yacc 7281.1Sabs usr.bin/lex 7291.11Slukem usr.bin/xlint 7301.142Sdrochner usr.bin/config 7311.1Sabs 7321.34SsimonbOther problems and possible solutions: 7331.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7341.1SabsSymptom:Complaints involving a Makefile. 7351.17SerhFix: Rebuild usr.bin/make: 7361.17Serh cd usr.bin/make && make && make install 7371.111Ssimonb Or, a failsafe method if that doesn't work: 7381.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 7391.17Serh 7401.1SabsFix: Make sure .mk files are up to date. 7411.1Sabs cd share/mk && make install 7421.2Smrg 7431.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 7441.142SdrochnerFix: Rebuild usr.bin/config 7451.1Sabs 7461.1SabsSymptom: 7471.1SabsFix: Rebuild usr.bin/yacc 7481.1Sabs 7491.1SabsSymptom: 7501.1SabsFix: Rebuild usr.bin/lex 7511.1Sabs 7521.1SabsSymptom: 7531.1SabsFix: rm /usr/lib/libbfd.a 7541.4Sitojun 7551.4SitojunSymptom:Obsolete intermediate files are used during compilation 7561.4SitojunFix: Try the following sequence of commands in the directory in question. 7571.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 7581.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 7591.4Sitojun may remain. The command tries to clean everything up) 7601.5Swiz 7611.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 7621.207Smbalmer pointer type 7631.5SwizFix: Rebuild and install usr.bin/menuc 7641.12Sitojun 7651.12SitojunSymptom:mklocale not found during build in share/locale/ctype 7661.12SitojunFix: Build and install usr.bin/mklocale 7671.13Sdogcow 7681.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 7691.13SdogcowFix: Rebuild and install lib/libc 7701.13Sdogcow 7711.142SdrochnerSymptom:usr.bin/config fails to build. 7721.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 7731.13Sdogcow 7741.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 7751.19ScgdFix: Rebuild and install lib/libc 7761.24Sabs 7771.24SabsSymptom:lint does not understand the '-X' option 7781.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 7791.223Sjoerg 7801.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 7811.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 7821.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 7831.257Sapb 7841.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 7851.257Sapb No such file or directory. 7861.257SapbCause: If a directory is created by mistake, then it is sometimes 7871.257Sapb deleted from the CVS repository using administrative commands 7881.257Sapb that bypass the normal cvs access controls. If your cvs working tree 7891.257Sapb contains references to a directory that has been deleted on the 7901.257Sapb server in this way, then "cvs update" reports this error. 7911.257SapbFix: Recursively delete the affected directory from your working tree 7921.257Sapb and try the update again. 793