[BACK]Return to UPDATING CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / src

Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.

Diff for /src/UPDATING between version 1.121 and 1.140

version 1.121, 2004/05/16 11:33:44 version 1.140, 2005/06/03 11:02:59
Line 1 
Line 1 
 $NetBSD$  $NetBSD$
   
 This file is intended to be a brief introduction to the build  This file (UPDATING) is intended to be a brief reference to recent
 process and a reference on what to do if something doesn't work.  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 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.
   
 For a more detailed description see Makefile.  See also: BUILDING, build.sh, Makefile.
   
 Recent changes:  Recent changes:
 ^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^
   
   20050531:
           genassym.sh(8) was moved to genassym(8). You need to either build
           tools first or install the version of genassym from /usr/sbin before
           you can build a kernel again.
   
   20050520:
           Because a kernfs bug which xentools relies on was fixed,
           xentools up to xentools20-2.0.3nb4 won't work with new kernel.
   
   20050417:
           postinstall(8) was moved from /etc to /usr/sbin and made part
           of the "base" set, to make it easier to invoke after an
           upgrade.
   
   20050325:
           pcppi(4) was separated in two devices, adding attimer(4).  Be sure
           to add a config line for an attimer(4) device in your kernel
           configuration, or you won't be able to set the pitch of the beep
           with wsconsctl.  Depending on the default value for the pitch, you
           might even not hear any more beep.  Also, it is advised to attach both
           devices the same way (i.e., both on isa or both on acpi) or the
           pcppi(4) device may fail to find the attimer(4) one.
   
   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:  20040516:
         The end-user modifiable X11 configuration has been moved          The end-user modifiable X11 configuration has been moved
         from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.          from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.
         Ensure that src and xsrc is up to date, and run          Ensure that src and xsrc is up to date, and run
         "make cleandir" in src/x11 before your next build.          "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:  20040426:
         Support for the original dynamic sysctl node structure has          Support for the original dynamic sysctl node structure has
         been removed in favor of the newer layout.  This affects          been removed in favor of the newer layout.  This affects
Line 35  Recent changes:
Line 143  Recent changes:
         cd ../../sbin/sysctl          cd ../../sbin/sysctl
         make USETOOLS=no dependall install          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:  20040425:
         The ffs superblock issues listed below under 20040109 and 20030402          The ffs superblock issues listed below under 20040109 and 20030402
         are now automatically addressed by the /etc/rc.d/fixsb script or by          are now automatically addressed by the /etc/rc.d/fixsb script or by
Line 582  Recent changes:
Line 695  Recent changes:
   
 Hints for a more successful build:  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:      Build a new kernel first:
         This makes sure that any new system calls or features          This makes sure that any new system calls or features
            expected by the new userland will be present.  This             expected by the new userland will be present.  This
Line 592  Hints for a more successful build:
Line 711  Hints for a more successful build:
            about one.  It also makes it easier to clean up after             about one.  It also makes it easier to clean up after
            a build.  It's also necessary if you want to use the             a build.  It's also necessary if you want to use the
            same source tree for multiple machines.             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              a) cd /usr/src ; make cleandir
             b) Add "OBJMACHINE=yes" to /etc/mk.conf              b) Add "OBJMACHINE=yes" to /etc/mk.conf
             c) Add "MKOBJDIRS=yes" to /etc/mk.conf              c) Add "MKOBJDIRS=yes" to /etc/mk.conf
Line 600  Hints for a more successful build:
Line 721  Hints for a more successful build:
            Note that running "make obj" in a directory will create             Note that running "make obj" in a directory will create
            in obj.$MACHINE directory.             in obj.$MACHINE directory.
     Build to a DESTDIR:      Build to a DESTDIR:
         This helps to keep old          This helps to keep old installed files (especially libraries)
            installed files (especially libraries) from interfering             from interfering with the new build.
            with the new build.             To build to a DESTDIR with build.sh, use the "-D" option.
            To build to a DESTDIR, set the DESTDIR environment             To build to a DESTDIR without using build.sh, set the DESTDIR
            variable before running make build.  It should be set to             environment variable before running make build.  It should be
            the pathname of an initially empty directory.             set to the pathname of an initially empty directory.
            Problems: you might need to update critical utilities             Problems: if you do not use build.sh, you might need to
                 without using DESTDIR since nothing is executed                  update critical utilities without using DESTDIR since
                 from what is installed in DESTDIR.                  nothing is executed from what is installed in DESTDIR.
                 (See critical utils, below)                  (See critical utils, below.)
     Build often:      Build often:
         This keeps critical utilities current enough to not choke          This keeps critical utilities current enough to not choke
         on any other part of the source tree that depends on up to          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:  What to do if things don't work:
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Legend:
Removed from v.1.121  
changed lines
  Added in v.1.140

CVSweb <webmaster@jp.NetBSD.org>