UPDATING revision 1.289
11.289Schristos$NetBSD: UPDATING,v 1.289 2017/12/26 20:04:03 christos 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.288Smartin20171225: 231.288Smartin removal of the vadvise syscall requires manual removal of all 241.288Smartin associated files from the libc build object directory (including 251.289Schristos the .depend files) - a command like: 261.288Smartin cd $OBJ && find . -type d -name libc | xargs rm -rf 271.289Schristos For architectures that support multiple "compat" binary targets, 281.289Schristos you'll need to cleanup both the regular libc directory and the 291.289Schristos compat one. 301.288Smartin 311.287Skre20171010: 321.287Skre a change to the build structure of external/bsd/acpica/bin/iasl 331.287Skre means that its objdir (or *.d and .depend at least) might need 341.287Skre to be manually removed - or a build done once without -u. 351.287Skre 361.286Smrg20170822: 371.286Smrg a new version of GMP has been imported and probably 381.286Smrg will break parts of builds related to themselves or GCC, both 391.286Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 401.286Smrg and MPC objdirs or build once without -u. 411.286Smrg 421.285Smrg20170816: 431.285Smrg a new version of MPFR and MPC have been imported and probably 441.285Smrg will break parts of builds related to themselves or GCC, both 451.285Smrg in the tools and the native section. Remove all GCC, GMP, MPFR 461.285Smrg and MPC objdirs or build once without -u. 471.285Smrg 481.284Smartin20170402: 491.284Smartin a new version of dhcpcd has been imported, which does not support 501.284Smartin update builds from the previous version. Remove your 511.284Smartin external/bsd/dhcpcd object dir or build once without -u. 521.284Smartin 531.281Sroy20170211: 541.281Sroy a new terminfo database has been imported. 551.281Sroy The structure of it has changed slightly from prior versions and 561.281Sroy an updated tic tool is required. 571.281Sroy If you build.sh, don't use -u 581.281Sroy 591.280Skre20170207: 601.278Skre various arch dependent libc/exect.S files were removed 611.279Skre Either remove the obj directories (lib/libc and compat/amd64/i386/lib 621.279Skre if it exists) or do a clean build. 631.279Skre (This is a bug in the make system, it should be corrected without 641.279Skre human intervention, but isn't.) 651.278Skre 661.277Smartin20170104: 671.277Smartin xinput build options have changed. 681.277Smartin Remove the obj directory (external/mit/xorg/bin/xinput) 691.277Smartin if you build.sh -u 701.277Smartin 711.276Smartin20170103: 721.276Smartin a new version of flex has been imported. 731.276Smartin Remove the file from obj (external/bsd/flex) 741.276Smartin if you build.sh -u 751.276Smartin 761.275Sspz20161014: 771.275Sspz a new version of OpenSSL has been imported. 781.275Sspz Remove the files from obj (crypto/external/bsd/openssl) 791.275Sspz if you build.sh -u 801.275Sspz 811.274Smartin20161009: 821.274Smartin a new version of dhcpcd has been imported with slightly changed 831.274Smartin build infrastructure. When doing a build.sh -u this requires 841.274Smartin pruning the external/bsd/dhcpcd objdir. 851.274Smartin 861.273Smrg20160914: 871.273Smrg i386, amd64, shark, ofppc and macppc have joined shark and x68k 881.273Smrg ports in using xorg-server 1.18. This requires a clean destdir 891.273Smrg and a clean objdir. 901.273Smrg 911.272Sdholland20160527: 921.272Sdholland i386 needs a full cleandir or objdir deletion because PIE has 931.272Sdholland been enabled. (see the amd64 entry two down for further info) 941.272Sdholland 951.270Schristos20160418: 961.270Schristos libedit needs manual removal of all autogenerated files since 971.271Schristos some of them are not autogenerated anymore. Remember that there 981.271Schristos might be two copies of libedit if your platform builds "compat". 991.270Schristos 1001.268Sriastrad20160410: 1011.268Sriastrad amd64 needs full "make cleandir" or deletion of objdir now that 1021.268Sriastrad PIE has been enabled for amd64. PIE, or position-independent 1031.268Sriastrad executables, means all code, including executables and not just 1041.268Sriastrad shared libraries, is position-independent and hence able to be 1051.268Sriastrad relocated by ASLR, address space layout randomization. 1061.268Sriastrad 1071.268Sriastrad The change was made in Makefile variables for compiler and 1081.268Sriastrad linker flags, for which make(1) does not record dependencies, 1091.268Sriastrad hence it is unable to detect that all .o files need rebuilding. 1101.268Sriastrad 1111.268Sriastrad Partial rebuilds with some modified source files will likely 1121.268Sriastrad fail when linking executables, since the linker refuses to mix 1131.268Sriastrad position-independent code with position-dependent code in 1141.268Sriastrad position-independent executables: 1151.268Sriastrad 1161.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 1171.268Sriastrad 1181.267Smrg20160401: 1191.267Smrg Ports switching to GCC 5.3 will need a full "make cleandir". 1201.269Sdholland Some people have found that cleandir is not sufficient, so if 1211.269Sdholland in doubt delete the entire object directory tree for gcc. 1221.267Smrg 1231.266Saymeric20160306: 1241.265Saymeric NetBSD's regexp implementation is now part of libnbcompat. 1251.265Saymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on 1261.265Saymeric non-NetBSD hosts if linked with stale object files produced 1271.265Saymeric while they included a non-NetBSD regex.h. 1281.265Saymeric In any case, you should "make cleandir" at least these tools 1291.265Saymeric before updating your toolchain. 1301.265Saymeric 1311.264Smartin20160125: 1321.264Smartin Dtrace has been enabled by default on some architectures. 1331.264Smartin When doing an update build, make sure to clean the etc/mtree 1341.264Smartin object directory before starting the build - otherwise the 1351.264Smartin needed directories in destdir will not be created. 1361.264Smartin An easy way to do this is: 1371.264Smartin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir 1381.264Smartin 1391.263Sdholland20150818: 1401.263Sdholland New acpica requires "make cleandir" in src/external/bsd/acpica 1411.263Sdholland again. 1421.263Sdholland 1431.262Schristos20150413: 1441.262Schristos New acpica requires "make cleandir" and reinstalling yacc 1451.262Schristos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and 1461.262Schristos also "make cleandir" in /usr/src/external/bsd/acpica. 1471.262Schristos 1481.261Smartin20150404: 1491.261Smartin Lint changes require a full rebuild of the tool, so make 1501.261Smartin sure to build without -u option to build.sh, or manually 1511.261Smartin do a make cleandir in src/tools/lint1 and 1521.261Smartin src/usr.bin/xlint. 1531.261Smartin 1541.260Sskrll20150310: 1551.260Sskrll Improvements to openssl for arm mean that update builds of 1561.260Sskrll the openssl libraries will fail. A make cleandir in 1571.260Sskrll external/bsd/openssl/lib is needed 1581.260Sskrll 1591.258Smartin20141026: 1601.259Smsaitoh A mishap during the import of pppd may cause your corruption 1611.258Smartin in your cvs directory if you happened to do a cvs update 1621.258Smartin during a short period of time. To fix, just remove the 1631.258Smartin directory src/external/bsd/ppp/dist/pppd completely 1641.258Smartin and let cvs restore it on next update. 1651.258Smartin 1661.256Sapb20140721: 1671.256Sapb The src/external/mit/lua/src directory was accidentally created 1681.256Sapb and then deleted in the CVS repository. If you get errors like 1691.256Sapb 1701.256Sapb cvs [update aborted]: cannot open directory 1711.256Sapb /cvsroot/src/external/mit/lua/src: No such file or directory 1721.256Sapb 1731.256Sapb then delete your local copy of that directory tree and try again. 1741.256Sapb 1751.255Sjoerg20140530: 1761.255Sjoerg ARM eABI switched to DWARF based exception handling. This requires 1771.255Sjoerg rebuilding all C++ code. It is strongly advised to do a clean build. 1781.255Sjoerg 1791.251Smartin20140131: 1801.253Sjoerg The new compiler_rt/libc integration moved a few things. It is strongly 1811.254Sskrll advised to do a clean build. At least lib/libc, the compat version(s) 1821.253Sjoerg of libc, libkern, rump and the kernels need to be cleaned. 1831.251Smartin 1841.250Schristos20131227: 1851.250Schristos 1. The new ntpd runs in a restricted mode to prevent amplification 1861.250Schristos attacks. If you need ntpdc to work you need to explicitly enable 1871.250Schristos mode7 in your config file. Make sure you put the necessary restrict 1881.250Schristos statements to avoid being exposed. 1891.250Schristos 2. strncat has moved from lib/libc to common/lib/libc; you might need 1901.250Schristos to make clean in libc 1911.250Schristos 1921.249Smrg20131129: 1931.249Smrg The GMP sources were updated, and builds will likely fail without 1941.249Smrg cleaning their build trees for both tools and in-tree, like below. 1951.249Smrg 1961.248Smrg20131128: 1971.248Smrg The MPC and MPFR sources were updated, and builds may require their 1981.248Smrg tools and in-tree directories cleaned for successful updates. 1991.248Smrg 2001.246Smartin20130605: 2011.247Sspz The kernel option FAST_IPSEC no longer exists, it's been renamed 2021.247Sspz to IPSEC (and the older IPSEC version removed). 2031.247Sspz 2041.247Sspz20130605: 2051.246Smartin Previous freetype installations eroneously installed private 2061.246Smartin header files. If you are building against a non-empty $DESTDIR, 2071.246Smartin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/. 2081.246Smartin 2091.245Smrg20130531: 2101.245Smrg The xdm update may cause build failure due to xdm.man being 2111.245Smrg in the obj tree. Make sure to ensure any like this: 2121.245Smrg nbmake: nbmake: don't know how to make xdm.man. Stop 2131.245Smrg is fixed by deleting the xdm.man in the obj tree. 2141.245Smrg 2151.244Smrg20130530: 2161.244Smrg Updates of many xsrc packages will leave old .pc files around. 2171.244Smrg Best to clean out the xsrc objdir entirely before rebuilds. 2181.244Smrg 2191.242Schristos20130301: 2201.242Schristos The removal of netiso requires manual removal of /usr/include/netiso 2211.243Schristos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump} 2221.242Schristos 2231.238Sdholland20120726: 2241.241Swiz The update of OpenSSL requires cleaning both the OpenSSL build 2251.241Swiz directory and DESTDIR. *Even non-update builds require cleaning 2261.240Sdholland DESTDIR.* Builds done without taking these steps may fail, or in 2271.241Swiz some cases may succeed and install broken OpenSSL libraries that 2281.240Sdholland cause third-party software to link incorrectly and/or crash. 2291.238Sdholland 2301.237Swiz20120507: 2311.241Swiz The database schema for makemandb was changed. You will 2321.237Swiz need to update the database using 'makemandb -f' or wait 2331.237Swiz for the next weekly run to fix it. 2341.237Swiz 2351.236Sbsh20120319: 2361.236Sbsh sys/conf/Makefile.kern.inc has been modified to adjust the 2371.236Sbsh size of db_symtab automatically. You need to update dbsym in 2381.236Sbsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If 2391.236Sbsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your 2401.236Sbsh mk.conf. 2411.236Sbsh 2421.235Sjoerg20120216: 2431.241Swiz Default for MKCATPAGES changed to NO. Update builds will fail 2441.241Swiz unless DESTDIR is cleaned manually. If you built between 20120207 2451.239Sdholland and 20120216, daily and weekly could have created an unreadable 2461.241Swiz /var/db/man.db index for apropos. Running makemandb -f or 2471.235Sjoerg the next run of weekly will fix it. 2481.233Sjoerg 2491.232Schristos20111227: 2501.232Schristos If you built between 20111225 and 20111227 you need to remove 2511.232Schristos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the 2521.232Schristos bump has been reverted. 2531.232Schristos 2541.231Stls20111125: 2551.231Stls The "rnd" pseudodevice has been added to sys/conf/std, which 2561.231Stls means it should no longer be explicitly listed in kernel 2571.231Stls configuration files. The line "pseudo-device rnd" should be 2581.231Stls removed from any custom kernel config files users may have. 2591.231Stls 2601.230Stls20111119: 2611.230Stls A problem with the datastructures used by the rndctl(8) 2621.230Stls utility (pointers in datastructures in an array, making 32->64 2631.230Stls bit compatibility very painful) has been fixed in a 2641.230Stls non-backwards-compatible way. If you replace your kernel, 2651.230Stls replace your rndctl executable too. 2661.241Swiz 2671.229Sjym20111001: 2681.229Sjym the prop_*_send_syscall() functions from proplib(3) have been 2691.229Sjym changed and their new version is not backward compatible with the old 2701.241Swiz one. So ensure that all consumers of these functions (currently: 2711.229Sjym quota2 code and its tests) are updated together with the new lib. 2721.229Sjym 2731.228Smrg20110817: 2741.228Smrg sparc has been changed to use GCC 4.5.3, so any objdir or 2751.228Smrg DESTDIR for them should be deleted before updating. 2761.228Smrg 2771.227Sriastrad20110806: 2781.227Sriastrad i386 and amd64 have been changed to use GCC 4.5.3, so any 2791.227Sriastrad objdir or DESTDIR for them should be deleted before updating. 2801.227Sriastrad 2811.226Smrg20110805: 2821.226Smrg The update to GCC 4.5.3 requires a non-trivial portion of 2831.226Smrg the tree to be cleaned. Best to delete both objdir and 2841.226Smrg DESTDIR before running this update. So far, only the 2851.226Smrg sparc64, mips and powerpc platforms have changed. 2861.226Smrg 2871.225Smatt20110803: 2881.241Swiz The layout of external/public-domain/xz has changed. To do an 2891.225Smatt update build you will have to remove the contents of the OBJDIR 2901.225Smatt for external/public-domain/xz/bin by hand as the xz entry there 2911.225Smatt is now a directory. 2921.225Smatt 2931.223Sjoerg20110410: 2941.241Swiz The configuration of src/tools/gcc has changed. To do an 2951.224Sdholland update build you have to clean both tools/binutils and 2961.224Sdholland tools/gcc by hand. 2971.223Sjoerg 2981.222Splunky20110328: 2991.222Splunky Building the Xorg binary was moved into a subdirectory to fix 3001.241Swiz ordering issues with "make all". It may be necessary to remove 3011.222Splunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86 3021.222Splunky if your update build fails, as the "Xorg" entry there is now a 3031.222Splunky directory. 3041.222Splunky 3051.220Sjoerg20110121: 3061.221Slukem Assembler files no longer use -traditional-cpp. This can break 3071.220Sjoerg the build of individual parts of the tree. This is handled 3081.220Sjoerg correctly by build.sh. Manual builds have to update /usr/share/mk 3091.220Sjoerg and re-run config(1) for any kernel configurations as needed. 3101.218Sjoerg 3111.217Sjruoho20101217: 3121.217Sjruoho The tcpdump(8) program was changed to drop privileges and chroot(2) 3131.241Swiz by default. It may be necessary to manually update passwd(5) and 3141.217Sjruoho group(5) in order to make the program work with existing setups. 3151.217Sjruoho 3161.216Schristos20101125: 3171.216Schristos The latest changes to setenv(3) dissallow setting environment 3181.241Swiz variables with names that contain '='. Revision 1.18 of env.c 3191.241Swiz assumed that this was allowed. Installing a new libc with an 3201.216Schristos old copy of /usr/bin/env causes env x=1 printenv | grep x= to 3211.216Schristos break which affects the autoconf tests for dependency finding, 3221.216Schristos so building gcc will end up printing: 3231.216Schristos checking dependency style of gcc... none 3241.216Schristos configure: error: no usable dependency style found 3251.216Schristos Fix it by rebuilding and re-installing env. 3261.138Slukem 3271.215Smrg20101119: 3281.215Smrg Recent Xorg updates in xsrc/external/mit/ may cause various build 3291.215Smrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you 3301.215Smrg have any build problems with xsrc, or problems with mismatched 3311.215Smrg versions between xorg-server and drivers. 3321.215Smrg 3331.213Sjmmv20100604: 3341.213Sjmmv The update of ATF to 0.9 causes old tests written in shell to fail 3351.213Sjmmv unless they are rebuilt. If you are building with MKUPDATE=yes, 3361.213Sjmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/ 3371.213Sjmmv trees by hand. 3381.213Sjmmv 3391.211Stnozaki20100522: 3401.212Smrg Recent Xorg updates in xsrc/external/mit/ will cause various build 3411.212Smrg problems. Delete your entire DESTDIR and OBJDIR if you have any 3421.212Smrg build problems with xsrc. 3431.212Smrg 3441.212Smrg20100522: 3451.211Stnozaki private section of <ctype.h> was splitted, and now mklocale(1) 3461.214Sdholland include ctype_local.h, so you have to make cleandir in tools/mklocale. 3471.211Stnozaki 3481.210Schristos20100520: 3491.241Swiz The location of the xkb compiled descriptions has changed. Please 3501.210Schristos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR. 3511.210Schristos 3521.209Snjoly20100222: 3531.209Snjoly The shared objects file extension has been changed from .so to 3541.209Snjoly .pico, in order to avoid conflicts with shared libraries names 3551.209Snjoly libXX.so. All now stale regular .so files can be removed from 3561.209Snjoly your object directories. 3571.209Snjoly 3581.208Sroy20100204: 3591.208Sroy The termcap database has been removed from the sources, 3601.208Sroy but has not been marked obsolete so it is not removed 3611.208Sroy from the system when upgrading. 3621.208Sroy As such, you will need to remove them from your object 3631.208Sroy and destination directories. 3641.208Sroy 3651.203Sdyoung20091101: 3661.205Sdholland After updating, it may be necessary to make the 'cleandir' 3671.205Sdholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a 3681.205Sdholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto 3691.205Sdholland src/tools/lex/ and src/usr.bin/lex/. 3701.203Sdyoung 3711.202Smrg20091001: 3721.206Sdholland On amd64 you must rebuild tools (to get the new binutils) 3731.206Sdholland before building a kernel, or the build fails on cpufunc.S. 3741.206Sdholland 3751.206Sdholland20091001: 3761.202Smrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb 3771.202Smrg symlink, failing the build. Delete the link, and the subdir 3781.202Smrg it is in, and retry your build. 3791.202Smrg 3801.201Sdsl20090718: 3811.201Sdsl libc build changed so that strchr() provides the extra entry 3821.241Swiz point for index(). Update build of libc.a (and libc_pic.a) 3831.201Sdsl may fail because the archive contains the unwanted index.o. 3841.201Sdsl (Similarly for strrchr() and rindex().) 3851.201Sdsl 3861.198Smrg20090709: 3871.198Smrg Native Xorg was upgraded again. Builds will probably fail again 3881.198Smrg without a clean objdir, at least for src/external/mit/xorg. 3891.198Smrg 3901.197Smrg20090616: 3911.197Smrg Native Xorg was upgraded. Builds will need a clean objdir for 3921.197Smrg src/external/mit/xorg. Upgrading a system from sets will not 3931.197Smrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc 3941.197Smrg subdirectory has been changed into a file, and this needs to 3951.197Smrg be manually "rm -r"'ed before installing xbase.tgz. 3961.197Smrg 3971.195Sperry20090501: 3981.195Sperry Several new functions were added to string.h/libc, and this 3991.195Sperry can cause autoconf problems during the tool build for people 4001.241Swiz who fail to clean out their tools objects properly. If you 4011.195Sperry note messages about stpcpy, stpncpy or strnlen accompanying a 4021.195Sperry failure during the tool build, clean out all your tools 4031.195Sperry objects and start again. 4041.195Sperry 4051.194Smrg20090325: 4061.194Smrg The i386 port was switched to i486 default toolchain. This requires 4071.194Smrg cleaning your src/tools directory and $TOOLDIR and rebuilding them. 4081.194Smrg 4091.192Sskrll20090126: 4101.241Swiz The __posix_fadvise50 system call changed assembly stub type. You 4111.207Smbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory 4121.207Smbalmer to avoid using the old assembly stub. 4131.192Sskrll 4141.191Sjoerg20090202: 4151.191Sjoerg pkg_install now depends on the pkgdb cache for automatic conflict 4161.191Sjoerg detection. It is recommented to rebuild the cache with 4171.191Sjoerg ``pkg_admin rebuild''. 4181.191Sjoerg 4191.184Schristos20090110: 4201.241Swiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade: 4211.241Swiz 1. Make sure your kernel has COMPAT_50 in it. Build and install. 4221.188Schristos This is needed even in the MODULAR kernel because there is 4231.188Schristos conditionally compiled code in rtsock.c. 4241.184Schristos 2. make sure build.sh completes and the binaries in a chroot work 4251.184Schristos before installing. 4261.184Schristos 3. If you don't use build.sh and you build directly to root, and 4271.241Swiz your build breaks in the middle, don't despair. Make sure headers 4281.184Schristos are installed properly, and start building libraries first libc 4291.184Schristos and libutil, install them and then continue building all the 4301.241Swiz libraries in src/lib and src/gnu/lib and install them. Once 4311.184Schristos the new libraries are installed, you can restart the build. 4321.184Schristos 4. If you compile packages and you notice link time warnings, 4331.189Shubertf rebuild the required packages to update their shared libraries. 4341.189Shubertf Any package you rebuild will require rebuilding all the packages 4351.189Shubertf that depend on it. 4361.186Schristos 5. Next time you run pwd_mkdb with the new binary, the file 4371.186Schristos will be upgraded and it will not be backwards compatible. 4381.190Sapb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see 4391.190Sapb lastlogx(5)) have been versioned, and there is a heuristic 4401.241Swiz for utmp. You are better off removing the old files after 4411.190Sapb upgrading. The automated clearing of /var/run during 4421.190Sapb boot, and the automated rotating of files in /var/log by 4431.190Sapb newsyslog(8), may mean that you do not have to remove the 4441.190Sapb files manually. 4451.190Sapb 7. The optional accounting file (/var/account/acct, see 4461.190Sapb accton(8)) has not been versioned, and will need to be 4471.190Sapb removed. The automatic rotation of the accounting file by 4481.190Sapb /etc/daily limits the bad consequences of failure to remove 4491.190Sapb the file. 4501.196Sdholland 8. Application software that writes time_t to binary files on 4511.241Swiz disk will break or need attention. Most notably: if you are 4521.196Sdholland using PostgreSQL < 8.4, you need to dump your databases, 4531.196Sdholland rebuild PostgreSQL with the new time_t, then restore. 4541.185Sjmcneill 4551.183Spgoyette20081219: 4561.183Spgoyette config(1) has been updated, and one of the files it creates - 4571.183Spgoyette swapnetbsd.o - has changed format. You need to rebuild config 4581.183Spgoyette (done automatically by build.sh) and then you need to rerun 4591.183Spgoyette config on all kernel configuration files before rebuilding those 4601.183Spgoyette kernels. 4611.183Spgoyette 4621.181Scube20081205: 4631.181Scube If you build with MKX11=no, you should remove /etc/rc.d/xdm and 4641.181Scube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc 4651.181Scube set and will appear as extra files for MKX11=no update builds. 4661.178Slukem 4671.179Stsutsui20081122: 4681.182Stsutsui On i386, various kernel options(4) in GENERIC including 4691.180Swiz file systems have been disabled and moved into kernel modules. 4701.180Swiz Before trying a new GENERIC kernel, you have to prepare the 4711.179Stsutsui following files as well as a new GENERIC kernel: 4721.179Stsutsui 4731.179Stsutsui - build and install kernel modules from src/sys/modules 4741.179Stsutsui 4751.179Stsutsui - install the latest bootloader, which will load a module 4761.180Swiz for the file system from which the kernel is loaded automatically 4771.179Stsutsui 4781.180Swiz If you have to load your kernel from a file system which is not of 4791.180Swiz the same type as the root file system, you have to load the necessary 4801.180Swiz file system module manually on the boot prompt or in the boot.cfg file. 4811.179Stsutsui 4821.178Slukem20080827: 4831.178Slukem If you built and installed a libc from sources between 4841.178Slukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3) 4851.178Slukem which results in false errors reported by lint(1). 4861.178Slukem Since this breaks the libc build itself, manual help is 4871.180Swiz needed -- lint must be disabled temporarily, e.g.: 4881.178Slukem $ (cd lib/libc && make MKLINT=no dependall install) 4891.178Slukem 4901.177Schristos20080813: 4911.177Schristos MKDEBUG build was broken because the .depend files did not know 4921.241Swiz about .go files. You need to remove all .depend files and rebuild. 4931.177Schristos 4941.200Sdholland20080802: 4951.200Sdholland A regression in binary compatibility for pthread_mutex_t has 4961.241Swiz been fixed. Unfortunately, the price is breaking compatibility 4971.200Sdholland for -current. 4981.200Sdholland 4991.200Sdholland Threaded programs (using libpthread) and C++ programs (using 5001.200Sdholland libstdc++) compiled after 20070907 and before 20080802 need to 5011.200Sdholland be recompiled. 5021.200Sdholland 5031.200Sdholland One way to find affected pkgsrc packages: 5041.200Sdholland 5051.200Sdholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO 5061.200Sdholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO 5071.200Sdholland 5081.175Ssimonb20080731: 5091.175Ssimonb WAPBL (metadata journaling support) has been added, but at this 5101.175Ssimonb time isn't backwards compatible with pre-WAPBL aware kernels 5111.175Ssimonb and userland (fsck_ffs in particular). Please make sure you 5121.175Ssimonb don't use a journaled filesystem with an older kernel/userland, 5131.176Ssimonb especially an uncleanly mounted journaled filesystem. WAPBL 5141.176Ssimonb also requires the super block to be in the UFS2 format. You 5151.176Ssimonb can use fsck_ffs -c 4 to update the superblock format. 5161.175Ssimonb 5171.174Slukem20080721: 5181.174Slukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR 5191.174Slukem isn't defined. 5201.174Slukem 5211.173Sfreza20080531: 5221.241Swiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed 5231.241Swiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8) 5241.173Sfreza utility needs to be rebuilt and reinstalled as older binaries 5251.241Swiz won't work correctly. The following sequence of commands: 5261.173Sfreza 5271.173Sfreza $ (cd sys/sys/ && nbmake-$arch includes) 5281.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch clean) 5291.173Sfreza $ (cd sbin/drvctl/ && nbmake-$arch all) 5301.173Sfreza 5311.173Sfreza leaves new drvctl utility in sbin/drvctl build directory. 5321.173Sfreza 5331.172Slukem20080503: 5341.172Slukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE. 5351.172Slukem 5361.171She20080521: 5371.171She For a while, unprivileged UPDATE builds would fail to 5381.171She succeed at the checkflist stage, complaining that 5391.171She ${DESTDIR}/stand/<arch>/ did not exist. A fix for this 5401.171She problem was committed to share/mk/bsd.kmodule.mk, revision 1.9. 5411.171She If you already hit this problem, update the .mk file, 5421.171She remove ${DESTDIR}/stand/<arch>, and re-run the build. 5431.171She 5441.174Slukem20080303: 5451.174Slukem Linker warnings are now fatal if $WARNS>0. 5461.174Slukem 5471.170Schristos20080126: 5481.170Schristos The posix_fadvise system call has been changed from an assembly 5491.241Swiz stub, to a c file that calls an assembly stub. You need to 5501.170Schristos 'rm -f posix_fadvise.* .depend' in the libc build directory to 5511.170Schristos avoid using the old assembly stub. 5521.170Schristos 5531.168Sjoerg20071209: 5541.241Swiz The acpiec(4) driver has been split into two attachments. If you 5551.168Sjoerg get ACPI errors before the attachment, please update your kernel 5561.169Swiz configuration file appropriately or see GENERIC for more details. 5571.168Sjoerg 5581.166Sxtraeme20071115: 5591.166Sxtraeme The it(4) driver has been renamed to itesio(4) and the old port 5601.166Sxtraeme argument specified in the kernel configuration file is not valid 5611.241Swiz anymore. The itesio(4) driver now uses the Super I/O address port 5621.241Swiz rather than the EC address port. Please update your kernel 5631.167Swiz configuration file appropriately or see GENERIC for more details. 5641.166Sxtraeme 5651.165Sjmmv20071028: 5661.165Sjmmv The pccons(4) driver has been removed from the NetBSD/shark port. 5671.165Sjmmv You need to update any custom kernel configuration file you have 5681.165Sjmmv to remove any references to pccons (which includes removing the 5691.165Sjmmv now useless XSERVER option) and replace them with the correct 5701.165Sjmmv entries for the wscons driver. See the GENERIC configuration file 5711.165Sjmmv for more details. 5721.165Sjmmv 5731.164Sgdt20070913: 5741.164Sgdt A latent bug in dhclient/dhcpd that caused it to be unable to 5751.164Sgdt enumerate interfaces was fixed. The bug began to cause 5761.164Sgdt problems after 20070911 when the kernel's SIOCGIFCONF 5771.164Sgdt implementation was repaired. From 20070529 to 20070911 racoon 5781.164Sgdt could not enumerate interfaces. (These are noted because 5791.164Sgdt normal kernel/userspace version matching hygiene is not 5801.164Sgdt sufficient to avoid this problem.) Ensure that both kernel 5811.164Sgdt and userland are from after 20070913. 5821.164Sgdt 5831.163Sjoerg20070703: 5841.241Swiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It 5851.199Sdholland calls the target-specific strip program, and the logic to pass 5861.199Sdholland down STRIP from make has been removed. This requires a 5871.199Sdholland re-installation of tools. 5881.163Sjoerg 5891.161Sdsl20070422: 5901.161Sdsl The way OS emulations lookup filenames inside the emulation root 5911.161Sdsl has been changed. Rather than modify the pathname (and copy back 5921.161Sdsl to userspace) namei() and lookup() directly check the emulation 5931.241Swiz root. One side effect is that absolute symlinks inside the emulated 5941.167Swiz root file system will be relative to that file system - unless they 5951.161Sdsl start /../ this is useful when the emulated root is a real install 5961.161Sdsl that has such links. 5971.161Sdsl This might affect symlinks that have been added to reference outside 5981.161Sdsl the emulated root. 5991.161Sdsl 6001.160Sjmcneill20070412: 6011.241Swiz The pckbc driver on sgimips IP32 has been removed. Use macekbc 6021.241Swiz instead. See the GENERIC32_IP3x kernel configuration for an 6031.160Sjmcneill example. 6041.160Sjmcneill 6051.159Sgdt20070319: 6061.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 6071.159Sgdt on many platforms due to incorrect flags settings. If you 6081.159Sgdt updated and built after about 20070315, do "nbmake-$arch 6091.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 6101.159Sgdt rebuild of object files that might have been built 6111.159Sgdt incorrectly, and ensure that you have at least 6121.159Sgdt src/lib/libc/Makefile 1.130. 6131.159Sgdt 6141.241Swiz20070210: 6151.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 6161.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 6171.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 6181.158Sdbj will allow dependencies on those files to get get rebuilt 6191.158Sdbj 6201.157Sapb20070209: 6211.157Sapb The threading model was changed when the newlock2 branch 6221.157Sapb was merged to NetBSD-current. If you boot with a new 6231.157Sapb kernel (version 4.99.10), then you also need a new pthread 6241.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 6251.157Sapb an old kernel, then you need the old pthread library 6261.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 6271.157Sapb the pthread library in sync, old threaded applications should 6281.157Sapb continue to work with an old or new kernel. Note that named(8) 6291.157Sapb is the only threaded application in the base system. 6301.157Sapb 6311.154She20061214: 6321.154She Following the move of string_to_flags() and flags_to_string() 6331.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 6341.154She will need to do a "make cleandir" in 6351.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 6361.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 6371.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 6381.156She as the installation images in distrib/ 6391.154She in order to excise stale references to the old stat_flags.h header 6401.154She file in the ls sources -- stat_flags.h has been removed. 6411.154She 6421.152Schristos20061108: 6431.152Schristos The configure script used in the src/tools/gcc compiler has been 6441.152Schristos changed to indicate that our libc has ssp support built-in and 6451.241Swiz does not depend on -lssp and -lssp-nonshared. You'll need to 6461.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 6471.152Schristos 6481.151Srpaulo20061009: 6491.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 6501.241Swiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 6511.151Srpaulo 6521.150Sbjh2120060814: 6531.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 6541.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 6551.150Sbjh21 kernel configuration for an example. X servers from the last 6561.150Sbjh21 few years should cope. 6571.150Sbjh21 6581.149Schristos20060703: 6591.241Swiz MPACPI is no more. We always configure PCI interrupts using ACPI 6601.241Swiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 6611.241Swiz to ACPI_SCANPCI. Thanks to work from fvdl. 6621.149Schristos 6631.148Sdogcow20060627: 6641.148Sdogcow socket(2) has changed, and its system call has been versioned. 6651.148Sdogcow For userlands with the old version of socket(2), make sure that 6661.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 6671.148Sdogcow errors will result. 6681.148Sdogcow 6691.1SabsHints for a more successful build: 6701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6711.123Sjmc Use build.sh, but do not use its "expert mode": 6721.132Sjmmv This will automatically build the tools in the 6731.123Sjmc correct order, and it will keep the tools and the 6741.123Sjmc new build products from interfering with the running 6751.123Sjmc system. This will allow you to ignore most of the 6761.123Sjmc other advice in this file. 6771.2Smrg Build a new kernel first: 6781.2Smrg This makes sure that any new system calls or features 6791.2Smrg expected by the new userland will be present. This 6801.2Smrg helps to avoid critical errors when upgrading. 6811.1Sabs Use object directories: 6821.1Sabs This helps to keep stale object 6831.1Sabs files from polluting the build if a Makefile "forgets" 6841.1Sabs about one. It also makes it easier to clean up after 6851.1Sabs a build. It's also necessary if you want to use the 6861.1Sabs same source tree for multiple machines. 6871.123Sjmc To use object directories with build.sh: 6881.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 6891.123Sjmc To use object directories without using build.sh: 6901.1Sabs a) cd /usr/src ; make cleandir 6911.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 6921.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 6931.1Sabs d) cd /usr/src ; make build 6941.2Smrg Note that running "make obj" in a directory will create 6951.2Smrg in obj.$MACHINE directory. 6961.1Sabs Build to a DESTDIR: 6971.123Sjmc This helps to keep old installed files (especially libraries) 6981.123Sjmc from interfering with the new build. 6991.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 7001.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 7011.123Sjmc environment variable before running make build. It should be 7021.123Sjmc set to the pathname of an initially empty directory. 7031.123Sjmc Problems: if you do not use build.sh, you might need to 7041.123Sjmc update critical utilities without using DESTDIR since 7051.123Sjmc nothing is executed from what is installed in DESTDIR. 7061.123Sjmc (See critical utils, below.) 7071.1Sabs Build often: 7081.1Sabs This keeps critical utilities current enough to not choke 7091.1Sabs on any other part of the source tree that depends on up to 7101.123Sjmc date functionality. If you use build.sh, you should not have 7111.123Sjmc this problem. 7121.241Swiz 7131.1SabsWhat to do if things don't work: 7141.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7151.230StlsWhen things don't work there are usually a few things that commonly 7161.1Sabsshould be done. 7171.1Sabs 1) make includes 7181.1Sabs This should be done automatically by make build. 7191.1Sabs 2) cd share/mk && make install 7201.1Sabs Again, automatically done by make build. 7211.1Sabs 7221.1SabsFailsafe rebuild of a small part of the tree: 7231.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7241.1SabsTo make sure you rebuild something correctly you want to do 7251.1Sabssomething like the following: 7261.1Sabs 1) Make sure the includes and .mk files are up to date. 7271.1Sabs 2) Make sure any program used to build the particular 7281.1Sabs utility is up to date. (yacc, lex, etc...) 7291.1Sabs 3) cd ...path/to/util... 7301.1Sabs make cleandir 7311.1Sabs rm ...all obj directories... 7321.1Sabs make cleandir # yes, again 7331.1Sabs make obj 7341.1Sabs make depend && make 7351.1Sabs 7361.1SabsFailsafe rebuild of the entire tree: 7371.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7381.1SabsIf you really want to make sure the source tree is clean and 7391.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 7401.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 7411.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 7421.1Sabs 7431.1Sabs---cut here--- 7441.1Sabs#!/bin/sh 7451.1Sabs. /etc/mk.conf 7461.1Sabs 7471.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7481.58Slukem NETBSDSRCDIR=/usr/src 7491.1Sabsfi 7501.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7511.1Sabs echo Unable to find sources 7521.1Sabs exit 1 7531.1Sabsfi 7541.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 7551.1Sabs 7561.1Sabsif [ -z $BSDOBJDIR ] ; then 7571.1Sabs BSDOBJDIR=/usr/obj 7581.1Sabsfi 7591.1Sabsif [ -d $BSDOBJDIR ] ; then 7601.1Sabs rm -rf $BSDOBJDIR 7611.1Sabsfi 7621.1Sabs 7631.58Slukemcd $NETBSDSRCDIR && make cleandir 7641.1Sabs 7651.1Sabs---cut here--- 7661.1Sabs 7671.1SabsCritical utilities: 7681.1Sabs^^^^^^^^^^^^^^^^^^^ 7691.3Sitojun usr.bin/compile_et 7701.1Sabs usr.bin/make 7711.1Sabs usr.bin/yacc 7721.1Sabs usr.bin/lex 7731.11Slukem usr.bin/xlint 7741.142Sdrochner usr.bin/config 7751.1Sabs 7761.34SsimonbOther problems and possible solutions: 7771.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7781.1SabsSymptom:Complaints involving a Makefile. 7791.17SerhFix: Rebuild usr.bin/make: 7801.17Serh cd usr.bin/make && make && make install 7811.111Ssimonb Or, a failsafe method if that doesn't work: 7821.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 7831.17Serh 7841.1SabsFix: Make sure .mk files are up to date. 7851.1Sabs cd share/mk && make install 7861.2Smrg 7871.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 7881.142SdrochnerFix: Rebuild usr.bin/config 7891.1Sabs 7901.1SabsSymptom: 7911.1SabsFix: Rebuild usr.bin/yacc 7921.1Sabs 7931.1SabsSymptom: 7941.1SabsFix: Rebuild usr.bin/lex 7951.1Sabs 7961.1SabsSymptom: 7971.1SabsFix: rm /usr/lib/libbfd.a 7981.4Sitojun 7991.4SitojunSymptom:Obsolete intermediate files are used during compilation 8001.4SitojunFix: Try the following sequence of commands in the directory in question. 8011.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 8021.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 8031.4Sitojun may remain. The command tries to clean everything up) 8041.5Swiz 8051.207SmbalmerSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible 8061.207Smbalmer pointer type 8071.5SwizFix: Rebuild and install usr.bin/menuc 8081.12Sitojun 8091.12SitojunSymptom:mklocale not found during build in share/locale/ctype 8101.12SitojunFix: Build and install usr.bin/mklocale 8111.13Sdogcow 8121.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 8131.13SdogcowFix: Rebuild and install lib/libc 8141.13Sdogcow 8151.142SdrochnerSymptom:usr.bin/config fails to build. 8161.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8171.13Sdogcow 8181.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8191.19ScgdFix: Rebuild and install lib/libc 8201.24Sabs 8211.24SabsSymptom:lint does not understand the '-X' option 8221.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 8231.223Sjoerg 8241.223SjoergSymptom:Update build fails in src/tools/gcc complaining that a variable 8251.223Sjoerg (e.g. CPPFLAGS) has changed since the previous run. 8261.223SjoergFix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build. 8271.257Sapb 8281.257SapbSymptom:cvs [update aborted]: cannot open directory /cvsroot/src/...: 8291.257Sapb No such file or directory. 8301.257SapbCause: If a directory is created by mistake, then it is sometimes 8311.257Sapb deleted from the CVS repository using administrative commands 8321.257Sapb that bypass the normal cvs access controls. If your cvs working tree 8331.257Sapb contains references to a directory that has been deleted on the 8341.257Sapb server in this way, then "cvs update" reports this error. 8351.257SapbFix: Recursively delete the affected directory from your working tree 8361.257Sapb and try the update again. 837