[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.167 and 1.208

version 1.167, 2007/11/17 09:53:16 version 1.208, 2010/02/04 22:25:21
Line 16  See also: BUILDING, build.sh, Makefile.
Line 16  See also: BUILDING, build.sh, Makefile.
 Recent changes:  Recent changes:
 ^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^
           The termcap database has been removed from the sources,
           but has not been marked obsolete so it is not removed
           from the system when upgrading.
           As such, you will need to remove them from your object
           and destination directories.
           After updating, it may be necessary to make the 'cleandir'
           target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
           'build.sh -u tools' or 'build.sh -u distribution'.  Ditto
           src/tools/lex/ and src/usr.bin/lex/.
           On amd64 you must rebuild tools (to get the new binutils)
           before building a kernel, or the build fails on cpufunc.S.
           An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
           symlink, failing the build.  Delete the link, and the subdir
           it is in, and retry your build.
           libc build changed so that strchr() provides the extra entry
           point for index(). Update build of libc.a (and libc_pic.a)
           may fail because the archive contains the unwanted index.o.
           (Similarly for strrchr() and rindex().)
           Native Xorg was upgraded again.  Builds will probably fail again
           without a clean objdir, at least for src/external/mit/xorg.
           Native Xorg was upgraded.  Builds will need a clean objdir for
           src/external/mit/xorg.  Upgrading a system from sets will not
           work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
           subdirectory has been changed into a file, and this needs to
           be manually "rm -r"'ed before installing xbase.tgz.
           Several new functions were added to string.h/libc, and this
           can cause autoconf problems during the tool build for people
           who fail to clean out their tools objects properly. If you
           note messages about stpcpy, stpncpy or strnlen accompanying a
           failure during the tool build, clean out all your tools
           objects and start again.
           The i386 port was switched to i486 default toolchain.  This requires
           cleaning your src/tools directory and $TOOLDIR and rebuilding them.
           The __posix_fadvise50 system call changed assembly stub type. You
           need to 'rm -f __posix_fadvise50.*' in the libc build directory
           to avoid using the old assembly stub.
           pkg_install now depends on the pkgdb cache for automatic conflict
           detection.  It is recommented to rebuild the cache with
           ``pkg_admin rebuild''.
           time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
           1. Make sure your kernel has COMPAT_50 in it. Build and install.
              This is needed even in the MODULAR kernel because there is
              conditionally compiled code in rtsock.c.
           2. make sure build.sh completes and the binaries in a chroot work
              before installing.
           3. If you don't use build.sh and you build directly to root, and
              your build breaks in the middle, don't despair. Make sure headers
              are installed properly, and start building libraries first libc
              and libutil, install them and then continue building all the
              libraries in src/lib and src/gnu/lib and install them. Once
              the new libraries are installed, you can restart the build.
           4. If you compile packages and you notice link time warnings,
              rebuild the required packages to update their shared libraries.
              Any package you rebuild will require rebuilding all the packages
              that depend on it.
           5. Next time you run pwd_mkdb with the new binary, the file
              will be upgraded and it will not be backwards compatible.
           6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
              lastlogx(5)) have been versioned, and there is a heuristic
              for utmp. You are better off removing the old files after
              upgrading.  The automated clearing of /var/run during
              boot, and the automated rotating of files in /var/log by
              newsyslog(8), may mean that you do not have to remove the
              files manually.
           7. The optional accounting file (/var/account/acct, see
              accton(8)) has not been versioned, and will need to be
              removed.  The automatic rotation of the accounting file by
              /etc/daily limits the bad consequences of failure to remove
              the file.
           8. Application software that writes time_t to binary files on
              disk will break or need attention. Most notably: if you are
              using PostgreSQL < 8.4, you need to dump your databases,
              rebuild PostgreSQL with the new time_t, then restore.
           config(1) has been updated, and one of the files it creates -
           swapnetbsd.o - has changed format.  You need to rebuild config
           (done automatically by build.sh) and then you need to rerun
           config on all kernel configuration files before rebuilding those
           If you build with MKX11=no, you should remove /etc/rc.d/xdm and
           /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
           set and will appear as extra files for MKX11=no update builds.
           On i386, various kernel options(4) in GENERIC including
           file systems have been disabled and moved into kernel modules.
           Before trying a new GENERIC kernel, you have to prepare the
           following files as well as a new GENERIC kernel:
           - build and install kernel modules from src/sys/modules
           - install the latest bootloader, which will load a module
             for the file system from which the kernel is loaded automatically
           If you have to load your kernel from a file system which is not of
           the same type as the root file system, you have to load the necessary
           file system module manually on the boot prompt or in the boot.cfg file.
           If you built and installed a libc from sources between
           2008/08/20 and 2008/08/26 you got a broken strtouq(3)
           which results in false errors reported by lint(1).
           Since this breaks the libc build itself, manual help is
           needed -- lint must be disabled temporarily, e.g.:
             $ (cd lib/libc && make MKLINT=no dependall install)
           MKDEBUG build was broken because the .depend files did not know
           about .go files. You need to remove all .depend files and rebuild.
           A regression in binary compatibility for pthread_mutex_t has
           been fixed. Unfortunately, the price is breaking compatibility
           for -current.
           Threaded programs (using libpthread) and C++ programs (using
           libstdc++) compiled after 20070907 and before 20080802 need to
           be recompiled.
           One way to find affected pkgsrc packages:
             $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
             $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
           WAPBL (metadata journaling support) has been added, but at this
           time isn't backwards compatible with pre-WAPBL aware kernels
           and userland (fsck_ffs in particular).  Please make sure you
           don't use a journaled filesystem with an older kernel/userland,
           especially an uncleanly mounted journaled filesystem.  WAPBL
           also requires the super block to be in the UFS2 format.  You
           can use fsck_ffs -c 4 to update the superblock format.
           Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
           isn't defined.
           The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
           from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
           utility needs to be rebuilt and reinstalled as older binaries
           won't work correctly. The following sequence of commands:
             $ (cd sys/sys/ && nbmake-$arch includes)
             $ (cd sbin/drvctl/ && nbmake-$arch clean)
             $ (cd sbin/drvctl/ && nbmake-$arch all)
           leaves new drvctl utility in sbin/drvctl build directory.
           The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
           For a while, unprivileged UPDATE builds would fail to
           succeed at the checkflist stage, complaining that
           ${DESTDIR}/stand/<arch>/ did not exist.  A fix for this
           problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
           If you already hit this problem, update the .mk file,
           remove ${DESTDIR}/stand/<arch>, and re-run the build.
           Linker warnings are now fatal if $WARNS>0.
           The posix_fadvise system call has been changed from an assembly
           stub, to a c file that calls an assembly stub. You need to
           'rm -f posix_fadvise.* .depend' in the libc build directory to
           avoid using the old assembly stub.
           The acpiec(4) driver has been split into two attachments. If you
           get ACPI errors before the attachment, please update your kernel
           configuration file appropriately or see GENERIC for more details.
 20071115:  20071115:
         The it(4) driver has been renamed to itesio(4) and the old port          The it(4) driver has been renamed to itesio(4) and the old port
         argument specified in the kernel configuration file is not valid          argument specified in the kernel configuration file is not valid
Line 42  Recent changes:
Line 242  Recent changes:
         and userland are from after 20070913.          and userland are from after 20070913.
 20070703:  20070703:
         nbinstall has been renamed as it calls the target specific and          nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
         the logic to pass down STRIP from mk been removed.  This forces          calls the target-specific strip program, and the logic to pass
         a re-installation of tools.          down STRIP from make has been removed.  This requires a
           re-installation of tools.
 20070422:  20070422:
         The way OS emulations lookup filenames inside the emulation root          The way OS emulations lookup filenames inside the emulation root
Line 262  Fix: Try the following sequence of comma
Line 463  Fix: Try the following sequence of comma
         (If you built the tree without "make obj" in the past, obsolete files          (If you built the tree without "make obj" in the past, obsolete files
         may remain.  The command tries to clean everything up)          may remain.  The command tries to clean everything up)
 Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type  Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
           pointer type
 Fix:    Rebuild and install usr.bin/menuc  Fix:    Rebuild and install usr.bin/menuc
 Symptom:mklocale not found during build in share/locale/ctype  Symptom:mklocale not found during build in share/locale/ctype

Removed from v.1.167  
changed lines
  Added in v.1.208

CVSweb <webmaster@jp.NetBSD.org>