1 $NetBSD: UPDATING,v 1.195 2009/05/01 23:08:25 perry Exp $
3 This file (UPDATING) is intended to be a brief reference to recent
4 changes that might cause problems in the build process, and a guide for
5 what to do if something doesn't work.
7 For a more detailed description of the recommended way to build NetBSD
8 using build.sh, see the BUILDING file.
10 Note that much of the advice in this UPDATING file was written before
11 build.sh existed. Nevertheless, the advice here may be useful for
12 working around specific problems with build.sh.
14 See also: BUILDING, build.sh, Makefile.
20 Several new functions were added to string.h/libc, and this
21 can cause autoconf problems during the tool build for people
22 who fail to clean out their tools objects properly. If you
23 note messages about stpcpy, stpncpy or strnlen accompanying a
24 failure during the tool build, clean out all your tools
25 objects and start again.
28 The i386 port was switched to i486 default toolchain. This requires
29 cleaning your src/tools directory and $TOOLDIR and rebuilding them.
32 The __posix_fadvise50 system call changed assembly stub type. You need to
33 'rm -f __posix_fadvise50.*' in the libc build directory to avoid using
34 the old assembly stub.
37 pkg_install now depends on the pkgdb cache for automatic conflict
38 detection. It is recommented to rebuild the cache with
39 ``pkg_admin rebuild''.
42 time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
43 1. Make sure your kernel has COMPAT_50 in it. Build and install.
44 This is needed even in the MODULAR kernel because there is
45 conditionally compiled code in rtsock.c.
46 2. make sure build.sh completes and the binaries in a chroot work
48 3. If you don't use build.sh and you build directly to root, and
49 your build breaks in the middle, don't despair. Make sure headers
50 are installed properly, and start building libraries first libc
51 and libutil, install them and then continue building all the
52 libraries in src/lib and src/gnu/lib and install them. Once
53 the new libraries are installed, you can restart the build.
54 4. If you compile packages and you notice link time warnings,
55 rebuild the required packages to update their shared libraries.
56 Any package you rebuild will require rebuilding all the packages
58 5. Next time you run pwd_mkdb with the new binary, the file
59 will be upgraded and it will not be backwards compatible.
60 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
61 lastlogx(5)) have been versioned, and there is a heuristic
62 for utmp. You are better off removing the old files after
63 upgrading. The automated clearing of /var/run during
64 boot, and the automated rotating of files in /var/log by
65 newsyslog(8), may mean that you do not have to remove the
67 7. The optional accounting file (/var/account/acct, see
68 accton(8)) has not been versioned, and will need to be
69 removed. The automatic rotation of the accounting file by
70 /etc/daily limits the bad consequences of failure to remove
72 8. Application software that writes time_t to binary files on
73 disk will break or need attention. Most notably: if you are
74 using PostgreSQL < 8.4, you need to dump your databases,
75 rebuild PostgreSQL with the new time_t, then restore.
78 config(1) has been updated, and one of the files it creates -
79 swapnetbsd.o - has changed format. You need to rebuild config
80 (done automatically by build.sh) and then you need to rerun
81 config on all kernel configuration files before rebuilding those
85 If you build with MKX11=no, you should remove /etc/rc.d/xdm and
86 /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
87 set and will appear as extra files for MKX11=no update builds.
90 On i386, various kernel options(4) in GENERIC including
91 file systems have been disabled and moved into kernel modules.
92 Before trying a new GENERIC kernel, you have to prepare the
93 following files as well as a new GENERIC kernel:
95 - build and install kernel modules from src/sys/modules
97 - install the latest bootloader, which will load a module
98 for the file system from which the kernel is loaded automatically
100 If you have to load your kernel from a file system which is not of
101 the same type as the root file system, you have to load the necessary
102 file system module manually on the boot prompt or in the boot.cfg file.
105 If you built and installed a libc from sources between
106 2008/08/20 and 2008/08/26 you got a broken strtouq(3)
107 which results in false errors reported by lint(1).
108 Since this breaks the libc build itself, manual help is
109 needed -- lint must be disabled temporarily, e.g.:
110 $ (cd lib/libc && make MKLINT=no dependall install)
113 MKDEBUG build was broken because the .depend files did not know
114 about .go files. You need to remove all .depend files and rebuild.
117 WAPBL (metadata journaling support) has been added, but at this
118 time isn't backwards compatible with pre-WAPBL aware kernels
119 and userland (fsck_ffs in particular). Please make sure you
120 don't use a journaled filesystem with an older kernel/userland,
121 especially an uncleanly mounted journaled filesystem. WAPBL
122 also requires the super block to be in the UFS2 format. You
123 can use fsck_ffs -c 4 to update the superblock format.
126 Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
130 The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
131 from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
132 utility needs to be rebuilt and reinstalled as older binaries
133 won't work correctly. The following sequence of commands:
135 $ (cd sys/sys/ && nbmake-$arch includes)
136 $ (cd sbin/drvctl/ && nbmake-$arch clean)
137 $ (cd sbin/drvctl/ && nbmake-$arch all)
139 leaves new drvctl utility in sbin/drvctl build directory.
142 The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
145 For a while, unprivileged UPDATE builds would fail to
146 succeed at the checkflist stage, complaining that
147 ${DESTDIR}/stand/<arch>/ did not exist. A fix for this
148 problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
149 If you already hit this problem, update the .mk file,
150 remove ${DESTDIR}/stand/<arch>, and re-run the build.
153 Linker warnings are now fatal if $WARNS>0.
156 The posix_fadvise system call has been changed from an assembly
157 stub, to a c file that calls an assembly stub. You need to
158 'rm -f posix_fadvise.* .depend' in the libc build directory to
159 avoid using the old assembly stub.
162 The acpiec(4) driver has been split into two attachments. If you
163 get ACPI errors before the attachment, please update your kernel
164 configuration file appropriately or see GENERIC for more details.
167 The it(4) driver has been renamed to itesio(4) and the old port
168 argument specified in the kernel configuration file is not valid
169 anymore. The itesio(4) driver now uses the Super I/O address port
170 rather than the EC address port. Please update your kernel
171 configuration file appropriately or see GENERIC for more details.
174 The pccons(4) driver has been removed from the NetBSD/shark port.
175 You need to update any custom kernel configuration file you have
176 to remove any references to pccons (which includes removing the
177 now useless XSERVER option) and replace them with the correct
178 entries for the wscons driver. See the GENERIC configuration file
182 A latent bug in dhclient/dhcpd that caused it to be unable to
183 enumerate interfaces was fixed. The bug began to cause
184 problems after 20070911 when the kernel's SIOCGIFCONF
185 implementation was repaired. From 20070529 to 20070911 racoon
186 could not enumerate interfaces. (These are noted because
187 normal kernel/userspace version matching hygiene is not
188 sufficient to avoid this problem.) Ensure that both kernel
189 and userland are from after 20070913.
192 nbinstall has been renamed as it calls the target specific and
193 the logic to pass down STRIP from mk been removed. This forces
194 a re-installation of tools.
197 The way OS emulations lookup filenames inside the emulation root
198 has been changed. Rather than modify the pathname (and copy back
199 to userspace) namei() and lookup() directly check the emulation
200 root. One side effect is that absolute symlinks inside the emulated
201 root file system will be relative to that file system - unless they
202 start /../ this is useful when the emulated root is a real install
204 This might affect symlinks that have been added to reference outside
208 The pckbc driver on sgimips IP32 has been removed. Use macekbc
209 instead. See the GENERIC32_IP3x kernel configuration for an
213 src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
214 on many platforms due to incorrect flags settings. If you
215 updated and built after about 20070315, do "nbmake-$arch
216 cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
217 rebuild of object files that might have been built
218 incorrectly, and ensure that you have at least
219 src/lib/libc/Makefile 1.130.
222 src/sys/sys/{sa.h,savar.h} were removed.
223 find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
224 | xargs egrep -l '/sa.h|/savar.h' | xargs rm
225 will allow dependencies on those files to get get rebuilt
228 The threading model was changed when the newlock2 branch
229 was merged to NetBSD-current. If you boot with a new
230 kernel (version 4.99.10), then you also need a new pthread
231 library (/usr/lib/libpthread.so.0.7). If you boot with
232 an old kernel, then you need the old pthread library
233 (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and
234 the pthread library in sync, old threaded applications should
235 continue to work with an old or new kernel. Note that named(8)
236 is the only threaded application in the base system.
239 Following the move of string_to_flags() and flags_to_string()
240 from the bin/ls/ sources to libutil, users doing UPDATE builds
241 will need to do a "make cleandir" in
242 tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
243 bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
244 usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
245 as the installation images in distrib/
246 in order to excise stale references to the old stat_flags.h header
247 file in the ls sources -- stat_flags.h has been removed.
250 The configure script used in the src/tools/gcc compiler has been
251 changed to indicate that our libc has ssp support built-in and
252 does not depend on -lssp and -lssp-nonshared. You'll need to
253 make clean in src/tools/gcc first to rebuild the compiler.
256 The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
257 available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
260 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
261 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC
262 kernel configuration for an example. X servers from the last
263 few years should cope.
266 MPACPI is no more. We always configure PCI interrupts using ACPI
267 if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
268 to ACPI_SCANPCI. Thanks to work from fvdl.
271 socket(2) has changed, and its system call has been versioned.
272 For userlands with the old version of socket(2), make sure that
273 your kernel has 'options COMPAT_30' set, or else 'bad system call'
276 Hints for a more successful build:
277 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
278 Use build.sh, but do not use its "expert mode":
279 This will automatically build the tools in the
280 correct order, and it will keep the tools and the
281 new build products from interfering with the running
282 system. This will allow you to ignore most of the
283 other advice in this file.
284 Build a new kernel first:
285 This makes sure that any new system calls or features
286 expected by the new userland will be present. This
287 helps to avoid critical errors when upgrading.
288 Use object directories:
289 This helps to keep stale object
290 files from polluting the build if a Makefile "forgets"
291 about one. It also makes it easier to clean up after
292 a build. It's also necessary if you want to use the
293 same source tree for multiple machines.
294 To use object directories with build.sh:
295 a) invoke build.sh with the "-M" or "-O" options.
296 To use object directories without using build.sh:
297 a) cd /usr/src ; make cleandir
298 b) Add "OBJMACHINE=yes" to /etc/mk.conf
299 c) Add "MKOBJDIRS=yes" to /etc/mk.conf
300 d) cd /usr/src ; make build
301 Note that running "make obj" in a directory will create
302 in obj.$MACHINE directory.
304 This helps to keep old installed files (especially libraries)
305 from interfering with the new build.
306 To build to a DESTDIR with build.sh, use the "-D" option.
307 To build to a DESTDIR without using build.sh, set the DESTDIR
308 environment variable before running make build. It should be
309 set to the pathname of an initially empty directory.
310 Problems: if you do not use build.sh, you might need to
311 update critical utilities without using DESTDIR since
312 nothing is executed from what is installed in DESTDIR.
313 (See critical utils, below.)
315 This keeps critical utilities current enough to not choke
316 on any other part of the source tree that depends on up to
317 date functionality. If you use build.sh, you should not have
320 What to do if things don't work:
321 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
322 When things don't work there is usually a few things that commonly
325 This should be done automatically by make build.
326 2) cd share/mk && make install
327 Again, automatically done by make build.
329 Failsafe rebuild of a small part of the tree:
330 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
331 To make sure you rebuild something correctly you want to do
332 something like the following:
333 1) Make sure the includes and .mk files are up to date.
334 2) Make sure any program used to build the particular
335 utility is up to date. (yacc, lex, etc...)
336 3) cd ...path/to/util...
338 rm ...all obj directories...
339 make cleandir # yes, again
343 Failsafe rebuild of the entire tree:
344 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
345 If you really want to make sure the source tree is clean and
346 ready for a build try the following. Note that sourcing /etc/mk.conf
347 (a make(1) Makefile) in this manner is not right, and will not work
348 for anyone who uses any make(1) features in /etc/mk.conf.
354 if [ -z $NETBSDSRCDIR ] ; then
355 NETBSDSRCDIR=/usr/src
357 if [ \! -d $NETBSDSRCDIR ] ; then
358 echo Unable to find sources
361 find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
363 if [ -z $BSDOBJDIR ] ; then
366 if [ -d $BSDOBJDIR ] ; then
370 cd $NETBSDSRCDIR && make cleandir
383 Other problems and possible solutions:
384 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
385 Symptom:Complaints involving a Makefile.
386 Fix: Rebuild usr.bin/make:
387 cd usr.bin/make && make && make install
388 Or, a failsafe method if that doesn't work:
389 cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
391 Fix: Make sure .mk files are up to date.
392 cd share/mk && make install
394 Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
395 Fix: Rebuild usr.bin/config
398 Fix: Rebuild usr.bin/yacc
401 Fix: Rebuild usr.bin/lex
404 Fix: rm /usr/lib/libbfd.a
406 Symptom:Obsolete intermediate files are used during compilation
407 Fix: Try the following sequence of commands in the directory in question.
408 make cleandir; rm `make print-objdir`; make cleandir; make obj
409 (If you built the tree without "make obj" in the past, obsolete files
410 may remain. The command tries to clean everything up)
412 Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
413 Fix: Rebuild and install usr.bin/menuc
415 Symptom:mklocale not found during build in share/locale/ctype
416 Fix: Build and install usr.bin/mklocale
418 Symptom:undefined reference to `__assert13' or `__unsetenv13'
419 Fix: Rebuild and install lib/libc
421 Symptom:usr.bin/config fails to build.
422 Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
424 Symptom:undefined reference to `getprogname' or `setprogname'
425 Fix: Rebuild and install lib/libc
427 Symptom:lint does not understand the '-X' option
428 Fix: May need to build & install libs with NOLINT=1 before rebuilding lint