UPDATING revision 1.213 1 1.213 jmmv $NetBSD: UPDATING,v 1.213 2010/06/04 15:11:31 jmmv 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.213 jmmv 20100604:
20 1.213 jmmv The update of ATF to 0.9 causes old tests written in shell to fail
21 1.213 jmmv unless they are rebuilt. If you are building with MKUPDATE=yes,
22 1.213 jmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/
23 1.213 jmmv trees by hand.
24 1.213 jmmv
25 1.211 tnozaki 20100522:
26 1.212 mrg Recent Xorg updates in xsrc/external/mit/ will cause various build
27 1.212 mrg problems. Delete your entire DESTDIR and OBJDIR if you have any
28 1.212 mrg build problems with xsrc.
29 1.212 mrg
30 1.212 mrg 20100522:
31 1.211 tnozaki private section of <ctype.h> was splitted, and now mklocale(1)
32 1.211 tnozaki include ctype_local.h, so you have to make cleandir tools/mklocale.
33 1.211 tnozaki
34 1.210 christos 20100520:
35 1.210 christos The location of the xkb compiled descriptions has changed. Please
36 1.210 christos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
37 1.210 christos
38 1.209 njoly 20100222:
39 1.209 njoly The shared objects file extension has been changed from .so to
40 1.209 njoly .pico, in order to avoid conflicts with shared libraries names
41 1.209 njoly libXX.so. All now stale regular .so files can be removed from
42 1.209 njoly your object directories.
43 1.209 njoly
44 1.208 roy 20100204:
45 1.208 roy The termcap database has been removed from the sources,
46 1.208 roy but has not been marked obsolete so it is not removed
47 1.208 roy from the system when upgrading.
48 1.208 roy As such, you will need to remove them from your object
49 1.208 roy and destination directories.
50 1.208 roy
51 1.203 dyoung 20091101:
52 1.205 dholland After updating, it may be necessary to make the 'cleandir'
53 1.205 dholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
54 1.205 dholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto
55 1.205 dholland src/tools/lex/ and src/usr.bin/lex/.
56 1.203 dyoung
57 1.202 mrg 20091001:
58 1.206 dholland On amd64 you must rebuild tools (to get the new binutils)
59 1.206 dholland before building a kernel, or the build fails on cpufunc.S.
60 1.206 dholland
61 1.206 dholland 20091001:
62 1.202 mrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
63 1.202 mrg symlink, failing the build. Delete the link, and the subdir
64 1.202 mrg it is in, and retry your build.
65 1.202 mrg
66 1.201 dsl 20090718:
67 1.201 dsl libc build changed so that strchr() provides the extra entry
68 1.201 dsl point for index(). Update build of libc.a (and libc_pic.a)
69 1.201 dsl may fail because the archive contains the unwanted index.o.
70 1.201 dsl (Similarly for strrchr() and rindex().)
71 1.201 dsl
72 1.198 mrg 20090709:
73 1.198 mrg Native Xorg was upgraded again. Builds will probably fail again
74 1.198 mrg without a clean objdir, at least for src/external/mit/xorg.
75 1.198 mrg
76 1.197 mrg 20090616:
77 1.197 mrg Native Xorg was upgraded. Builds will need a clean objdir for
78 1.197 mrg src/external/mit/xorg. Upgrading a system from sets will not
79 1.197 mrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
80 1.197 mrg subdirectory has been changed into a file, and this needs to
81 1.197 mrg be manually "rm -r"'ed before installing xbase.tgz.
82 1.197 mrg
83 1.195 perry 20090501:
84 1.195 perry Several new functions were added to string.h/libc, and this
85 1.195 perry can cause autoconf problems during the tool build for people
86 1.195 perry who fail to clean out their tools objects properly. If you
87 1.195 perry note messages about stpcpy, stpncpy or strnlen accompanying a
88 1.195 perry failure during the tool build, clean out all your tools
89 1.195 perry objects and start again.
90 1.195 perry
91 1.194 mrg 20090325:
92 1.194 mrg The i386 port was switched to i486 default toolchain. This requires
93 1.194 mrg cleaning your src/tools directory and $TOOLDIR and rebuilding them.
94 1.194 mrg
95 1.192 skrll 20090126:
96 1.207 mbalmer The __posix_fadvise50 system call changed assembly stub type. You
97 1.207 mbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory
98 1.207 mbalmer to avoid using the old assembly stub.
99 1.192 skrll
100 1.191 joerg 20090202:
101 1.191 joerg pkg_install now depends on the pkgdb cache for automatic conflict
102 1.191 joerg detection. It is recommented to rebuild the cache with
103 1.191 joerg ``pkg_admin rebuild''.
104 1.191 joerg
105 1.184 christos 20090110:
106 1.184 christos time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
107 1.184 christos 1. Make sure your kernel has COMPAT_50 in it. Build and install.
108 1.188 christos This is needed even in the MODULAR kernel because there is
109 1.188 christos conditionally compiled code in rtsock.c.
110 1.184 christos 2. make sure build.sh completes and the binaries in a chroot work
111 1.184 christos before installing.
112 1.184 christos 3. If you don't use build.sh and you build directly to root, and
113 1.187 dholland your build breaks in the middle, don't despair. Make sure headers
114 1.184 christos are installed properly, and start building libraries first libc
115 1.184 christos and libutil, install them and then continue building all the
116 1.184 christos libraries in src/lib and src/gnu/lib and install them. Once
117 1.184 christos the new libraries are installed, you can restart the build.
118 1.184 christos 4. If you compile packages and you notice link time warnings,
119 1.189 hubertf rebuild the required packages to update their shared libraries.
120 1.189 hubertf Any package you rebuild will require rebuilding all the packages
121 1.189 hubertf that depend on it.
122 1.186 christos 5. Next time you run pwd_mkdb with the new binary, the file
123 1.186 christos will be upgraded and it will not be backwards compatible.
124 1.190 apb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
125 1.190 apb lastlogx(5)) have been versioned, and there is a heuristic
126 1.190 apb for utmp. You are better off removing the old files after
127 1.190 apb upgrading. The automated clearing of /var/run during
128 1.190 apb boot, and the automated rotating of files in /var/log by
129 1.190 apb newsyslog(8), may mean that you do not have to remove the
130 1.190 apb files manually.
131 1.190 apb 7. The optional accounting file (/var/account/acct, see
132 1.190 apb accton(8)) has not been versioned, and will need to be
133 1.190 apb removed. The automatic rotation of the accounting file by
134 1.190 apb /etc/daily limits the bad consequences of failure to remove
135 1.190 apb the file.
136 1.196 dholland 8. Application software that writes time_t to binary files on
137 1.196 dholland disk will break or need attention. Most notably: if you are
138 1.196 dholland using PostgreSQL < 8.4, you need to dump your databases,
139 1.196 dholland rebuild PostgreSQL with the new time_t, then restore.
140 1.185 jmcneill
141 1.183 pgoyette 20081219:
142 1.183 pgoyette config(1) has been updated, and one of the files it creates -
143 1.183 pgoyette swapnetbsd.o - has changed format. You need to rebuild config
144 1.183 pgoyette (done automatically by build.sh) and then you need to rerun
145 1.183 pgoyette config on all kernel configuration files before rebuilding those
146 1.183 pgoyette kernels.
147 1.183 pgoyette
148 1.181 cube 20081205:
149 1.181 cube If you build with MKX11=no, you should remove /etc/rc.d/xdm and
150 1.181 cube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
151 1.181 cube set and will appear as extra files for MKX11=no update builds.
152 1.178 lukem
153 1.179 tsutsui 20081122:
154 1.182 tsutsui On i386, various kernel options(4) in GENERIC including
155 1.180 wiz file systems have been disabled and moved into kernel modules.
156 1.180 wiz Before trying a new GENERIC kernel, you have to prepare the
157 1.179 tsutsui following files as well as a new GENERIC kernel:
158 1.179 tsutsui
159 1.179 tsutsui - build and install kernel modules from src/sys/modules
160 1.179 tsutsui
161 1.179 tsutsui - install the latest bootloader, which will load a module
162 1.180 wiz for the file system from which the kernel is loaded automatically
163 1.179 tsutsui
164 1.180 wiz If you have to load your kernel from a file system which is not of
165 1.180 wiz the same type as the root file system, you have to load the necessary
166 1.180 wiz file system module manually on the boot prompt or in the boot.cfg file.
167 1.179 tsutsui
168 1.178 lukem 20080827:
169 1.178 lukem If you built and installed a libc from sources between
170 1.178 lukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3)
171 1.178 lukem which results in false errors reported by lint(1).
172 1.178 lukem Since this breaks the libc build itself, manual help is
173 1.180 wiz needed -- lint must be disabled temporarily, e.g.:
174 1.178 lukem $ (cd lib/libc && make MKLINT=no dependall install)
175 1.178 lukem
176 1.177 christos 20080813:
177 1.177 christos MKDEBUG build was broken because the .depend files did not know
178 1.177 christos about .go files. You need to remove all .depend files and rebuild.
179 1.177 christos
180 1.200 dholland 20080802:
181 1.200 dholland A regression in binary compatibility for pthread_mutex_t has
182 1.200 dholland been fixed. Unfortunately, the price is breaking compatibility
183 1.200 dholland for -current.
184 1.200 dholland
185 1.200 dholland Threaded programs (using libpthread) and C++ programs (using
186 1.200 dholland libstdc++) compiled after 20070907 and before 20080802 need to
187 1.200 dholland be recompiled.
188 1.200 dholland
189 1.200 dholland One way to find affected pkgsrc packages:
190 1.200 dholland
191 1.200 dholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
192 1.200 dholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
193 1.200 dholland
194 1.175 simonb 20080731:
195 1.175 simonb WAPBL (metadata journaling support) has been added, but at this
196 1.175 simonb time isn't backwards compatible with pre-WAPBL aware kernels
197 1.175 simonb and userland (fsck_ffs in particular). Please make sure you
198 1.175 simonb don't use a journaled filesystem with an older kernel/userland,
199 1.176 simonb especially an uncleanly mounted journaled filesystem. WAPBL
200 1.176 simonb also requires the super block to be in the UFS2 format. You
201 1.176 simonb can use fsck_ffs -c 4 to update the superblock format.
202 1.175 simonb
203 1.174 lukem 20080721:
204 1.174 lukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
205 1.174 lukem isn't defined.
206 1.174 lukem
207 1.173 freza 20080531:
208 1.173 freza The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
209 1.173 freza from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
210 1.173 freza utility needs to be rebuilt and reinstalled as older binaries
211 1.173 freza won't work correctly. The following sequence of commands:
212 1.173 freza
213 1.173 freza $ (cd sys/sys/ && nbmake-$arch includes)
214 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch clean)
215 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch all)
216 1.173 freza
217 1.173 freza leaves new drvctl utility in sbin/drvctl build directory.
218 1.173 freza
219 1.172 lukem 20080503:
220 1.172 lukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
221 1.172 lukem
222 1.171 he 20080521:
223 1.171 he For a while, unprivileged UPDATE builds would fail to
224 1.171 he succeed at the checkflist stage, complaining that
225 1.171 he ${DESTDIR}/stand/<arch>/ did not exist. A fix for this
226 1.171 he problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
227 1.171 he If you already hit this problem, update the .mk file,
228 1.171 he remove ${DESTDIR}/stand/<arch>, and re-run the build.
229 1.171 he
230 1.174 lukem 20080303:
231 1.174 lukem Linker warnings are now fatal if $WARNS>0.
232 1.174 lukem
233 1.170 christos 20080126:
234 1.170 christos The posix_fadvise system call has been changed from an assembly
235 1.170 christos stub, to a c file that calls an assembly stub. You need to
236 1.170 christos 'rm -f posix_fadvise.* .depend' in the libc build directory to
237 1.170 christos avoid using the old assembly stub.
238 1.170 christos
239 1.168 joerg 20071209:
240 1.168 joerg The acpiec(4) driver has been split into two attachments. If you
241 1.168 joerg get ACPI errors before the attachment, please update your kernel
242 1.169 wiz configuration file appropriately or see GENERIC for more details.
243 1.168 joerg
244 1.166 xtraeme 20071115:
245 1.166 xtraeme The it(4) driver has been renamed to itesio(4) and the old port
246 1.166 xtraeme argument specified in the kernel configuration file is not valid
247 1.166 xtraeme anymore. The itesio(4) driver now uses the Super I/O address port
248 1.166 xtraeme rather than the EC address port. Please update your kernel
249 1.167 wiz configuration file appropriately or see GENERIC for more details.
250 1.166 xtraeme
251 1.165 jmmv 20071028:
252 1.165 jmmv The pccons(4) driver has been removed from the NetBSD/shark port.
253 1.165 jmmv You need to update any custom kernel configuration file you have
254 1.165 jmmv to remove any references to pccons (which includes removing the
255 1.165 jmmv now useless XSERVER option) and replace them with the correct
256 1.165 jmmv entries for the wscons driver. See the GENERIC configuration file
257 1.165 jmmv for more details.
258 1.165 jmmv
259 1.164 gdt 20070913:
260 1.164 gdt A latent bug in dhclient/dhcpd that caused it to be unable to
261 1.164 gdt enumerate interfaces was fixed. The bug began to cause
262 1.164 gdt problems after 20070911 when the kernel's SIOCGIFCONF
263 1.164 gdt implementation was repaired. From 20070529 to 20070911 racoon
264 1.164 gdt could not enumerate interfaces. (These are noted because
265 1.164 gdt normal kernel/userspace version matching hygiene is not
266 1.164 gdt sufficient to avoid this problem.) Ensure that both kernel
267 1.164 gdt and userland are from after 20070913.
268 1.164 gdt
269 1.163 joerg 20070703:
270 1.199 dholland nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
271 1.199 dholland calls the target-specific strip program, and the logic to pass
272 1.199 dholland down STRIP from make has been removed. This requires a
273 1.199 dholland re-installation of tools.
274 1.163 joerg
275 1.161 dsl 20070422:
276 1.161 dsl The way OS emulations lookup filenames inside the emulation root
277 1.161 dsl has been changed. Rather than modify the pathname (and copy back
278 1.161 dsl to userspace) namei() and lookup() directly check the emulation
279 1.161 dsl root. One side effect is that absolute symlinks inside the emulated
280 1.167 wiz root file system will be relative to that file system - unless they
281 1.161 dsl start /../ this is useful when the emulated root is a real install
282 1.161 dsl that has such links.
283 1.161 dsl This might affect symlinks that have been added to reference outside
284 1.161 dsl the emulated root.
285 1.161 dsl
286 1.160 jmcneill 20070412:
287 1.160 jmcneill The pckbc driver on sgimips IP32 has been removed. Use macekbc
288 1.160 jmcneill instead. See the GENERIC32_IP3x kernel configuration for an
289 1.160 jmcneill example.
290 1.160 jmcneill
291 1.159 gdt 20070319:
292 1.159 gdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
293 1.159 gdt on many platforms due to incorrect flags settings. If you
294 1.159 gdt updated and built after about 20070315, do "nbmake-$arch
295 1.159 gdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
296 1.159 gdt rebuild of object files that might have been built
297 1.159 gdt incorrectly, and ensure that you have at least
298 1.159 gdt src/lib/libc/Makefile 1.130.
299 1.159 gdt
300 1.158 dbj 20070210:
301 1.158 dbj src/sys/sys/{sa.h,savar.h} were removed.
302 1.158 dbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
303 1.158 dbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm
304 1.158 dbj will allow dependencies on those files to get get rebuilt
305 1.158 dbj
306 1.157 apb 20070209:
307 1.157 apb The threading model was changed when the newlock2 branch
308 1.157 apb was merged to NetBSD-current. If you boot with a new
309 1.157 apb kernel (version 4.99.10), then you also need a new pthread
310 1.157 apb library (/usr/lib/libpthread.so.0.7). If you boot with
311 1.157 apb an old kernel, then you need the old pthread library
312 1.157 apb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and
313 1.157 apb the pthread library in sync, old threaded applications should
314 1.157 apb continue to work with an old or new kernel. Note that named(8)
315 1.157 apb is the only threaded application in the base system.
316 1.157 apb
317 1.154 he 20061214:
318 1.154 he Following the move of string_to_flags() and flags_to_string()
319 1.154 he from the bin/ls/ sources to libutil, users doing UPDATE builds
320 1.154 he will need to do a "make cleandir" in
321 1.154 he tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
322 1.154 he bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
323 1.156 he usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
324 1.156 he as the installation images in distrib/
325 1.154 he in order to excise stale references to the old stat_flags.h header
326 1.154 he file in the ls sources -- stat_flags.h has been removed.
327 1.154 he
328 1.152 christos 20061108:
329 1.152 christos The configure script used in the src/tools/gcc compiler has been
330 1.152 christos changed to indicate that our libc has ssp support built-in and
331 1.152 christos does not depend on -lssp and -lssp-nonshared. You'll need to
332 1.152 christos make clean in src/tools/gcc first to rebuild the compiler.
333 1.152 christos
334 1.151 rpaulo 20061009:
335 1.151 rpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
336 1.151 rpaulo available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
337 1.151 rpaulo
338 1.150 bjh21 20060814:
339 1.150 bjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
340 1.150 bjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC
341 1.150 bjh21 kernel configuration for an example. X servers from the last
342 1.150 bjh21 few years should cope.
343 1.150 bjh21
344 1.149 christos 20060703:
345 1.149 christos MPACPI is no more. We always configure PCI interrupts using ACPI
346 1.149 christos if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
347 1.149 christos to ACPI_SCANPCI. Thanks to work from fvdl.
348 1.149 christos
349 1.148 dogcow 20060627:
350 1.148 dogcow socket(2) has changed, and its system call has been versioned.
351 1.148 dogcow For userlands with the old version of socket(2), make sure that
352 1.148 dogcow your kernel has 'options COMPAT_30' set, or else 'bad system call'
353 1.148 dogcow errors will result.
354 1.148 dogcow
355 1.1 abs Hints for a more successful build:
356 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
357 1.123 jmc Use build.sh, but do not use its "expert mode":
358 1.132 jmmv This will automatically build the tools in the
359 1.123 jmc correct order, and it will keep the tools and the
360 1.123 jmc new build products from interfering with the running
361 1.123 jmc system. This will allow you to ignore most of the
362 1.123 jmc other advice in this file.
363 1.2 mrg Build a new kernel first:
364 1.2 mrg This makes sure that any new system calls or features
365 1.2 mrg expected by the new userland will be present. This
366 1.2 mrg helps to avoid critical errors when upgrading.
367 1.1 abs Use object directories:
368 1.1 abs This helps to keep stale object
369 1.1 abs files from polluting the build if a Makefile "forgets"
370 1.1 abs about one. It also makes it easier to clean up after
371 1.1 abs a build. It's also necessary if you want to use the
372 1.1 abs same source tree for multiple machines.
373 1.123 jmc To use object directories with build.sh:
374 1.123 jmc a) invoke build.sh with the "-M" or "-O" options.
375 1.123 jmc To use object directories without using build.sh:
376 1.1 abs a) cd /usr/src ; make cleandir
377 1.2 mrg b) Add "OBJMACHINE=yes" to /etc/mk.conf
378 1.2 mrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf
379 1.1 abs d) cd /usr/src ; make build
380 1.2 mrg Note that running "make obj" in a directory will create
381 1.2 mrg in obj.$MACHINE directory.
382 1.1 abs Build to a DESTDIR:
383 1.123 jmc This helps to keep old installed files (especially libraries)
384 1.123 jmc from interfering with the new build.
385 1.123 jmc To build to a DESTDIR with build.sh, use the "-D" option.
386 1.123 jmc To build to a DESTDIR without using build.sh, set the DESTDIR
387 1.123 jmc environment variable before running make build. It should be
388 1.123 jmc set to the pathname of an initially empty directory.
389 1.123 jmc Problems: if you do not use build.sh, you might need to
390 1.123 jmc update critical utilities without using DESTDIR since
391 1.123 jmc nothing is executed from what is installed in DESTDIR.
392 1.123 jmc (See critical utils, below.)
393 1.1 abs Build often:
394 1.1 abs This keeps critical utilities current enough to not choke
395 1.1 abs on any other part of the source tree that depends on up to
396 1.123 jmc date functionality. If you use build.sh, you should not have
397 1.123 jmc this problem.
398 1.1 abs
399 1.1 abs What to do if things don't work:
400 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
401 1.1 abs When things don't work there is usually a few things that commonly
402 1.1 abs should be done.
403 1.1 abs 1) make includes
404 1.1 abs This should be done automatically by make build.
405 1.1 abs 2) cd share/mk && make install
406 1.1 abs Again, automatically done by make build.
407 1.1 abs
408 1.1 abs Failsafe rebuild of a small part of the tree:
409 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
410 1.1 abs To make sure you rebuild something correctly you want to do
411 1.1 abs something like the following:
412 1.1 abs 1) Make sure the includes and .mk files are up to date.
413 1.1 abs 2) Make sure any program used to build the particular
414 1.1 abs utility is up to date. (yacc, lex, etc...)
415 1.1 abs 3) cd ...path/to/util...
416 1.1 abs make cleandir
417 1.1 abs rm ...all obj directories...
418 1.1 abs make cleandir # yes, again
419 1.1 abs make obj
420 1.1 abs make depend && make
421 1.1 abs
422 1.1 abs Failsafe rebuild of the entire tree:
423 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
424 1.1 abs If you really want to make sure the source tree is clean and
425 1.2 mrg ready for a build try the following. Note that sourcing /etc/mk.conf
426 1.2 mrg (a make(1) Makefile) in this manner is not right, and will not work
427 1.2 mrg for anyone who uses any make(1) features in /etc/mk.conf.
428 1.1 abs
429 1.1 abs ---cut here---
430 1.1 abs #!/bin/sh
431 1.1 abs . /etc/mk.conf
432 1.1 abs
433 1.58 lukem if [ -z $NETBSDSRCDIR ] ; then
434 1.58 lukem NETBSDSRCDIR=/usr/src
435 1.1 abs fi
436 1.58 lukem if [ \! -d $NETBSDSRCDIR ] ; then
437 1.1 abs echo Unable to find sources
438 1.1 abs exit 1
439 1.1 abs fi
440 1.58 lukem find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
441 1.1 abs
442 1.1 abs if [ -z $BSDOBJDIR ] ; then
443 1.1 abs BSDOBJDIR=/usr/obj
444 1.1 abs fi
445 1.1 abs if [ -d $BSDOBJDIR ] ; then
446 1.1 abs rm -rf $BSDOBJDIR
447 1.1 abs fi
448 1.1 abs
449 1.58 lukem cd $NETBSDSRCDIR && make cleandir
450 1.1 abs
451 1.1 abs ---cut here---
452 1.1 abs
453 1.1 abs Critical utilities:
454 1.1 abs ^^^^^^^^^^^^^^^^^^^
455 1.3 itojun usr.bin/compile_et
456 1.1 abs usr.bin/make
457 1.1 abs usr.bin/yacc
458 1.1 abs usr.bin/lex
459 1.11 lukem usr.bin/xlint
460 1.142 drochner usr.bin/config
461 1.1 abs
462 1.34 simonb Other problems and possible solutions:
463 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
464 1.1 abs Symptom:Complaints involving a Makefile.
465 1.17 erh Fix: Rebuild usr.bin/make:
466 1.17 erh cd usr.bin/make && make && make install
467 1.111 simonb Or, a failsafe method if that doesn't work:
468 1.17 erh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
469 1.17 erh
470 1.1 abs Fix: Make sure .mk files are up to date.
471 1.1 abs cd share/mk && make install
472 1.2 mrg
473 1.2 mrg Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
474 1.142 drochner Fix: Rebuild usr.bin/config
475 1.1 abs
476 1.1 abs Symptom:
477 1.1 abs Fix: Rebuild usr.bin/yacc
478 1.1 abs
479 1.1 abs Symptom:
480 1.1 abs Fix: Rebuild usr.bin/lex
481 1.1 abs
482 1.1 abs Symptom:
483 1.1 abs Fix: rm /usr/lib/libbfd.a
484 1.4 itojun
485 1.4 itojun Symptom:Obsolete intermediate files are used during compilation
486 1.4 itojun Fix: Try the following sequence of commands in the directory in question.
487 1.4 itojun make cleandir; rm `make print-objdir`; make cleandir; make obj
488 1.4 itojun (If you built the tree without "make obj" in the past, obsolete files
489 1.4 itojun may remain. The command tries to clean everything up)
490 1.5 wiz
491 1.207 mbalmer Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
492 1.207 mbalmer pointer type
493 1.5 wiz Fix: Rebuild and install usr.bin/menuc
494 1.12 itojun
495 1.12 itojun Symptom:mklocale not found during build in share/locale/ctype
496 1.12 itojun Fix: Build and install usr.bin/mklocale
497 1.13 dogcow
498 1.86 kleink Symptom:undefined reference to `__assert13' or `__unsetenv13'
499 1.13 dogcow Fix: Rebuild and install lib/libc
500 1.13 dogcow
501 1.142 drochner Symptom:usr.bin/config fails to build.
502 1.19 cgd Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
503 1.13 dogcow
504 1.19 cgd Symptom:undefined reference to `getprogname' or `setprogname'
505 1.19 cgd Fix: Rebuild and install lib/libc
506 1.24 abs
507 1.24 abs Symptom:lint does not understand the '-X' option
508 1.24 abs Fix: May need to build & install libs with NOLINT=1 before rebuilding lint
509