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