UPDATING revision 1.146
11.146Spavel$NetBSD: UPDATING,v 1.146 2006/06/02 19:01:00 pavel Exp $ 21.1Sabs 31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent 41.123Sjmcchanges that might cause problems in the build process, and a guide for 51.123Sjmcwhat to do if something doesn't work. 61.1Sabs 71.123SjmcFor a more detailed description of the recommended way to build NetBSD 81.123Sjmcusing build.sh, see the BUILDING file. 91.123Sjmc 101.123SjmcNote that much of the advice in this UPDATING file was written before 111.123Sjmcbuild.sh existed. Nevertheless, the advice here may be useful for 121.123Sjmcworking around specific problems with build.sh. 131.123Sjmc 141.123SjmcSee also: BUILDING, build.sh, Makefile. 151.1Sabs 161.1SabsRecent changes: 171.1Sabs^^^^^^^^^^^^^^^ 181.138Slukem 191.146Spavel20060526: 201.146Spavel the kernel links script for i386 and xen was changed to set the 211.146Spavel load address correctly, for the benefit of MULTIBOOT boot loaders 221.146Spavel (like Grub). If you use a linker (ld) older than from 2006/04/17, it 231.146Spavel will be unable to link the kernel because of a bug, and you will 241.146Spavel have to update at least src/gnu/dist/binutils/ld and recompile the 251.146Spavel linker. If using the build.sh script, the easiest way is with a 261.146Spavel "build.sh tools" command, with any other options that you use 271.146Spavel normally. When using build.sh, the linker binary is installed as 281.146Spavel ${TOOLDIR}/bin/i386--netbsdelf-ld. 291.145Smartin20060131: 301.145Smartin the protocol between the sparc64 bootloader (ofwboot) and 311.145Smartin the kernel was changed. Before installing a new kernel, 321.145Smartin you need to update ofwboot. After a full build, just copy 331.145Smartin /usr/mdec/ofwboot to /, or do a rebuild of 341.145Smartin src/sys/arch/sparc/stand/ofwboot and install the result to /. 351.145Smartin 361.144Syamt20050917: 371.144Syamt arch/*/conf/std.* was changed to include conf/std, which 381.144Syamt contains MI options previously enabled by default. 391.144Syamt If you have kernel config files which doesn't include 401.144Syamt arch/*/conf/std.*, you need to edit them to include conf/std 411.144Syamt to get the previous configuration. 421.144Syamt 431.143Slukem20050830: 441.143Slukem named.conf was moved from /etc/namedb to /etc. 451.143Slukem postinstall(8) migrates this during interactive use. 461.143Slukem Users of MKUPDATE=yes will need to manually rectify 471.143Slukem this in their DESTDIR. 481.143Slukem 491.142Sdrochner20050825: 501.142Sdrochner Some data structures in sys/device.h, related to interface 511.142Sdrochner attributes and locator names, were changed. config(1) was 521.142Sdrochner modified to emit the new data structures. 531.142Sdrochner Thus usr.bin/config must be updated (and run on the kernel 541.142Sdrochner configuration file) before a new kernel can be built. 551.142Sdrochner 561.139Schristos20050531: 571.141Saugustss genassym.sh(8) was moved to genassym(1). You need to either build 581.141Saugustss tools first or install the version of genassym from /usr/bin before 591.139Schristos you can build a kernel again. 601.139Schristos 611.140Syamt20050520: 621.140Syamt Because a kernfs bug which xentools relies on was fixed, 631.140Syamt xentools up to xentools20-2.0.3nb4 won't work with new kernel. 641.140Syamt 651.138Slukem20050417: 661.138Slukem postinstall(8) was moved from /etc to /usr/sbin and made part 671.138Slukem of the "base" set, to make it easier to invoke after an 681.138Slukem upgrade. 691.138Slukem 701.136Scube20050325: 711.136Scube pcppi(4) was separated in two devices, adding attimer(4). Be sure 721.136Scube to add a config line for an attimer(4) device in your kernel 731.136Scube configuration, or you won't be able to set the pitch of the beep 741.137Scube with wsconsctl. Depending on the default value for the pitch, you 751.137Scube might even not hear any more beep. Also, it is advised to attach both 761.137Scube devices the same way (i.e., both on isa or both on acpi) or the 771.137Scube pcppi(4) device may fail to find the attimer(4) one. 781.136Scube 791.135Sjmc20050211: 801.135Sjmc Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in 811.135Sjmc some of the cross tools to fail if they use configure. Some configure's 821.135Sjmc cache the environment passed in and notice the new environment is 831.135Sjmc different and abort. Doing a clean in tools/ should be enough to 841.135Sjmc make a build continue. 851.135Sjmc 861.134Schristos20050109: 871.134Schristos Since su is using pam by default now, make sure that you have 881.134Schristos /etc/pam.d populated (postinstall will do that automatically 891.134Schristos for you). Otherwise su will fail open (i.e. will not require 901.134Schristos a password). 911.134Schristos 921.133Schristos20041229: 931.133Schristos Make had a path resolution bug that manifested itself as not 941.133Schristos being able to install openpam.3. This bug has been fixed, but 951.133Schristos you might need to rebuild make manually first to get through 961.133Schristos the build. 971.133Schristos 981.130Schristos20041201: 991.130Schristos Userland programs have been changed to use /dev/bpf instead of 1001.130Schristos /dev/bpfX. You need to create that device by installing a new 1011.131Swiz MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]* 1021.99Smrg 1031.129Sjmc20041006: 1041.129Sjmc 1051.129Sjmc A bug was introduced into /bin/sh (var.c rev 1.35) which causes 1061.129Sjmc variables to not export correctly to subshells in all cases. This 1071.129Sjmc will cause builds to break if that version of /bin/sh is installed 1081.129Sjmc on the system. The proper version of /bin/sh can be verified with: 1091.129Sjmc 1101.129Sjmc ident /bin/sh | grep var 1111.129Sjmc 1121.129Sjmc Any /bin/sh w. version 1.35 will not work and needs to be updated 1131.129Sjmc before attempting a build. 1141.129Sjmc 1151.127Schristos20041001: 1161.127Schristos The ipfilter kernel sources moved from sys/netinet to 1171.127Schristos dist/sys/ipf/netinet. Due to the move some Makefile 1181.127Schristos dependencies are now dangling requiring a make cleandir 1191.128She before they work again (kdump, ktruss, rescue, ipf, and 1201.128She ftp-proxy are the victims). 1211.127Schristos 1221.125Satatat20040715: 1231.125Satatat The rc.d/sendmail script now uses a heuristic to determine 1241.125Satatat if sendmail should be started at boot time. It checks the 1251.125Satatat contents of /etc/mailer.conf, /etc/mail/submit.cf, and the 1261.125Satatat owner and mode of the sendmail binary to see if any changes 1271.125Satatat to the mail infrastructure have been made. If no changes 1281.125Satatat are detected, it will start an SMTP listener. 1291.125Satatat 1301.125Satatat Setting sendmail=NO in /etc/rc.conf will override this. 1311.125Satatat 1321.125Satatat If you are only using sendmail by default and only for 1331.125Satatat local delivery, it is important that you also update your 1341.125Satatat sendmail.cf so that the SMTP listener only listens on the 1351.125Satatat loopback interface. 1361.125Satatat 1371.125Satatat20040715: 1381.125Satatat The method by which athhal-elf.o gets pulled into i386 1391.125Satatat kernel builds has been changed again. The latest version 1401.125Satatat of bsd.files.mk is no longer required. 1411.125Satatat 1421.124Sjmc20040621: 1431.124Sjmc Due to the recent rototill of tools/compat it's crucial one starts 1441.124Sjmc from a clean objdir under tools/*. 1451.124Sjmc 1461.124Sjmc This is mostly due to generated files (yacc and lex sources) needing 1471.125Satatat to be generated with new rules from bsd.hostprog.mk. 1481.124Sjmc 1491.124Sjmc The safest course is to rm -rf all objects under tools before building. 1501.124Sjmc 1511.121Slukem20040516: 1521.121Slukem The end-user modifiable X11 configuration has been moved 1531.121Slukem from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>. 1541.121Slukem Ensure that src and xsrc is up to date, and run 1551.121Slukem "make cleandir" in src/x11 before your next build. 1561.121Slukem 1571.126Slukem postinstall currently doesn't migrate the files from 1581.126Slukem /usr/X11R6/lib/X11/* to /etc/X11/* although it does 1591.126Slukem detect that this needs to occur, so you'll have to 1601.126Slukem manually move these files yourself. 1611.126Slukem 1621.119Satatat20040426: 1631.119Satatat Support for the original dynamic sysctl node structure has 1641.119Satatat been removed in favor of the newer layout. This affects 1651.119Satatat consumers of the create and delete interface, as well as 1661.119Satatat the dynamic discovery mechanism. This is believed only to 1671.119Satatat be the sysctl(8) binary itself, at this point in time, so 1681.119Satatat the only effect of this should be that a sysctl binary 1691.119Satatat built from sources dated between 2003/12/04 and 2004/03/24 1701.119Satatat will not work on a kernel built from sources dated after 1711.119Satatat 2004/04/25. If you need a new sysctl binary but build.sh 1721.119Satatat does not work, make sure that your revision of 1731.120Satatat src/sys/sys/sysctl.h is 1.112 (or later), and then the 1741.120Satatat do the following: 1751.119Satatat 1761.120Satatat cd /usr/src (or wherever your source tree is) 1771.120Satatat make USETOOLS=no includes 1781.120Satatat cd lib/libc 1791.120Satatat make USETOOLS=no dependall install 1801.120Satatat cd ../../sbin/sysctl 1811.119Satatat make USETOOLS=no dependall install 1821.119Satatat 1831.122Sitojun If you are using older sysctl binary, GNU autoconf would fail to 1841.122Sitojun identify your machine architecture, and tries to build binary for 1851.122Sitojun "unknown-unknown-netbsd20F" or something like that. if that happens, 1861.122Sitojun make sure to follow the above steps. 1871.122Sitojun 1881.118Sdbj20040425: 1891.118Sdbj The ffs superblock issues listed below under 20040109 and 20030402 1901.118Sdbj are now automatically addressed by the /etc/rc.d/fixsb script or by 1911.118Sdbj sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 1921.118Sdbj invocation mentioned below will continue to work and is now 1931.118Sdbj automated by those scripts. Note that under certain circumstances, 1941.118Sdbj affected filesystems upgraded to a -current kernel first before 1951.118Sdbj upgrading their userland with the fixsb and fsck_ffs fixes may 1961.118Sdbj encounter a 'freeing free inode' panic when writing to the affected 1971.118Sdbj filesystem, so it is a good idea to repair the filesystem as soon as 1981.118Sdbj possible. For more details on the fixsb script, see pr install/25138. 1991.118Sdbj 2001.115Schristos20040418: 2011.121Slukem statfs(2) and friends have been replaced with statvfs(2). Before 2021.115Schristos installing a newly build userland make sure that you are running 2031.115Schristos a newly built kernel with COMPAT_20 set. In addition your libc 2041.115Schristos build might not work (undefined SYS_statfs symbol) because make 2051.115Schristos clean does not know how to remove files it does not know about 2061.116Schristos anymore. Manually remove all generated .S sources and objects 2071.116Schristos from the libc build directory. 2081.115Schristos 2091.114Sjmc20040326: 2101.114Sjmc The method by which athhal-elf.o gets pulled into i386 kernel builds 2111.117Sjmc has been changed. The file is now stored as a uuencoded file in CVS 2121.114Sjmc and the generated Makefile will use the new .uue rules from bsd.file.mk 2131.114Sjmc to build it. 2141.114Sjmc 2151.114Sjmc This means you must have the latest bsd.files.mk installed when 2161.114Sjmc building a kernel without USETOOLS=yes. 2171.114Sjmc 2181.113Sdan20040318: 2191.113Sdan A bug in the cgd(4) blowfish code was corrected, without 2201.113Sdan provision of backwards compatibility, after several public 2211.113Sdan notices over several months. Users of cgd with blowfish cipher 2221.113Sdan ONLY must dump their data before updating their kernels, and 2231.113Sdan recreate cgd's and restore data using the new kernel. See 2241.113Sdan (recent message to current-users, URL when mail-index has updated) 2251.113Sdan 2261.108Sbjh2120040313: 2271.108Sbjh21 On acorn32, the opms and qms drivers have been withdrawn, and 2281.108Sbjh21 the old wsqms driver is now called qms. Kernel config files 2291.108Sbjh21 will need updating. See the ones in sys/arch/acorn32/conf 2301.108Sbjh21 for examples. 2311.108Sbjh21 2321.106Sbjh2120040125: 2331.106Sbjh21 On acorn32, the beep and sysbeep devices are no longer 2341.106Sbjh21 needed, and will need to be deleted from kernel configuration 2351.106Sbjh21 files. 2361.105Sbjh21 2371.102Sdbj20040109: 2381.102Sdbj Compatibility for old ffs superblock layouts has been 2391.102Sdbj added, and the restrictive fsck checks have been reenabled 2401.102Sdbj when using those layouts. If you have been using -current 2411.102Sdbj since 20030402, you may find that fsck again signals fatal 2421.110Sdbj superblock mismatches. To repair, make sure you have 2431.111Ssimonb an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 2441.109Sdbj to complete the filesystem upgrade. A message has 2451.111Ssimonb been added to the kernel which should detect this problem. 2461.111Ssimonb See the following discussion for more information: 2471.112Skeihan http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html 2481.102Sdbj 2491.99Smrg20031203: 2501.100Skeihan New binutils builds may fail due to old dependencies. 2511.99Smrg It's necessary to "make cleandir" to ensure that 2521.99Smrg the dependencies will be rebuilt correctly. 2531.98Swiz 2541.98Swiz20031111: 2551.98Swiz A newer mkdep is needed. Error noting that is 2561.98Swiz cc: Ambiguous abbreviation -- 2571.97Slukem 2581.97Slukem20031008: 2591.97Slukem /usr/include/sys/disklabel_mbr.h was removed. 2601.97Slukem It's necessary to "make cleandir" to ensure that 2611.97Slukem the dependencies will be rebuilt correctly. 2621.96Schristos 2631.109Sdbj20031007: 2641.111Ssimonb A sign exension bug was fixed which set all the high bits 2651.111Ssimonb of our newly expanded ffs fs_flags. This should only 2661.111Ssimonb affect users who installed or upgraded in September of 2003. 2671.109Sdbj A small utility program was posted to tech-kern which 2681.111Ssimonb should fix this problem, and a warning message was added 2691.111Ssimonb to the kernel which should discover and warn about it. See 2701.111Ssimonb http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html 2711.109Sdbj 2721.96Schristos20030906: 2731.96Schristos With the addition of siginfo support the old signal trampoline 2741.96Schristos code has been deprecated to COMPAT_16. Make sure that your running 2751.96Schristos kernel has COMPAT_16 enabled before building userland. 2761.94Schristos 2771.94Schristos20030801: 2781.95Swiz With the new openssl, there is some header and library shuffling. 2791.94Schristos rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \ 2801.95Swiz /usr/lib/libdes* before building. 2811.92Swiz 2821.92Swiz20030703: 2831.92Swiz Texinfo was updated to 4.6. To avoid failures when trying to 2841.92Swiz build the included texinfo files, do: 2851.92Swiz 2861.92Swiz cd src/gnu/usr.bin/texinfo 2871.92Swiz make MKINFO=no dependall install 2881.90Swiz 2891.90Swiz20030630: 2901.101Sjunyoung Groff was updated to 1.19; it's probably necessary to do 2911.91Swiz cd share/mk && make install 2921.90Swiz cd src/gnu/usr.bin/groff 2931.90Swiz make MKMAN=no dependall install 2941.90Swiz (untested). 2951.89Schristos 2961.89Schristos20030516: 2971.89Schristos Due to bugs in the export handling code, invalid export lines 2981.89Schristos were accepted before and caused the kernel to panic when 2991.89Schristos mountd got restarted because it freed memory that had already 3001.89Schristos been freed. This has been fixed and the kernel checks 3011.89Schristos export addresses very strictly. If you upgrade your kernel, 3021.89Schristos make sure you also upgrade mountd, because if your export 3031.89Schristos file contains lines with an old inet4 address syntax (i.e. 3041.89Schristos a.b.c or a.b or a), they will get rejected by the new kernel. 3051.87Sbjh21 3061.87Sbjh2120030402: 3071.87Sbjh21 The superblock layout for FFS was changed. If you have 1.6 3081.87Sbjh21 fsck binaries, they will signal a fatal superblock mismatch 3091.87Sbjh21 with the first alternate, because they compare too many 3101.87Sbjh21 fields (even ones that aren't useful). If possible, upgrade 3111.87Sbjh21 your fsck_ffs binary before using a new kernel. 3121.87Sbjh21 None of this signals actual filesystem damage. 3131.85Satatat 3141.85Satatat20030324: 3151.85Satatat sendmail version 8.12.8 was imported. Since sendmail is 3161.85Satatat now setgid to the smmsp group, and runs in "collection" 3171.85Satatat mode for most common activities, there is a new config 3181.85Satatat file called submit.cf that needs to live in /etc/mail. 3191.85Satatat The generic submit.cf sample in /usr/share/sendmail/cf 3201.85Satatat is named netbsd-msp.cf. Upgrading your regular sendmail 3211.85Satatat configuration file is also strongly advised. 3221.85Satatat 3231.85Satatat See the section named "MESSAGE SUBMISSION PROGRAM" in 3241.85Satatat the updated /usr/share/sendmail/README file for more 3251.85Satatat information. 3261.82Swiz 3271.82Swiz20030117: 3281.82Swiz Texinfo was updated to 4.3. To avoid failures when trying to 3291.82Swiz build the included texinfo files, do: 3301.82Swiz 3311.82Swiz cd src/gnu/usr.bin/texinfo 3321.82Swiz make MKINFO=no dependall install 3331.81Slukem 3341.81Slukem20021223: 3351.81Slukem The METALOG format changed slightly, to remove the leading 3361.81Slukem "${DESTDIR}" from path names. 3371.81Slukem This only affects people building with UNPRIVED. 3381.81Slukem For complete safety, remove the DESTDIR entirely and 3391.81Slukem update tools/mtree, before running make build. 3401.88Sitojun 3411.88Sitojun20021219: 3421.88Sitojun CVS repository layout was changed. See the following for details 3431.88Sitojun if you are using (anonymous) cvs to update your tree. 3441.88Sitojun 3451.93Ssalo http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html 3461.80Slukem 3471.80Slukem20021219: 3481.80Slukem install(1) had a '-N dbdir' option added, to specify an 3491.80Slukem alternate location to look up users & groups (instead 3501.80Slukem of the host system passwd(5) and group(5) databases). 3511.80Slukem 3521.80Slukem The build system was modified to take advantage of 3531.80Slukem this option (using ${NETBSDSRCDIR}/etc), so if you 3541.83Skei use USETOOLS==no, you may have to rebuild and 3551.80Slukem reinstall usr.bin/xinstall first. 3561.78Slukem 3571.78Slukem20021130: 3581.78Slukem fparseln(3) moved from libutil to libc. 3591.78Slukem If building to DESTDIR=/, reinstall the includes 3601.78Slukem and rebuild libc: 3611.78Slukem make includes 3621.78Slukem make do-lib-libc 3631.78Slukem If using build.sh, "cd tools/compat && make clean" 3641.78Slukem before rebuilding the tools. 3651.77Slukem 3661.77Slukem20021126: 3671.77Slukem The mk.conf(5) variable SYS_INCLUDE has been deprecated, 3681.77Slukem including the optional "SYS_INCLUDE=symlinks" support. 3691.77Slukem All header files, including <sys/*.h> are copied into 3701.77Slukem /usr/include. 3711.76Sthorpej 3721.76Sthorpej20021121: 3731.76Sthorpej The C run-time support files crtbegin.o and crtend.o 3741.76Sthorpej (and their companions crtbeginS.o and crtendS.o) were 3751.76Sthorpej split up, with new crti.o and crtn.o files resulting. 3761.76Sthorpej This means that libtool needs to be rebuilt once the 3771.76Sthorpej new libraries are installed. The process of rebuilding 3781.76Sthorpej libtool will cause it to automatically notice the new 3791.76Sthorpej required files, but it *must* be rebuilt in order to 3801.76Sthorpej do this. 3811.76Sthorpej 3821.76Sthorpej An out-of-date libtool will result in shared libraries 3831.76Sthorpej which lack _init() and _fini() routines, which means that 3841.76Sthorpej their global contructors/destructors will not be invoked. 3851.75Sthorpej 3861.75Sthorpej20021121: 3871.75Sthorpej A bug related to how ARM ELF objects were tagged has been 3881.75Sthorpej corrected. 3891.75Sthorpej 3901.75Sthorpej NetBSD ARM ELF uses the soft-VFP floating point model by 3911.75Sthorpej default. However, the assembler lacked support for marking 3921.75Sthorpej objects as using the VFP floating point format, and the 3931.79Swiz compiler was not properly passing the flag indicating "soft-VFP" 3941.75Sthorpej to the assembler. 3951.75Sthorpej 3961.75Sthorpej Unfortunately, this means that the linker will now consider 3971.75Sthorpej old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be 3981.75Sthorpej incompatible with new (properly marked) objects. 3991.75Sthorpej 4001.75Sthorpej The problem will only manifest itself if you attempt to compile 4011.75Sthorpej a new program using the fixed toolchain, and link that program 4021.75Sthorpej against old libraries which do not have the proper "softvfp" 4031.75Sthorpej markings. ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES 4041.75Sthorpej WILL CONTINUE TO WORK PROPERLY. 4051.75Sthorpej 4061.75Sthorpej The only work-around for the problem is to recompile all of 4071.75Sthorpej the libraries on the system. The easiest way to do this for 4081.79Swiz system libraries is to install a binary snapshot; they are 4091.93Ssalo generally available on releng.NetBSD.org. Any packages you 4101.75Sthorpej have installed which supply libraries will have to be recompiled 4111.75Sthorpej if you wish to link new programs against those libraries. 4121.75Sthorpej 4131.75Sthorpej If you have questions about this matter, please contact 4141.93Ssalo port-arm@NetBSD.org. 4151.73Sprovos 4161.73Sprovos20021011: 4171.73Sprovos Systrace has been improved to support privilege elevation. 4181.73Sprovos Updating the kernel requires the userland part of systrace 4191.79Swiz to be rebuilt. 4201.72Sthorpej 4211.72Sthorpej20021010: 4221.72Sthorpej The config(8) grammar was changed to allow options to register 4231.72Sthorpej dependencies on attributes, as well as other options. Users 4241.72Sthorpej must update and reinstall usr.sbin/config before building a new 4251.72Sthorpej kernel. 4261.70Sthorpej 4271.70Sthorpej20021009: 4281.70Sthorpej A new attribute dependency syntax was introduced to config(8), 4291.70Sthorpej which is now used by the SCSI configuration description. Users 4301.71Swiz must update and reinstall usr.sbin/config before building a new 4311.70Sthorpej kernel. 4321.69Sthorpej 4331.69Sthorpej20021003: 4341.69Sthorpej Several changes have been made to the autoconfiguration 4351.69Sthorpej framework. Users must update and reinstall usr.sbin/config 4361.69Sthorpej before building a new kernel. 4371.74Sjschauma 4381.74Sjschauma20021001: 4391.74Sjschauma The i386mp branch has been merged. To compile a kernel, users 4401.74Sjschauma will need to add the option 'cpu* at mainbus?' to their configuration 4411.74Sjschauma file. Multiprocessor kernels will need 4421.74Sjschauma ioapic* at mainbus? apid ? 4431.74Sjschauma options MULTIPROCESSOR 4441.74Sjschauma options COM_MPLOCK 4451.68Slukem 4461.68Slukem20020922: 4471.68Slukem MKDYNAMICROOT=yes enabled by default, which means that 4481.68Slukem certain shared libraries are installed into /lib, the shared 4491.68Slukem linker is installed into /libexec, and all programs in /bin 4501.68Slukem and /sbin are dynamically linked. 4511.68Slukem If you do not use "make build", you should ensure that 4521.68Slukem you have the libraries and shared linker in the new locations, 4531.68Slukem with: 4541.68Slukem make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so 4551.67Slukem 4561.67Slukem20020917: 4571.67Slukem USE_NEW_TOOLCHAIN has been replaced with: 4581.67Slukem - TOOLCHAIN_MISSING -- set to "yes" on platforms for which 4591.67Slukem there is no working in-tree toolchain (hppa, ns32k, sh5, 4601.67Slukem x86_64). 4611.67Slukem - EXTERNAL_TOOLCHAIN -- if defined by the user, points to the 4621.79Swiz root of an external toolchain (e.g. /usr/local/gnu). This 4631.67Slukem enables the cross-build framework even for TOOLCHAIN_MISSING 4641.67Slukem platforms. 4651.66Sgehenna 4661.66Sgehenna20020906: 4671.66Sgehenna gehenna-devsw has been merged into the trunk. Need to update and 4681.79Swiz reinstall usr.sbin/config before building the kernel. 4691.65Slukem 4701.65Slukem20020822: 4711.65Slukem Crunched rescue tools (contents of /bin and /sbin, plus others) 4721.65Slukem are now provided in /rescue. 4731.65Slukem 4741.65Slukem To ensure that these are built statically linked (no matter 4751.65Slukem what the setting of LDSTATIC is), use a crunchgen(1) built 4761.65Slukem from sources newer than 20020820 (see the next entry). 4771.65Slukem 4781.65Slukem20020820: 4791.65Slukem crunchgen(1) changed to ensure that the generated program 4801.65Slukem is statically linked. 4811.65Slukem 4821.65Slukem Solution: update and reinstall usr.bin/crunch 4831.84Sgrant 4841.84Sgrant20020605: 4851.84Sgrant smmsp user/group has been added for sendmail. 4861.84Sgrant 4871.84Sgrant Add the following into /etc/group: 4881.84Sgrant 4891.84Sgrant smmsp:*:17: 4901.84Sgrant 4911.84Sgrant and the following to /etc/master.passwd (via vipw): 4921.84Sgrant 4931.84Sgrant smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin 4941.61Sitojun 4951.61Sitojun20020515: 4961.61Sitojun sshd user/group has been added. Need to hand add this in, or sshd 4971.61Sitojun will not let you log in (with default, or UsePrivlegeSeparation=yes) 4981.61Sitojun 4991.61Sitojun Add the following into /etc/group: 5001.61Sitojun 5011.61Sitojun sshd:*:16: 5021.61Sitojun 5031.61Sitojun and the following to /etc/master.passwd (via vipw): 5041.61Sitojun 5051.63Senami sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin 5061.61Sitojun 5071.79Swiz Also /var/chroot/sshd directory needs to be present (digged as part of 5081.79Swiz the build process). 5091.60Ssommerfe 5101.60Ssommerfe20020426: 5111.60Ssommerfe NBUILDJOBS obsoleted in favor of just using -j. 5121.59Slukem 5131.59Slukem20020426: 5141.59Slukem etc/postinstall added, which performs various checks for 5151.59Slukem configuration file updates and changes, and can fix most of 5161.59Slukem the problems identified. 5171.59Slukem This should make it much easier to upgrade a system's 5181.59Slukem configuration from earlier systems (as far back as NetBSD 1.5). 5191.56Slukem 5201.56Slukem20020320: 5211.79Swiz <bsd.lib.mk> needs a new install(1) for its "-a cmd" support. 5221.79Swiz Build and install at usr.bin/xinstall before the build. 5231.56Slukem 5241.55Sitojun20020319: 5251.79Swiz Raw IPv6 socket now makes strict checking for sa_family and sa_len 5261.79Swiz on send(2) operation. Be sure to have sbin/rtsol and usr.sbin/rtsold 5271.55Sitojun newer than November 2001 when you upgrade the kernel. 5281.55Sitojun 5291.54Sitojun20020311: 5301.54Sitojun ssh configuration files were moved from /etc to /etc/ssh. Beware 5311.54Sitojun if you restart your machine from remote. Note that sshd.conf needs 5321.54Sitojun to be changed (due to the use of "/etc" inside). 5331.54Sitojun 5341.54Sitojun20020223: 5351.53Smatt Users of the VAX port will need to rebuild and install gas 5361.53Smatt so it deal with the now present register prefix used in all 5371.53Smatt the VAX assembly files. 5381.53Smatt 5391.50Sitojun20020118: 5401.50Sitojun ntpd user/group has been added. Need to hand add this in or builds 5411.50Sitojun will break as mtree aborts early. 5421.50Sitojun 5431.50Sitojun Add the following into /etc/group: 5441.50Sitojun 5451.50Sitojun ntpd:*:15: 5461.50Sitojun 5471.50Sitojun and the following to /etc/master.passwd (via vipw): 5481.50Sitojun 5491.50Sitojun ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin 5501.50Sitojun 5511.49Sjmc20011207: 5521.49Sjmc If you're attempting to build a snapshot on sparc64 and are getting 5531.49Sjmc reloc errors from the toolchain groff binary this means your native 5541.49Sjmc toolchain has some broken C++ bits. 5551.49Sjmc 5561.49Sjmc To fix: 5571.49Sjmc 5581.49Sjmc Build a new toolchain (i.e. build.sh -t) 5591.49Sjmc Use the new toolchain to build and install natively (i.e. /usr/lib) 5601.49Sjmc 5611.49Sjmc gnu/lib/libgcc 5621.51Spooka gnu/lib/libstdc++ 5631.49Sjmc 5641.49Sjmc After this a snapshot will be able to be built. 5651.49Sjmc 5661.47Sjmc20011201: 5671.47Sjmc In order for a sparc64 build to work you must have a working awk. If 5681.47Sjmc you've built and installed a system with the new toolchain up to this 5691.52Swiz point you do not have a working awk as its ability to do floating 5701.47Sjmc point is broken. 5711.47Sjmc 5721.47Sjmc To build: 5731.47Sjmc 5741.47Sjmc remake and install gnu/lib/libgcc 5751.47Sjmc remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links 5761.48Sjmc against the new libgcc.a) 5771.47Sjmc 5781.46Sthorpej20011128: 5791.46Sthorpej Kernel config information was changed to use defflag in 5801.46Sthorpej the various "files" files. Bug fixes to config(8) are 5811.46Sthorpej required in order for this to work properly. Make sure 5821.46Sthorpej to build and install in usr.sbin/config before attempting 5831.46Sthorpej to build a new kernel. 5841.46Sthorpej 5851.45Syamt20011030: 5861.45Syamt libc/locale/wcstod.c now needs new lint(1). Update lint(1) 5871.45Syamt before building libc. 5881.43Smason 5891.44Stv20011029: 5901.44Stv The new document BUILDING.mdoc (view with nroff | more, or 5911.44Stv see pre-generated .txt and .html versions) describes the build 5921.44Stv procedure in great detail. BUILDING, and the USE_NEW_TOOLCHAIN 5931.44Stv build process, are intended in the long run to replace this 5941.44Stv manual update log. 5951.44Stv 5961.44Stv Users building a USE_NEW_TOOLCHAIN system should read the 5971.44Stv BUILDING document for caveats. Generally, BUILDING supersedes 5981.44Stv UPDATING for these systems, as tool updating is taken care of 5991.44Stv by the new build system. 6001.42Sperry 6011.42Sperry20011028: 6021.42Sperry src/etc/Makefile now needs install to be able to handle 6031.42Sperry symlinks that point to nowhere. A bug in install that 6041.42Sperry prevented this was corrected. 6051.42Sperry 6061.42Sperry Solution: update and reinstall usr.bin/xinstall 6071.42Sperry Better Solution: Use the new toolchain and it will just work 6081.42Sperry for you. 6091.40Slukem 6101.40Slukem20011006: 6111.40Slukem /etc/mtree/NetBSD.dist has been updated to take advantage of 6121.40Slukem absolute path support added to mtree(8). Older mtree(8)s don't 6131.40Slukem understand the format. 6141.40Slukem 6151.40Slukem Solution: update and reinstall usr.sbin/mtree 6161.39Sjmc 6171.39Sjmc20011004: 6181.39Sjmc Crunchgen has been updated to work via reach-over makefiles. Updating 6191.39Sjmc is suggested before running a snapshot build 6201.36Stv 6211.35Sthorpej20010915: 6221.35Sthorpej The new "ubcperf" code committed by Chuck Silvers removed 6231.35Sthorpej a header file, uvm/uvm_vnode.h. There may be stale .depend 6241.35Sthorpej files that still reference this file. 6251.35Sthorpej 6261.35Sthorpej Solution: "make cleandir && make dependall" in affected 6271.35Sthorpej directories. 6281.31Senami 6291.31Senami20010803: 6301.31Senami grep.info is now built from grep.texi using makeinfo. Since it 6311.31Senami requires makeinfo v4.0, you need to install new texinfo before 6321.31Senami building gnu/usr.bin/grep. To install new texinfo, please follow 6331.31Senami the instruction described in 20010726 entry. 6341.30Senami 6351.64Ssommerfe20010803: 6361.41Swiz (i386 only): i386 kernel now uses new instructions like 6371.111Ssimonb `fxsave' which old gas doesn't understand. To build the 6381.64Ssommerfe kernel successfully, you need to build and install a new toolchain, 6391.64Ssommerfe (i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" 6401.64Ssommerfe from your kernel configuration until you rebuild your userland. 6411.64Ssommerfe See 20011029 above and BUILDING file in this directory for more information. 6421.64Ssommerfe [updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled] 6431.29Sbjh21 6441.29Sbjh2120010731: 6451.29Sbjh21 Bootloader update on ELF platforms. DDB in kernels from before 6461.29Sbjh21 this will be unable to read symbol tables provided by newer 6471.29Sbjh21 bootloaders. 6481.27Sassar 6491.27Sassar20010726: 6501.27Sassar Texinfo was updated to 4.0. To avoid failures when trying to 6511.28Sassar build the included texinfo files, do: 6521.28Sassar 6531.28Sassar cd src/gnu/usr.bin/texinfo 6541.28Sassar make MKINFO=no dependall install 6551.25Sthorpej 6561.25Sthorpej20010718: 6571.25Sthorpej Enabled correct .init/.fini processing in crt0. The way this 6581.25Sthorpej was done was to change a -I directive to cc(1), which means 6591.25Sthorpej make(1) will have a stale dependency (it will be checking the 6601.25Sthorpej timestamp on the wrong "dot_init.h"). 6611.25Sthorpej 6621.25Sthorpej The symptom you will see is that new programs die with SIGSEGV 6631.25Sthorpej if you have a stale dependency. 6641.25Sthorpej 6651.25Sthorpej Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so 6661.25Sthorpej before starting your build. 6671.26Sthorpej 6681.26Sthorpej20010628: 6691.26Sthorpej A construct was added to uvm_page.h that uncovered a bug 6701.26Sthorpej in lint(1). If you get a warning/error about a non-portable 6711.26Sthorpej bitfield, update your lint(1) before proceeding. 6721.21Sjmc 6731.21Sjmc20010226: 6741.22Sjmc Added named user/group to system. Need to hand add this in or builds 6751.21Sjmc will break as mtree aborts early. 6761.21Sjmc 6771.21Sjmc To work around add by hand: 6781.21Sjmc 6791.21Sjmc named:*:14: 6801.21Sjmc 6811.22Sjmc to /etc/group and add: 6821.22Sjmc 6831.22Sjmc named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin 6841.22Sjmc 6851.22Sjmc to master.passwd (use vipw for instance if doing by hand). 6861.22Sjmc 6871.22Sjmc Now a make build should progress. 6881.18Sjmc 6891.18Sjmc20010219: 6901.52Swiz get/setprogname() added. Any hostprogs that may use this will need 6911.111Ssimonb to be bootstrapped manually until the host system is current. 6921.18Sjmc 6931.111Ssimonb Known problems: sys/arch/macppc/stand/fixcoff 6941.19Scgd usr.sbin/config (adding -DMAKE_BOOTSTRAP to 6951.19Scgd CFLAGS and rebuilding should work) 6961.20Sjmc usr.sbin/mdsetimage - Build a static copy if 6971.111Ssimonb building a snapshot before fully bootstrapped. 6981.15Schristos 6991.15Schristos20010204: 7001.15Schristos prepare the code to compile with stricter gcc flags. in 7011.15Schristos particular start eliminating redundant declarations. Yacc 7021.15Schristos needs to be installed before make build. 7031.10Schristos 7041.10Schristos20010114: 7051.10Schristos introduce .if commands(target) in make(1). You need to 7061.10Schristos bring everything up-to-date first, then without installing 7071.23Stron anything make and install in usr.bin/make, then proceed 7081.10Schristos with make build. 7091.9Ssommerfe 7101.9Ssommerfe20010101: 7111.9Ssommerfe bsd.subdir.mk committed 20001230 had a bug which caused 7121.9Ssommerfe afterinstall targets to run too soon; update again. 7131.8Ssommerfe 7141.8Ssommerfe20001230: 7151.8Ssommerfe New share/mk files needed to support .WAIT in SUBDIR variables. 7161.8Ssommerfe If you get make errors, 7171.8Ssommerfe (cd share/mk; make install) 7181.8Ssommerfe Also, PRINTOBJDIR has changed and is now used more heavily. 7191.6Sad 7201.6Sad20001019: 7211.7Sad The `ca' device driver has been replaced by `ld'; although the 7221.6Sad major and minor numbers haven't changed, you should update your /dev 7231.6Sad directory. 7241.1Sabs 7251.4Sitojun20000929: 7261.4Sitojun The following make directives are obsoleted. 7271.4Sitojun MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 7281.4Sitojun By default, RSA is built into libcrypto. IDEA and RC5 will not be 7291.16Swiz built into libcrypto. By using MKCRYPTO_{RC5,IDEA}, you can build 7301.4Sitojun additional library libcrypto_{idea,rc5}. 7311.1Sabs 7321.1Sabs 7331.1SabsHints for a more successful build: 7341.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7351.123Sjmc Use build.sh, but do not use its "expert mode": 7361.132Sjmmv This will automatically build the tools in the 7371.123Sjmc correct order, and it will keep the tools and the 7381.123Sjmc new build products from interfering with the running 7391.123Sjmc system. This will allow you to ignore most of the 7401.123Sjmc other advice in this file. 7411.2Smrg Build a new kernel first: 7421.2Smrg This makes sure that any new system calls or features 7431.2Smrg expected by the new userland will be present. This 7441.2Smrg helps to avoid critical errors when upgrading. 7451.1Sabs Use object directories: 7461.1Sabs This helps to keep stale object 7471.1Sabs files from polluting the build if a Makefile "forgets" 7481.1Sabs about one. It also makes it easier to clean up after 7491.1Sabs a build. It's also necessary if you want to use the 7501.1Sabs same source tree for multiple machines. 7511.123Sjmc To use object directories with build.sh: 7521.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 7531.123Sjmc To use object directories without using build.sh: 7541.1Sabs a) cd /usr/src ; make cleandir 7551.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 7561.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 7571.1Sabs d) cd /usr/src ; make build 7581.2Smrg Note that running "make obj" in a directory will create 7591.2Smrg in obj.$MACHINE directory. 7601.1Sabs Build to a DESTDIR: 7611.123Sjmc This helps to keep old installed files (especially libraries) 7621.123Sjmc from interfering with the new build. 7631.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 7641.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 7651.123Sjmc environment variable before running make build. It should be 7661.123Sjmc set to the pathname of an initially empty directory. 7671.123Sjmc Problems: if you do not use build.sh, you might need to 7681.123Sjmc update critical utilities without using DESTDIR since 7691.123Sjmc nothing is executed from what is installed in DESTDIR. 7701.123Sjmc (See critical utils, below.) 7711.1Sabs Build often: 7721.1Sabs This keeps critical utilities current enough to not choke 7731.1Sabs on any other part of the source tree that depends on up to 7741.123Sjmc date functionality. If you use build.sh, you should not have 7751.123Sjmc this problem. 7761.1Sabs 7771.1SabsWhat to do if things don't work: 7781.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7791.1SabsWhen things don't work there is usually a few things that commonly 7801.1Sabsshould be done. 7811.1Sabs 1) make includes 7821.1Sabs This should be done automatically by make build. 7831.1Sabs 2) cd share/mk && make install 7841.1Sabs Again, automatically done by make build. 7851.1Sabs 7861.1SabsFailsafe rebuild of a small part of the tree: 7871.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7881.1SabsTo make sure you rebuild something correctly you want to do 7891.1Sabssomething like the following: 7901.1Sabs 1) Make sure the includes and .mk files are up to date. 7911.1Sabs 2) Make sure any program used to build the particular 7921.1Sabs utility is up to date. (yacc, lex, etc...) 7931.1Sabs 3) cd ...path/to/util... 7941.1Sabs make cleandir 7951.1Sabs rm ...all obj directories... 7961.1Sabs make cleandir # yes, again 7971.1Sabs make obj 7981.1Sabs make depend && make 7991.1Sabs 8001.1SabsFailsafe rebuild of the entire tree: 8011.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8021.1SabsIf you really want to make sure the source tree is clean and 8031.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 8041.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 8051.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 8061.1Sabs 8071.1Sabs---cut here--- 8081.1Sabs#!/bin/sh 8091.1Sabs. /etc/mk.conf 8101.1Sabs 8111.58Slukemif [ -z $NETBSDSRCDIR ] ; then 8121.58Slukem NETBSDSRCDIR=/usr/src 8131.1Sabsfi 8141.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 8151.1Sabs echo Unable to find sources 8161.1Sabs exit 1 8171.1Sabsfi 8181.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 8191.1Sabs 8201.1Sabsif [ -z $BSDOBJDIR ] ; then 8211.1Sabs BSDOBJDIR=/usr/obj 8221.1Sabsfi 8231.1Sabsif [ -d $BSDOBJDIR ] ; then 8241.1Sabs rm -rf $BSDOBJDIR 8251.1Sabsfi 8261.1Sabs 8271.58Slukemcd $NETBSDSRCDIR && make cleandir 8281.1Sabs 8291.1Sabs---cut here--- 8301.1Sabs 8311.1SabsCritical utilities: 8321.1Sabs^^^^^^^^^^^^^^^^^^^ 8331.3Sitojun usr.bin/compile_et 8341.1Sabs usr.bin/make 8351.1Sabs usr.bin/yacc 8361.1Sabs usr.bin/lex 8371.11Slukem usr.bin/xlint 8381.142Sdrochner usr.bin/config 8391.1Sabs 8401.34SsimonbOther problems and possible solutions: 8411.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8421.1SabsSymptom:Complaints involving a Makefile. 8431.17SerhFix: Rebuild usr.bin/make: 8441.17Serh cd usr.bin/make && make && make install 8451.111Ssimonb Or, a failsafe method if that doesn't work: 8461.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 8471.17Serh 8481.1SabsFix: Make sure .mk files are up to date. 8491.1Sabs cd share/mk && make install 8501.2Smrg 8511.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 8521.142SdrochnerFix: Rebuild usr.bin/config 8531.1Sabs 8541.1SabsSymptom: 8551.1SabsFix: Rebuild usr.bin/yacc 8561.1Sabs 8571.1SabsSymptom: 8581.1SabsFix: Rebuild usr.bin/lex 8591.1Sabs 8601.1SabsSymptom: 8611.1SabsFix: rm /usr/lib/libbfd.a 8621.4Sitojun 8631.4SitojunSymptom:Obsolete intermediate files are used during compilation 8641.4SitojunFix: Try the following sequence of commands in the directory in question. 8651.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 8661.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 8671.4Sitojun may remain. The command tries to clean everything up) 8681.5Swiz 8691.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 8701.5SwizFix: Rebuild and install usr.bin/menuc 8711.12Sitojun 8721.12SitojunSymptom:mklocale not found during build in share/locale/ctype 8731.12SitojunFix: Build and install usr.bin/mklocale 8741.13Sdogcow 8751.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 8761.13SdogcowFix: Rebuild and install lib/libc 8771.13Sdogcow 8781.142SdrochnerSymptom:usr.bin/config fails to build. 8791.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8801.13Sdogcow 8811.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8821.19ScgdFix: Rebuild and install lib/libc 8831.24Sabs 8841.24SabsSymptom:lint does not understand the '-X' option 8851.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 886