UPDATING revision 1.189 1 1.189 hubertf $NetBSD: UPDATING,v 1.189 2009/01/14 15:53:29 hubertf Exp $
2 1.1 abs
3 1.123 jmc This file (UPDATING) is intended to be a brief reference to recent
4 1.123 jmc changes that might cause problems in the build process, and a guide for
5 1.123 jmc what to do if something doesn't work.
6 1.1 abs
7 1.123 jmc For a more detailed description of the recommended way to build NetBSD
8 1.123 jmc using build.sh, see the BUILDING file.
9 1.123 jmc
10 1.123 jmc Note that much of the advice in this UPDATING file was written before
11 1.123 jmc build.sh existed. Nevertheless, the advice here may be useful for
12 1.123 jmc working around specific problems with build.sh.
13 1.123 jmc
14 1.123 jmc See also: BUILDING, build.sh, Makefile.
15 1.1 abs
16 1.1 abs Recent changes:
17 1.1 abs ^^^^^^^^^^^^^^^
18 1.138 lukem
19 1.184 christos 20090110:
20 1.184 christos time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
21 1.184 christos 1. Make sure your kernel has COMPAT_50 in it. Build and install.
22 1.188 christos This is needed even in the MODULAR kernel because there is
23 1.188 christos conditionally compiled code in rtsock.c.
24 1.184 christos 2. make sure build.sh completes and the binaries in a chroot work
25 1.184 christos before installing.
26 1.184 christos 3. If you don't use build.sh and you build directly to root, and
27 1.187 dholland your build breaks in the middle, don't despair. Make sure headers
28 1.184 christos are installed properly, and start building libraries first libc
29 1.184 christos and libutil, install them and then continue building all the
30 1.184 christos libraries in src/lib and src/gnu/lib and install them. Once
31 1.184 christos the new libraries are installed, you can restart the build.
32 1.184 christos 4. If you compile packages and you notice link time warnings,
33 1.189 hubertf rebuild the required packages to update their shared libraries.
34 1.189 hubertf Any package you rebuild will require rebuilding all the packages
35 1.189 hubertf that depend on it.
36 1.186 christos 5. Next time you run pwd_mkdb with the new binary, the file
37 1.186 christos will be upgraded and it will not be backwards compatible.
38 1.186 christos 6. The utmpx/wtmpx files have been versioned, and there is
39 1.186 christos a heuristic for utmp. You are better off removing the
40 1.188 christos old files after upgrading. The accounting file has not
41 1.188 christos been versioned, and will need to be removed.
42 1.185 jmcneill
43 1.183 pgoyette 20081219:
44 1.183 pgoyette config(1) has been updated, and one of the files it creates -
45 1.183 pgoyette swapnetbsd.o - has changed format. You need to rebuild config
46 1.183 pgoyette (done automatically by build.sh) and then you need to rerun
47 1.183 pgoyette config on all kernel configuration files before rebuilding those
48 1.183 pgoyette kernels.
49 1.183 pgoyette
50 1.181 cube 20081205:
51 1.181 cube If you build with MKX11=no, you should remove /etc/rc.d/xdm and
52 1.181 cube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
53 1.181 cube set and will appear as extra files for MKX11=no update builds.
54 1.178 lukem
55 1.179 tsutsui 20081122:
56 1.182 tsutsui On i386, various kernel options(4) in GENERIC including
57 1.180 wiz file systems have been disabled and moved into kernel modules.
58 1.180 wiz Before trying a new GENERIC kernel, you have to prepare the
59 1.179 tsutsui following files as well as a new GENERIC kernel:
60 1.179 tsutsui
61 1.179 tsutsui - build and install kernel modules from src/sys/modules
62 1.179 tsutsui
63 1.179 tsutsui - install the latest bootloader, which will load a module
64 1.180 wiz for the file system from which the kernel is loaded automatically
65 1.179 tsutsui
66 1.180 wiz If you have to load your kernel from a file system which is not of
67 1.180 wiz the same type as the root file system, you have to load the necessary
68 1.180 wiz file system module manually on the boot prompt or in the boot.cfg file.
69 1.179 tsutsui
70 1.178 lukem 20080827:
71 1.178 lukem If you built and installed a libc from sources between
72 1.178 lukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3)
73 1.178 lukem which results in false errors reported by lint(1).
74 1.178 lukem Since this breaks the libc build itself, manual help is
75 1.180 wiz needed -- lint must be disabled temporarily, e.g.:
76 1.178 lukem $ (cd lib/libc && make MKLINT=no dependall install)
77 1.178 lukem
78 1.177 christos 20080813:
79 1.177 christos MKDEBUG build was broken because the .depend files did not know
80 1.177 christos about .go files. You need to remove all .depend files and rebuild.
81 1.177 christos
82 1.175 simonb 20080731:
83 1.175 simonb WAPBL (metadata journaling support) has been added, but at this
84 1.175 simonb time isn't backwards compatible with pre-WAPBL aware kernels
85 1.175 simonb and userland (fsck_ffs in particular). Please make sure you
86 1.175 simonb don't use a journaled filesystem with an older kernel/userland,
87 1.176 simonb especially an uncleanly mounted journaled filesystem. WAPBL
88 1.176 simonb also requires the super block to be in the UFS2 format. You
89 1.176 simonb can use fsck_ffs -c 4 to update the superblock format.
90 1.175 simonb
91 1.174 lukem 20080721:
92 1.174 lukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
93 1.174 lukem isn't defined.
94 1.174 lukem
95 1.173 freza 20080531:
96 1.173 freza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
97 1.173 freza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
98 1.173 freza utility needs to be rebuilt and reinstalled as older binaries
99 1.173 freza won't work correctly. The following sequence of commands:
100 1.173 freza
101 1.173 freza $ (cd sys/sys/ && nbmake-$arch includes)
102 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch clean)
103 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch all)
104 1.173 freza
105 1.173 freza leaves new drvctl utility in sbin/drvctl build directory.
106 1.173 freza
107 1.172 lukem 20080503:
108 1.172 lukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
109 1.172 lukem
110 1.171 he 20080521:
111 1.171 he For a while, unprivileged UPDATE builds would fail to
112 1.171 he succeed at the checkflist stage, complaining that
113 1.171 he ${DESTDIR}/stand/<arch>/ did not exist. A fix for this
114 1.171 he problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
115 1.171 he If you already hit this problem, update the .mk file,
116 1.171 he remove ${DESTDIR}/stand/<arch>, and re-run the build.
117 1.171 he
118 1.174 lukem 20080303:
119 1.174 lukem Linker warnings are now fatal if $WARNS>0.
120 1.174 lukem
121 1.170 christos 20080126:
122 1.170 christos The posix_fadvise system call has been changed from an assembly
123 1.170 christos stub, to a c file that calls an assembly stub. You need to
124 1.170 christos 'rm -f posix_fadvise.* .depend' in the libc build directory to
125 1.170 christos avoid using the old assembly stub.
126 1.170 christos
127 1.168 joerg 20071209:
128 1.168 joerg The acpiec(4) driver has been split into two attachments. If you
129 1.168 joerg get ACPI errors before the attachment, please update your kernel
130 1.169 wiz configuration file appropriately or see GENERIC for more details.
131 1.168 joerg
132 1.166 xtraeme 20071115:
133 1.166 xtraeme The it(4) driver has been renamed to itesio(4) and the old port
134 1.166 xtraeme argument specified in the kernel configuration file is not valid
135 1.166 xtraeme anymore. The itesio(4) driver now uses the Super I/O address port
136 1.166 xtraeme rather than the EC address port. Please update your kernel
137 1.167 wiz configuration file appropriately or see GENERIC for more details.
138 1.166 xtraeme
139 1.165 jmmv 20071028:
140 1.165 jmmv The pccons(4) driver has been removed from the NetBSD/shark port.
141 1.165 jmmv You need to update any custom kernel configuration file you have
142 1.165 jmmv to remove any references to pccons (which includes removing the
143 1.165 jmmv now useless XSERVER option) and replace them with the correct
144 1.165 jmmv entries for the wscons driver. See the GENERIC configuration file
145 1.165 jmmv for more details.
146 1.165 jmmv
147 1.164 gdt 20070913:
148 1.164 gdt A latent bug in dhclient/dhcpd that caused it to be unable to
149 1.164 gdt enumerate interfaces was fixed. The bug began to cause
150 1.164 gdt problems after 20070911 when the kernel's SIOCGIFCONF
151 1.164 gdt implementation was repaired. From 20070529 to 20070911 racoon
152 1.164 gdt could not enumerate interfaces. (These are noted because
153 1.164 gdt normal kernel/userspace version matching hygiene is not
154 1.164 gdt sufficient to avoid this problem.) Ensure that both kernel
155 1.164 gdt and userland are from after 20070913.
156 1.164 gdt
157 1.163 joerg 20070703:
158 1.163 joerg nbinstall has been renamed as it calls the target specific and
159 1.163 joerg the logic to pass down STRIP from mk been removed. This forces
160 1.163 joerg a re-installation of tools.
161 1.163 joerg
162 1.161 dsl 20070422:
163 1.161 dsl The way OS emulations lookup filenames inside the emulation root
164 1.161 dsl has been changed. Rather than modify the pathname (and copy back
165 1.161 dsl to userspace) namei() and lookup() directly check the emulation
166 1.161 dsl root. One side effect is that absolute symlinks inside the emulated
167 1.167 wiz root file system will be relative to that file system - unless they
168 1.161 dsl start /../ this is useful when the emulated root is a real install
169 1.161 dsl that has such links.
170 1.161 dsl This might affect symlinks that have been added to reference outside
171 1.161 dsl the emulated root.
172 1.161 dsl
173 1.160 jmcneill 20070412:
174 1.160 jmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc
175 1.160 jmcneill instead. See the GENERIC32_IP3x kernel configuration for an
176 1.160 jmcneill example.
177 1.160 jmcneill
178 1.159 gdt 20070319:
179 1.159 gdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
180 1.159 gdt on many platforms due to incorrect flags settings. If you
181 1.159 gdt updated and built after about 20070315, do "nbmake-$arch
182 1.159 gdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
183 1.159 gdt rebuild of object files that might have been built
184 1.159 gdt incorrectly, and ensure that you have at least
185 1.159 gdt src/lib/libc/Makefile 1.130.
186 1.159 gdt
187 1.158 dbj 20070210:
188 1.158 dbj src/sys/sys/{sa.h,savar.h} were removed.
189 1.158 dbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
190 1.158 dbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm
191 1.158 dbj will allow dependencies on those files to get get rebuilt
192 1.158 dbj
193 1.157 apb 20070209:
194 1.157 apb The threading model was changed when the newlock2 branch
195 1.157 apb was merged to NetBSD-current. If you boot with a new
196 1.157 apb kernel (version 4.99.10), then you also need a new pthread
197 1.157 apb library (/usr/lib/libpthread.so.0.7). If you boot with
198 1.157 apb an old kernel, then you need the old pthread library
199 1.157 apb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and
200 1.157 apb the pthread library in sync, old threaded applications should
201 1.157 apb continue to work with an old or new kernel. Note that named(8)
202 1.157 apb is the only threaded application in the base system.
203 1.157 apb
204 1.154 he 20061214:
205 1.154 he Following the move of string_to_flags() and flags_to_string()
206 1.154 he from the bin/ls/ sources to libutil, users doing UPDATE builds
207 1.154 he will need to do a "make cleandir" in
208 1.154 he tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
209 1.154 he bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
210 1.156 he usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
211 1.156 he as the installation images in distrib/
212 1.154 he in order to excise stale references to the old stat_flags.h header
213 1.154 he file in the ls sources -- stat_flags.h has been removed.
214 1.154 he
215 1.152 christos 20061108:
216 1.152 christos The configure script used in the src/tools/gcc compiler has been
217 1.152 christos changed to indicate that our libc has ssp support built-in and
218 1.152 christos does not depend on -lssp and -lssp-nonshared. You'll need to
219 1.152 christos make clean in src/tools/gcc first to rebuild the compiler.
220 1.152 christos
221 1.151 rpaulo 20061009:
222 1.151 rpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
223 1.151 rpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
224 1.151 rpaulo
225 1.150 bjh21 20060814:
226 1.150 bjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
227 1.150 bjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC
228 1.150 bjh21 kernel configuration for an example. X servers from the last
229 1.150 bjh21 few years should cope.
230 1.150 bjh21
231 1.149 christos 20060703:
232 1.149 christos MPACPI is no more. We always configure PCI interrupts using ACPI
233 1.149 christos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
234 1.149 christos to ACPI_SCANPCI. Thanks to work from fvdl.
235 1.149 christos
236 1.148 dogcow 20060627:
237 1.148 dogcow socket(2) has changed, and its system call has been versioned.
238 1.148 dogcow For userlands with the old version of socket(2), make sure that
239 1.148 dogcow your kernel has 'options COMPAT_30' set, or else 'bad system call'
240 1.148 dogcow errors will result.
241 1.148 dogcow
242 1.1 abs Hints for a more successful build:
243 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
244 1.123 jmc Use build.sh, but do not use its "expert mode":
245 1.132 jmmv This will automatically build the tools in the
246 1.123 jmc correct order, and it will keep the tools and the
247 1.123 jmc new build products from interfering with the running
248 1.123 jmc system. This will allow you to ignore most of the
249 1.123 jmc other advice in this file.
250 1.2 mrg Build a new kernel first:
251 1.2 mrg This makes sure that any new system calls or features
252 1.2 mrg expected by the new userland will be present. This
253 1.2 mrg helps to avoid critical errors when upgrading.
254 1.1 abs Use object directories:
255 1.1 abs This helps to keep stale object
256 1.1 abs files from polluting the build if a Makefile "forgets"
257 1.1 abs about one. It also makes it easier to clean up after
258 1.1 abs a build. It's also necessary if you want to use the
259 1.1 abs same source tree for multiple machines.
260 1.123 jmc To use object directories with build.sh:
261 1.123 jmc a) invoke build.sh with the "-M" or "-O" options.
262 1.123 jmc To use object directories without using build.sh:
263 1.1 abs a) cd /usr/src ; make cleandir
264 1.2 mrg b) Add "OBJMACHINE=yes" to /etc/mk.conf
265 1.2 mrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf
266 1.1 abs d) cd /usr/src ; make build
267 1.2 mrg Note that running "make obj" in a directory will create
268 1.2 mrg in obj.$MACHINE directory.
269 1.1 abs Build to a DESTDIR:
270 1.123 jmc This helps to keep old installed files (especially libraries)
271 1.123 jmc from interfering with the new build.
272 1.123 jmc To build to a DESTDIR with build.sh, use the "-D" option.
273 1.123 jmc To build to a DESTDIR without using build.sh, set the DESTDIR
274 1.123 jmc environment variable before running make build. It should be
275 1.123 jmc set to the pathname of an initially empty directory.
276 1.123 jmc Problems: if you do not use build.sh, you might need to
277 1.123 jmc update critical utilities without using DESTDIR since
278 1.123 jmc nothing is executed from what is installed in DESTDIR.
279 1.123 jmc (See critical utils, below.)
280 1.1 abs Build often:
281 1.1 abs This keeps critical utilities current enough to not choke
282 1.1 abs on any other part of the source tree that depends on up to
283 1.123 jmc date functionality. If you use build.sh, you should not have
284 1.123 jmc this problem.
285 1.1 abs
286 1.1 abs What to do if things don't work:
287 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
288 1.1 abs When things don't work there is usually a few things that commonly
289 1.1 abs should be done.
290 1.1 abs 1) make includes
291 1.1 abs This should be done automatically by make build.
292 1.1 abs 2) cd share/mk && make install
293 1.1 abs Again, automatically done by make build.
294 1.1 abs
295 1.1 abs Failsafe rebuild of a small part of the tree:
296 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
297 1.1 abs To make sure you rebuild something correctly you want to do
298 1.1 abs something like the following:
299 1.1 abs 1) Make sure the includes and .mk files are up to date.
300 1.1 abs 2) Make sure any program used to build the particular
301 1.1 abs utility is up to date. (yacc, lex, etc...)
302 1.1 abs 3) cd ...path/to/util...
303 1.1 abs make cleandir
304 1.1 abs rm ...all obj directories...
305 1.1 abs make cleandir # yes, again
306 1.1 abs make obj
307 1.1 abs make depend && make
308 1.1 abs
309 1.1 abs Failsafe rebuild of the entire tree:
310 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
311 1.1 abs If you really want to make sure the source tree is clean and
312 1.2 mrg ready for a build try the following. Note that sourcing /etc/mk.conf
313 1.2 mrg (a make(1) Makefile) in this manner is not right, and will not work
314 1.2 mrg for anyone who uses any make(1) features in /etc/mk.conf.
315 1.1 abs
316 1.1 abs ---cut here---
317 1.1 abs #!/bin/sh
318 1.1 abs . /etc/mk.conf
319 1.1 abs
320 1.58 lukem if [ -z $NETBSDSRCDIR ] ; then
321 1.58 lukem NETBSDSRCDIR=/usr/src
322 1.1 abs fi
323 1.58 lukem if [ \! -d $NETBSDSRCDIR ] ; then
324 1.1 abs echo Unable to find sources
325 1.1 abs exit 1
326 1.1 abs fi
327 1.58 lukem find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
328 1.1 abs
329 1.1 abs if [ -z $BSDOBJDIR ] ; then
330 1.1 abs BSDOBJDIR=/usr/obj
331 1.1 abs fi
332 1.1 abs if [ -d $BSDOBJDIR ] ; then
333 1.1 abs rm -rf $BSDOBJDIR
334 1.1 abs fi
335 1.1 abs
336 1.58 lukem cd $NETBSDSRCDIR && make cleandir
337 1.1 abs
338 1.1 abs ---cut here---
339 1.1 abs
340 1.1 abs Critical utilities:
341 1.1 abs ^^^^^^^^^^^^^^^^^^^
342 1.3 itojun usr.bin/compile_et
343 1.1 abs usr.bin/make
344 1.1 abs usr.bin/yacc
345 1.1 abs usr.bin/lex
346 1.11 lukem usr.bin/xlint
347 1.142 drochner usr.bin/config
348 1.1 abs
349 1.34 simonb Other problems and possible solutions:
350 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
351 1.1 abs Symptom:Complaints involving a Makefile.
352 1.17 erh Fix: Rebuild usr.bin/make:
353 1.17 erh cd usr.bin/make && make && make install
354 1.111 simonb Or, a failsafe method if that doesn't work:
355 1.17 erh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
356 1.17 erh
357 1.1 abs Fix: Make sure .mk files are up to date.
358 1.1 abs cd share/mk && make install
359 1.2 mrg
360 1.2 mrg Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
361 1.142 drochner Fix: Rebuild usr.bin/config
362 1.1 abs
363 1.1 abs Symptom:
364 1.1 abs Fix: Rebuild usr.bin/yacc
365 1.1 abs
366 1.1 abs Symptom:
367 1.1 abs Fix: Rebuild usr.bin/lex
368 1.1 abs
369 1.1 abs Symptom:
370 1.1 abs Fix: rm /usr/lib/libbfd.a
371 1.4 itojun
372 1.4 itojun Symptom:Obsolete intermediate files are used during compilation
373 1.4 itojun Fix: Try the following sequence of commands in the directory in question.
374 1.4 itojun make cleandir; rm `make print-objdir`; make cleandir; make obj
375 1.4 itojun (If you built the tree without "make obj" in the past, obsolete files
376 1.4 itojun may remain. The command tries to clean everything up)
377 1.5 wiz
378 1.5 wiz Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
379 1.5 wiz Fix: Rebuild and install usr.bin/menuc
380 1.12 itojun
381 1.12 itojun Symptom:mklocale not found during build in share/locale/ctype
382 1.12 itojun Fix: Build and install usr.bin/mklocale
383 1.13 dogcow
384 1.86 kleink Symptom:undefined reference to `__assert13' or `__unsetenv13'
385 1.13 dogcow Fix: Rebuild and install lib/libc
386 1.13 dogcow
387 1.142 drochner Symptom:usr.bin/config fails to build.
388 1.19 cgd Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
389 1.13 dogcow
390 1.19 cgd Symptom:undefined reference to `getprogname' or `setprogname'
391 1.19 cgd Fix: Rebuild and install lib/libc
392 1.24 abs
393 1.24 abs Symptom:lint does not understand the '-X' option
394 1.24 abs Fix: May need to build & install libs with NOLINT=1 before rebuilding lint
395