Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. =================================================================== RCS file: /ftp/cvs/cvsroot/src/UPDATING,v rcsdiff: /ftp/cvs/cvsroot/src/UPDATING,v: warning: Unknown phrases like `commitid ...;' are present. retrieving revision 1.102 retrieving revision 1.127 diff -u -p -r1.102 -r1.127 --- src/UPDATING 2004/01/09 19:36:28 1.102 +++ src/UPDATING 2004/10/01 15:29:23 1.127 @@ -1,20 +1,154 @@ -$NetBSD: UPDATING,v 1.102 2004/01/09 19:36:28 dbj Exp $ +$NetBSD: UPDATING,v 1.127 2004/10/01 15:29:23 christos Exp $ -This file is intended to be a brief introduction to the build -process and a reference on what to do if something doesn't work. +This file (UPDATING) is intended to be a brief reference to recent +changes that might cause problems in the build process, and a guide for +what to do if something doesn't work. -For a more detailed description see Makefile. +For a more detailed description of the recommended way to build NetBSD +using build.sh, see the BUILDING file. + +Note that much of the advice in this UPDATING file was written before +build.sh existed. Nevertheless, the advice here may be useful for +working around specific problems with build.sh. + +See also: BUILDING, build.sh, Makefile. Recent changes: ^^^^^^^^^^^^^^^ +20041001: + The ipfilter kernel sources moved from sys/netinet to + dist/sys/ipf/netinet. Due to the move some Makefile + dependencies are now dangling requiring a make cleandir + before they work again (kdump, ktruss, rescue, ipf are + amongst the victims). + +20040715: + The rc.d/sendmail script now uses a heuristic to determine + if sendmail should be started at boot time. It checks the + contents of /etc/mailer.conf, /etc/mail/submit.cf, and the + owner and mode of the sendmail binary to see if any changes + to the mail infrastructure have been made. If no changes + are detected, it will start an SMTP listener. + + Setting sendmail=NO in /etc/rc.conf will override this. + + If you are only using sendmail by default and only for + local delivery, it is important that you also update your + sendmail.cf so that the SMTP listener only listens on the + loopback interface. + +20040715: + The method by which athhal-elf.o gets pulled into i386 + kernel builds has been changed again. The latest version + of bsd.files.mk is no longer required. + +20040621: + Due to the recent rototill of tools/compat it's crucial one starts + from a clean objdir under tools/*. + + This is mostly due to generated files (yacc and lex sources) needing + to be generated with new rules from bsd.hostprog.mk. + + The safest course is to rm -rf all objects under tools before building. + +20040516: + The end-user modifiable X11 configuration has been moved + from /usr/X11R6/lib/X11/ to /etc/X11/. + Ensure that src and xsrc is up to date, and run + "make cleandir" in src/x11 before your next build. + + postinstall currently doesn't migrate the files from + /usr/X11R6/lib/X11/* to /etc/X11/* although it does + detect that this needs to occur, so you'll have to + manually move these files yourself. + +20040426: + Support for the original dynamic sysctl node structure has + been removed in favor of the newer layout. This affects + consumers of the create and delete interface, as well as + the dynamic discovery mechanism. This is believed only to + be the sysctl(8) binary itself, at this point in time, so + the only effect of this should be that a sysctl binary + built from sources dated between 2003/12/04 and 2004/03/24 + will not work on a kernel built from sources dated after + 2004/04/25. If you need a new sysctl binary but build.sh + does not work, make sure that your revision of + src/sys/sys/sysctl.h is 1.112 (or later), and then the + do the following: + + cd /usr/src (or wherever your source tree is) + make USETOOLS=no includes + cd lib/libc + make USETOOLS=no dependall install + cd ../../sbin/sysctl + make USETOOLS=no dependall install + + If you are using older sysctl binary, GNU autoconf would fail to + identify your machine architecture, and tries to build binary for + "unknown-unknown-netbsd20F" or something like that. if that happens, + make sure to follow the above steps. + +20040425: + The ffs superblock issues listed below under 20040109 and 20030402 + are now automatically addressed by the /etc/rc.d/fixsb script or by + sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 + invocation mentioned below will continue to work and is now + automated by those scripts. Note that under certain circumstances, + affected filesystems upgraded to a -current kernel first before + upgrading their userland with the fixsb and fsck_ffs fixes may + encounter a 'freeing free inode' panic when writing to the affected + filesystem, so it is a good idea to repair the filesystem as soon as + possible. For more details on the fixsb script, see pr install/25138. + +20040418: + statfs(2) and friends have been replaced with statvfs(2). Before + installing a newly build userland make sure that you are running + a newly built kernel with COMPAT_20 set. In addition your libc + build might not work (undefined SYS_statfs symbol) because make + clean does not know how to remove files it does not know about + anymore. Manually remove all generated .S sources and objects + from the libc build directory. + +20040326: + The method by which athhal-elf.o gets pulled into i386 kernel builds + has been changed. The file is now stored as a uuencoded file in CVS + and the generated Makefile will use the new .uue rules from bsd.file.mk + to build it. + + This means you must have the latest bsd.files.mk installed when + building a kernel without USETOOLS=yes. + +20040318: + A bug in the cgd(4) blowfish code was corrected, without + provision of backwards compatibility, after several public + notices over several months. Users of cgd with blowfish cipher + ONLY must dump their data before updating their kernels, and + recreate cgd's and restore data using the new kernel. See + (recent message to current-users, URL when mail-index has updated) + +20040313: + On acorn32, the opms and qms drivers have been withdrawn, and + the old wsqms driver is now called qms. Kernel config files + will need updating. See the ones in sys/arch/acorn32/conf + for examples. + +20040125: + On acorn32, the beep and sysbeep devices are no longer + needed, and will need to be deleted from kernel configuration + files. + 20040109: Compatibility for old ffs superblock layouts has been added, and the restrictive fsck checks have been reenabled when using those layouts. If you have been using -current since 20030402, you may find that fsck again signals fatal - superblock mismatches. To work around, you can use - fsck -b 32 to restore an alternate superblock. + superblock mismatches. To repair, make sure you have + an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 + to complete the filesystem upgrade. A message has + been added to the kernel which should detect this problem. + See the following discussion for more information: + http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html 20031203: New binutils builds may fail due to old dependencies. @@ -30,6 +164,15 @@ Recent changes: It's necessary to "make cleandir" to ensure that the dependencies will be rebuilt correctly. +20031007: + A sign exension bug was fixed which set all the high bits + of our newly expanded ffs fs_flags. This should only + affect users who installed or upgraded in September of 2003. + A small utility program was posted to tech-kern which + should fix this problem, and a warning message was added + to the kernel which should discover and warn about it. See + http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html + 20030906: With the addition of siginfo support the old signal trampoline code has been deprecated to COMPAT_16. Make sure that your running @@ -395,7 +538,7 @@ Recent changes: 20010803: (i386 only): i386 kernel now uses new instructions like - `fxsave' which old gas doesn't understand. To build the + `fxsave' which old gas doesn't understand. To build the kernel successfully, you need to build and install a new toolchain, (i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" from your kernel configuration until you rebuild your userland. @@ -449,13 +592,13 @@ Recent changes: 20010219: get/setprogname() added. Any hostprogs that may use this will need - to be bootstrapped manually until the host system is current. + to be bootstrapped manually until the host system is current. - Known problems: sys/arch/macppc/stand/fixcoff + Known problems: sys/arch/macppc/stand/fixcoff usr.sbin/config (adding -DMAKE_BOOTSTRAP to CFLAGS and rebuilding should work) usr.sbin/mdsetimage - Build a static copy if - building a snapshot before fully bootstrapped. + building a snapshot before fully bootstrapped. 20010204: prepare the code to compile with stricter gcc flags. in @@ -493,6 +636,12 @@ Recent changes: Hints for a more successful build: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + Use build.sh, but do not use its "expert mode": + This will will automatically build the tools in the + correct order, and it will keep the tools and the + new build products from interfering with the running + system. This will allow you to ignore most of the + other advice in this file. Build a new kernel first: This makes sure that any new system calls or features expected by the new userland will be present. This @@ -503,7 +652,9 @@ Hints for a more successful build: about one. It also makes it easier to clean up after a build. It's also necessary if you want to use the same source tree for multiple machines. - To use object directories: + To use object directories with build.sh: + a) invoke build.sh with the "-M" or "-O" options. + To use object directories without using build.sh: a) cd /usr/src ; make cleandir b) Add "OBJMACHINE=yes" to /etc/mk.conf c) Add "MKOBJDIRS=yes" to /etc/mk.conf @@ -511,20 +662,21 @@ Hints for a more successful build: Note that running "make obj" in a directory will create in obj.$MACHINE directory. Build to a DESTDIR: - This helps to keep old - installed files (especially libraries) from interfering - with the new build. - To build to a DESTDIR, set the DESTDIR environment - variable before running make build. It should be set to - the pathname of an initially empty directory. - Problems: you might need to update critical utilities - without using DESTDIR since nothing is executed - from what is installed in DESTDIR. - (See critical utils, below) + This helps to keep old installed files (especially libraries) + from interfering with the new build. + To build to a DESTDIR with build.sh, use the "-D" option. + To build to a DESTDIR without using build.sh, set the DESTDIR + environment variable before running make build. It should be + set to the pathname of an initially empty directory. + Problems: if you do not use build.sh, you might need to + update critical utilities without using DESTDIR since + nothing is executed from what is installed in DESTDIR. + (See critical utils, below.) Build often: This keeps critical utilities current enough to not choke on any other part of the source tree that depends on up to - date functionality. + date functionality. If you use build.sh, you should not have + this problem. What to do if things don't work: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -598,7 +750,7 @@ Fix: Rebuild gnu/usr.bin/egcs Symptom:Complaints involving a Makefile. Fix: Rebuild usr.bin/make: cd usr.bin/make && make && make install - Or, a failsafe method if that doesn't work: + Or, a failsafe method if that doesn't work: cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin Fix: Make sure .mk files are up to date.