UPDATING revision 1.139
11.139Schristos$NetBSD: UPDATING,v 1.139 2005/05/31 18:42:44 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.123SjmcSee also: BUILDING, build.sh, Makefile. 151.1Sabs 161.1SabsRecent changes: 171.1Sabs^^^^^^^^^^^^^^^ 181.138Slukem 191.139Schristos20050531: 201.139Schristos genassym.sh(8) was moved to genassym(8). You need to either build 211.139Schristos tools first or install the version of genassym from /usr/sbin before 221.139Schristos you can build a kernel again. 231.139Schristos 241.138Slukem20050417: 251.138Slukem postinstall(8) was moved from /etc to /usr/sbin and made part 261.138Slukem of the "base" set, to make it easier to invoke after an 271.138Slukem upgrade. 281.138Slukem 291.136Scube20050325: 301.136Scube pcppi(4) was separated in two devices, adding attimer(4). Be sure 311.136Scube to add a config line for an attimer(4) device in your kernel 321.136Scube configuration, or you won't be able to set the pitch of the beep 331.137Scube with wsconsctl. Depending on the default value for the pitch, you 341.137Scube might even not hear any more beep. Also, it is advised to attach both 351.137Scube devices the same way (i.e., both on isa or both on acpi) or the 361.137Scube pcppi(4) device may fail to find the attimer(4) one. 371.136Scube 381.135Sjmc20050211: 391.135Sjmc Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in 401.135Sjmc some of the cross tools to fail if they use configure. Some configure's 411.135Sjmc cache the environment passed in and notice the new environment is 421.135Sjmc different and abort. Doing a clean in tools/ should be enough to 431.135Sjmc make a build continue. 441.135Sjmc 451.134Schristos20050109: 461.134Schristos Since su is using pam by default now, make sure that you have 471.134Schristos /etc/pam.d populated (postinstall will do that automatically 481.134Schristos for you). Otherwise su will fail open (i.e. will not require 491.134Schristos a password). 501.134Schristos 511.133Schristos20041229: 521.133Schristos Make had a path resolution bug that manifested itself as not 531.133Schristos being able to install openpam.3. This bug has been fixed, but 541.133Schristos you might need to rebuild make manually first to get through 551.133Schristos the build. 561.133Schristos 571.130Schristos20041201: 581.130Schristos Userland programs have been changed to use /dev/bpf instead of 591.130Schristos /dev/bpfX. You need to create that device by installing a new 601.131Swiz MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]* 611.99Smrg 621.129Sjmc20041006: 631.129Sjmc 641.129Sjmc A bug was introduced into /bin/sh (var.c rev 1.35) which causes 651.129Sjmc variables to not export correctly to subshells in all cases. This 661.129Sjmc will cause builds to break if that version of /bin/sh is installed 671.129Sjmc on the system. The proper version of /bin/sh can be verified with: 681.129Sjmc 691.129Sjmc ident /bin/sh | grep var 701.129Sjmc 711.129Sjmc Any /bin/sh w. version 1.35 will not work and needs to be updated 721.129Sjmc before attempting a build. 731.129Sjmc 741.127Schristos20041001: 751.127Schristos The ipfilter kernel sources moved from sys/netinet to 761.127Schristos dist/sys/ipf/netinet. Due to the move some Makefile 771.127Schristos dependencies are now dangling requiring a make cleandir 781.128She before they work again (kdump, ktruss, rescue, ipf, and 791.128She ftp-proxy are the victims). 801.127Schristos 811.125Satatat20040715: 821.125Satatat The rc.d/sendmail script now uses a heuristic to determine 831.125Satatat if sendmail should be started at boot time. It checks the 841.125Satatat contents of /etc/mailer.conf, /etc/mail/submit.cf, and the 851.125Satatat owner and mode of the sendmail binary to see if any changes 861.125Satatat to the mail infrastructure have been made. If no changes 871.125Satatat are detected, it will start an SMTP listener. 881.125Satatat 891.125Satatat Setting sendmail=NO in /etc/rc.conf will override this. 901.125Satatat 911.125Satatat If you are only using sendmail by default and only for 921.125Satatat local delivery, it is important that you also update your 931.125Satatat sendmail.cf so that the SMTP listener only listens on the 941.125Satatat loopback interface. 951.125Satatat 961.125Satatat20040715: 971.125Satatat The method by which athhal-elf.o gets pulled into i386 981.125Satatat kernel builds has been changed again. The latest version 991.125Satatat of bsd.files.mk is no longer required. 1001.125Satatat 1011.124Sjmc20040621: 1021.124Sjmc Due to the recent rototill of tools/compat it's crucial one starts 1031.124Sjmc from a clean objdir under tools/*. 1041.124Sjmc 1051.124Sjmc This is mostly due to generated files (yacc and lex sources) needing 1061.125Satatat to be generated with new rules from bsd.hostprog.mk. 1071.124Sjmc 1081.124Sjmc The safest course is to rm -rf all objects under tools before building. 1091.124Sjmc 1101.121Slukem20040516: 1111.121Slukem The end-user modifiable X11 configuration has been moved 1121.121Slukem from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>. 1131.121Slukem Ensure that src and xsrc is up to date, and run 1141.121Slukem "make cleandir" in src/x11 before your next build. 1151.121Slukem 1161.126Slukem postinstall currently doesn't migrate the files from 1171.126Slukem /usr/X11R6/lib/X11/* to /etc/X11/* although it does 1181.126Slukem detect that this needs to occur, so you'll have to 1191.126Slukem manually move these files yourself. 1201.126Slukem 1211.119Satatat20040426: 1221.119Satatat Support for the original dynamic sysctl node structure has 1231.119Satatat been removed in favor of the newer layout. This affects 1241.119Satatat consumers of the create and delete interface, as well as 1251.119Satatat the dynamic discovery mechanism. This is believed only to 1261.119Satatat be the sysctl(8) binary itself, at this point in time, so 1271.119Satatat the only effect of this should be that a sysctl binary 1281.119Satatat built from sources dated between 2003/12/04 and 2004/03/24 1291.119Satatat will not work on a kernel built from sources dated after 1301.119Satatat 2004/04/25. If you need a new sysctl binary but build.sh 1311.119Satatat does not work, make sure that your revision of 1321.120Satatat src/sys/sys/sysctl.h is 1.112 (or later), and then the 1331.120Satatat do the following: 1341.119Satatat 1351.120Satatat cd /usr/src (or wherever your source tree is) 1361.120Satatat make USETOOLS=no includes 1371.120Satatat cd lib/libc 1381.120Satatat make USETOOLS=no dependall install 1391.120Satatat cd ../../sbin/sysctl 1401.119Satatat make USETOOLS=no dependall install 1411.119Satatat 1421.122Sitojun If you are using older sysctl binary, GNU autoconf would fail to 1431.122Sitojun identify your machine architecture, and tries to build binary for 1441.122Sitojun "unknown-unknown-netbsd20F" or something like that. if that happens, 1451.122Sitojun make sure to follow the above steps. 1461.122Sitojun 1471.118Sdbj20040425: 1481.118Sdbj The ffs superblock issues listed below under 20040109 and 20030402 1491.118Sdbj are now automatically addressed by the /etc/rc.d/fixsb script or by 1501.118Sdbj sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 1511.118Sdbj invocation mentioned below will continue to work and is now 1521.118Sdbj automated by those scripts. Note that under certain circumstances, 1531.118Sdbj affected filesystems upgraded to a -current kernel first before 1541.118Sdbj upgrading their userland with the fixsb and fsck_ffs fixes may 1551.118Sdbj encounter a 'freeing free inode' panic when writing to the affected 1561.118Sdbj filesystem, so it is a good idea to repair the filesystem as soon as 1571.118Sdbj possible. For more details on the fixsb script, see pr install/25138. 1581.118Sdbj 1591.115Schristos20040418: 1601.121Slukem statfs(2) and friends have been replaced with statvfs(2). Before 1611.115Schristos installing a newly build userland make sure that you are running 1621.115Schristos a newly built kernel with COMPAT_20 set. In addition your libc 1631.115Schristos build might not work (undefined SYS_statfs symbol) because make 1641.115Schristos clean does not know how to remove files it does not know about 1651.116Schristos anymore. Manually remove all generated .S sources and objects 1661.116Schristos from the libc build directory. 1671.115Schristos 1681.114Sjmc20040326: 1691.114Sjmc The method by which athhal-elf.o gets pulled into i386 kernel builds 1701.117Sjmc has been changed. The file is now stored as a uuencoded file in CVS 1711.114Sjmc and the generated Makefile will use the new .uue rules from bsd.file.mk 1721.114Sjmc to build it. 1731.114Sjmc 1741.114Sjmc This means you must have the latest bsd.files.mk installed when 1751.114Sjmc building a kernel without USETOOLS=yes. 1761.114Sjmc 1771.113Sdan20040318: 1781.113Sdan A bug in the cgd(4) blowfish code was corrected, without 1791.113Sdan provision of backwards compatibility, after several public 1801.113Sdan notices over several months. Users of cgd with blowfish cipher 1811.113Sdan ONLY must dump their data before updating their kernels, and 1821.113Sdan recreate cgd's and restore data using the new kernel. See 1831.113Sdan (recent message to current-users, URL when mail-index has updated) 1841.113Sdan 1851.108Sbjh2120040313: 1861.108Sbjh21 On acorn32, the opms and qms drivers have been withdrawn, and 1871.108Sbjh21 the old wsqms driver is now called qms. Kernel config files 1881.108Sbjh21 will need updating. See the ones in sys/arch/acorn32/conf 1891.108Sbjh21 for examples. 1901.108Sbjh21 1911.106Sbjh2120040125: 1921.106Sbjh21 On acorn32, the beep and sysbeep devices are no longer 1931.106Sbjh21 needed, and will need to be deleted from kernel configuration 1941.106Sbjh21 files. 1951.105Sbjh21 1961.102Sdbj20040109: 1971.102Sdbj Compatibility for old ffs superblock layouts has been 1981.102Sdbj added, and the restrictive fsck checks have been reenabled 1991.102Sdbj when using those layouts. If you have been using -current 2001.102Sdbj since 20030402, you may find that fsck again signals fatal 2011.110Sdbj superblock mismatches. To repair, make sure you have 2021.111Ssimonb an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 2031.109Sdbj to complete the filesystem upgrade. A message has 2041.111Ssimonb been added to the kernel which should detect this problem. 2051.111Ssimonb See the following discussion for more information: 2061.112Skeihan http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html 2071.102Sdbj 2081.99Smrg20031203: 2091.100Skeihan New binutils builds may fail due to old dependencies. 2101.99Smrg It's necessary to "make cleandir" to ensure that 2111.99Smrg the dependencies will be rebuilt correctly. 2121.98Swiz 2131.98Swiz20031111: 2141.98Swiz A newer mkdep is needed. Error noting that is 2151.98Swiz cc: Ambiguous abbreviation -- 2161.97Slukem 2171.97Slukem20031008: 2181.97Slukem /usr/include/sys/disklabel_mbr.h was removed. 2191.97Slukem It's necessary to "make cleandir" to ensure that 2201.97Slukem the dependencies will be rebuilt correctly. 2211.96Schristos 2221.109Sdbj20031007: 2231.111Ssimonb A sign exension bug was fixed which set all the high bits 2241.111Ssimonb of our newly expanded ffs fs_flags. This should only 2251.111Ssimonb affect users who installed or upgraded in September of 2003. 2261.109Sdbj A small utility program was posted to tech-kern which 2271.111Ssimonb should fix this problem, and a warning message was added 2281.111Ssimonb to the kernel which should discover and warn about it. See 2291.111Ssimonb http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html 2301.109Sdbj 2311.96Schristos20030906: 2321.96Schristos With the addition of siginfo support the old signal trampoline 2331.96Schristos code has been deprecated to COMPAT_16. Make sure that your running 2341.96Schristos kernel has COMPAT_16 enabled before building userland. 2351.94Schristos 2361.94Schristos20030801: 2371.95Swiz With the new openssl, there is some header and library shuffling. 2381.94Schristos rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \ 2391.95Swiz /usr/lib/libdes* before building. 2401.92Swiz 2411.92Swiz20030703: 2421.92Swiz Texinfo was updated to 4.6. To avoid failures when trying to 2431.92Swiz build the included texinfo files, do: 2441.92Swiz 2451.92Swiz cd src/gnu/usr.bin/texinfo 2461.92Swiz make MKINFO=no dependall install 2471.90Swiz 2481.90Swiz20030630: 2491.101Sjunyoung Groff was updated to 1.19; it's probably necessary to do 2501.91Swiz cd share/mk && make install 2511.90Swiz cd src/gnu/usr.bin/groff 2521.90Swiz make MKMAN=no dependall install 2531.90Swiz (untested). 2541.89Schristos 2551.89Schristos20030516: 2561.89Schristos Due to bugs in the export handling code, invalid export lines 2571.89Schristos were accepted before and caused the kernel to panic when 2581.89Schristos mountd got restarted because it freed memory that had already 2591.89Schristos been freed. This has been fixed and the kernel checks 2601.89Schristos export addresses very strictly. If you upgrade your kernel, 2611.89Schristos make sure you also upgrade mountd, because if your export 2621.89Schristos file contains lines with an old inet4 address syntax (i.e. 2631.89Schristos a.b.c or a.b or a), they will get rejected by the new kernel. 2641.87Sbjh21 2651.87Sbjh2120030402: 2661.87Sbjh21 The superblock layout for FFS was changed. If you have 1.6 2671.87Sbjh21 fsck binaries, they will signal a fatal superblock mismatch 2681.87Sbjh21 with the first alternate, because they compare too many 2691.87Sbjh21 fields (even ones that aren't useful). If possible, upgrade 2701.87Sbjh21 your fsck_ffs binary before using a new kernel. 2711.87Sbjh21 None of this signals actual filesystem damage. 2721.85Satatat 2731.85Satatat20030324: 2741.85Satatat sendmail version 8.12.8 was imported. Since sendmail is 2751.85Satatat now setgid to the smmsp group, and runs in "collection" 2761.85Satatat mode for most common activities, there is a new config 2771.85Satatat file called submit.cf that needs to live in /etc/mail. 2781.85Satatat The generic submit.cf sample in /usr/share/sendmail/cf 2791.85Satatat is named netbsd-msp.cf. Upgrading your regular sendmail 2801.85Satatat configuration file is also strongly advised. 2811.85Satatat 2821.85Satatat See the section named "MESSAGE SUBMISSION PROGRAM" in 2831.85Satatat the updated /usr/share/sendmail/README file for more 2841.85Satatat information. 2851.82Swiz 2861.82Swiz20030117: 2871.82Swiz Texinfo was updated to 4.3. To avoid failures when trying to 2881.82Swiz build the included texinfo files, do: 2891.82Swiz 2901.82Swiz cd src/gnu/usr.bin/texinfo 2911.82Swiz make MKINFO=no dependall install 2921.81Slukem 2931.81Slukem20021223: 2941.81Slukem The METALOG format changed slightly, to remove the leading 2951.81Slukem "${DESTDIR}" from path names. 2961.81Slukem This only affects people building with UNPRIVED. 2971.81Slukem For complete safety, remove the DESTDIR entirely and 2981.81Slukem update tools/mtree, before running make build. 2991.88Sitojun 3001.88Sitojun20021219: 3011.88Sitojun CVS repository layout was changed. See the following for details 3021.88Sitojun if you are using (anonymous) cvs to update your tree. 3031.88Sitojun 3041.93Ssalo http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html 3051.80Slukem 3061.80Slukem20021219: 3071.80Slukem install(1) had a '-N dbdir' option added, to specify an 3081.80Slukem alternate location to look up users & groups (instead 3091.80Slukem of the host system passwd(5) and group(5) databases). 3101.80Slukem 3111.80Slukem The build system was modified to take advantage of 3121.80Slukem this option (using ${NETBSDSRCDIR}/etc), so if you 3131.83Skei use USETOOLS==no, you may have to rebuild and 3141.80Slukem reinstall usr.bin/xinstall first. 3151.78Slukem 3161.78Slukem20021130: 3171.78Slukem fparseln(3) moved from libutil to libc. 3181.78Slukem If building to DESTDIR=/, reinstall the includes 3191.78Slukem and rebuild libc: 3201.78Slukem make includes 3211.78Slukem make do-lib-libc 3221.78Slukem If using build.sh, "cd tools/compat && make clean" 3231.78Slukem before rebuilding the tools. 3241.77Slukem 3251.77Slukem20021126: 3261.77Slukem The mk.conf(5) variable SYS_INCLUDE has been deprecated, 3271.77Slukem including the optional "SYS_INCLUDE=symlinks" support. 3281.77Slukem All header files, including <sys/*.h> are copied into 3291.77Slukem /usr/include. 3301.76Sthorpej 3311.76Sthorpej20021121: 3321.76Sthorpej The C run-time support files crtbegin.o and crtend.o 3331.76Sthorpej (and their companions crtbeginS.o and crtendS.o) were 3341.76Sthorpej split up, with new crti.o and crtn.o files resulting. 3351.76Sthorpej This means that libtool needs to be rebuilt once the 3361.76Sthorpej new libraries are installed. The process of rebuilding 3371.76Sthorpej libtool will cause it to automatically notice the new 3381.76Sthorpej required files, but it *must* be rebuilt in order to 3391.76Sthorpej do this. 3401.76Sthorpej 3411.76Sthorpej An out-of-date libtool will result in shared libraries 3421.76Sthorpej which lack _init() and _fini() routines, which means that 3431.76Sthorpej their global contructors/destructors will not be invoked. 3441.75Sthorpej 3451.75Sthorpej20021121: 3461.75Sthorpej A bug related to how ARM ELF objects were tagged has been 3471.75Sthorpej corrected. 3481.75Sthorpej 3491.75Sthorpej NetBSD ARM ELF uses the soft-VFP floating point model by 3501.75Sthorpej default. However, the assembler lacked support for marking 3511.75Sthorpej objects as using the VFP floating point format, and the 3521.79Swiz compiler was not properly passing the flag indicating "soft-VFP" 3531.75Sthorpej to the assembler. 3541.75Sthorpej 3551.75Sthorpej Unfortunately, this means that the linker will now consider 3561.75Sthorpej old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be 3571.75Sthorpej incompatible with new (properly marked) objects. 3581.75Sthorpej 3591.75Sthorpej The problem will only manifest itself if you attempt to compile 3601.75Sthorpej a new program using the fixed toolchain, and link that program 3611.75Sthorpej against old libraries which do not have the proper "softvfp" 3621.75Sthorpej markings. ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES 3631.75Sthorpej WILL CONTINUE TO WORK PROPERLY. 3641.75Sthorpej 3651.75Sthorpej The only work-around for the problem is to recompile all of 3661.75Sthorpej the libraries on the system. The easiest way to do this for 3671.79Swiz system libraries is to install a binary snapshot; they are 3681.93Ssalo generally available on releng.NetBSD.org. Any packages you 3691.75Sthorpej have installed which supply libraries will have to be recompiled 3701.75Sthorpej if you wish to link new programs against those libraries. 3711.75Sthorpej 3721.75Sthorpej If you have questions about this matter, please contact 3731.93Ssalo port-arm@NetBSD.org. 3741.73Sprovos 3751.73Sprovos20021011: 3761.73Sprovos Systrace has been improved to support privilege elevation. 3771.73Sprovos Updating the kernel requires the userland part of systrace 3781.79Swiz to be rebuilt. 3791.72Sthorpej 3801.72Sthorpej20021010: 3811.72Sthorpej The config(8) grammar was changed to allow options to register 3821.72Sthorpej dependencies on attributes, as well as other options. Users 3831.72Sthorpej must update and reinstall usr.sbin/config before building a new 3841.72Sthorpej kernel. 3851.70Sthorpej 3861.70Sthorpej20021009: 3871.70Sthorpej A new attribute dependency syntax was introduced to config(8), 3881.70Sthorpej which is now used by the SCSI configuration description. Users 3891.71Swiz must update and reinstall usr.sbin/config before building a new 3901.70Sthorpej kernel. 3911.69Sthorpej 3921.69Sthorpej20021003: 3931.69Sthorpej Several changes have been made to the autoconfiguration 3941.69Sthorpej framework. Users must update and reinstall usr.sbin/config 3951.69Sthorpej before building a new kernel. 3961.74Sjschauma 3971.74Sjschauma20021001: 3981.74Sjschauma The i386mp branch has been merged. To compile a kernel, users 3991.74Sjschauma will need to add the option 'cpu* at mainbus?' to their configuration 4001.74Sjschauma file. Multiprocessor kernels will need 4011.74Sjschauma ioapic* at mainbus? apid ? 4021.74Sjschauma options MULTIPROCESSOR 4031.74Sjschauma options COM_MPLOCK 4041.68Slukem 4051.68Slukem20020922: 4061.68Slukem MKDYNAMICROOT=yes enabled by default, which means that 4071.68Slukem certain shared libraries are installed into /lib, the shared 4081.68Slukem linker is installed into /libexec, and all programs in /bin 4091.68Slukem and /sbin are dynamically linked. 4101.68Slukem If you do not use "make build", you should ensure that 4111.68Slukem you have the libraries and shared linker in the new locations, 4121.68Slukem with: 4131.68Slukem make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so 4141.67Slukem 4151.67Slukem20020917: 4161.67Slukem USE_NEW_TOOLCHAIN has been replaced with: 4171.67Slukem - TOOLCHAIN_MISSING -- set to "yes" on platforms for which 4181.67Slukem there is no working in-tree toolchain (hppa, ns32k, sh5, 4191.67Slukem x86_64). 4201.67Slukem - EXTERNAL_TOOLCHAIN -- if defined by the user, points to the 4211.79Swiz root of an external toolchain (e.g. /usr/local/gnu). This 4221.67Slukem enables the cross-build framework even for TOOLCHAIN_MISSING 4231.67Slukem platforms. 4241.66Sgehenna 4251.66Sgehenna20020906: 4261.66Sgehenna gehenna-devsw has been merged into the trunk. Need to update and 4271.79Swiz reinstall usr.sbin/config before building the kernel. 4281.65Slukem 4291.65Slukem20020822: 4301.65Slukem Crunched rescue tools (contents of /bin and /sbin, plus others) 4311.65Slukem are now provided in /rescue. 4321.65Slukem 4331.65Slukem To ensure that these are built statically linked (no matter 4341.65Slukem what the setting of LDSTATIC is), use a crunchgen(1) built 4351.65Slukem from sources newer than 20020820 (see the next entry). 4361.65Slukem 4371.65Slukem20020820: 4381.65Slukem crunchgen(1) changed to ensure that the generated program 4391.65Slukem is statically linked. 4401.65Slukem 4411.65Slukem Solution: update and reinstall usr.bin/crunch 4421.84Sgrant 4431.84Sgrant20020605: 4441.84Sgrant smmsp user/group has been added for sendmail. 4451.84Sgrant 4461.84Sgrant Add the following into /etc/group: 4471.84Sgrant 4481.84Sgrant smmsp:*:17: 4491.84Sgrant 4501.84Sgrant and the following to /etc/master.passwd (via vipw): 4511.84Sgrant 4521.84Sgrant smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin 4531.61Sitojun 4541.61Sitojun20020515: 4551.61Sitojun sshd user/group has been added. Need to hand add this in, or sshd 4561.61Sitojun will not let you log in (with default, or UsePrivlegeSeparation=yes) 4571.61Sitojun 4581.61Sitojun Add the following into /etc/group: 4591.61Sitojun 4601.61Sitojun sshd:*:16: 4611.61Sitojun 4621.61Sitojun and the following to /etc/master.passwd (via vipw): 4631.61Sitojun 4641.63Senami sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin 4651.61Sitojun 4661.79Swiz Also /var/chroot/sshd directory needs to be present (digged as part of 4671.79Swiz the build process). 4681.60Ssommerfe 4691.60Ssommerfe20020426: 4701.60Ssommerfe NBUILDJOBS obsoleted in favor of just using -j. 4711.59Slukem 4721.59Slukem20020426: 4731.59Slukem etc/postinstall added, which performs various checks for 4741.59Slukem configuration file updates and changes, and can fix most of 4751.59Slukem the problems identified. 4761.59Slukem This should make it much easier to upgrade a system's 4771.59Slukem configuration from earlier systems (as far back as NetBSD 1.5). 4781.56Slukem 4791.56Slukem20020320: 4801.79Swiz <bsd.lib.mk> needs a new install(1) for its "-a cmd" support. 4811.79Swiz Build and install at usr.bin/xinstall before the build. 4821.56Slukem 4831.55Sitojun20020319: 4841.79Swiz Raw IPv6 socket now makes strict checking for sa_family and sa_len 4851.79Swiz on send(2) operation. Be sure to have sbin/rtsol and usr.sbin/rtsold 4861.55Sitojun newer than November 2001 when you upgrade the kernel. 4871.55Sitojun 4881.54Sitojun20020311: 4891.54Sitojun ssh configuration files were moved from /etc to /etc/ssh. Beware 4901.54Sitojun if you restart your machine from remote. Note that sshd.conf needs 4911.54Sitojun to be changed (due to the use of "/etc" inside). 4921.54Sitojun 4931.54Sitojun20020223: 4941.53Smatt Users of the VAX port will need to rebuild and install gas 4951.53Smatt so it deal with the now present register prefix used in all 4961.53Smatt the VAX assembly files. 4971.53Smatt 4981.50Sitojun20020118: 4991.50Sitojun ntpd user/group has been added. Need to hand add this in or builds 5001.50Sitojun will break as mtree aborts early. 5011.50Sitojun 5021.50Sitojun Add the following into /etc/group: 5031.50Sitojun 5041.50Sitojun ntpd:*:15: 5051.50Sitojun 5061.50Sitojun and the following to /etc/master.passwd (via vipw): 5071.50Sitojun 5081.50Sitojun ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin 5091.50Sitojun 5101.49Sjmc20011207: 5111.49Sjmc If you're attempting to build a snapshot on sparc64 and are getting 5121.49Sjmc reloc errors from the toolchain groff binary this means your native 5131.49Sjmc toolchain has some broken C++ bits. 5141.49Sjmc 5151.49Sjmc To fix: 5161.49Sjmc 5171.49Sjmc Build a new toolchain (i.e. build.sh -t) 5181.49Sjmc Use the new toolchain to build and install natively (i.e. /usr/lib) 5191.49Sjmc 5201.49Sjmc gnu/lib/libgcc 5211.51Spooka gnu/lib/libstdc++ 5221.49Sjmc 5231.49Sjmc After this a snapshot will be able to be built. 5241.49Sjmc 5251.47Sjmc20011201: 5261.47Sjmc In order for a sparc64 build to work you must have a working awk. If 5271.47Sjmc you've built and installed a system with the new toolchain up to this 5281.52Swiz point you do not have a working awk as its ability to do floating 5291.47Sjmc point is broken. 5301.47Sjmc 5311.47Sjmc To build: 5321.47Sjmc 5331.47Sjmc remake and install gnu/lib/libgcc 5341.47Sjmc remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links 5351.48Sjmc against the new libgcc.a) 5361.47Sjmc 5371.46Sthorpej20011128: 5381.46Sthorpej Kernel config information was changed to use defflag in 5391.46Sthorpej the various "files" files. Bug fixes to config(8) are 5401.46Sthorpej required in order for this to work properly. Make sure 5411.46Sthorpej to build and install in usr.sbin/config before attempting 5421.46Sthorpej to build a new kernel. 5431.46Sthorpej 5441.45Syamt20011030: 5451.45Syamt libc/locale/wcstod.c now needs new lint(1). Update lint(1) 5461.45Syamt before building libc. 5471.43Smason 5481.44Stv20011029: 5491.44Stv The new document BUILDING.mdoc (view with nroff | more, or 5501.44Stv see pre-generated .txt and .html versions) describes the build 5511.44Stv procedure in great detail. BUILDING, and the USE_NEW_TOOLCHAIN 5521.44Stv build process, are intended in the long run to replace this 5531.44Stv manual update log. 5541.44Stv 5551.44Stv Users building a USE_NEW_TOOLCHAIN system should read the 5561.44Stv BUILDING document for caveats. Generally, BUILDING supersedes 5571.44Stv UPDATING for these systems, as tool updating is taken care of 5581.44Stv by the new build system. 5591.42Sperry 5601.42Sperry20011028: 5611.42Sperry src/etc/Makefile now needs install to be able to handle 5621.42Sperry symlinks that point to nowhere. A bug in install that 5631.42Sperry prevented this was corrected. 5641.42Sperry 5651.42Sperry Solution: update and reinstall usr.bin/xinstall 5661.42Sperry Better Solution: Use the new toolchain and it will just work 5671.42Sperry for you. 5681.40Slukem 5691.40Slukem20011006: 5701.40Slukem /etc/mtree/NetBSD.dist has been updated to take advantage of 5711.40Slukem absolute path support added to mtree(8). Older mtree(8)s don't 5721.40Slukem understand the format. 5731.40Slukem 5741.40Slukem Solution: update and reinstall usr.sbin/mtree 5751.39Sjmc 5761.39Sjmc20011004: 5771.39Sjmc Crunchgen has been updated to work via reach-over makefiles. Updating 5781.39Sjmc is suggested before running a snapshot build 5791.36Stv 5801.35Sthorpej20010915: 5811.35Sthorpej The new "ubcperf" code committed by Chuck Silvers removed 5821.35Sthorpej a header file, uvm/uvm_vnode.h. There may be stale .depend 5831.35Sthorpej files that still reference this file. 5841.35Sthorpej 5851.35Sthorpej Solution: "make cleandir && make dependall" in affected 5861.35Sthorpej directories. 5871.31Senami 5881.31Senami20010803: 5891.31Senami grep.info is now built from grep.texi using makeinfo. Since it 5901.31Senami requires makeinfo v4.0, you need to install new texinfo before 5911.31Senami building gnu/usr.bin/grep. To install new texinfo, please follow 5921.31Senami the instruction described in 20010726 entry. 5931.30Senami 5941.64Ssommerfe20010803: 5951.41Swiz (i386 only): i386 kernel now uses new instructions like 5961.111Ssimonb `fxsave' which old gas doesn't understand. To build the 5971.64Ssommerfe kernel successfully, you need to build and install a new toolchain, 5981.64Ssommerfe (i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" 5991.64Ssommerfe from your kernel configuration until you rebuild your userland. 6001.64Ssommerfe See 20011029 above and BUILDING file in this directory for more information. 6011.64Ssommerfe [updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled] 6021.29Sbjh21 6031.29Sbjh2120010731: 6041.29Sbjh21 Bootloader update on ELF platforms. DDB in kernels from before 6051.29Sbjh21 this will be unable to read symbol tables provided by newer 6061.29Sbjh21 bootloaders. 6071.27Sassar 6081.27Sassar20010726: 6091.27Sassar Texinfo was updated to 4.0. To avoid failures when trying to 6101.28Sassar build the included texinfo files, do: 6111.28Sassar 6121.28Sassar cd src/gnu/usr.bin/texinfo 6131.28Sassar make MKINFO=no dependall install 6141.25Sthorpej 6151.25Sthorpej20010718: 6161.25Sthorpej Enabled correct .init/.fini processing in crt0. The way this 6171.25Sthorpej was done was to change a -I directive to cc(1), which means 6181.25Sthorpej make(1) will have a stale dependency (it will be checking the 6191.25Sthorpej timestamp on the wrong "dot_init.h"). 6201.25Sthorpej 6211.25Sthorpej The symptom you will see is that new programs die with SIGSEGV 6221.25Sthorpej if you have a stale dependency. 6231.25Sthorpej 6241.25Sthorpej Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so 6251.25Sthorpej before starting your build. 6261.26Sthorpej 6271.26Sthorpej20010628: 6281.26Sthorpej A construct was added to uvm_page.h that uncovered a bug 6291.26Sthorpej in lint(1). If you get a warning/error about a non-portable 6301.26Sthorpej bitfield, update your lint(1) before proceeding. 6311.21Sjmc 6321.21Sjmc20010226: 6331.22Sjmc Added named user/group to system. Need to hand add this in or builds 6341.21Sjmc will break as mtree aborts early. 6351.21Sjmc 6361.21Sjmc To work around add by hand: 6371.21Sjmc 6381.21Sjmc named:*:14: 6391.21Sjmc 6401.22Sjmc to /etc/group and add: 6411.22Sjmc 6421.22Sjmc named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin 6431.22Sjmc 6441.22Sjmc to master.passwd (use vipw for instance if doing by hand). 6451.22Sjmc 6461.22Sjmc Now a make build should progress. 6471.18Sjmc 6481.18Sjmc20010219: 6491.52Swiz get/setprogname() added. Any hostprogs that may use this will need 6501.111Ssimonb to be bootstrapped manually until the host system is current. 6511.18Sjmc 6521.111Ssimonb Known problems: sys/arch/macppc/stand/fixcoff 6531.19Scgd usr.sbin/config (adding -DMAKE_BOOTSTRAP to 6541.19Scgd CFLAGS and rebuilding should work) 6551.20Sjmc usr.sbin/mdsetimage - Build a static copy if 6561.111Ssimonb building a snapshot before fully bootstrapped. 6571.15Schristos 6581.15Schristos20010204: 6591.15Schristos prepare the code to compile with stricter gcc flags. in 6601.15Schristos particular start eliminating redundant declarations. Yacc 6611.15Schristos needs to be installed before make build. 6621.10Schristos 6631.10Schristos20010114: 6641.10Schristos introduce .if commands(target) in make(1). You need to 6651.10Schristos bring everything up-to-date first, then without installing 6661.23Stron anything make and install in usr.bin/make, then proceed 6671.10Schristos with make build. 6681.9Ssommerfe 6691.9Ssommerfe20010101: 6701.9Ssommerfe bsd.subdir.mk committed 20001230 had a bug which caused 6711.9Ssommerfe afterinstall targets to run too soon; update again. 6721.8Ssommerfe 6731.8Ssommerfe20001230: 6741.8Ssommerfe New share/mk files needed to support .WAIT in SUBDIR variables. 6751.8Ssommerfe If you get make errors, 6761.8Ssommerfe (cd share/mk; make install) 6771.8Ssommerfe Also, PRINTOBJDIR has changed and is now used more heavily. 6781.6Sad 6791.6Sad20001019: 6801.7Sad The `ca' device driver has been replaced by `ld'; although the 6811.6Sad major and minor numbers haven't changed, you should update your /dev 6821.6Sad directory. 6831.1Sabs 6841.4Sitojun20000929: 6851.4Sitojun The following make directives are obsoleted. 6861.4Sitojun MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 6871.4Sitojun By default, RSA is built into libcrypto. IDEA and RC5 will not be 6881.16Swiz built into libcrypto. By using MKCRYPTO_{RC5,IDEA}, you can build 6891.4Sitojun additional library libcrypto_{idea,rc5}. 6901.1Sabs 6911.1Sabs 6921.1SabsHints for a more successful build: 6931.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 6941.123Sjmc Use build.sh, but do not use its "expert mode": 6951.132Sjmmv This will automatically build the tools in the 6961.123Sjmc correct order, and it will keep the tools and the 6971.123Sjmc new build products from interfering with the running 6981.123Sjmc system. This will allow you to ignore most of the 6991.123Sjmc other advice in this file. 7001.2Smrg Build a new kernel first: 7011.2Smrg This makes sure that any new system calls or features 7021.2Smrg expected by the new userland will be present. This 7031.2Smrg helps to avoid critical errors when upgrading. 7041.1Sabs Use object directories: 7051.1Sabs This helps to keep stale object 7061.1Sabs files from polluting the build if a Makefile "forgets" 7071.1Sabs about one. It also makes it easier to clean up after 7081.1Sabs a build. It's also necessary if you want to use the 7091.1Sabs same source tree for multiple machines. 7101.123Sjmc To use object directories with build.sh: 7111.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 7121.123Sjmc To use object directories without using build.sh: 7131.1Sabs a) cd /usr/src ; make cleandir 7141.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 7151.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 7161.1Sabs d) cd /usr/src ; make build 7171.2Smrg Note that running "make obj" in a directory will create 7181.2Smrg in obj.$MACHINE directory. 7191.1Sabs Build to a DESTDIR: 7201.123Sjmc This helps to keep old installed files (especially libraries) 7211.123Sjmc from interfering with the new build. 7221.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 7231.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 7241.123Sjmc environment variable before running make build. It should be 7251.123Sjmc set to the pathname of an initially empty directory. 7261.123Sjmc Problems: if you do not use build.sh, you might need to 7271.123Sjmc update critical utilities without using DESTDIR since 7281.123Sjmc nothing is executed from what is installed in DESTDIR. 7291.123Sjmc (See critical utils, below.) 7301.1Sabs Build often: 7311.1Sabs This keeps critical utilities current enough to not choke 7321.1Sabs on any other part of the source tree that depends on up to 7331.123Sjmc date functionality. If you use build.sh, you should not have 7341.123Sjmc this problem. 7351.1Sabs 7361.1SabsWhat to do if things don't work: 7371.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7381.1SabsWhen things don't work there is usually a few things that commonly 7391.1Sabsshould be done. 7401.1Sabs 1) make includes 7411.1Sabs This should be done automatically by make build. 7421.1Sabs 2) cd share/mk && make install 7431.1Sabs Again, automatically done by make build. 7441.1Sabs 7451.1SabsFailsafe rebuild of a small part of the tree: 7461.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7471.1SabsTo make sure you rebuild something correctly you want to do 7481.1Sabssomething like the following: 7491.1Sabs 1) Make sure the includes and .mk files are up to date. 7501.1Sabs 2) Make sure any program used to build the particular 7511.1Sabs utility is up to date. (yacc, lex, etc...) 7521.1Sabs 3) cd ...path/to/util... 7531.1Sabs make cleandir 7541.1Sabs rm ...all obj directories... 7551.1Sabs make cleandir # yes, again 7561.1Sabs make obj 7571.1Sabs make depend && make 7581.1Sabs 7591.1SabsFailsafe rebuild of the entire tree: 7601.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 7611.1SabsIf you really want to make sure the source tree is clean and 7621.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 7631.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 7641.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 7651.1Sabs 7661.1Sabs---cut here--- 7671.1Sabs#!/bin/sh 7681.1Sabs. /etc/mk.conf 7691.1Sabs 7701.58Slukemif [ -z $NETBSDSRCDIR ] ; then 7711.58Slukem NETBSDSRCDIR=/usr/src 7721.1Sabsfi 7731.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 7741.1Sabs echo Unable to find sources 7751.1Sabs exit 1 7761.1Sabsfi 7771.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 7781.1Sabs 7791.1Sabsif [ -z $BSDOBJDIR ] ; then 7801.1Sabs BSDOBJDIR=/usr/obj 7811.1Sabsfi 7821.1Sabsif [ -d $BSDOBJDIR ] ; then 7831.1Sabs rm -rf $BSDOBJDIR 7841.1Sabsfi 7851.1Sabs 7861.58Slukemcd $NETBSDSRCDIR && make cleandir 7871.1Sabs 7881.1Sabs---cut here--- 7891.1Sabs 7901.1SabsCritical utilities: 7911.1Sabs^^^^^^^^^^^^^^^^^^^ 7921.1Sabs gnu/usr.bin/egcs 7931.3Sitojun usr.bin/compile_et 7941.1Sabs usr.bin/make 7951.1Sabs usr.bin/yacc 7961.1Sabs usr.bin/lex 7971.11Slukem usr.bin/xlint 7981.2Smrg usr.sbin/config 7991.1Sabs 8001.34SsimonbOther problems and possible solutions: 8011.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8021.1SabsSymptom:Unreasonable compiler errors. 8031.1SabsFix: Rebuild gnu/usr.bin/egcs 8041.1Sabs 8051.1SabsSymptom:Complaints involving a Makefile. 8061.17SerhFix: Rebuild usr.bin/make: 8071.17Serh cd usr.bin/make && make && make install 8081.111Ssimonb Or, a failsafe method if that doesn't work: 8091.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 8101.17Serh 8111.1SabsFix: Make sure .mk files are up to date. 8121.1Sabs cd share/mk && make install 8131.2Smrg 8141.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 8151.2SmrgFix: Rebuild usr.sbin/config 8161.1Sabs 8171.1SabsSymptom: 8181.1SabsFix: Rebuild usr.bin/yacc 8191.1Sabs 8201.1SabsSymptom: 8211.1SabsFix: Rebuild usr.bin/lex 8221.1Sabs 8231.1SabsSymptom: 8241.1SabsFix: rm /usr/lib/libbfd.a 8251.4Sitojun 8261.4SitojunSymptom:Obsolete intermediate files are used during compilation 8271.4SitojunFix: Try the following sequence of commands in the directory in question. 8281.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 8291.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 8301.4Sitojun may remain. The command tries to clean everything up) 8311.5Swiz 8321.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 8331.5SwizFix: Rebuild and install usr.bin/menuc 8341.12Sitojun 8351.12SitojunSymptom:mklocale not found during build in share/locale/ctype 8361.12SitojunFix: Build and install usr.bin/mklocale 8371.13Sdogcow 8381.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 8391.13SdogcowFix: Rebuild and install lib/libc 8401.13Sdogcow 8411.19ScgdSymptom:usr.sbin/config fails to build. 8421.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 8431.13Sdogcow 8441.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 8451.19ScgdFix: Rebuild and install lib/libc 8461.24Sabs 8471.24SabsSymptom:lint does not understand the '-X' option 8481.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 849