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.112
retrieving revision 1.135
diff -u -p -r1.112 -r1.135
--- src/UPDATING 2004/03/16 14:33:03 1.112
+++ src/UPDATING 2005/02/11 17:50:13 1.135
@@ -1,12 +1,166 @@
-$NetBSD: UPDATING,v 1.112 2004/03/16 14:33:03 keihan Exp $
+$NetBSD: UPDATING,v 1.135 2005/02/11 17:50:13 jmc 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:
^^^^^^^^^^^^^^^
+20050211:
+ Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in
+ some of the cross tools to fail if they use configure. Some configure's
+ cache the environment passed in and notice the new environment is
+ different and abort. Doing a clean in tools/ should be enough to
+ make a build continue.
+
+20050109:
+ Since su is using pam by default now, make sure that you have
+ /etc/pam.d populated (postinstall will do that automatically
+ for you). Otherwise su will fail open (i.e. will not require
+ a password).
+
+20041229:
+ Make had a path resolution bug that manifested itself as not
+ being able to install openpam.3. This bug has been fixed, but
+ you might need to rebuild make manually first to get through
+ the build.
+
+20041201:
+ Userland programs have been changed to use /dev/bpf instead of
+ /dev/bpfX. You need to create that device by installing a new
+ MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]*
+
+20041006:
+
+ A bug was introduced into /bin/sh (var.c rev 1.35) which causes
+ variables to not export correctly to subshells in all cases. This
+ will cause builds to break if that version of /bin/sh is installed
+ on the system. The proper version of /bin/sh can be verified with:
+
+ ident /bin/sh | grep var
+
+ Any /bin/sh w. version 1.35 will not work and needs to be updated
+ before attempting a build.
+
+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, and
+ ftp-proxy are 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
@@ -517,6 +671,12 @@ Recent changes:
Hints for a more successful build:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ Use build.sh, but do not use its "expert mode":
+ This 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
@@ -527,7 +687,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
@@ -535,20 +697,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:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^