UPDATING revision 1.159
11.159Sgdt$NetBSD: UPDATING,v 1.159 2007/03/25 16:23:04 gdt 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.159Sgdt20070319: 201.159Sgdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so 211.159Sgdt on many platforms due to incorrect flags settings. If you 221.159Sgdt updated and built after about 20070315, do "nbmake-$arch 231.159Sgdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a 241.159Sgdt rebuild of object files that might have been built 251.159Sgdt incorrectly, and ensure that you have at least 261.159Sgdt src/lib/libc/Makefile 1.130. 271.159Sgdt 281.158Sdbj20070210: 291.158Sdbj src/sys/sys/{sa.h,savar.h} were removed. 301.158Sdbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \ 311.158Sdbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm 321.158Sdbj will allow dependencies on those files to get get rebuilt 331.158Sdbj 341.157Sapb20070209: 351.157Sapb The threading model was changed when the newlock2 branch 361.157Sapb was merged to NetBSD-current. If you boot with a new 371.157Sapb kernel (version 4.99.10), then you also need a new pthread 381.157Sapb library (/usr/lib/libpthread.so.0.7). If you boot with 391.157Sapb an old kernel, then you need the old pthread library 401.157Sapb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and 411.157Sapb the pthread library in sync, old threaded applications should 421.157Sapb continue to work with an old or new kernel. Note that named(8) 431.157Sapb is the only threaded application in the base system. 441.157Sapb 451.154She20061214: 461.154She Following the move of string_to_flags() and flags_to_string() 471.154She from the bin/ls/ sources to libutil, users doing UPDATE builds 481.154She will need to do a "make cleandir" in 491.154She tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/, 501.154She bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/, 511.156She usr.bin/xinstall/, libexec/ftpd/, rescue/, as well 521.156She as the installation images in distrib/ 531.154She in order to excise stale references to the old stat_flags.h header 541.154She file in the ls sources -- stat_flags.h has been removed. 551.154She 561.152Schristos20061108: 571.152Schristos The configure script used in the src/tools/gcc compiler has been 581.152Schristos changed to indicate that our libc has ssp support built-in and 591.152Schristos does not depend on -lssp and -lssp-nonshared. You'll need to 601.152Schristos make clean in src/tools/gcc first to rebuild the compiler. 611.152Schristos 621.151Srpaulo20061009: 631.151Srpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer 641.151Srpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. 651.151Srpaulo 661.150Sbjh2120060814: 671.150Sbjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been 681.150Sbjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC 691.150Sbjh21 kernel configuration for an example. X servers from the last 701.150Sbjh21 few years should cope. 711.150Sbjh21 721.149Schristos20060703: 731.149Schristos MPACPI is no more. We always configure PCI interrupts using ACPI 741.149Schristos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed 751.149Schristos to ACPI_SCANPCI. Thanks to work from fvdl. 761.149Schristos 771.148Sdogcow20060627: 781.148Sdogcow socket(2) has changed, and its system call has been versioned. 791.148Sdogcow For userlands with the old version of socket(2), make sure that 801.148Sdogcow your kernel has 'options COMPAT_30' set, or else 'bad system call' 811.148Sdogcow errors will result. 821.148Sdogcow 831.146Spavel20060526: 841.147Schristos The kernel linker scripts for i386 and xen 851.147Schristos (sys/arch/i386/conf/kern.ldscript*) were changed to set the 861.146Spavel load address correctly, for the benefit of MULTIBOOT boot loaders 871.146Spavel (like Grub). If you use a linker (ld) older than from 2006/04/17, it 881.147Schristos will be unable to link the kernel because of a bug and ld will fail 891.147Schristos with an error like: 901.147Schristos ../../../../arch/i386/conf/kern.ldscript:45 \ 911.147Schristos non constant expression for load base 921.147Schristos You need to update at least src/gnu/dist/binutils/ld and recompile 931.147Schristos and install the linker. If using the build.sh script, the easiest 941.147Schristos way is with a "build.sh tools" command, with any other options 951.147Schristos that you use normally. When using build.sh, the linker binary is 961.147Schristos installed as ${TOOLDIR}/bin/i386--netbsdelf-ld. 971.147Schristos 981.145Smartin20060131: 991.145Smartin the protocol between the sparc64 bootloader (ofwboot) and 1001.145Smartin the kernel was changed. Before installing a new kernel, 1011.145Smartin you need to update ofwboot. After a full build, just copy 1021.145Smartin /usr/mdec/ofwboot to /, or do a rebuild of 1031.145Smartin src/sys/arch/sparc/stand/ofwboot and install the result to /. 1041.145Smartin 1051.144Syamt20050917: 1061.144Syamt arch/*/conf/std.* was changed to include conf/std, which 1071.144Syamt contains MI options previously enabled by default. 1081.144Syamt If you have kernel config files which doesn't include 1091.144Syamt arch/*/conf/std.*, you need to edit them to include conf/std 1101.144Syamt to get the previous configuration. 1111.144Syamt 1121.143Slukem20050830: 1131.143Slukem named.conf was moved from /etc/namedb to /etc. 1141.143Slukem postinstall(8) migrates this during interactive use. 1151.143Slukem Users of MKUPDATE=yes will need to manually rectify 1161.143Slukem this in their DESTDIR. 1171.143Slukem 1181.142Sdrochner20050825: 1191.142Sdrochner Some data structures in sys/device.h, related to interface 1201.142Sdrochner attributes and locator names, were changed. config(1) was 1211.142Sdrochner modified to emit the new data structures. 1221.142Sdrochner Thus usr.bin/config must be updated (and run on the kernel 1231.142Sdrochner configuration file) before a new kernel can be built. 1241.142Sdrochner 1251.139Schristos20050531: 1261.141Saugustss genassym.sh(8) was moved to genassym(1). You need to either build 1271.141Saugustss tools first or install the version of genassym from /usr/bin before 1281.139Schristos you can build a kernel again. 1291.139Schristos 1301.140Syamt20050520: 1311.140Syamt Because a kernfs bug which xentools relies on was fixed, 1321.140Syamt xentools up to xentools20-2.0.3nb4 won't work with new kernel. 1331.140Syamt 1341.138Slukem20050417: 1351.138Slukem postinstall(8) was moved from /etc to /usr/sbin and made part 1361.138Slukem of the "base" set, to make it easier to invoke after an 1371.138Slukem upgrade. 1381.138Slukem 1391.136Scube20050325: 1401.136Scube pcppi(4) was separated in two devices, adding attimer(4). Be sure 1411.136Scube to add a config line for an attimer(4) device in your kernel 1421.136Scube configuration, or you won't be able to set the pitch of the beep 1431.137Scube with wsconsctl. Depending on the default value for the pitch, you 1441.137Scube might even not hear any more beep. Also, it is advised to attach both 1451.137Scube devices the same way (i.e., both on isa or both on acpi) or the 1461.137Scube pcppi(4) device may fail to find the attimer(4) one. 1471.136Scube 1481.135Sjmc20050211: 1491.135Sjmc Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in 1501.135Sjmc some of the cross tools to fail if they use configure. Some configure's 1511.135Sjmc cache the environment passed in and notice the new environment is 1521.135Sjmc different and abort. Doing a clean in tools/ should be enough to 1531.135Sjmc make a build continue. 1541.135Sjmc 1551.134Schristos20050109: 1561.134Schristos Since su is using pam by default now, make sure that you have 1571.134Schristos /etc/pam.d populated (postinstall will do that automatically 1581.134Schristos for you). Otherwise su will fail open (i.e. will not require 1591.134Schristos a password). 1601.134Schristos 1611.133Schristos20041229: 1621.133Schristos Make had a path resolution bug that manifested itself as not 1631.133Schristos being able to install openpam.3. This bug has been fixed, but 1641.133Schristos you might need to rebuild make manually first to get through 1651.133Schristos the build. 1661.133Schristos 1671.130Schristos20041201: 1681.130Schristos Userland programs have been changed to use /dev/bpf instead of 1691.130Schristos /dev/bpfX. You need to create that device by installing a new 1701.131Swiz MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]* 1711.99Smrg 1721.129Sjmc20041006: 1731.129Sjmc 1741.129Sjmc A bug was introduced into /bin/sh (var.c rev 1.35) which causes 1751.129Sjmc variables to not export correctly to subshells in all cases. This 1761.129Sjmc will cause builds to break if that version of /bin/sh is installed 1771.129Sjmc on the system. The proper version of /bin/sh can be verified with: 1781.129Sjmc 1791.129Sjmc ident /bin/sh | grep var 1801.129Sjmc 1811.129Sjmc Any /bin/sh w. version 1.35 will not work and needs to be updated 1821.129Sjmc before attempting a build. 1831.129Sjmc 1841.127Schristos20041001: 1851.127Schristos The ipfilter kernel sources moved from sys/netinet to 1861.127Schristos dist/sys/ipf/netinet. Due to the move some Makefile 1871.127Schristos dependencies are now dangling requiring a make cleandir 1881.128She before they work again (kdump, ktruss, rescue, ipf, and 1891.128She ftp-proxy are the victims). 1901.127Schristos 1911.125Satatat20040715: 1921.125Satatat The rc.d/sendmail script now uses a heuristic to determine 1931.125Satatat if sendmail should be started at boot time. It checks the 1941.125Satatat contents of /etc/mailer.conf, /etc/mail/submit.cf, and the 1951.125Satatat owner and mode of the sendmail binary to see if any changes 1961.125Satatat to the mail infrastructure have been made. If no changes 1971.125Satatat are detected, it will start an SMTP listener. 1981.125Satatat 1991.125Satatat Setting sendmail=NO in /etc/rc.conf will override this. 2001.125Satatat 2011.125Satatat If you are only using sendmail by default and only for 2021.125Satatat local delivery, it is important that you also update your 2031.125Satatat sendmail.cf so that the SMTP listener only listens on the 2041.125Satatat loopback interface. 2051.125Satatat 2061.125Satatat20040715: 2071.125Satatat The method by which athhal-elf.o gets pulled into i386 2081.125Satatat kernel builds has been changed again. The latest version 2091.125Satatat of bsd.files.mk is no longer required. 2101.125Satatat 2111.124Sjmc20040621: 2121.124Sjmc Due to the recent rototill of tools/compat it's crucial one starts 2131.124Sjmc from a clean objdir under tools/*. 2141.124Sjmc 2151.124Sjmc This is mostly due to generated files (yacc and lex sources) needing 2161.125Satatat to be generated with new rules from bsd.hostprog.mk. 2171.124Sjmc 2181.124Sjmc The safest course is to rm -rf all objects under tools before building. 2191.124Sjmc 2201.121Slukem20040516: 2211.121Slukem The end-user modifiable X11 configuration has been moved 2221.121Slukem from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>. 2231.121Slukem Ensure that src and xsrc is up to date, and run 2241.121Slukem "make cleandir" in src/x11 before your next build. 2251.121Slukem 2261.126Slukem postinstall currently doesn't migrate the files from 2271.126Slukem /usr/X11R6/lib/X11/* to /etc/X11/* although it does 2281.126Slukem detect that this needs to occur, so you'll have to 2291.126Slukem manually move these files yourself. 2301.126Slukem 2311.119Satatat20040426: 2321.119Satatat Support for the original dynamic sysctl node structure has 2331.119Satatat been removed in favor of the newer layout. This affects 2341.119Satatat consumers of the create and delete interface, as well as 2351.119Satatat the dynamic discovery mechanism. This is believed only to 2361.119Satatat be the sysctl(8) binary itself, at this point in time, so 2371.119Satatat the only effect of this should be that a sysctl binary 2381.119Satatat built from sources dated between 2003/12/04 and 2004/03/24 2391.119Satatat will not work on a kernel built from sources dated after 2401.119Satatat 2004/04/25. If you need a new sysctl binary but build.sh 2411.119Satatat does not work, make sure that your revision of 2421.120Satatat src/sys/sys/sysctl.h is 1.112 (or later), and then the 2431.120Satatat do the following: 2441.119Satatat 2451.120Satatat cd /usr/src (or wherever your source tree is) 2461.120Satatat make USETOOLS=no includes 2471.120Satatat cd lib/libc 2481.120Satatat make USETOOLS=no dependall install 2491.120Satatat cd ../../sbin/sysctl 2501.119Satatat make USETOOLS=no dependall install 2511.119Satatat 2521.122Sitojun If you are using older sysctl binary, GNU autoconf would fail to 2531.122Sitojun identify your machine architecture, and tries to build binary for 2541.122Sitojun "unknown-unknown-netbsd20F" or something like that. if that happens, 2551.122Sitojun make sure to follow the above steps. 2561.122Sitojun 2571.118Sdbj20040425: 2581.118Sdbj The ffs superblock issues listed below under 20040109 and 20030402 2591.118Sdbj are now automatically addressed by the /etc/rc.d/fixsb script or by 2601.118Sdbj sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 2611.118Sdbj invocation mentioned below will continue to work and is now 2621.118Sdbj automated by those scripts. Note that under certain circumstances, 2631.118Sdbj affected filesystems upgraded to a -current kernel first before 2641.118Sdbj upgrading their userland with the fixsb and fsck_ffs fixes may 2651.118Sdbj encounter a 'freeing free inode' panic when writing to the affected 2661.118Sdbj filesystem, so it is a good idea to repair the filesystem as soon as 2671.118Sdbj possible. For more details on the fixsb script, see pr install/25138. 2681.118Sdbj 2691.115Schristos20040418: 2701.121Slukem statfs(2) and friends have been replaced with statvfs(2). Before 2711.115Schristos installing a newly build userland make sure that you are running 2721.115Schristos a newly built kernel with COMPAT_20 set. In addition your libc 2731.115Schristos build might not work (undefined SYS_statfs symbol) because make 2741.115Schristos clean does not know how to remove files it does not know about 2751.116Schristos anymore. Manually remove all generated .S sources and objects 2761.116Schristos from the libc build directory. 2771.115Schristos 2781.114Sjmc20040326: 2791.114Sjmc The method by which athhal-elf.o gets pulled into i386 kernel builds 2801.117Sjmc has been changed. The file is now stored as a uuencoded file in CVS 2811.114Sjmc and the generated Makefile will use the new .uue rules from bsd.file.mk 2821.114Sjmc to build it. 2831.114Sjmc 2841.114Sjmc This means you must have the latest bsd.files.mk installed when 2851.114Sjmc building a kernel without USETOOLS=yes. 2861.114Sjmc 2871.113Sdan20040318: 2881.113Sdan A bug in the cgd(4) blowfish code was corrected, without 2891.113Sdan provision of backwards compatibility, after several public 2901.113Sdan notices over several months. Users of cgd with blowfish cipher 2911.113Sdan ONLY must dump their data before updating their kernels, and 2921.113Sdan recreate cgd's and restore data using the new kernel. See 2931.113Sdan (recent message to current-users, URL when mail-index has updated) 2941.113Sdan 2951.108Sbjh2120040313: 2961.108Sbjh21 On acorn32, the opms and qms drivers have been withdrawn, and 2971.108Sbjh21 the old wsqms driver is now called qms. Kernel config files 2981.108Sbjh21 will need updating. See the ones in sys/arch/acorn32/conf 2991.108Sbjh21 for examples. 3001.108Sbjh21 3011.106Sbjh2120040125: 3021.106Sbjh21 On acorn32, the beep and sysbeep devices are no longer 3031.106Sbjh21 needed, and will need to be deleted from kernel configuration 3041.106Sbjh21 files. 3051.105Sbjh21 3061.102Sdbj20040109: 3071.102Sdbj Compatibility for old ffs superblock layouts has been 3081.102Sdbj added, and the restrictive fsck checks have been reenabled 3091.102Sdbj when using those layouts. If you have been using -current 3101.102Sdbj since 20030402, you may find that fsck again signals fatal 3111.110Sdbj superblock mismatches. To repair, make sure you have 3121.111Ssimonb an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 3131.109Sdbj to complete the filesystem upgrade. A message has 3141.111Ssimonb been added to the kernel which should detect this problem. 3151.111Ssimonb See the following discussion for more information: 3161.112Skeihan http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html 3171.102Sdbj 3181.99Smrg20031203: 3191.100Skeihan New binutils builds may fail due to old dependencies. 3201.99Smrg It's necessary to "make cleandir" to ensure that 3211.99Smrg the dependencies will be rebuilt correctly. 3221.98Swiz 3231.98Swiz20031111: 3241.98Swiz A newer mkdep is needed. Error noting that is 3251.98Swiz cc: Ambiguous abbreviation -- 3261.97Slukem 3271.97Slukem20031008: 3281.97Slukem /usr/include/sys/disklabel_mbr.h was removed. 3291.97Slukem It's necessary to "make cleandir" to ensure that 3301.97Slukem the dependencies will be rebuilt correctly. 3311.96Schristos 3321.109Sdbj20031007: 3331.153Sreed A sign extension bug was fixed which set all the high bits 3341.111Ssimonb of our newly expanded ffs fs_flags. This should only 3351.111Ssimonb affect users who installed or upgraded in September of 2003. 3361.109Sdbj A small utility program was posted to tech-kern which 3371.111Ssimonb should fix this problem, and a warning message was added 3381.111Ssimonb to the kernel which should discover and warn about it. See 3391.111Ssimonb http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html 3401.109Sdbj 3411.96Schristos20030906: 3421.96Schristos With the addition of siginfo support the old signal trampoline 3431.96Schristos code has been deprecated to COMPAT_16. Make sure that your running 3441.96Schristos kernel has COMPAT_16 enabled before building userland. 3451.94Schristos 3461.94Schristos20030801: 3471.95Swiz With the new openssl, there is some header and library shuffling. 3481.94Schristos rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \ 3491.95Swiz /usr/lib/libdes* before building. 3501.92Swiz 3511.92Swiz20030703: 3521.92Swiz Texinfo was updated to 4.6. To avoid failures when trying to 3531.92Swiz build the included texinfo files, do: 3541.92Swiz 3551.92Swiz cd src/gnu/usr.bin/texinfo 3561.92Swiz make MKINFO=no dependall install 3571.90Swiz 3581.90Swiz20030630: 3591.101Sjunyoung Groff was updated to 1.19; it's probably necessary to do 3601.91Swiz cd share/mk && make install 3611.90Swiz cd src/gnu/usr.bin/groff 3621.90Swiz make MKMAN=no dependall install 3631.90Swiz (untested). 3641.89Schristos 3651.89Schristos20030516: 3661.89Schristos Due to bugs in the export handling code, invalid export lines 3671.89Schristos were accepted before and caused the kernel to panic when 3681.89Schristos mountd got restarted because it freed memory that had already 3691.89Schristos been freed. This has been fixed and the kernel checks 3701.89Schristos export addresses very strictly. If you upgrade your kernel, 3711.89Schristos make sure you also upgrade mountd, because if your export 3721.89Schristos file contains lines with an old inet4 address syntax (i.e. 3731.89Schristos a.b.c or a.b or a), they will get rejected by the new kernel. 3741.87Sbjh21 3751.87Sbjh2120030402: 3761.87Sbjh21 The superblock layout for FFS was changed. If you have 1.6 3771.87Sbjh21 fsck binaries, they will signal a fatal superblock mismatch 3781.87Sbjh21 with the first alternate, because they compare too many 3791.87Sbjh21 fields (even ones that aren't useful). If possible, upgrade 3801.87Sbjh21 your fsck_ffs binary before using a new kernel. 3811.87Sbjh21 None of this signals actual filesystem damage. 3821.85Satatat 3831.85Satatat20030324: 3841.85Satatat sendmail version 8.12.8 was imported. Since sendmail is 3851.85Satatat now setgid to the smmsp group, and runs in "collection" 3861.85Satatat mode for most common activities, there is a new config 3871.85Satatat file called submit.cf that needs to live in /etc/mail. 3881.85Satatat The generic submit.cf sample in /usr/share/sendmail/cf 3891.85Satatat is named netbsd-msp.cf. Upgrading your regular sendmail 3901.85Satatat configuration file is also strongly advised. 3911.85Satatat 3921.85Satatat See the section named "MESSAGE SUBMISSION PROGRAM" in 3931.85Satatat the updated /usr/share/sendmail/README file for more 3941.85Satatat information. 3951.82Swiz 3961.82Swiz20030117: 3971.82Swiz Texinfo was updated to 4.3. To avoid failures when trying to 3981.82Swiz build the included texinfo files, do: 3991.82Swiz 4001.82Swiz cd src/gnu/usr.bin/texinfo 4011.82Swiz make MKINFO=no dependall install 4021.81Slukem 4031.81Slukem20021223: 4041.81Slukem The METALOG format changed slightly, to remove the leading 4051.81Slukem "${DESTDIR}" from path names. 4061.81Slukem This only affects people building with UNPRIVED. 4071.81Slukem For complete safety, remove the DESTDIR entirely and 4081.81Slukem update tools/mtree, before running make build. 4091.88Sitojun 4101.88Sitojun20021219: 4111.88Sitojun CVS repository layout was changed. See the following for details 4121.88Sitojun if you are using (anonymous) cvs to update your tree. 4131.88Sitojun 4141.93Ssalo http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html 4151.80Slukem 4161.80Slukem20021219: 4171.80Slukem install(1) had a '-N dbdir' option added, to specify an 4181.80Slukem alternate location to look up users & groups (instead 4191.80Slukem of the host system passwd(5) and group(5) databases). 4201.80Slukem 4211.80Slukem The build system was modified to take advantage of 4221.80Slukem this option (using ${NETBSDSRCDIR}/etc), so if you 4231.83Skei use USETOOLS==no, you may have to rebuild and 4241.80Slukem reinstall usr.bin/xinstall first. 4251.78Slukem 4261.78Slukem20021130: 4271.78Slukem fparseln(3) moved from libutil to libc. 4281.78Slukem If building to DESTDIR=/, reinstall the includes 4291.78Slukem and rebuild libc: 4301.78Slukem make includes 4311.78Slukem make do-lib-libc 4321.78Slukem If using build.sh, "cd tools/compat && make clean" 4331.78Slukem before rebuilding the tools. 4341.77Slukem 4351.77Slukem20021126: 4361.77Slukem The mk.conf(5) variable SYS_INCLUDE has been deprecated, 4371.77Slukem including the optional "SYS_INCLUDE=symlinks" support. 4381.77Slukem All header files, including <sys/*.h> are copied into 4391.77Slukem /usr/include. 4401.76Sthorpej 4411.76Sthorpej20021121: 4421.76Sthorpej The C run-time support files crtbegin.o and crtend.o 4431.76Sthorpej (and their companions crtbeginS.o and crtendS.o) were 4441.76Sthorpej split up, with new crti.o and crtn.o files resulting. 4451.76Sthorpej This means that libtool needs to be rebuilt once the 4461.76Sthorpej new libraries are installed. The process of rebuilding 4471.76Sthorpej libtool will cause it to automatically notice the new 4481.76Sthorpej required files, but it *must* be rebuilt in order to 4491.76Sthorpej do this. 4501.76Sthorpej 4511.76Sthorpej An out-of-date libtool will result in shared libraries 4521.76Sthorpej which lack _init() and _fini() routines, which means that 4531.153Sreed their global constructors/destructors will not be invoked. 4541.75Sthorpej 4551.75Sthorpej20021121: 4561.75Sthorpej A bug related to how ARM ELF objects were tagged has been 4571.75Sthorpej corrected. 4581.75Sthorpej 4591.75Sthorpej NetBSD ARM ELF uses the soft-VFP floating point model by 4601.75Sthorpej default. However, the assembler lacked support for marking 4611.75Sthorpej objects as using the VFP floating point format, and the 4621.79Swiz compiler was not properly passing the flag indicating "soft-VFP" 4631.75Sthorpej to the assembler. 4641.75Sthorpej 4651.75Sthorpej Unfortunately, this means that the linker will now consider 4661.75Sthorpej old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be 4671.75Sthorpej incompatible with new (properly marked) objects. 4681.75Sthorpej 4691.75Sthorpej The problem will only manifest itself if you attempt to compile 4701.75Sthorpej a new program using the fixed toolchain, and link that program 4711.75Sthorpej against old libraries which do not have the proper "softvfp" 4721.75Sthorpej markings. ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES 4731.75Sthorpej WILL CONTINUE TO WORK PROPERLY. 4741.75Sthorpej 4751.75Sthorpej The only work-around for the problem is to recompile all of 4761.75Sthorpej the libraries on the system. The easiest way to do this for 4771.79Swiz system libraries is to install a binary snapshot; they are 4781.93Ssalo generally available on releng.NetBSD.org. Any packages you 4791.75Sthorpej have installed which supply libraries will have to be recompiled 4801.75Sthorpej if you wish to link new programs against those libraries. 4811.75Sthorpej 4821.75Sthorpej If you have questions about this matter, please contact 4831.93Ssalo port-arm@NetBSD.org. 4841.73Sprovos 4851.73Sprovos20021011: 4861.73Sprovos Systrace has been improved to support privilege elevation. 4871.73Sprovos Updating the kernel requires the userland part of systrace 4881.79Swiz to be rebuilt. 4891.72Sthorpej 4901.72Sthorpej20021010: 4911.72Sthorpej The config(8) grammar was changed to allow options to register 4921.72Sthorpej dependencies on attributes, as well as other options. Users 4931.72Sthorpej must update and reinstall usr.sbin/config before building a new 4941.72Sthorpej kernel. 4951.70Sthorpej 4961.70Sthorpej20021009: 4971.70Sthorpej A new attribute dependency syntax was introduced to config(8), 4981.70Sthorpej which is now used by the SCSI configuration description. Users 4991.71Swiz must update and reinstall usr.sbin/config before building a new 5001.70Sthorpej kernel. 5011.69Sthorpej 5021.69Sthorpej20021003: 5031.69Sthorpej Several changes have been made to the autoconfiguration 5041.69Sthorpej framework. Users must update and reinstall usr.sbin/config 5051.69Sthorpej before building a new kernel. 5061.74Sjschauma 5071.74Sjschauma20021001: 5081.74Sjschauma The i386mp branch has been merged. To compile a kernel, users 5091.74Sjschauma will need to add the option 'cpu* at mainbus?' to their configuration 5101.74Sjschauma file. Multiprocessor kernels will need 5111.74Sjschauma ioapic* at mainbus? apid ? 5121.74Sjschauma options MULTIPROCESSOR 5131.74Sjschauma options COM_MPLOCK 5141.68Slukem 5151.68Slukem20020922: 5161.68Slukem MKDYNAMICROOT=yes enabled by default, which means that 5171.68Slukem certain shared libraries are installed into /lib, the shared 5181.68Slukem linker is installed into /libexec, and all programs in /bin 5191.68Slukem and /sbin are dynamically linked. 5201.68Slukem If you do not use "make build", you should ensure that 5211.68Slukem you have the libraries and shared linker in the new locations, 5221.68Slukem with: 5231.68Slukem make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so 5241.67Slukem 5251.67Slukem20020917: 5261.67Slukem USE_NEW_TOOLCHAIN has been replaced with: 5271.67Slukem - TOOLCHAIN_MISSING -- set to "yes" on platforms for which 5281.67Slukem there is no working in-tree toolchain (hppa, ns32k, sh5, 5291.67Slukem x86_64). 5301.67Slukem - EXTERNAL_TOOLCHAIN -- if defined by the user, points to the 5311.79Swiz root of an external toolchain (e.g. /usr/local/gnu). This 5321.67Slukem enables the cross-build framework even for TOOLCHAIN_MISSING 5331.67Slukem platforms. 5341.66Sgehenna 5351.66Sgehenna20020906: 5361.66Sgehenna gehenna-devsw has been merged into the trunk. Need to update and 5371.79Swiz reinstall usr.sbin/config before building the kernel. 5381.65Slukem 5391.65Slukem20020822: 5401.65Slukem Crunched rescue tools (contents of /bin and /sbin, plus others) 5411.65Slukem are now provided in /rescue. 5421.65Slukem 5431.65Slukem To ensure that these are built statically linked (no matter 5441.65Slukem what the setting of LDSTATIC is), use a crunchgen(1) built 5451.65Slukem from sources newer than 20020820 (see the next entry). 5461.65Slukem 5471.65Slukem20020820: 5481.65Slukem crunchgen(1) changed to ensure that the generated program 5491.65Slukem is statically linked. 5501.65Slukem 5511.65Slukem Solution: update and reinstall usr.bin/crunch 5521.84Sgrant 5531.84Sgrant20020605: 5541.84Sgrant smmsp user/group has been added for sendmail. 5551.84Sgrant 5561.84Sgrant Add the following into /etc/group: 5571.84Sgrant 5581.84Sgrant smmsp:*:17: 5591.84Sgrant 5601.84Sgrant and the following to /etc/master.passwd (via vipw): 5611.84Sgrant 5621.84Sgrant smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin 5631.61Sitojun 5641.61Sitojun20020515: 5651.61Sitojun sshd user/group has been added. Need to hand add this in, or sshd 5661.153Sreed will not let you log in (with default, or UsePrivilegeSeparation=yes) 5671.61Sitojun 5681.61Sitojun Add the following into /etc/group: 5691.61Sitojun 5701.61Sitojun sshd:*:16: 5711.61Sitojun 5721.61Sitojun and the following to /etc/master.passwd (via vipw): 5731.61Sitojun 5741.63Senami sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin 5751.61Sitojun 5761.79Swiz Also /var/chroot/sshd directory needs to be present (digged as part of 5771.79Swiz the build process). 5781.60Ssommerfe 5791.60Ssommerfe20020426: 5801.60Ssommerfe NBUILDJOBS obsoleted in favor of just using -j. 5811.59Slukem 5821.59Slukem20020426: 5831.59Slukem etc/postinstall added, which performs various checks for 5841.59Slukem configuration file updates and changes, and can fix most of 5851.59Slukem the problems identified. 5861.59Slukem This should make it much easier to upgrade a system's 5871.59Slukem configuration from earlier systems (as far back as NetBSD 1.5). 5881.56Slukem 5891.56Slukem20020320: 5901.79Swiz <bsd.lib.mk> needs a new install(1) for its "-a cmd" support. 5911.79Swiz Build and install at usr.bin/xinstall before the build. 5921.56Slukem 5931.55Sitojun20020319: 5941.79Swiz Raw IPv6 socket now makes strict checking for sa_family and sa_len 5951.79Swiz on send(2) operation. Be sure to have sbin/rtsol and usr.sbin/rtsold 5961.55Sitojun newer than November 2001 when you upgrade the kernel. 5971.55Sitojun 5981.54Sitojun20020311: 5991.54Sitojun ssh configuration files were moved from /etc to /etc/ssh. Beware 6001.54Sitojun if you restart your machine from remote. Note that sshd.conf needs 6011.54Sitojun to be changed (due to the use of "/etc" inside). 6021.54Sitojun 6031.54Sitojun20020223: 6041.53Smatt Users of the VAX port will need to rebuild and install gas 6051.53Smatt so it deal with the now present register prefix used in all 6061.53Smatt the VAX assembly files. 6071.53Smatt 6081.50Sitojun20020118: 6091.50Sitojun ntpd user/group has been added. Need to hand add this in or builds 6101.50Sitojun will break as mtree aborts early. 6111.50Sitojun 6121.50Sitojun Add the following into /etc/group: 6131.50Sitojun 6141.50Sitojun ntpd:*:15: 6151.50Sitojun 6161.50Sitojun and the following to /etc/master.passwd (via vipw): 6171.50Sitojun 6181.50Sitojun ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin 6191.50Sitojun 6201.49Sjmc20011207: 6211.49Sjmc If you're attempting to build a snapshot on sparc64 and are getting 6221.49Sjmc reloc errors from the toolchain groff binary this means your native 6231.49Sjmc toolchain has some broken C++ bits. 6241.49Sjmc 6251.49Sjmc To fix: 6261.49Sjmc 6271.49Sjmc Build a new toolchain (i.e. build.sh -t) 6281.49Sjmc Use the new toolchain to build and install natively (i.e. /usr/lib) 6291.49Sjmc 6301.49Sjmc gnu/lib/libgcc 6311.51Spooka gnu/lib/libstdc++ 6321.49Sjmc 6331.49Sjmc After this a snapshot will be able to be built. 6341.49Sjmc 6351.47Sjmc20011201: 6361.47Sjmc In order for a sparc64 build to work you must have a working awk. If 6371.47Sjmc you've built and installed a system with the new toolchain up to this 6381.52Swiz point you do not have a working awk as its ability to do floating 6391.47Sjmc point is broken. 6401.47Sjmc 6411.47Sjmc To build: 6421.47Sjmc 6431.47Sjmc remake and install gnu/lib/libgcc 6441.47Sjmc remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links 6451.48Sjmc against the new libgcc.a) 6461.47Sjmc 6471.46Sthorpej20011128: 6481.46Sthorpej Kernel config information was changed to use defflag in 6491.46Sthorpej the various "files" files. Bug fixes to config(8) are 6501.46Sthorpej required in order for this to work properly. Make sure 6511.46Sthorpej to build and install in usr.sbin/config before attempting 6521.46Sthorpej to build a new kernel. 6531.46Sthorpej 6541.45Syamt20011030: 6551.45Syamt libc/locale/wcstod.c now needs new lint(1). Update lint(1) 6561.45Syamt before building libc. 6571.43Smason 6581.44Stv20011029: 6591.44Stv The new document BUILDING.mdoc (view with nroff | more, or 6601.44Stv see pre-generated .txt and .html versions) describes the build 6611.44Stv procedure in great detail. BUILDING, and the USE_NEW_TOOLCHAIN 6621.44Stv build process, are intended in the long run to replace this 6631.44Stv manual update log. 6641.44Stv 6651.44Stv Users building a USE_NEW_TOOLCHAIN system should read the 6661.44Stv BUILDING document for caveats. Generally, BUILDING supersedes 6671.44Stv UPDATING for these systems, as tool updating is taken care of 6681.44Stv by the new build system. 6691.42Sperry 6701.42Sperry20011028: 6711.42Sperry src/etc/Makefile now needs install to be able to handle 6721.42Sperry symlinks that point to nowhere. A bug in install that 6731.42Sperry prevented this was corrected. 6741.42Sperry 6751.42Sperry Solution: update and reinstall usr.bin/xinstall 6761.42Sperry Better Solution: Use the new toolchain and it will just work 6771.42Sperry for you. 6781.40Slukem 6791.40Slukem20011006: 6801.40Slukem /etc/mtree/NetBSD.dist has been updated to take advantage of 6811.40Slukem absolute path support added to mtree(8). Older mtree(8)s don't 6821.40Slukem understand the format. 6831.40Slukem 6841.40Slukem Solution: update and reinstall usr.sbin/mtree 6851.39Sjmc 6861.39Sjmc20011004: 6871.39Sjmc Crunchgen has been updated to work via reach-over makefiles. Updating 6881.39Sjmc is suggested before running a snapshot build 6891.36Stv 6901.35Sthorpej20010915: 6911.35Sthorpej The new "ubcperf" code committed by Chuck Silvers removed 6921.35Sthorpej a header file, uvm/uvm_vnode.h. There may be stale .depend 6931.35Sthorpej files that still reference this file. 6941.35Sthorpej 6951.35Sthorpej Solution: "make cleandir && make dependall" in affected 6961.35Sthorpej directories. 6971.31Senami 6981.31Senami20010803: 6991.31Senami grep.info is now built from grep.texi using makeinfo. Since it 7001.31Senami requires makeinfo v4.0, you need to install new texinfo before 7011.31Senami building gnu/usr.bin/grep. To install new texinfo, please follow 7021.31Senami the instruction described in 20010726 entry. 7031.30Senami 7041.64Ssommerfe20010803: 7051.41Swiz (i386 only): i386 kernel now uses new instructions like 7061.111Ssimonb `fxsave' which old gas doesn't understand. To build the 7071.64Ssommerfe kernel successfully, you need to build and install a new toolchain, 7081.64Ssommerfe (i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" 7091.64Ssommerfe from your kernel configuration until you rebuild your userland. 7101.64Ssommerfe See 20011029 above and BUILDING file in this directory for more information. 7111.64Ssommerfe [updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled] 7121.29Sbjh21 7131.29Sbjh2120010731: 7141.29Sbjh21 Bootloader update on ELF platforms. DDB in kernels from before 7151.29Sbjh21 this will be unable to read symbol tables provided by newer 7161.29Sbjh21 bootloaders. 7171.27Sassar 7181.27Sassar20010726: 7191.27Sassar Texinfo was updated to 4.0. To avoid failures when trying to 7201.28Sassar build the included texinfo files, do: 7211.28Sassar 7221.28Sassar cd src/gnu/usr.bin/texinfo 7231.28Sassar make MKINFO=no dependall install 7241.25Sthorpej 7251.25Sthorpej20010718: 7261.25Sthorpej Enabled correct .init/.fini processing in crt0. The way this 7271.25Sthorpej was done was to change a -I directive to cc(1), which means 7281.25Sthorpej make(1) will have a stale dependency (it will be checking the 7291.25Sthorpej timestamp on the wrong "dot_init.h"). 7301.25Sthorpej 7311.25Sthorpej The symptom you will see is that new programs die with SIGSEGV 7321.25Sthorpej if you have a stale dependency. 7331.25Sthorpej 7341.25Sthorpej Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so 7351.25Sthorpej before starting your build. 7361.26Sthorpej 7371.26Sthorpej20010628: 7381.26Sthorpej A construct was added to uvm_page.h that uncovered a bug 7391.26Sthorpej in lint(1). If you get a warning/error about a non-portable 7401.26Sthorpej bitfield, update your lint(1) before proceeding. 7411.21Sjmc 7421.21Sjmc20010226: 7431.22Sjmc Added named user/group to system. Need to hand add this in or builds 7441.21Sjmc will break as mtree aborts early. 7451.21Sjmc 7461.21Sjmc To work around add by hand: 7471.21Sjmc 7481.21Sjmc named:*:14: 7491.21Sjmc 7501.22Sjmc to /etc/group and add: 7511.22Sjmc 7521.22Sjmc named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin 7531.22Sjmc 7541.22Sjmc to master.passwd (use vipw for instance if doing by hand). 7551.22Sjmc 7561.22Sjmc Now a make build should progress. 7571.18Sjmc 7581.18Sjmc20010219: 7591.52Swiz get/setprogname() added. Any hostprogs that may use this will need 7601.111Ssimonb to be bootstrapped manually until the host system is current. 7611.18Sjmc 7621.111Ssimonb Known problems: sys/arch/macppc/stand/fixcoff 7631.19Scgd usr.sbin/config (adding -DMAKE_BOOTSTRAP to 7641.19Scgd CFLAGS and rebuilding should work) 7651.20Sjmc usr.sbin/mdsetimage - Build a static copy if 7661.111Ssimonb building a snapshot before fully bootstrapped. 7671.15Schristos 7681.15Schristos20010204: 7691.15Schristos prepare the code to compile with stricter gcc flags. in 7701.15Schristos particular start eliminating redundant declarations. Yacc 7711.15Schristos needs to be installed before make build. 7721.10Schristos 7731.10Schristos20010114: 7741.10Schristos introduce .if commands(target) in make(1). You need to 7751.10Schristos bring everything up-to-date first, then without installing 7761.23Stron anything make and install in usr.bin/make, then proceed 7771.10Schristos with make build. 7781.9Ssommerfe 7791.9Ssommerfe20010101: 7801.9Ssommerfe bsd.subdir.mk committed 20001230 had a bug which caused 7811.9Ssommerfe afterinstall targets to run too soon; update again. 7821.8Ssommerfe 7831.8Ssommerfe20001230: 7841.8Ssommerfe New share/mk files needed to support .WAIT in SUBDIR variables. 7851.8Ssommerfe If you get make errors, 7861.8Ssommerfe (cd share/mk; make install) 7871.8Ssommerfe Also, PRINTOBJDIR has changed and is now used more heavily. 7881.6Sad 7891.6Sad20001019: 7901.7Sad The `ca' device driver has been replaced by `ld'; although the 7911.6Sad major and minor numbers haven't changed, you should update your /dev 7921.6Sad directory. 7931.1Sabs 7941.4Sitojun20000929: 7951.4Sitojun The following make directives are obsoleted. 7961.4Sitojun MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 7971.4Sitojun By default, RSA is built into libcrypto. IDEA and RC5 will not be 7981.16Swiz built into libcrypto. By using MKCRYPTO_{RC5,IDEA}, you can build 7991.4Sitojun additional library libcrypto_{idea,rc5}. 8001.1Sabs 8011.1Sabs 8021.1SabsHints for a more successful build: 8031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8041.123Sjmc Use build.sh, but do not use its "expert mode": 8051.132Sjmmv This will automatically build the tools in the 8061.123Sjmc correct order, and it will keep the tools and the 8071.123Sjmc new build products from interfering with the running 8081.123Sjmc system. This will allow you to ignore most of the 8091.123Sjmc other advice in this file. 8101.2Smrg Build a new kernel first: 8111.2Smrg This makes sure that any new system calls or features 8121.2Smrg expected by the new userland will be present. This 8131.2Smrg helps to avoid critical errors when upgrading. 8141.1Sabs Use object directories: 8151.1Sabs This helps to keep stale object 8161.1Sabs files from polluting the build if a Makefile "forgets" 8171.1Sabs about one. It also makes it easier to clean up after 8181.1Sabs a build. It's also necessary if you want to use the 8191.1Sabs same source tree for multiple machines. 8201.123Sjmc To use object directories with build.sh: 8211.123Sjmc a) invoke build.sh with the "-M" or "-O" options. 8221.123Sjmc To use object directories without using build.sh: 8231.1Sabs a) cd /usr/src ; make cleandir 8241.2Smrg b) Add "OBJMACHINE=yes" to /etc/mk.conf 8251.2Smrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf 8261.1Sabs d) cd /usr/src ; make build 8271.2Smrg Note that running "make obj" in a directory will create 8281.2Smrg in obj.$MACHINE directory. 8291.1Sabs Build to a DESTDIR: 8301.123Sjmc This helps to keep old installed files (especially libraries) 8311.123Sjmc from interfering with the new build. 8321.123Sjmc To build to a DESTDIR with build.sh, use the "-D" option. 8331.123Sjmc To build to a DESTDIR without using build.sh, set the DESTDIR 8341.123Sjmc environment variable before running make build. It should be 8351.123Sjmc set to the pathname of an initially empty directory. 8361.123Sjmc Problems: if you do not use build.sh, you might need to 8371.123Sjmc update critical utilities without using DESTDIR since 8381.123Sjmc nothing is executed from what is installed in DESTDIR. 8391.123Sjmc (See critical utils, below.) 8401.1Sabs Build often: 8411.1Sabs This keeps critical utilities current enough to not choke 8421.1Sabs on any other part of the source tree that depends on up to 8431.123Sjmc date functionality. If you use build.sh, you should not have 8441.123Sjmc this problem. 8451.1Sabs 8461.1SabsWhat to do if things don't work: 8471.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8481.1SabsWhen things don't work there is usually a few things that commonly 8491.1Sabsshould be done. 8501.1Sabs 1) make includes 8511.1Sabs This should be done automatically by make build. 8521.1Sabs 2) cd share/mk && make install 8531.1Sabs Again, automatically done by make build. 8541.1Sabs 8551.1SabsFailsafe rebuild of a small part of the tree: 8561.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8571.1SabsTo make sure you rebuild something correctly you want to do 8581.1Sabssomething like the following: 8591.1Sabs 1) Make sure the includes and .mk files are up to date. 8601.1Sabs 2) Make sure any program used to build the particular 8611.1Sabs utility is up to date. (yacc, lex, etc...) 8621.1Sabs 3) cd ...path/to/util... 8631.1Sabs make cleandir 8641.1Sabs rm ...all obj directories... 8651.1Sabs make cleandir # yes, again 8661.1Sabs make obj 8671.1Sabs make depend && make 8681.1Sabs 8691.1SabsFailsafe rebuild of the entire tree: 8701.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 8711.1SabsIf you really want to make sure the source tree is clean and 8721.2Smrgready for a build try the following. Note that sourcing /etc/mk.conf 8731.2Smrg(a make(1) Makefile) in this manner is not right, and will not work 8741.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf. 8751.1Sabs 8761.1Sabs---cut here--- 8771.1Sabs#!/bin/sh 8781.1Sabs. /etc/mk.conf 8791.1Sabs 8801.58Slukemif [ -z $NETBSDSRCDIR ] ; then 8811.58Slukem NETBSDSRCDIR=/usr/src 8821.1Sabsfi 8831.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then 8841.1Sabs echo Unable to find sources 8851.1Sabs exit 1 8861.1Sabsfi 8871.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \; 8881.1Sabs 8891.1Sabsif [ -z $BSDOBJDIR ] ; then 8901.1Sabs BSDOBJDIR=/usr/obj 8911.1Sabsfi 8921.1Sabsif [ -d $BSDOBJDIR ] ; then 8931.1Sabs rm -rf $BSDOBJDIR 8941.1Sabsfi 8951.1Sabs 8961.58Slukemcd $NETBSDSRCDIR && make cleandir 8971.1Sabs 8981.1Sabs---cut here--- 8991.1Sabs 9001.1SabsCritical utilities: 9011.1Sabs^^^^^^^^^^^^^^^^^^^ 9021.3Sitojun usr.bin/compile_et 9031.1Sabs usr.bin/make 9041.1Sabs usr.bin/yacc 9051.1Sabs usr.bin/lex 9061.11Slukem usr.bin/xlint 9071.142Sdrochner usr.bin/config 9081.1Sabs 9091.34SsimonbOther problems and possible solutions: 9101.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 9111.1SabsSymptom:Complaints involving a Makefile. 9121.17SerhFix: Rebuild usr.bin/make: 9131.17Serh cd usr.bin/make && make && make install 9141.111Ssimonb Or, a failsafe method if that doesn't work: 9151.17Serh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin 9161.17Serh 9171.1SabsFix: Make sure .mk files are up to date. 9181.1Sabs cd share/mk && make install 9191.2Smrg 9201.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC. 9211.142SdrochnerFix: Rebuild usr.bin/config 9221.1Sabs 9231.1SabsSymptom: 9241.1SabsFix: Rebuild usr.bin/yacc 9251.1Sabs 9261.1SabsSymptom: 9271.1SabsFix: Rebuild usr.bin/lex 9281.1Sabs 9291.1SabsSymptom: 9301.1SabsFix: rm /usr/lib/libbfd.a 9311.4Sitojun 9321.4SitojunSymptom:Obsolete intermediate files are used during compilation 9331.4SitojunFix: Try the following sequence of commands in the directory in question. 9341.4Sitojun make cleandir; rm `make print-objdir`; make cleandir; make obj 9351.4Sitojun (If you built the tree without "make obj" in the past, obsolete files 9361.4Sitojun may remain. The command tries to clean everything up) 9371.5Swiz 9381.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type 9391.5SwizFix: Rebuild and install usr.bin/menuc 9401.12Sitojun 9411.12SitojunSymptom:mklocale not found during build in share/locale/ctype 9421.12SitojunFix: Build and install usr.bin/mklocale 9431.13Sdogcow 9441.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13' 9451.13SdogcowFix: Rebuild and install lib/libc 9461.13Sdogcow 9471.142SdrochnerSymptom:usr.bin/config fails to build. 9481.19ScgdFix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. 9491.13Sdogcow 9501.19ScgdSymptom:undefined reference to `getprogname' or `setprogname' 9511.19ScgdFix: Rebuild and install lib/libc 9521.24Sabs 9531.24SabsSymptom:lint does not understand the '-X' option 9541.24SabsFix: May need to build & install libs with NOLINT=1 before rebuilding lint 955