UPDATING revision 1.138
11.138Slukem$NetBSD: UPDATING,v 1.138 2005/04/17 23:12:40 lukem 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.138Slukem20050417: 201.138Slukem postinstall(8) was moved from /etc to /usr/sbin and made part 211.138Slukem of the "base" set, to make it easier to invoke after an 221.138Slukem upgrade. 231.138Slukem 241.136Scube20050325: 251.136Scube pcppi(4) was separated in two devices, adding attimer(4). Be sure 261.136Scube to add a config line for an attimer(4) device in your kernel 271.136Scube configuration, or you won't be able to set the pitch of the beep 281.137Scube with wsconsctl. Depending on the default value for the pitch, you 291.137Scube might even not hear any more beep. Also, it is advised to attach both 301.137Scube devices the same way (i.e., both on isa or both on acpi) or the 311.137Scube pcppi(4) device may fail to find the attimer(4) one. 321.136Scube 331.135Sjmc20050211: 341.135Sjmc Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in 351.135Sjmc some of the cross tools to fail if they use configure. Some configure's 361.135Sjmc cache the environment passed in and notice the new environment is 371.135Sjmc different and abort. Doing a clean in tools/ should be enough to 381.135Sjmc make a build continue. 391.135Sjmc 401.134Schristos20050109: 411.134Schristos Since su is using pam by default now, make sure that you have 421.134Schristos /etc/pam.d populated (postinstall will do that automatically 431.134Schristos for you). Otherwise su will fail open (i.e. will not require 441.134Schristos a password). 451.134Schristos 461.133Schristos20041229: 471.133Schristos Make had a path resolution bug that manifested itself as not 481.133Schristos being able to install openpam.3. This bug has been fixed, but 491.133Schristos you might need to rebuild make manually first to get through 501.133Schristos the build. 511.133Schristos 521.130Schristos20041201: 531.130Schristos Userland programs have been changed to use /dev/bpf instead of 541.130Schristos /dev/bpfX. You need to create that device by installing a new 551.131Swiz MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]* 561.99Smrg 571.129Sjmc20041006: 581.129Sjmc 591.129Sjmc A bug was introduced into /bin/sh (var.c rev 1.35) which causes 601.129Sjmc variables to not export correctly to subshells in all cases. This 611.129Sjmc will cause builds to break if that version of /bin/sh is installed 621.129Sjmc on the system. The proper version of /bin/sh can be verified with: 631.129Sjmc 641.129Sjmc ident /bin/sh | grep var 651.129Sjmc 661.129Sjmc Any /bin/sh w. version 1.35 will not work and needs to be updated 671.129Sjmc before attempting a build. 681.129Sjmc 691.127Schristos20041001: 701.127Schristos The ipfilter kernel sources moved from sys/netinet to 711.127Schristos dist/sys/ipf/netinet. Due to the move some Makefile 721.127Schristos dependencies are now dangling requiring a make cleandir 731.128She before they work again (kdump, ktruss, rescue, ipf, and 741.128She ftp-proxy are the victims). 751.127Schristos 761.125Satatat20040715: 771.125Satatat The rc.d/sendmail script now uses a heuristic to determine 781.125Satatat if sendmail should be started at boot time. It checks the 791.125Satatat contents of /etc/mailer.conf, /etc/mail/submit.cf, and the 801.125Satatat owner and mode of the sendmail binary to see if any changes 811.125Satatat to the mail infrastructure have been made. If no changes 821.125Satatat are detected, it will start an SMTP listener. 831.125Satatat 841.125Satatat Setting sendmail=NO in /etc/rc.conf will override this. 851.125Satatat 861.125Satatat If you are only using sendmail by default and only for 871.125Satatat local delivery, it is important that you also update your 881.125Satatat sendmail.cf so that the SMTP listener only listens on the 891.125Satatat loopback interface. 901.125Satatat 911.125Satatat20040715: 921.125Satatat The method by which athhal-elf.o gets pulled into i386 931.125Satatat kernel builds has been changed again. The latest version 941.125Satatat of bsd.files.mk is no longer required. 951.125Satatat 961.124Sjmc20040621: 971.124Sjmc Due to the recent rototill of tools/compat it's crucial one starts 981.124Sjmc from a clean objdir under tools/*. 991.124Sjmc 1001.124Sjmc This is mostly due to generated files (yacc and lex sources) needing 1011.125Satatat to be generated with new rules from bsd.hostprog.mk. 1021.124Sjmc 1031.124Sjmc The safest course is to rm -rf all objects under tools before building. 1041.124Sjmc 1051.121Slukem20040516: 1061.121Slukem The end-user modifiable X11 configuration has been moved 1071.121Slukem from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>. 1081.121Slukem Ensure that src and xsrc is up to date, and run 1091.121Slukem "make cleandir" in src/x11 before your next build. 1101.121Slukem 1111.126Slukem postinstall currently doesn't migrate the files from 1121.126Slukem /usr/X11R6/lib/X11/* to /etc/X11/* although it does 1131.126Slukem detect that this needs to occur, so you'll have to 1141.126Slukem manually move these files yourself. 1151.126Slukem 1161.119Satatat20040426: 1171.119Satatat Support for the original dynamic sysctl node structure has 1181.119Satatat been removed in favor of the newer layout. This affects 1191.119Satatat consumers of the create and delete interface, as well as 1201.119Satatat the dynamic discovery mechanism. This is believed only to 1211.119Satatat be the sysctl(8) binary itself, at this point in time, so 1221.119Satatat the only effect of this should be that a sysctl binary 1231.119Satatat built from sources dated between 2003/12/04 and 2004/03/24 1241.119Satatat will not work on a kernel built from sources dated after 1251.119Satatat 2004/04/25. If you need a new sysctl binary but build.sh 1261.119Satatat does not work, make sure that your revision of 1271.120Satatat src/sys/sys/sysctl.h is 1.112 (or later), and then the 1281.120Satatat do the following: 1291.119Satatat 1301.120Satatat cd /usr/src (or wherever your source tree is) 1311.120Satatat make USETOOLS=no includes 1321.120Satatat cd lib/libc 1331.120Satatat make USETOOLS=no dependall install 1341.120Satatat cd ../../sbin/sysctl 1351.119Satatat make USETOOLS=no dependall install 1361.119Satatat 1371.122Sitojun If you are using older sysctl binary, GNU autoconf would fail to 1381.122Sitojun identify your machine architecture, and tries to build binary for 1391.122Sitojun "unknown-unknown-netbsd20F" or something like that. if that happens, 1401.122Sitojun make sure to follow the above steps. 1411.122Sitojun 1421.118Sdbj20040425: 1431.118Sdbj The ffs superblock issues listed below under 20040109 and 20030402 1441.118Sdbj are now automatically addressed by the /etc/rc.d/fixsb script or by 1451.118Sdbj sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 1461.118Sdbj invocation mentioned below will continue to work and is now 1471.118Sdbj automated by those scripts. Note that under certain circumstances, 1481.118Sdbj affected filesystems upgraded to a -current kernel first before 1491.118Sdbj upgrading their userland with the fixsb and fsck_ffs fixes may 1501.118Sdbj encounter a 'freeing free inode' panic when writing to the affected 1511.118Sdbj filesystem, so it is a good idea to repair the filesystem as soon as 1521.118Sdbj possible. For more details on the fixsb script, see pr install/25138. 1531.118Sdbj 1541.115Schristos20040418: 1551.121Slukem statfs(2) and friends have been replaced with statvfs(2). Before 1561.115Schristos installing a newly build userland make sure that you are running 1571.115Schristos a newly built kernel with COMPAT_20 set. In addition your libc 1581.115Schristos build might not work (undefined SYS_statfs symbol) because make 1591.115Schristos clean does not know how to remove files it does not know about 1601.116Schristos anymore. Manually remove all generated .S sources and objects 1611.116Schristos from the libc build directory. 1621.115Schristos 1631.114Sjmc20040326: 1641.114Sjmc The method by which athhal-elf.o gets pulled into i386 kernel builds 1651.117Sjmc has been changed. The file is now stored as a uuencoded file in CVS 1661.114Sjmc and the generated Makefile will use the new .uue rules from bsd.file.mk 1671.114Sjmc to build it. 1681.114Sjmc 1691.114Sjmc This means you must have the latest bsd.files.mk installed when 1701.114Sjmc building a kernel without USETOOLS=yes. 1711.114Sjmc 1721.113Sdan20040318: 1731.113Sdan A bug in the cgd(4) blowfish code was corrected, without 1741.113Sdan provision of backwards compatibility, after several public 1751.113Sdan notices over several months. Users of cgd with blowfish cipher 1761.113Sdan ONLY must dump their data before updating their kernels, and 1771.113Sdan recreate cgd's and restore data using the new kernel. See 1781.113Sdan (recent message to current-users, URL when mail-index has updated) 1791.113Sdan 1801.108Sbjh2120040313: 1811.108Sbjh21 On acorn32, the opms and qms drivers have been withdrawn, and 1821.108Sbjh21 the old wsqms driver is now called qms. Kernel config files 1831.108Sbjh21 will need updating. See the ones in sys/arch/acorn32/conf 1841.108Sbjh21 for examples. 1851.108Sbjh21 1861.106Sbjh2120040125: 1871.106Sbjh21 On acorn32, the beep and sysbeep devices are no longer 1881.106Sbjh21 needed, and will need to be deleted from kernel configuration 1891.106Sbjh21 files. 1901.105Sbjh21 1911.102Sdbj20040109: 1921.102Sdbj Compatibility for old ffs superblock layouts has been 1931.102Sdbj added, and the restrictive fsck checks have been reenabled 1941.102Sdbj when using those layouts. If you have been using -current 1951.102Sdbj since 20030402, you may find that fsck again signals fatal 1961.110Sdbj superblock mismatches. To repair, make sure you have 1971.111Ssimonb an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 1981.109Sdbj to complete the filesystem upgrade. A message has 1991.111Ssimonb been added to the kernel which should detect this problem. 2001.111Ssimonb See the following discussion for more information: 2011.112Skeihan http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html 2021.102Sdbj 2031.99Smrg20031203: 2041.100Skeihan New binutils builds may fail due to old dependencies. 2051.99Smrg It's necessary to "make cleandir" to ensure that 2061.99Smrg the dependencies will be rebuilt correctly. 2071.98Swiz 2081.98Swiz20031111: 2091.98Swiz A newer mkdep is needed. Error noting that is 2101.98Swiz cc: Ambiguous abbreviation -- 2111.97Slukem 2121.97Slukem20031008: 2131.97Slukem /usr/include/sys/disklabel_mbr.h was removed. 2141.97Slukem It's necessary to "make cleandir" to ensure that 2151.97Slukem the dependencies will be rebuilt correctly. 2161.96Schristos 2171.109Sdbj20031007: 2181.111Ssimonb A sign exension bug was fixed which set all the high bits 2191.111Ssimonb of our newly expanded ffs fs_flags. This should only 2201.111Ssimonb affect users who installed or upgraded in September of 2003. 2211.109Sdbj A small utility program was posted to tech-kern which 2221.111Ssimonb should fix this problem, and a warning message was added 2231.111Ssimonb to the kernel which should discover and warn about it. See 2241.111Ssimonb http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html 2251.109Sdbj 2261.96Schristos20030906: 2271.96Schristos With the addition of siginfo support the old signal trampoline 2281.96Schristos code has been deprecated to COMPAT_16. Make sure that your running 2291.96Schristos kernel has COMPAT_16 enabled before building userland. 2301.94Schristos 2311.94Schristos20030801: 2321.95Swiz With the new openssl, there is some header and library shuffling. 2331.94Schristos rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \ 2341.95Swiz /usr/lib/libdes* before building. 2351.92Swiz 2361.92Swiz20030703: 2371.92Swiz Texinfo was updated to 4.6. To avoid failures when trying to 2381.92Swiz build the included texinfo files, do: 2391.92Swiz 2401.92Swiz cd src/gnu/usr.bin/texinfo 2411.92Swiz make MKINFO=no dependall install 2421.90Swiz 2431.90Swiz20030630: 2441.101Sjunyoung Groff was updated to 1.19; it's probably necessary to do 2451.91Swiz cd share/mk && make install 2461.90Swiz cd src/gnu/usr.bin/groff 2471.90Swiz make MKMAN=no dependall install 2481.90Swiz (untested). 2491.89Schristos 2501.89Schristos20030516: 2511.89Schristos Due to bugs in the export handling code, invalid export lines 2521.89Schristos were accepted before and caused the kernel to panic when 2531.89Schristos mountd got restarted because it freed memory that had already 2541.89Schristos been freed. This has been fixed and the kernel checks 2551.89Schristos export addresses very strictly. If you upgrade your kernel, 2561.89Schristos make sure you also upgrade mountd, because if your export 2571.89Schristos file contains lines with an old inet4 address syntax (i.e. 2581.89Schristos a.b.c or a.b or a), they will get rejected by the new kernel. 2591.87Sbjh21 2601.87Sbjh2120030402: 2611.87Sbjh21 The superblock layout for FFS was changed. If you have 1.6 2621.87Sbjh21 fsck binaries, they will signal a fatal superblock mismatch 2631.87Sbjh21 with the first alternate, because they compare too many 2641.87Sbjh21 fields (even ones that aren't useful). If possible, upgrade 2651.87Sbjh21 your fsck_ffs binary before using a new kernel. 2661.87Sbjh21 None of this signals actual filesystem damage. 2671.85Satatat 2681.85Satatat20030324: 2691.85Satatat sendmail version 8.12.8 was imported. Since sendmail is 2701.85Satatat now setgid to the smmsp group, and runs in "collection" 2711.85Satatat mode for most common activities, there is a new config 2721.85Satatat file called submit.cf that needs to live in /etc/mail. 2731.85Satatat The generic submit.cf sample in /usr/share/sendmail/cf 2741.85Satatat is named netbsd-msp.cf. Upgrading your regular sendmail 2751.85Satatat configuration file is also strongly advised. 2761.85Satatat 2771.85Satatat See the section named "MESSAGE SUBMISSION PROGRAM" in 2781.85Satatat the updated /usr/share/sendmail/README file for more 2791.85Satatat information. 2801.82Swiz 2811.82Swiz20030117: 2821.82Swiz Texinfo was updated to 4.3. To avoid failures when trying to 2831.82Swiz build the included texinfo files, do: 2841.82Swiz 2851.82Swiz cd src/gnu/usr.bin/texinfo 2861.82Swiz make MKINFO=no dependall install 2871.81Slukem 2881.81Slukem20021223: 2891.81Slukem The METALOG format changed slightly, to remove the leading 2901.81Slukem "${DESTDIR}" from path names. 2911.81Slukem This only affects people building with UNPRIVED. 2921.81Slukem For complete safety, remove the DESTDIR entirely and 2931.81Slukem update tools/mtree, before running make build. 2941.88Sitojun 2951.88Sitojun20021219: 2961.88Sitojun CVS repository layout was changed. See the following for details 2971.88Sitojun if you are using (anonymous) cvs to update your tree. 2981.88Sitojun 2991.93Ssalo http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html 3001.80Slukem 3011.80Slukem20021219: 3021.80Slukem install(1) had a '-N dbdir' option added, to specify an 3031.80Slukem alternate location to look up users & groups (instead 3041.80Slukem of the host system passwd(5) and group(5) databases). 3051.80Slukem 3061.80Slukem The build system was modified to take advantage of 3071.80Slukem this option (using ${NETBSDSRCDIR}/etc), so if you 3081.83Skei use USETOOLS==no, you may have to rebuild and 3091.80Slukem reinstall usr.bin/xinstall first. 3101.78Slukem 3111.78Slukem20021130: 3121.78Slukem fparseln(3) moved from libutil to libc. 3131.78Slukem If building to DESTDIR=/, reinstall the includes 3141.78Slukem and rebuild libc: 3151.78Slukem make includes 3161.78Slukem make do-lib-libc 3171.78Slukem If using build.sh, "cd tools/compat && make clean" 3181.78Slukem before rebuilding the tools. 3191.77Slukem 3201.77Slukem20021126: 3211.77Slukem The mk.conf(5) variable SYS_INCLUDE has been deprecated, 3221.77Slukem including the optional "SYS_INCLUDE=symlinks" support. 3231.77Slukem All header files, including <sys/*.h> are copied into 3241.77Slukem /usr/include. 3251.76Sthorpej 3261.76Sthorpej20021121: 3271.76Sthorpej The C run-time support files crtbegin.o and crtend.o 3281.76Sthorpej (and their companions crtbeginS.o and crtendS.o) were 3291.76Sthorpej split up, with new crti.o and crtn.o files resulting. 3301.76Sthorpej This means that libtool needs to be rebuilt once the 3311.76Sthorpej new libraries are installed. The process of rebuilding 3321.76Sthorpej libtool will cause it to automatically notice the new 3331.76Sthorpej required files, but it *must* be rebuilt in order to 3341.76Sthorpej do this. 3351.76Sthorpej 3361.76Sthorpej An out-of-date libtool will result in shared libraries 3371.76Sthorpej which lack _init() and _fini() routines, which means that 3381.76Sthorpej their global contructors/destructors will not be invoked. 3391.75Sthorpej 3401.75Sthorpej20021121: 3411.75Sthorpej A bug related to how ARM ELF objects were tagged has been 3421.75Sthorpej corrected. 3431.75Sthorpej 3441.75Sthorpej NetBSD ARM ELF uses the soft-VFP floating point model by 3451.75Sthorpej default. However, the assembler lacked support for marking 3461.75Sthorpej objects as using the VFP floating point format, and the 3471.79Swiz compiler was not properly passing the flag indicating "soft-VFP" 3481.75Sthorpej to the assembler. 3491.75Sthorpej 3501.75Sthorpej Unfortunately, this means that the linker will now consider 3511.75Sthorpej old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be 3521.75Sthorpej incompatible with new (properly marked) objects. 3531.75Sthorpej 3541.75Sthorpej The problem will only manifest itself if you attempt to compile 3551.75Sthorpej a new program using the fixed toolchain, and link that program 3561.75Sthorpej against old libraries which do not have the proper "softvfp" 3571.75Sthorpej markings. ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES 3581.75Sthorpej WILL CONTINUE TO WORK PROPERLY. 3591.75Sthorpej 3601.75Sthorpej The only work-around for the problem is to recompile all of 3611.75Sthorpej the libraries on the system. The easiest way to do this for 3621.79Swiz system libraries is to install a binary snapshot; they are 3631.93Ssalo generally available on releng.NetBSD.org. Any packages you 3641.75Sthorpej have installed which supply libraries will have to be recompiled 3651.75Sthorpej if you wish to link new programs against those libraries. 3661.75Sthorpej 3671.75Sthorpej If you have questions about this matter, please contact 3681.93Ssalo port-arm@NetBSD.org. 3691.73Sprovos 3701.73Sprovos20021011: 3711.73Sprovos Systrace has been improved to support privilege elevation. 3721.73Sprovos Updating the kernel requires the userland part of systrace 3731.79Swiz to be rebuilt. 3741.72Sthorpej 3751.72Sthorpej20021010: 3761.72Sthorpej The config(8) grammar was changed to allow options to register 3771.72Sthorpej dependencies on attributes, as well as other options. Users 3781.72Sthorpej must update and reinstall usr.sbin/config before building a new 3791.72Sthorpej kernel. 3801.70Sthorpej 3811.70Sthorpej20021009: 3821.70Sthorpej A new attribute dependency syntax was introduced to config(8), 3831.70Sthorpej which is now used by the SCSI configuration description. Users 3841.71Swiz must update and reinstall usr.sbin/config before building a new 3851.70Sthorpej kernel. 3861.69Sthorpej 3871.69Sthorpej20021003: 3881.69Sthorpej Several changes have been made to the autoconfiguration 3891.69Sthorpej framework. Users must update and reinstall usr.sbin/config 3901.69Sthorpej before building a new kernel. 3911.74Sjschauma 3921.74Sjschauma20021001: 3931.74Sjschauma The i386mp branch has been merged. To compile a kernel, users 3941.74Sjschauma will need to add the option 'cpu* at mainbus?' to their configuration 3951.74Sjschauma file. Multiprocessor kernels will need 3961.74Sjschauma ioapic* at mainbus? apid ? 3971.74Sjschauma options MULTIPROCESSOR 3981.74Sjschauma options COM_MPLOCK 3991.68Slukem 4001.68Slukem20020922: 4011.68Slukem MKDYNAMICROOT=yes enabled by default, which means that 4021.68Slukem certain shared libraries are installed into /lib, the shared 4031.68Slukem linker is installed into /libexec, and all programs in /bin 4041.68Slukem and /sbin are dynamically linked. 4051.68Slukem If you do not use "make build", you should ensure that 4061.68Slukem you have the libraries and shared linker in the new locations, 4071.68Slukem with: 4081.68Slukem make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so 4091.67Slukem 4101.67Slukem20020917: 4111.67Slukem USE_NEW_TOOLCHAIN has been replaced with: 4121.67Slukem - TOOLCHAIN_MISSING -- set to "yes" on platforms for which 4131.67Slukem there is no working in-tree toolchain (hppa, ns32k, sh5, 4141.67Slukem x86_64). 4151.67Slukem - EXTERNAL_TOOLCHAIN -- if defined by the user, points to the 4161.79Swiz root of an external toolchain (e.g. /usr/local/gnu). This 4171.67Slukem enables the cross-build framework even for TOOLCHAIN_MISSING 4181.67Slukem platforms. 4191.66Sgehenna 4201.66Sgehenna20020906: 4211.66Sgehenna gehenna-devsw has been merged into the trunk. Need to update and 4221.79Swiz reinstall usr.sbin/config before building the kernel. 4231.65Slukem 4241.65Slukem20020822: 4251.65Slukem Crunched rescue tools (contents of /bin and /sbin, plus others) 4261.65Slukem are now provided in /rescue. 4271.65Slukem 4281.65Slukem To ensure that these are built statically linked (no matter 4291.65Slukem what the setting of LDSTATIC is), use a crunchgen(1) built 4301.65Slukem from sources newer than 20020820 (see the next entry). 4311.65Slukem 4321.65Slukem20020820: 4331.65Slukem crunchgen(1) changed to ensure that the generated program 4341.65Slukem is statically linked. 4351.65Slukem 4361.65Slukem Solution: update and reinstall usr.bin/crunch 4371.84Sgrant 4381.84Sgrant20020605: 4391.84Sgrant smmsp user/group has been added for sendmail. 4401.84Sgrant 4411.84Sgrant Add the following into /etc/group: 4421.84Sgrant 4431.84Sgrant smmsp:*:17: 4441.84Sgrant 4451.84Sgrant and the following to /etc/master.passwd (via vipw): 4461.84Sgrant 4471.84Sgrant smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin 4481.61Sitojun 4491.61Sitojun20020515: 4501.61Sitojun sshd user/group has been added. Need to hand add this in, or sshd 4511.61Sitojun will not let you log in (with default, or UsePrivlegeSeparation=yes) 4521.61Sitojun 4531.61Sitojun Add the following into /etc/group: 4541.61Sitojun 4551.61Sitojun sshd:*:16: 4561.61Sitojun 4571.61Sitojun and the following to /etc/master.passwd (via vipw): 4581.61Sitojun 4591.63Senami sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin 4601.61Sitojun 4611.79Swiz Also /var/chroot/sshd directory needs to be present (digged as part of 4621.79Swiz the build process). 4631.60Ssommerfe 4641.60Ssommerfe20020426: 4651.60Ssommerfe NBUILDJOBS obsoleted in favor of just using -j. 4661.59Slukem 4671.59Slukem20020426: 4681.59Slukem etc/postinstall added, which performs various checks for 4691.59Slukem configuration file updates and changes, and can fix most of 4701.59Slukem the problems identified. 4711.59Slukem This should make it much easier to upgrade a system's 4721.59Slukem configuration from earlier systems (as far back as NetBSD 1.5). 4731.56Slukem 4741.56Slukem20020320: 4751.79Swiz <bsd.lib.mk> needs a new install(1) for its "-a cmd" support. 4761.79Swiz Build and install at usr.bin/xinstall before the build. 4771.56Slukem 4781.55Sitojun20020319: 4791.79Swiz Raw IPv6 socket now makes strict checking for sa_family and sa_len 4801.79Swiz on send(2) operation. Be sure to have sbin/rtsol and usr.sbin/rtsold 4811.55Sitojun newer than November 2001 when you upgrade the kernel. 4821.55Sitojun 4831.54Sitojun20020311: 4841.54Sitojun ssh configuration files were moved from /etc to /etc/ssh. Beware 4851.54Sitojun if you restart your machine from remote. Note that sshd.conf needs 4861.54Sitojun to be changed (due to the use of "/etc" inside). 4871.54Sitojun 4881.54Sitojun20020223: 4891.53Smatt Users of the VAX port will need to rebuild and install gas 4901.53Smatt so it deal with the now present register prefix used in all 4911.53Smatt the VAX assembly files. 4921.53Smatt 4931.50Sitojun20020118: 4941.50Sitojun ntpd user/group has been added. Need to hand add this in or builds 4951.50Sitojun will break as mtree aborts early. 4961.50Sitojun 4971.50Sitojun Add the following into /etc/group: 4981.50Sitojun 4991.50Sitojun ntpd:*:15: 5001.50Sitojun 5011.50Sitojun and the following to /etc/master.passwd (via vipw): 5021.50Sitojun 5031.50Sitojun ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin 5041.50Sitojun 5051.49Sjmc20011207: 5061.49Sjmc If you're attempting to build a snapshot on sparc64 and are getting 5071.49Sjmc reloc errors from the toolchain groff binary this means your native 5081.49Sjmc toolchain has some broken C++ bits. 5091.49Sjmc 5101.49Sjmc To fix: 5111.49Sjmc 5121.49Sjmc Build a new toolchain (i.e. build.sh -t) 5131.49Sjmc Use the new toolchain to build and install natively (i.e. /usr/lib) 5141.49Sjmc 5151.49Sjmc gnu/lib/libgcc 5161.51Spooka gnu/lib/libstdc++ 5171.49Sjmc 5181.49Sjmc After this a snapshot will be able to be built. 5191.49Sjmc 5201.47Sjmc20011201: 5211.47Sjmc In order for a sparc64 build to work you must have a working awk. If 5221.47Sjmc you've built and installed a system with the new toolchain up to this 5231.52Swiz point you do not have a working awk as its ability to do floating 5241.47Sjmc point is broken. 5251.47Sjmc 5261.47Sjmc To build: 5271.47Sjmc 5281.47Sjmc remake and install gnu/lib/libgcc 5291.47Sjmc remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links 5301.48Sjmc against the new libgcc.a) 5311.47Sjmc 5321.46Sthorpej20011128: 5331.46Sthorpej Kernel config information was changed to use defflag in 5341.46Sthorpej the various "files" files. Bug fixes to config(8) are 5351.46Sthorpej required in order for this to work properly. Make sure 5361.46Sthorpej to build and install in usr.sbin/config before attempting 5371.46Sthorpej to build a new kernel. 5381.46Sthorpej 5391.45Syamt20011030: 5401.45Syamt libc/locale/wcstod.c now needs new lint(1). Update lint(1) 5411.45Syamt before building libc. 5421.43Smason 5431.44Stv20011029: 5441.44Stv The new document BUILDING.mdoc (view with nroff | more, or 5451.44Stv see pre-generated .txt and .html versions) describes the build 5461.44Stv procedure in great detail. BUILDING, and the USE_NEW_TOOLCHAIN 5471.44Stv build process, are intended in the long run to replace this 5481.44Stv manual update log. 5491.44Stv 5501.44Stv Users building a USE_NEW_TOOLCHAIN system should read the 5511.44Stv BUILDING document for caveats. Generally, BUILDING supersedes 5521.44Stv UPDATING for these systems, as tool updating is taken care of 5531.44Stv by the new build system. 5541.42Sperry 5551.42Sperry20011028: 5561.42Sperry src/etc/Makefile now needs install to be able to handle 5571.42Sperry symlinks that point to nowhere. A bug in install that 5581.42Sperry prevented this was corrected. 5591.42Sperry 5601.42Sperry Solution: update and reinstall usr.bin/xinstall 5611.42Sperry Better Solution: Use the new toolchain and it will just work 5621.42Sperry for you. 5631.40Slukem 5641.40Slukem20011006: 5651.40Slukem /etc/mtree/NetBSD.dist has been updated to take advantage of 5661.40Slukem absolute path support added to mtree(8). Older mtree(8)s don't 5671.40Slukem understand the format. 5681.40Slukem 5691.40Slukem Solution: update and reinstall usr.sbin/mtree 5701.39Sjmc 5711.39Sjmc20011004: 5721.39Sjmc Crunchgen has been updated to work via reach-over makefiles. Updating 5731.39Sjmc is suggested before running a snapshot build 5741.36Stv 5751.35Sthorpej20010915: 5761.35Sthorpej The new "ubcperf" code committed by Chuck Silvers removed 5771.35Sthorpej a header file, uvm/uvm_vnode.h. There may be stale .depend 5781.35Sthorpej files that still reference this file. 5791.35Sthorpej 5801.35Sthorpej Solution: "make cleandir && make dependall" in affected 5811.35Sthorpej directories. 5821.31Senami 5831.31Senami20010803: 5841.31Senami grep.info is now built from grep.texi using makeinfo. Since it 5851.31Senami requires makeinfo v4.0, you need to install new texinfo before 5861.31Senami building gnu/usr.bin/grep. To install new texinfo, please follow 5871.31Senami the instruction described in 20010726 entry. 5881.30Senami 5891.64Ssommerfe20010803: 5901.41Swiz (i386 only): i386 kernel now uses new instructions like 5911.111Ssimonb `fxsave' which old gas doesn't understand. To build the 5921.64Ssommerfe kernel successfully, you need to build and install a new toolchain, 5931.64Ssommerfe (i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" 5941.64Ssommerfe from your kernel configuration until you rebuild your userland. 5951.64Ssommerfe See 20011029 above and BUILDING file in this directory for more information. 5961.64Ssommerfe [updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled] 5971.29Sbjh21 5981.29Sbjh2120010731: 5991.29Sbjh21 Bootloader update on ELF platforms. DDB in kernels from before 6001.29Sbjh21 this will be unable to read symbol tables provided by newer 6011.29Sbjh21 bootloaders. 6021.27Sassar 6031.27Sassar20010726: 6041.27Sassar Texinfo was updated to 4.0. To avoid failures when trying to 6051.28Sassar build the included texinfo files, do: 6061.28Sassar 6071.28Sassar cd src/gnu/usr.bin/texinfo 6081.28Sassar make MKINFO=no dependall install 6091.25Sthorpej 6101.25Sthorpej20010718: 6111.25Sthorpej Enabled correct .init/.fini processing in crt0. The way this 6121.25Sthorpej was done was to change a -I directive to cc(1), which means 6131.25Sthorpej make(1) will have a stale dependency (it will be checking the 6141.25Sthorpej timestamp on the wrong "dot_init.h"). 6151.25Sthorpej 6161.25Sthorpej The symptom you will see is that new programs die with SIGSEGV 6171.25Sthorpej if you have a stale dependency. 6181.25Sthorpej 6191.25Sthorpej Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so 6201.25Sthorpej before starting your build. 6211.26Sthorpej 6221.26Sthorpej20010628: 6231.26Sthorpej A construct was added to uvm_page.h that uncovered a bug 6241.26Sthorpej in lint(1). If you get a warning/error about a non-portable 6251.26Sthorpej bitfield, update your lint(1) before proceeding. 6261.21Sjmc 6271.21Sjmc20010226: 6281.22Sjmc Added named user/group to system. Need to hand add this in or builds 6291.21Sjmc will break as mtree aborts early. 6301.21Sjmc 6311.21Sjmc To work around add by hand: 6321.21Sjmc 6331.21Sjmc named:*:14: 6341.21Sjmc 6351.22Sjmc to /etc/group and add: 6361.22Sjmc 6371.22Sjmc named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin 6381.22Sjmc 6391.22Sjmc to master.passwd (use vipw for instance if doing by hand). 6401.22Sjmc 6411.22Sjmc Now a make build should progress. 6421.18Sjmc 6431.18Sjmc20010219: 6441.52Swiz get/setprogname() added. Any hostprogs that may use this will need 6451.111Ssimonb to be bootstrapped manually until the host system is current. 6461.18Sjmc 6471.111Ssimonb Known problems: sys/arch/macppc/stand/fixcoff 6481.19Scgd usr.sbin/config (adding -DMAKE_BOOTSTRAP to 6491.19Scgd CFLAGS and rebuilding should work) 6501.20Sjmc usr.sbin/mdsetimage - Build a static copy if 6511.111Ssimonb building a snapshot before fully bootstrapped. 6521.15Schristos 6531.15Schristos20010204: 6541.15Schristos prepare the code to compile with stricter gcc flags. in 6551.15Schristos particular start eliminating redundant declarations. Yacc 6561.15Schristos needs to be installed before make build. 6571.10Schristos 6581.10Schristos20010114: 6591.10Schristos introduce .if commands(target) in make(1). You need to 6601.10Schristos bring everything up-to-date first, then without installing 6611.23Stron anything make and install in usr.bin/make, then proceed 6621.10Schristos with make build. 6631.9Ssommerfe 6641.9Ssommerfe20010101: 6651.9Ssommerfe bsd.subdir.mk committed 20001230 had a bug which caused 6661.9Ssommerfe afterinstall targets to run too soon; update again. 6671.8Ssommerfe 6681.8Ssommerfe20001230: 6691.8Ssommerfe New share/mk files needed to support .WAIT in SUBDIR variables. 6701.8Ssommerfe If you get make errors, 6711.8Ssommerfe (cd share/mk; make install) 6721.8Ssommerfe Also, PRINTOBJDIR has changed and is now used more heavily. 6731.6Sad 6741.6Sad20001019: 6751.7Sad The `ca' device driver has been replaced by `ld'; although the 6761.6Sad major and minor numbers haven't changed, you should update your /dev 6771.6Sad directory. 6781.1Sabs 6791.4Sitojun20000929: 6801.4Sitojun The following make directives are obsoleted. 6811.4Sitojun MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 6821.4Sitojun By default, RSA is built into libcrypto. IDEA and RC5 will not be 6831.16Swiz built into libcrypto. By using MKCRYPTO_{RC5,IDEA}, you can build 6841.4Sitojun additional library libcrypto_{idea,rc5}. 6851.1Sabs 6861.1Sabs 6871.1SabsHints for a more successful build: 6881.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6891.123Sjmc Use build.sh, but do not use its "expert mode": 6901.132Sjmmv This will automatically build the tools in the 6911.123Sjmc correct order, and it will keep the tools and the 6921.123Sjmc new build products from interfering with the running 6931.123Sjmc system. This will allow you to ignore most of the 6941.123Sjmc other advice in this file. 6951.2Smrg Build a new kernel first: 6961.2Smrg This makes sure that any new system calls or features 6971.2Smrg expected by the new userland will be present. This 6981.2Smrg helps to avoid critical errors when upgrading. 6991.1Sabs Use object directories: 7001.1Sabs This helps to keep stale object 7011.1Sabs files from polluting the build if a Makefile "forgets" 7021.1Sabs about one. It also makes it easier to clean up after 7031.1Sabs a build. It's also necessary if you want to use the 7041.1Sabs same source tree for multiple machines. 7051.123Sjmc To use object directories with build.sh: 7061.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 7071.123Sjmc To use object directories without using build.sh: 7081.1Sabs a) cd /usr/src ; make cleandir 7091.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 7101.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 7111.1Sabs d) cd /usr/src ; make build 7121.2Smrg Note that running "make obj" in a directory will create 7131.2Smrg in obj.$MACHINE directory. 7141.1Sabs Build to a DESTDIR: 7151.123Sjmc This helps to keep old installed files (especially libraries) 7161.123Sjmc from interfering with the new build. 7171.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 7181.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 7191.123Sjmc environment variable before running make build. It should be 7201.123Sjmc set to the pathname of an initially empty directory. 7211.123Sjmc Problems: if you do not use build.sh, you might need to 7221.123Sjmc update critical utilities without using DESTDIR since 7231.123Sjmc nothing is executed from what is installed in DESTDIR. 7241.123Sjmc (See critical utils, below.) 7251.1Sabs Build often: 7261.1Sabs This keeps critical utilities current enough to not choke 7271.1Sabs on any other part of the source tree that depends on up to 7281.123Sjmc date functionality. If you use build.sh, you should not have 7291.123Sjmc this problem. 7301.1Sabs 7311.1SabsWhat to do if things don't work: 7321.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7331.1SabsWhen things don't work there is usually a few things that commonly 7341.1Sabsshould be done. 7351.1Sabs 1) make includes 7361.1Sabs This should be done automatically by make build. 7371.1Sabs 2) cd share/mk && make install 7381.1Sabs Again, automatically done by make build. 7391.1Sabs 7401.1SabsFailsafe rebuild of a small part of the tree: 7411.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7421.1SabsTo make sure you rebuild something correctly you want to do 7431.1Sabssomething like the following: 7441.1Sabs 1) Make sure the includes and .mk files are up to date. 7451.1Sabs 2) Make sure any program used to build the particular 7461.1Sabs utility is up to date. (yacc, lex, etc...) 7471.1Sabs 3) cd ...path/to/util... 7481.1Sabs make cleandir 7491.1Sabs rm ...all obj directories... 7501.1Sabs make cleandir # yes, again 7511.1Sabs make obj 7521.1Sabs make depend && make 7531.1Sabs 7541.1SabsFailsafe rebuild of the entire tree: 7551.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7561.1SabsIf you really want to make sure the source tree is clean and 7571.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 7581.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 7591.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 7601.1Sabs 7611.1Sabs---cut here--- 7621.1Sabs#!/bin/sh 7631.1Sabs. /etc/mk.conf 7641.1Sabs 7651.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7661.58Slukem NETBSDSRCDIR=/usr/src 7671.1Sabsfi 7681.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7691.1Sabs echo Unable to find sources 7701.1Sabs exit 1 7711.1Sabsfi 7721.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 7731.1Sabs 7741.1Sabsif [ -z $BSDOBJDIR ] ; then 7751.1Sabs BSDOBJDIR=/usr/obj 7761.1Sabsfi 7771.1Sabsif [ -d $BSDOBJDIR ] ; then 7781.1Sabs rm -rf $BSDOBJDIR 7791.1Sabsfi 7801.1Sabs 7811.58Slukemcd $NETBSDSRCDIR && make cleandir 7821.1Sabs 7831.1Sabs---cut here--- 7841.1Sabs 7851.1SabsCritical utilities: 7861.1Sabs^^^^^^^^^^^^^^^^^^^ 7871.1Sabs gnu/usr.bin/egcs 7881.3Sitojun usr.bin/compile_et 7891.1Sabs usr.bin/make 7901.1Sabs usr.bin/yacc 7911.1Sabs usr.bin/lex 7921.11Slukem usr.bin/xlint 7931.2Smrg usr.sbin/config 7941.1Sabs 7951.34SsimonbOther problems and possible solutions: 7961.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7971.1SabsSymptom:Unreasonable compiler errors. 7981.1SabsFix: Rebuild gnu/usr.bin/egcs 7991.1Sabs 8001.1SabsSymptom:Complaints involving a Makefile. 8011.17SerhFix: Rebuild usr.bin/make: 8021.17Serh cd usr.bin/make && make && make install 8031.111Ssimonb Or, a failsafe method if that doesn't work: 8041.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 8051.17Serh 8061.1SabsFix: Make sure .mk files are up to date. 8071.1Sabs cd share/mk && make install 8081.2Smrg 8091.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 8101.2SmrgFix: Rebuild usr.sbin/config 8111.1Sabs 8121.1SabsSymptom: 8131.1SabsFix: Rebuild usr.bin/yacc 8141.1Sabs 8151.1SabsSymptom: 8161.1SabsFix: Rebuild usr.bin/lex 8171.1Sabs 8181.1SabsSymptom: 8191.1SabsFix: rm /usr/lib/libbfd.a 8201.4Sitojun 8211.4SitojunSymptom:Obsolete intermediate files are used during compilation 8221.4SitojunFix: Try the following sequence of commands in the directory in question. 8231.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 8241.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 8251.4Sitojun may remain. The command tries to clean everything up) 8261.5Swiz 8271.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 8281.5SwizFix: Rebuild and install usr.bin/menuc 8291.12Sitojun 8301.12SitojunSymptom:mklocale not found during build in share/locale/ctype 8311.12SitojunFix: Build and install usr.bin/mklocale 8321.13Sdogcow 8331.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 8341.13SdogcowFix: Rebuild and install lib/libc 8351.13Sdogcow 8361.19ScgdSymptom:usr.sbin/config fails to build. 8371.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8381.13Sdogcow 8391.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8401.19ScgdFix: Rebuild and install lib/libc 8411.24Sabs 8421.24SabsSymptom:lint does not understand the '-X' option 8431.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 844