UPDATING revision 1.335 1 1.335 chs $NetBSD: UPDATING,v 1.335 2022/11/17 06:40:38 chs 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.257 apb Sections are marked with "^^^^^". After the section on "Recent changes"
15 1.257 apb are several sections containing more general information.
16 1.257 apb
17 1.123 jmc See also: BUILDING, build.sh, Makefile.
18 1.1 abs
19 1.1 abs Recent changes:
20 1.1 abs ^^^^^^^^^^^^^^^
21 1.230 tls
22 1.335 chs 20221116:
23 1.335 chs
24 1.335 chs The addition to NetBSD's version of UFS2 of support for extended
25 1.335 chs attributes broke backward compatibility with previous releases
26 1.335 chs of NetBSD, so UFS2 has been restored to being compatible with
27 1.335 chs previous NetBSD releases by disabling extended attributes.
28 1.335 chs (Note that ACLs are implemented as extended attributes, so
29 1.335 chs this changes disables ACLs as well.)
30 1.335 chs
31 1.335 chs Support for UFS2 with extended attributes is now available in a new
32 1.335 chs UFS variant called UFS2ea. If you have created extended attributes
33 1.335 chs in an original UFS2 file system then "fsck -p" will now fail due to
34 1.335 chs the unexpected presence of extended attributes and "fsck -y" will
35 1.335 chs remove all extended attributes. If you wish to preserve extended
36 1.335 chs attributes rather than delete them, there is a utility to convert
37 1.335 chs a UFS2 file system to UFS2ea and leave extended attributes in place,
38 1.335 chs but this should be used with caution since it will preserve any
39 1.335 chs extended attributes that have been corrupted by the backward
40 1.335 chs incompatibility too.
41 1.335 chs
42 1.335 chs If you wish to use a UFS2ea file system as your root file system,
43 1.335 chs then you will need to update your boot loader to a version that
44 1.335 chs supports UFS2ea.
45 1.335 chs
46 1.335 chs For more information, see:
47 1.335 chs https://wiki.netbsd.org/features/UFS2ea
48 1.335 chs
49 1.334 mrg 20221111:
50 1.334 mrg The new libdrm import worsened the conflict issues for the
51 1.334 mrg kdump/ktruss ioctl, and i915 now conflicts with base, and has
52 1.334 mrg been turned off. This will cause update build issues like:
53 1.334 mrg
54 1.334 mrg kdump-ioctl.c:12175:143: error: 'DRM_IOCTL_I915_DESTROY_HEAP'
55 1.334 mrg undeclared here (not in a function);
56 1.334 mrg did you mean 'DRM_IOCTL_MODE_DESTROY_DUMB'?
57 1.334 mrg
58 1.334 mrg You'll need to clean usr.bin/ktruss, usr.bin/kdump, and rescue.
59 1.334 mrg
60 1.331 riastrad 20220921:
61 1.331 riastrad Since the kernel version was bumped to 9.99.100, the bootloader
62 1.333 riastrad must be updated on x86 or EFI boot platforms in order to load
63 1.333 riastrad modules from boot.cfg(5) or interactively at the bootloader
64 1.333 riastrad prompt.
65 1.333 riastrad
66 1.333 riastrad The kernel can still load modules at runtime, with modload(8)
67 1.333 riastrad or modules.conf(5), with no bootloader update. This will not
68 1.333 riastrad affect release branches because it only applies to patch
69 1.333 riastrad numbers >=100.
70 1.333 riastrad
71 1.333 riastrad On x86 (i386 or amd64) with BIOS boot, this requires copying a
72 1.333 riastrad new /usr/mdec/boot to /boot. You can build this in the destdir
73 1.333 riastrad by running `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
74 1.333 riastrad sys/arch/i386/stand.
75 1.333 riastrad
76 1.333 riastrad On platforms with EFI boot (including x86 with EFI boot), this
77 1.333 riastrad requires copying a new /usr/mdec/boot*.efi to the EFI/BOOT/
78 1.333 riastrad directory on the EFI system partition. The boot*.efi file is:
79 1.333 riastrad
80 1.333 riastrad aarch64 bootaa64.efi
81 1.333 riastrad amd64 bootx64.efi
82 1.333 riastrad arm bootarm.efi (32-bit arm)
83 1.333 riastrad i386 bootx32.efi
84 1.333 riastrad
85 1.333 riastrad You can build this in the destdir by running
86 1.333 riastrad `$TOOLDIR/bin/nbmake-$ARCH dependall install' in
87 1.333 riastrad sys/stand/efiboot/boot*.
88 1.331 riastrad
89 1.330 lukem 20220821:
90 1.330 lukem Support for building extsrc/ has been deprecated.
91 1.330 lukem EXTSRCSRCDIR and MKEXTSRC have been deprecated.
92 1.330 lukem
93 1.329 mrg 20220714:
94 1.329 mrg Updates to xorg-server and associated drivers may cause builds to
95 1.329 mrg fail. Cleaning both DESTDIR and the xorg build tree may be needed.
96 1.329 mrg
97 1.328 martin 20220628:
98 1.328 martin Changes in the build of src/games/robots require a clean build
99 1.328 martin of that program.
100 1.328 martin
101 1.324 martin 20211116:
102 1.324 martin Changes in the xorg build require clean obj dirs for external/mit/xorg
103 1.325 martin (or a full clean/non-update build).
104 1.324 martin
105 1.323 nia 20211112:
106 1.323 nia Device tree sources were updated for evbarm. Some device nodes
107 1.323 nia (in particular, ld(4) devices on the ROCKPro64) will be renumbered.
108 1.323 nia
109 1.322 martin 20211014:
110 1.323 nia MKPIE default for aarch64 has changed, a clean build is required.
111 1.322 martin
112 1.321 christos 20210917:
113 1.321 christos Changed MNT_ACLS to default to POSIX1e ACLs instead of NFSv4
114 1.321 christos ACLs, to be compatible with FreeBSD. If you are using NFSv4 ACLs
115 1.321 christos and have "acls" in /etc/fstab you'll need to change it to "nfs4acls".
116 1.321 christos
117 1.319 mrg 20210711:
118 1.319 mrg Updated GMP sources may require cleaning in tools/gmp and/or in
119 1.319 mrg external/lgpl3/gmp/lib, particularly if GCC itself does not build.
120 1.319 mrg
121 1.318 mrg 20210417:
122 1.318 mrg GCC 10 was enabled for several platforms. If builds fail in either
123 1.318 mrg tools/gcc or external/gpl/gcc, first try cleaning those objects and
124 1.318 mrg removing the $DESTDIR/usr/include/g++ subdirectory.
125 1.318 mrg
126 1.317 rillig 20201230:
127 1.317 rillig lint1/ops.c is no longer autogenerated. If this makes the build
128 1.317 rillig fail, clean $OBJDIR/tools/*lint* and $OBJDIR/usr.bin/*xlint*.
129 1.317 rillig
130 1.316 mrg 20201016:
131 1.316 mrg MIPS kernel modules have been disabled until they work. This will
132 1.316 mrg turn up in extra files in the DESTDIR, which should be cleaned.
133 1.316 mrg
134 1.315 mrg 20200925:
135 1.315 mrg GNU MPC and MPFR have been updated. At least MPFR needs cleaning
136 1.315 mrg in both the tools and external dirs.
137 1.315 mrg
138 1.314 mrg 20200912:
139 1.314 mrg GCC 9 has arrived for Arm and x86 platforms, and will be coming
140 1.314 mrg for several more, as will binutils 2.34. Clean as required.
141 1.314 mrg
142 1.313 mrg 20200907:
143 1.313 mrg GCC 9 is coming, and binutils has been updated for MIPS. This
144 1.313 mrg probably requires cleaning the tools/binutils.
145 1.313 mrg
146 1.311 mrg 20200811:
147 1.312 mrg GCC updates may require cleaning the objdir. This may occur
148 1.312 mrg due to GCC 7.5 update, GCC 8.4 move to gcc.old, or the upcoming
149 1.312 mrg GCC 9 upgrade.
150 1.311 mrg
151 1.309 christos 20200614:
152 1.310 christos blacklist* has been renamed to blocklist*. postinstall(8)
153 1.332 gutterid should handle the migration.
154 1.309 christos
155 1.308 christos 20200601:
156 1.308 christos Due to a mistake in LIBISPRIVATE handling, .so libraries were
157 1.308 christos created in the build directories and need cleaning.
158 1.308 christos
159 1.307 mrg 20200311:
160 1.307 mrg GCC 8 ports will need cleaning in src/tools/gcc and
161 1.307 mrg src/external/gpl3/gcc due to GCC 8.4 update.
162 1.307 mrg
163 1.306 christos 20191118:
164 1.306 christos More architectures were switched to gcc8:
165 1.306 christos i386, ia64 powerpc64, sparc, sparc64, arm
166 1.306 christos The same comments as in 20191022 apply.
167 1.306 christos
168 1.305 martin 20191112:
169 1.305 martin The LLVM update requires a clean rebuild for all architectures using
170 1.305 martin LLVM during the tools build phase (i386, amd64, aarch64).
171 1.305 martin
172 1.304 martin 20191022:
173 1.304 martin Ports amd64 and aarch64 switched to GCC 8.3 by default.
174 1.304 martin In-place ("expert mode", build.sh -E) builds are not supported
175 1.304 martin when going from a GCC 7 userland to GCC 8. Do a regular
176 1.304 martin build to a different DESTDIR (or preferably: build.sh -U) at least
177 1.306 christos once and install sets, or download comp.{tar.xz,tgz} from the
178 1.304 martin daily builds and install that before doing the next in-place build.
179 1.304 martin
180 1.303 mrg 20191001:
181 1.303 mrg GCC 8.3 was imported. Builds of src/tools/gcc may fail if
182 1.303 mrg old builds with GCC 7 output now uses GCC 8. Clean this
183 1.303 mrg directory, and also clean src/external/gpl3/gcc.
184 1.303 mrg
185 1.302 riastrad 20190903:
186 1.306 christos Files with names that coincide with existing files' names on
187 1.302 riastrad case-insensitive file systems were inadvertently committed, for
188 1.302 riastrad radeon GPU firmware. We cannot mark these as obsolete for
189 1.302 riastrad postinstall to fix, so if you updated src since 2019-08-26, and
190 1.302 riastrad ran build.sh distribution or ran build.sh release, you must
191 1.302 riastrad manually delete the following files in your DESTDIR (which is
192 1.302 riastrad usually $OBJDIR/destir.$ARCH), or from / if you have installed
193 1.302 riastrad them:
194 1.302 riastrad
195 1.302 riastrad /libdata/firmware/radeon/bonaire_ce.bin
196 1.302 riastrad /libdata/firmware/radeon/bonaire_mc.bin
197 1.302 riastrad /libdata/firmware/radeon/bonaire_me.bin
198 1.302 riastrad /libdata/firmware/radeon/bonaire_mec.bin
199 1.302 riastrad /libdata/firmware/radeon/bonaire_pfp.bin
200 1.302 riastrad /libdata/firmware/radeon/bonaire_rlc.bin
201 1.302 riastrad /libdata/firmware/radeon/bonaire_sdma.bin
202 1.302 riastrad /libdata/firmware/radeon/bonaire_smc.bin
203 1.302 riastrad /libdata/firmware/radeon/bonaire_uvd.bin
204 1.302 riastrad /libdata/firmware/radeon/hainan_ce.bin
205 1.302 riastrad /libdata/firmware/radeon/hainan_mc.bin
206 1.302 riastrad /libdata/firmware/radeon/hainan_me.bin
207 1.302 riastrad /libdata/firmware/radeon/hainan_pfp.bin
208 1.302 riastrad /libdata/firmware/radeon/hainan_rlc.bin
209 1.302 riastrad /libdata/firmware/radeon/hainan_smc.bin
210 1.302 riastrad /libdata/firmware/radeon/hawaii_ce.bin
211 1.302 riastrad /libdata/firmware/radeon/hawaii_mc.bin
212 1.302 riastrad /libdata/firmware/radeon/hawaii_me.bin
213 1.302 riastrad /libdata/firmware/radeon/hawaii_mec.bin
214 1.302 riastrad /libdata/firmware/radeon/hawaii_pfp.bin
215 1.302 riastrad /libdata/firmware/radeon/hawaii_rlc.bin
216 1.302 riastrad /libdata/firmware/radeon/hawaii_sdma.bin
217 1.302 riastrad /libdata/firmware/radeon/hawaii_smc.bin
218 1.302 riastrad /libdata/firmware/radeon/kabini_ce.bin
219 1.302 riastrad /libdata/firmware/radeon/kabini_me.bin
220 1.302 riastrad /libdata/firmware/radeon/kabini_mec.bin
221 1.302 riastrad /libdata/firmware/radeon/kabini_pfp.bin
222 1.302 riastrad /libdata/firmware/radeon/kabini_rlc.bin
223 1.302 riastrad /libdata/firmware/radeon/kabini_sdma.bin
224 1.302 riastrad /libdata/firmware/radeon/kaveri_ce.bin
225 1.302 riastrad /libdata/firmware/radeon/kaveri_me.bin
226 1.302 riastrad /libdata/firmware/radeon/kaveri_mec.bin
227 1.302 riastrad /libdata/firmware/radeon/kaveri_mec2.bin
228 1.302 riastrad /libdata/firmware/radeon/kaveri_pfp.bin
229 1.302 riastrad /libdata/firmware/radeon/kaveri_rlc.bin
230 1.302 riastrad /libdata/firmware/radeon/kaveri_sdma.bin
231 1.302 riastrad /libdata/firmware/radeon/mullins_ce.bin
232 1.302 riastrad /libdata/firmware/radeon/mullins_me.bin
233 1.302 riastrad /libdata/firmware/radeon/mullins_mec.bin
234 1.302 riastrad /libdata/firmware/radeon/mullins_pfp.bin
235 1.302 riastrad /libdata/firmware/radeon/mullins_rlc.bin
236 1.302 riastrad /libdata/firmware/radeon/mullins_sdma.bin
237 1.302 riastrad /libdata/firmware/radeon/oland_ce.bin
238 1.302 riastrad /libdata/firmware/radeon/oland_mc.bin
239 1.302 riastrad /libdata/firmware/radeon/oland_me.bin
240 1.302 riastrad /libdata/firmware/radeon/oland_pfp.bin
241 1.302 riastrad /libdata/firmware/radeon/oland_rlc.bin
242 1.302 riastrad /libdata/firmware/radeon/oland_smc.bin
243 1.302 riastrad /libdata/firmware/radeon/pitcairn_ce.bin
244 1.302 riastrad /libdata/firmware/radeon/pitcairn_mc.bin
245 1.302 riastrad /libdata/firmware/radeon/pitcairn_me.bin
246 1.302 riastrad /libdata/firmware/radeon/pitcairn_pfp.bin
247 1.302 riastrad /libdata/firmware/radeon/pitcairn_rlc.bin
248 1.302 riastrad /libdata/firmware/radeon/pitcairn_smc.bin
249 1.302 riastrad /libdata/firmware/radeon/tahiti_ce.bin
250 1.302 riastrad /libdata/firmware/radeon/tahiti_mc.bin
251 1.302 riastrad /libdata/firmware/radeon/tahiti_me.bin
252 1.302 riastrad /libdata/firmware/radeon/tahiti_pfp.bin
253 1.302 riastrad /libdata/firmware/radeon/tahiti_rlc.bin
254 1.302 riastrad /libdata/firmware/radeon/tahiti_smc.bin
255 1.302 riastrad /libdata/firmware/radeon/verde_ce.bin
256 1.302 riastrad /libdata/firmware/radeon/verde_mc.bin
257 1.302 riastrad /libdata/firmware/radeon/verde_me.bin
258 1.302 riastrad /libdata/firmware/radeon/verde_pfp.bin
259 1.302 riastrad /libdata/firmware/radeon/verde_rlc.bin
260 1.302 riastrad /libdata/firmware/radeon/verde_smc.bin
261 1.302 riastrad
262 1.302 riastrad We will re-import these radeon firmware images another way
263 1.302 riastrad later.
264 1.302 riastrad
265 1.301 martin 20190727:
266 1.301 martin The uefi bootloader has gained tftp support and needs a clean
267 1.301 martin build. If you do update builds, manually clean its object
268 1.301 martin directory by something like:
269 1.301 martin cd sys/arch/i386/stand/efiboot && make clean
270 1.301 martin
271 1.300 martin 20190723:
272 1.300 martin The jemalloc allocator in libc is now build without extended
273 1.300 martin debugging (for performance reasons). In update builds make sure
274 1.326 andvar to rebuild it completely, by removing all affected object files,
275 1.300 martin including compat builds, something like:
276 1.300 martin cd /usr/obj && find . -type d -name jemalloc|xargs rm -rf
277 1.300 martin
278 1.299 mrg 20190207:
279 1.299 mrg GCC 7 switched for many ports. Update builds are likely to fail.
280 1.299 mrg
281 1.298 martin 20180924:
282 1.298 martin A newer OpenSSL version has been imported. If you are doing
283 1.298 martin update builds, make sure to remove all old obj dirs, like:
284 1.298 martin cd /usr/obj && find . -type d -name openssl | xargs rm -rf
285 1.298 martin
286 1.297 joerg 20180717:
287 1.297 joerg On aarch64 int64_t and related types have changed from long long
288 1.297 joerg to long. This requires recompiling all C++ binaries.
289 1.297 joerg
290 1.296 martin 20180713:
291 1.296 martin On amd64 and i386 static binaries are now build position
292 1.296 martin independend. This requires recompilation of all object
293 1.296 martin files used to create the crunched /rescue binary.
294 1.296 martin Clean the rescue directory in your obj directory before
295 1.296 martin doing an update build, otherwise linking will fail.
296 1.296 martin
297 1.293 jakllsch 20180414:
298 1.293 jakllsch Existing binutils was migrated to binutils.old. Manual
299 1.293 jakllsch removal of tools/binutils objects directory may be required
300 1.293 jakllsch to fix tools build failure.
301 1.293 jakllsch
302 1.292 mrg 20180311:
303 1.292 mrg bdftopcf was updated and may need cleaning in the
304 1.292 mrg src/external/mit/xorg/tools/bdftopcf subdirectory if there are
305 1.292 mrg link errors.
306 1.292 mrg
307 1.291 mrg 20180212:
308 1.291 mrg between OpenSSL and GCC updates, many things may fail to build.
309 1.291 mrg any failure that looks like GCC or openssl is best handled by
310 1.291 mrg a clean destdir and objdir. Full cleandir and destdir deletion
311 1.291 mrg is recommended if build failures occur.
312 1.291 mrg
313 1.288 martin 20171225:
314 1.288 martin removal of the vadvise syscall requires manual removal of all
315 1.288 martin associated files from the libc build object directory (including
316 1.289 christos the .depend files) - a command like:
317 1.288 martin cd $OBJ && find . -type d -name libc | xargs rm -rf
318 1.289 christos For architectures that support multiple "compat" binary targets,
319 1.289 christos you'll need to cleanup both the regular libc directory and the
320 1.290 martin compat ones (the above command will do that).
321 1.288 martin
322 1.287 kre 20171010:
323 1.287 kre a change to the build structure of external/bsd/acpica/bin/iasl
324 1.287 kre means that its objdir (or *.d and .depend at least) might need
325 1.287 kre to be manually removed - or a build done once without -u.
326 1.287 kre
327 1.286 mrg 20170822:
328 1.286 mrg a new version of GMP has been imported and probably
329 1.286 mrg will break parts of builds related to themselves or GCC, both
330 1.286 mrg in the tools and the native section. Remove all GCC, GMP, MPFR
331 1.286 mrg and MPC objdirs or build once without -u.
332 1.286 mrg
333 1.285 mrg 20170816:
334 1.285 mrg a new version of MPFR and MPC have been imported and probably
335 1.285 mrg will break parts of builds related to themselves or GCC, both
336 1.285 mrg in the tools and the native section. Remove all GCC, GMP, MPFR
337 1.285 mrg and MPC objdirs or build once without -u.
338 1.285 mrg
339 1.284 martin 20170402:
340 1.284 martin a new version of dhcpcd has been imported, which does not support
341 1.284 martin update builds from the previous version. Remove your
342 1.284 martin external/bsd/dhcpcd object dir or build once without -u.
343 1.284 martin
344 1.281 roy 20170211:
345 1.281 roy a new terminfo database has been imported.
346 1.281 roy The structure of it has changed slightly from prior versions and
347 1.281 roy an updated tic tool is required.
348 1.281 roy If you build.sh, don't use -u
349 1.281 roy
350 1.280 kre 20170207:
351 1.278 kre various arch dependent libc/exect.S files were removed
352 1.279 kre Either remove the obj directories (lib/libc and compat/amd64/i386/lib
353 1.279 kre if it exists) or do a clean build.
354 1.279 kre (This is a bug in the make system, it should be corrected without
355 1.279 kre human intervention, but isn't.)
356 1.278 kre
357 1.277 martin 20170104:
358 1.277 martin xinput build options have changed.
359 1.277 martin Remove the obj directory (external/mit/xorg/bin/xinput)
360 1.277 martin if you build.sh -u
361 1.277 martin
362 1.276 martin 20170103:
363 1.276 martin a new version of flex has been imported.
364 1.276 martin Remove the file from obj (external/bsd/flex)
365 1.276 martin if you build.sh -u
366 1.276 martin
367 1.275 spz 20161014:
368 1.275 spz a new version of OpenSSL has been imported.
369 1.275 spz Remove the files from obj (crypto/external/bsd/openssl)
370 1.275 spz if you build.sh -u
371 1.275 spz
372 1.274 martin 20161009:
373 1.274 martin a new version of dhcpcd has been imported with slightly changed
374 1.274 martin build infrastructure. When doing a build.sh -u this requires
375 1.274 martin pruning the external/bsd/dhcpcd objdir.
376 1.274 martin
377 1.273 mrg 20160914:
378 1.273 mrg i386, amd64, shark, ofppc and macppc have joined shark and x68k
379 1.273 mrg ports in using xorg-server 1.18. This requires a clean destdir
380 1.273 mrg and a clean objdir.
381 1.273 mrg
382 1.272 dholland 20160527:
383 1.272 dholland i386 needs a full cleandir or objdir deletion because PIE has
384 1.272 dholland been enabled. (see the amd64 entry two down for further info)
385 1.272 dholland
386 1.270 christos 20160418:
387 1.270 christos libedit needs manual removal of all autogenerated files since
388 1.271 christos some of them are not autogenerated anymore. Remember that there
389 1.271 christos might be two copies of libedit if your platform builds "compat".
390 1.270 christos
391 1.268 riastrad 20160410:
392 1.268 riastrad amd64 needs full "make cleandir" or deletion of objdir now that
393 1.268 riastrad PIE has been enabled for amd64. PIE, or position-independent
394 1.268 riastrad executables, means all code, including executables and not just
395 1.268 riastrad shared libraries, is position-independent and hence able to be
396 1.268 riastrad relocated by ASLR, address space layout randomization.
397 1.268 riastrad
398 1.268 riastrad The change was made in Makefile variables for compiler and
399 1.268 riastrad linker flags, for which make(1) does not record dependencies,
400 1.268 riastrad hence it is unable to detect that all .o files need rebuilding.
401 1.268 riastrad
402 1.268 riastrad Partial rebuilds with some modified source files will likely
403 1.268 riastrad fail when linking executables, since the linker refuses to mix
404 1.268 riastrad position-independent code with position-dependent code in
405 1.268 riastrad position-independent executables:
406 1.268 riastrad
407 1.268 riastrad .../x86_64--netbsd/bin/ld: foo.o: relocation R_X86_64_32 against `...' cannot be used when making a shared object; recompile with -fPIC
408 1.268 riastrad
409 1.267 mrg 20160401:
410 1.267 mrg Ports switching to GCC 5.3 will need a full "make cleandir".
411 1.269 dholland Some people have found that cleandir is not sufficient, so if
412 1.269 dholland in doubt delete the entire object directory tree for gcc.
413 1.267 mrg
414 1.266 aymeric 20160306:
415 1.265 aymeric NetBSD's regexp implementation is now part of libnbcompat.
416 1.265 aymeric Nblex, nbm4, nbpax, nbsed use it and they may crash on
417 1.265 aymeric non-NetBSD hosts if linked with stale object files produced
418 1.265 aymeric while they included a non-NetBSD regex.h.
419 1.265 aymeric In any case, you should "make cleandir" at least these tools
420 1.265 aymeric before updating your toolchain.
421 1.265 aymeric
422 1.264 martin 20160125:
423 1.264 martin Dtrace has been enabled by default on some architectures.
424 1.264 martin When doing an update build, make sure to clean the etc/mtree
425 1.264 martin object directory before starting the build - otherwise the
426 1.264 martin needed directories in destdir will not be created.
427 1.264 martin An easy way to do this is:
428 1.264 martin cd src/etc/mtree && $TOOLDIR/bin/nbmake-$arch cleandir
429 1.264 martin
430 1.263 dholland 20150818:
431 1.263 dholland New acpica requires "make cleandir" in src/external/bsd/acpica
432 1.263 dholland again.
433 1.263 dholland
434 1.262 christos 20150413:
435 1.262 christos New acpica requires "make cleandir" and reinstalling yacc
436 1.262 christos in /usr/src/external/bsd/byacc and /usr/src/tools/yacc and
437 1.262 christos also "make cleandir" in /usr/src/external/bsd/acpica.
438 1.262 christos
439 1.261 martin 20150404:
440 1.261 martin Lint changes require a full rebuild of the tool, so make
441 1.261 martin sure to build without -u option to build.sh, or manually
442 1.261 martin do a make cleandir in src/tools/lint1 and
443 1.261 martin src/usr.bin/xlint.
444 1.261 martin
445 1.260 skrll 20150310:
446 1.260 skrll Improvements to openssl for arm mean that update builds of
447 1.260 skrll the openssl libraries will fail. A make cleandir in
448 1.260 skrll external/bsd/openssl/lib is needed
449 1.260 skrll
450 1.258 martin 20141026:
451 1.259 msaitoh A mishap during the import of pppd may cause your corruption
452 1.258 martin in your cvs directory if you happened to do a cvs update
453 1.258 martin during a short period of time. To fix, just remove the
454 1.258 martin directory src/external/bsd/ppp/dist/pppd completely
455 1.258 martin and let cvs restore it on next update.
456 1.258 martin
457 1.256 apb 20140721:
458 1.256 apb The src/external/mit/lua/src directory was accidentally created
459 1.256 apb and then deleted in the CVS repository. If you get errors like
460 1.256 apb
461 1.256 apb cvs [update aborted]: cannot open directory
462 1.256 apb /cvsroot/src/external/mit/lua/src: No such file or directory
463 1.256 apb
464 1.256 apb then delete your local copy of that directory tree and try again.
465 1.256 apb
466 1.255 joerg 20140530:
467 1.255 joerg ARM eABI switched to DWARF based exception handling. This requires
468 1.255 joerg rebuilding all C++ code. It is strongly advised to do a clean build.
469 1.255 joerg
470 1.251 martin 20140131:
471 1.253 joerg The new compiler_rt/libc integration moved a few things. It is strongly
472 1.254 skrll advised to do a clean build. At least lib/libc, the compat version(s)
473 1.253 joerg of libc, libkern, rump and the kernels need to be cleaned.
474 1.251 martin
475 1.250 christos 20131227:
476 1.250 christos 1. The new ntpd runs in a restricted mode to prevent amplification
477 1.250 christos attacks. If you need ntpdc to work you need to explicitly enable
478 1.250 christos mode7 in your config file. Make sure you put the necessary restrict
479 1.250 christos statements to avoid being exposed.
480 1.250 christos 2. strncat has moved from lib/libc to common/lib/libc; you might need
481 1.250 christos to make clean in libc
482 1.250 christos
483 1.249 mrg 20131129:
484 1.249 mrg The GMP sources were updated, and builds will likely fail without
485 1.249 mrg cleaning their build trees for both tools and in-tree, like below.
486 1.249 mrg
487 1.248 mrg 20131128:
488 1.248 mrg The MPC and MPFR sources were updated, and builds may require their
489 1.248 mrg tools and in-tree directories cleaned for successful updates.
490 1.248 mrg
491 1.246 martin 20130605:
492 1.247 spz The kernel option FAST_IPSEC no longer exists, it's been renamed
493 1.247 spz to IPSEC (and the older IPSEC version removed).
494 1.247 spz
495 1.247 spz 20130605:
496 1.320 andvar Previous freetype installations erroneously installed private
497 1.246 martin header files. If you are building against a non-empty $DESTDIR,
498 1.246 martin please remove ${DESTDIR}//usr/X11R7/include/freetype2/freetype/.
499 1.246 martin
500 1.245 mrg 20130531:
501 1.245 mrg The xdm update may cause build failure due to xdm.man being
502 1.245 mrg in the obj tree. Make sure to ensure any like this:
503 1.245 mrg nbmake: nbmake: don't know how to make xdm.man. Stop
504 1.245 mrg is fixed by deleting the xdm.man in the obj tree.
505 1.245 mrg
506 1.244 mrg 20130530:
507 1.244 mrg Updates of many xsrc packages will leave old .pc files around.
508 1.244 mrg Best to clean out the xsrc objdir entirely before rebuilds.
509 1.244 mrg
510 1.242 christos 20130301:
511 1.242 christos The removal of netiso requires manual removal of /usr/include/netiso
512 1.243 christos prior to the build and make cleandir in /usr/src/usr.bin/{ktruss,kdump}
513 1.242 christos
514 1.238 dholland 20120726:
515 1.241 wiz The update of OpenSSL requires cleaning both the OpenSSL build
516 1.241 wiz directory and DESTDIR. *Even non-update builds require cleaning
517 1.240 dholland DESTDIR.* Builds done without taking these steps may fail, or in
518 1.241 wiz some cases may succeed and install broken OpenSSL libraries that
519 1.240 dholland cause third-party software to link incorrectly and/or crash.
520 1.238 dholland
521 1.237 wiz 20120507:
522 1.241 wiz The database schema for makemandb was changed. You will
523 1.237 wiz need to update the database using 'makemandb -f' or wait
524 1.237 wiz for the next weekly run to fix it.
525 1.237 wiz
526 1.236 bsh 20120319:
527 1.236 bsh sys/conf/Makefile.kern.inc has been modified to adjust the
528 1.236 bsh size of db_symtab automatically. You need to update dbsym in
529 1.236 bsh your $TOOLDIR to build kernels with options SYMTAB_SPACE. If
530 1.236 bsh you don't want this behavior, add AUTO_SYMTAB_SPACE=no to your
531 1.236 bsh mk.conf.
532 1.236 bsh
533 1.235 joerg 20120216:
534 1.241 wiz Default for MKCATPAGES changed to NO. Update builds will fail
535 1.241 wiz unless DESTDIR is cleaned manually. If you built between 20120207
536 1.239 dholland and 20120216, daily and weekly could have created an unreadable
537 1.241 wiz /var/db/man.db index for apropos. Running makemandb -f or
538 1.235 joerg the next run of weekly will fix it.
539 1.233 joerg
540 1.232 christos 20111227:
541 1.232 christos If you built between 20111225 and 20111227 you need to remove
542 1.232 christos /usr/lib/libpam.so.4* and /usr/lib/security/*.so.4, since the
543 1.232 christos bump has been reverted.
544 1.232 christos
545 1.231 tls 20111125:
546 1.231 tls The "rnd" pseudodevice has been added to sys/conf/std, which
547 1.231 tls means it should no longer be explicitly listed in kernel
548 1.231 tls configuration files. The line "pseudo-device rnd" should be
549 1.231 tls removed from any custom kernel config files users may have.
550 1.231 tls
551 1.230 tls 20111119:
552 1.230 tls A problem with the datastructures used by the rndctl(8)
553 1.230 tls utility (pointers in datastructures in an array, making 32->64
554 1.230 tls bit compatibility very painful) has been fixed in a
555 1.230 tls non-backwards-compatible way. If you replace your kernel,
556 1.230 tls replace your rndctl executable too.
557 1.241 wiz
558 1.229 jym 20111001:
559 1.229 jym the prop_*_send_syscall() functions from proplib(3) have been
560 1.229 jym changed and their new version is not backward compatible with the old
561 1.241 wiz one. So ensure that all consumers of these functions (currently:
562 1.229 jym quota2 code and its tests) are updated together with the new lib.
563 1.229 jym
564 1.228 mrg 20110817:
565 1.228 mrg sparc has been changed to use GCC 4.5.3, so any objdir or
566 1.228 mrg DESTDIR for them should be deleted before updating.
567 1.228 mrg
568 1.227 riastrad 20110806:
569 1.227 riastrad i386 and amd64 have been changed to use GCC 4.5.3, so any
570 1.227 riastrad objdir or DESTDIR for them should be deleted before updating.
571 1.227 riastrad
572 1.226 mrg 20110805:
573 1.226 mrg The update to GCC 4.5.3 requires a non-trivial portion of
574 1.226 mrg the tree to be cleaned. Best to delete both objdir and
575 1.226 mrg DESTDIR before running this update. So far, only the
576 1.226 mrg sparc64, mips and powerpc platforms have changed.
577 1.226 mrg
578 1.225 matt 20110803:
579 1.241 wiz The layout of external/public-domain/xz has changed. To do an
580 1.225 matt update build you will have to remove the contents of the OBJDIR
581 1.225 matt for external/public-domain/xz/bin by hand as the xz entry there
582 1.225 matt is now a directory.
583 1.225 matt
584 1.223 joerg 20110410:
585 1.241 wiz The configuration of src/tools/gcc has changed. To do an
586 1.224 dholland update build you have to clean both tools/binutils and
587 1.224 dholland tools/gcc by hand.
588 1.223 joerg
589 1.222 plunky 20110328:
590 1.222 plunky Building the Xorg binary was moved into a subdirectory to fix
591 1.241 wiz ordering issues with "make all". It may be necessary to remove
592 1.222 plunky the OBJDIR for external/mit/xorg/server/xorg-server/hw/xfree86
593 1.222 plunky if your update build fails, as the "Xorg" entry there is now a
594 1.222 plunky directory.
595 1.222 plunky
596 1.220 joerg 20110121:
597 1.221 lukem Assembler files no longer use -traditional-cpp. This can break
598 1.220 joerg the build of individual parts of the tree. This is handled
599 1.220 joerg correctly by build.sh. Manual builds have to update /usr/share/mk
600 1.220 joerg and re-run config(1) for any kernel configurations as needed.
601 1.218 joerg
602 1.217 jruoho 20101217:
603 1.217 jruoho The tcpdump(8) program was changed to drop privileges and chroot(2)
604 1.241 wiz by default. It may be necessary to manually update passwd(5) and
605 1.217 jruoho group(5) in order to make the program work with existing setups.
606 1.217 jruoho
607 1.216 christos 20101125:
608 1.327 andvar The latest changes to setenv(3) disallow setting environment
609 1.241 wiz variables with names that contain '='. Revision 1.18 of env.c
610 1.241 wiz assumed that this was allowed. Installing a new libc with an
611 1.216 christos old copy of /usr/bin/env causes env x=1 printenv | grep x= to
612 1.216 christos break which affects the autoconf tests for dependency finding,
613 1.216 christos so building gcc will end up printing:
614 1.216 christos checking dependency style of gcc... none
615 1.216 christos configure: error: no usable dependency style found
616 1.216 christos Fix it by rebuilding and re-installing env.
617 1.138 lukem
618 1.215 mrg 20101119:
619 1.215 mrg Recent Xorg updates in xsrc/external/mit/ may cause various build
620 1.215 mrg or run-time problems. Delete your entire DESTDIR and OBJDIR if you
621 1.215 mrg have any build problems with xsrc, or problems with mismatched
622 1.215 mrg versions between xorg-server and drivers.
623 1.215 mrg
624 1.213 jmmv 20100604:
625 1.213 jmmv The update of ATF to 0.9 causes old tests written in shell to fail
626 1.213 jmmv unless they are rebuilt. If you are building with MKUPDATE=yes,
627 1.213 jmmv you need to clean the src/external/bsd/atf/tests/ and the src/tests/
628 1.213 jmmv trees by hand.
629 1.213 jmmv
630 1.211 tnozaki 20100522:
631 1.212 mrg Recent Xorg updates in xsrc/external/mit/ will cause various build
632 1.212 mrg problems. Delete your entire DESTDIR and OBJDIR if you have any
633 1.212 mrg build problems with xsrc.
634 1.212 mrg
635 1.212 mrg 20100522:
636 1.320 andvar private section of <ctype.h> was split, and now mklocale(1)
637 1.214 dholland include ctype_local.h, so you have to make cleandir in tools/mklocale.
638 1.211 tnozaki
639 1.210 christos 20100520:
640 1.241 wiz The location of the xkb compiled descriptions has changed. Please
641 1.210 christos remove usr/X11R7/lib/X11/xkb/compiled from your $DESTDIR.
642 1.210 christos
643 1.209 njoly 20100222:
644 1.209 njoly The shared objects file extension has been changed from .so to
645 1.209 njoly .pico, in order to avoid conflicts with shared libraries names
646 1.209 njoly libXX.so. All now stale regular .so files can be removed from
647 1.209 njoly your object directories.
648 1.209 njoly
649 1.208 roy 20100204:
650 1.208 roy The termcap database has been removed from the sources,
651 1.208 roy but has not been marked obsolete so it is not removed
652 1.208 roy from the system when upgrading.
653 1.208 roy As such, you will need to remove them from your object
654 1.208 roy and destination directories.
655 1.208 roy
656 1.203 dyoung 20091101:
657 1.205 dholland After updating, it may be necessary to make the 'cleandir'
658 1.205 dholland target in src/tools/yacc/ and in src/usr.bin/yacc/ before a
659 1.205 dholland 'build.sh -u tools' or 'build.sh -u distribution'. Ditto
660 1.205 dholland src/tools/lex/ and src/usr.bin/lex/.
661 1.203 dyoung
662 1.202 mrg 20091001:
663 1.206 dholland On amd64 you must rebuild tools (to get the new binutils)
664 1.206 dholland before building a kernel, or the build fails on cpufunc.S.
665 1.206 dholland
666 1.206 dholland 20091001:
667 1.202 mrg An error will create a ./usr/X11R7/lib/X11/xkb/compiled/xkb
668 1.202 mrg symlink, failing the build. Delete the link, and the subdir
669 1.202 mrg it is in, and retry your build.
670 1.202 mrg
671 1.201 dsl 20090718:
672 1.201 dsl libc build changed so that strchr() provides the extra entry
673 1.241 wiz point for index(). Update build of libc.a (and libc_pic.a)
674 1.201 dsl may fail because the archive contains the unwanted index.o.
675 1.201 dsl (Similarly for strrchr() and rindex().)
676 1.201 dsl
677 1.198 mrg 20090709:
678 1.198 mrg Native Xorg was upgraded again. Builds will probably fail again
679 1.198 mrg without a clean objdir, at least for src/external/mit/xorg.
680 1.198 mrg
681 1.197 mrg 20090616:
682 1.197 mrg Native Xorg was upgraded. Builds will need a clean objdir for
683 1.197 mrg src/external/mit/xorg. Upgrading a system from sets will not
684 1.197 mrg work properly yet as the /usr/X11R7/lib/X11/xkb/symbols/pc
685 1.197 mrg subdirectory has been changed into a file, and this needs to
686 1.197 mrg be manually "rm -r"'ed before installing xbase.tgz.
687 1.197 mrg
688 1.195 perry 20090501:
689 1.195 perry Several new functions were added to string.h/libc, and this
690 1.195 perry can cause autoconf problems during the tool build for people
691 1.241 wiz who fail to clean out their tools objects properly. If you
692 1.195 perry note messages about stpcpy, stpncpy or strnlen accompanying a
693 1.195 perry failure during the tool build, clean out all your tools
694 1.195 perry objects and start again.
695 1.195 perry
696 1.194 mrg 20090325:
697 1.194 mrg The i386 port was switched to i486 default toolchain. This requires
698 1.194 mrg cleaning your src/tools directory and $TOOLDIR and rebuilding them.
699 1.194 mrg
700 1.192 skrll 20090126:
701 1.241 wiz The __posix_fadvise50 system call changed assembly stub type. You
702 1.207 mbalmer need to 'rm -f __posix_fadvise50.*' in the libc build directory
703 1.207 mbalmer to avoid using the old assembly stub.
704 1.192 skrll
705 1.191 joerg 20090202:
706 1.191 joerg pkg_install now depends on the pkgdb cache for automatic conflict
707 1.320 andvar detection. It is recommended to rebuild the cache with
708 1.191 joerg ``pkg_admin rebuild''.
709 1.191 joerg
710 1.184 christos 20090110:
711 1.241 wiz time_t and dev_t have been bumped to 64 bit quantities. To upgrade:
712 1.241 wiz 1. Make sure your kernel has COMPAT_50 in it. Build and install.
713 1.188 christos This is needed even in the MODULAR kernel because there is
714 1.188 christos conditionally compiled code in rtsock.c.
715 1.184 christos 2. make sure build.sh completes and the binaries in a chroot work
716 1.184 christos before installing.
717 1.184 christos 3. If you don't use build.sh and you build directly to root, and
718 1.241 wiz your build breaks in the middle, don't despair. Make sure headers
719 1.184 christos are installed properly, and start building libraries first libc
720 1.184 christos and libutil, install them and then continue building all the
721 1.241 wiz libraries in src/lib and src/gnu/lib and install them. Once
722 1.184 christos the new libraries are installed, you can restart the build.
723 1.184 christos 4. If you compile packages and you notice link time warnings,
724 1.189 hubertf rebuild the required packages to update their shared libraries.
725 1.189 hubertf Any package you rebuild will require rebuilding all the packages
726 1.189 hubertf that depend on it.
727 1.186 christos 5. Next time you run pwd_mkdb with the new binary, the file
728 1.186 christos will be upgraded and it will not be backwards compatible.
729 1.190 apb 6. The utmpx/wtmpx files (/var/run/utmpx and /var/log/wtmpx, see
730 1.190 apb lastlogx(5)) have been versioned, and there is a heuristic
731 1.241 wiz for utmp. You are better off removing the old files after
732 1.190 apb upgrading. The automated clearing of /var/run during
733 1.190 apb boot, and the automated rotating of files in /var/log by
734 1.190 apb newsyslog(8), may mean that you do not have to remove the
735 1.190 apb files manually.
736 1.190 apb 7. The optional accounting file (/var/account/acct, see
737 1.190 apb accton(8)) has not been versioned, and will need to be
738 1.190 apb removed. The automatic rotation of the accounting file by
739 1.190 apb /etc/daily limits the bad consequences of failure to remove
740 1.190 apb the file.
741 1.196 dholland 8. Application software that writes time_t to binary files on
742 1.241 wiz disk will break or need attention. Most notably: if you are
743 1.196 dholland using PostgreSQL < 8.4, you need to dump your databases,
744 1.196 dholland rebuild PostgreSQL with the new time_t, then restore.
745 1.185 jmcneill
746 1.183 pgoyette 20081219:
747 1.183 pgoyette config(1) has been updated, and one of the files it creates -
748 1.183 pgoyette swapnetbsd.o - has changed format. You need to rebuild config
749 1.183 pgoyette (done automatically by build.sh) and then you need to rerun
750 1.183 pgoyette config on all kernel configuration files before rebuilding those
751 1.183 pgoyette kernels.
752 1.183 pgoyette
753 1.181 cube 20081205:
754 1.181 cube If you build with MKX11=no, you should remove /etc/rc.d/xdm and
755 1.181 cube /etc/rc.d/xfs from DESTDIR because those files were moved to the xetc
756 1.181 cube set and will appear as extra files for MKX11=no update builds.
757 1.178 lukem
758 1.179 tsutsui 20081122:
759 1.182 tsutsui On i386, various kernel options(4) in GENERIC including
760 1.180 wiz file systems have been disabled and moved into kernel modules.
761 1.180 wiz Before trying a new GENERIC kernel, you have to prepare the
762 1.179 tsutsui following files as well as a new GENERIC kernel:
763 1.179 tsutsui
764 1.179 tsutsui - build and install kernel modules from src/sys/modules
765 1.179 tsutsui
766 1.179 tsutsui - install the latest bootloader, which will load a module
767 1.180 wiz for the file system from which the kernel is loaded automatically
768 1.179 tsutsui
769 1.180 wiz If you have to load your kernel from a file system which is not of
770 1.180 wiz the same type as the root file system, you have to load the necessary
771 1.180 wiz file system module manually on the boot prompt or in the boot.cfg file.
772 1.179 tsutsui
773 1.178 lukem 20080827:
774 1.178 lukem If you built and installed a libc from sources between
775 1.178 lukem 2008/08/20 and 2008/08/26 you got a broken strtouq(3)
776 1.178 lukem which results in false errors reported by lint(1).
777 1.178 lukem Since this breaks the libc build itself, manual help is
778 1.180 wiz needed -- lint must be disabled temporarily, e.g.:
779 1.178 lukem $ (cd lib/libc && make MKLINT=no dependall install)
780 1.178 lukem
781 1.177 christos 20080813:
782 1.177 christos MKDEBUG build was broken because the .depend files did not know
783 1.241 wiz about .go files. You need to remove all .depend files and rebuild.
784 1.177 christos
785 1.200 dholland 20080802:
786 1.200 dholland A regression in binary compatibility for pthread_mutex_t has
787 1.241 wiz been fixed. Unfortunately, the price is breaking compatibility
788 1.200 dholland for -current.
789 1.200 dholland
790 1.200 dholland Threaded programs (using libpthread) and C++ programs (using
791 1.200 dholland libstdc++) compiled after 20070907 and before 20080802 need to
792 1.200 dholland be recompiled.
793 1.200 dholland
794 1.200 dholland One way to find affected pkgsrc packages:
795 1.200 dholland
796 1.200 dholland $ grep REQUIRES=/usr/lib/libpthread /var/db/pkg/*/+BUILD_INFO
797 1.200 dholland $ grep REQUIRES=/usr/lib/libstdc++ /var/db/pkg/*/+BUILD_INFO
798 1.200 dholland
799 1.175 simonb 20080731:
800 1.175 simonb WAPBL (metadata journaling support) has been added, but at this
801 1.175 simonb time isn't backwards compatible with pre-WAPBL aware kernels
802 1.175 simonb and userland (fsck_ffs in particular). Please make sure you
803 1.175 simonb don't use a journaled filesystem with an older kernel/userland,
804 1.176 simonb especially an uncleanly mounted journaled filesystem. WAPBL
805 1.176 simonb also requires the super block to be in the UFS2 format. You
806 1.176 simonb can use fsck_ffs -c 4 to update the superblock format.
807 1.175 simonb
808 1.174 lukem 20080721:
809 1.174 lukem Assembler warnings are now fatal if $WARNS>0 and $NOGCCERROR
810 1.174 lukem isn't defined.
811 1.174 lukem
812 1.173 freza 20080531:
813 1.241 wiz The ioctl number of DRVSUSPENDDEV command on /dev/drvctl changed
814 1.241 wiz from 125 (conflicted with DRVCTLCOMMAND) to 129. The drvctl(8)
815 1.173 freza utility needs to be rebuilt and reinstalled as older binaries
816 1.241 wiz won't work correctly. The following sequence of commands:
817 1.173 freza
818 1.173 freza $ (cd sys/sys/ && nbmake-$arch includes)
819 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch clean)
820 1.173 freza $ (cd sbin/drvctl/ && nbmake-$arch all)
821 1.173 freza
822 1.173 freza leaves new drvctl utility in sbin/drvctl build directory.
823 1.173 freza
824 1.172 lukem 20080503:
825 1.172 lukem The <bsd.lib.mk> variable MKPRIVATELIB was renamed to LIBISPRIVATE.
826 1.172 lukem
827 1.171 he 20080521:
828 1.171 he For a while, unprivileged UPDATE builds would fail to
829 1.171 he succeed at the checkflist stage, complaining that
830 1.171 he ${DESTDIR}/stand/<arch>/ did not exist. A fix for this
831 1.171 he problem was committed to share/mk/bsd.kmodule.mk, revision 1.9.
832 1.171 he If you already hit this problem, update the .mk file,
833 1.171 he remove ${DESTDIR}/stand/<arch>, and re-run the build.
834 1.171 he
835 1.174 lukem 20080303:
836 1.174 lukem Linker warnings are now fatal if $WARNS>0.
837 1.174 lukem
838 1.170 christos 20080126:
839 1.170 christos The posix_fadvise system call has been changed from an assembly
840 1.241 wiz stub, to a c file that calls an assembly stub. You need to
841 1.170 christos 'rm -f posix_fadvise.* .depend' in the libc build directory to
842 1.170 christos avoid using the old assembly stub.
843 1.170 christos
844 1.168 joerg 20071209:
845 1.241 wiz The acpiec(4) driver has been split into two attachments. If you
846 1.168 joerg get ACPI errors before the attachment, please update your kernel
847 1.169 wiz configuration file appropriately or see GENERIC for more details.
848 1.168 joerg
849 1.166 xtraeme 20071115:
850 1.166 xtraeme The it(4) driver has been renamed to itesio(4) and the old port
851 1.166 xtraeme argument specified in the kernel configuration file is not valid
852 1.241 wiz anymore. The itesio(4) driver now uses the Super I/O address port
853 1.241 wiz rather than the EC address port. Please update your kernel
854 1.167 wiz configuration file appropriately or see GENERIC for more details.
855 1.166 xtraeme
856 1.165 jmmv 20071028:
857 1.165 jmmv The pccons(4) driver has been removed from the NetBSD/shark port.
858 1.165 jmmv You need to update any custom kernel configuration file you have
859 1.165 jmmv to remove any references to pccons (which includes removing the
860 1.165 jmmv now useless XSERVER option) and replace them with the correct
861 1.165 jmmv entries for the wscons driver. See the GENERIC configuration file
862 1.165 jmmv for more details.
863 1.165 jmmv
864 1.164 gdt 20070913:
865 1.164 gdt A latent bug in dhclient/dhcpd that caused it to be unable to
866 1.164 gdt enumerate interfaces was fixed. The bug began to cause
867 1.164 gdt problems after 20070911 when the kernel's SIOCGIFCONF
868 1.164 gdt implementation was repaired. From 20070529 to 20070911 racoon
869 1.164 gdt could not enumerate interfaces. (These are noted because
870 1.164 gdt normal kernel/userspace version matching hygiene is not
871 1.164 gdt sufficient to avoid this problem.) Ensure that both kernel
872 1.164 gdt and userland are from after 20070913.
873 1.164 gdt
874 1.163 joerg 20070703:
875 1.241 wiz nbinstall has been renamed ${MACHINE_GNU_ARCH}-install. It
876 1.199 dholland calls the target-specific strip program, and the logic to pass
877 1.199 dholland down STRIP from make has been removed. This requires a
878 1.199 dholland re-installation of tools.
879 1.163 joerg
880 1.161 dsl 20070422:
881 1.161 dsl The way OS emulations lookup filenames inside the emulation root
882 1.161 dsl has been changed. Rather than modify the pathname (and copy back
883 1.161 dsl to userspace) namei() and lookup() directly check the emulation
884 1.241 wiz root. One side effect is that absolute symlinks inside the emulated
885 1.167 wiz root file system will be relative to that file system - unless they
886 1.161 dsl start /../ this is useful when the emulated root is a real install
887 1.161 dsl that has such links.
888 1.161 dsl This might affect symlinks that have been added to reference outside
889 1.161 dsl the emulated root.
890 1.161 dsl
891 1.160 jmcneill 20070412:
892 1.241 wiz The pckbc driver on sgimips IP32 has been removed. Use macekbc
893 1.241 wiz instead. See the GENERIC32_IP3x kernel configuration for an
894 1.160 jmcneill example.
895 1.160 jmcneill
896 1.159 gdt 20070319:
897 1.159 gdt src/lib/libc/Makefile revision 1.129 broke libc and ld.elf_so
898 1.159 gdt on many platforms due to incorrect flags settings. If you
899 1.159 gdt updated and built after about 20070315, do "nbmake-$arch
900 1.159 gdt cleandir" in src/lib/libc and src/libexec/ld.elf_so to force a
901 1.159 gdt rebuild of object files that might have been built
902 1.159 gdt incorrectly, and ensure that you have at least
903 1.159 gdt src/lib/libc/Makefile 1.130.
904 1.159 gdt
905 1.241 wiz 20070210:
906 1.158 dbj src/sys/sys/{sa.h,savar.h} were removed.
907 1.158 dbj find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
908 1.158 dbj | xargs egrep -l '/sa.h|/savar.h' | xargs rm
909 1.158 dbj will allow dependencies on those files to get get rebuilt
910 1.158 dbj
911 1.157 apb 20070209:
912 1.157 apb The threading model was changed when the newlock2 branch
913 1.157 apb was merged to NetBSD-current. If you boot with a new
914 1.157 apb kernel (version 4.99.10), then you also need a new pthread
915 1.157 apb library (/usr/lib/libpthread.so.0.7). If you boot with
916 1.157 apb an old kernel, then you need the old pthread library
917 1.157 apb (/usr/lib/libpthread.so.0.6). Provided you keep the kernel and
918 1.157 apb the pthread library in sync, old threaded applications should
919 1.157 apb continue to work with an old or new kernel. Note that named(8)
920 1.157 apb is the only threaded application in the base system.
921 1.157 apb
922 1.154 he 20061214:
923 1.154 he Following the move of string_to_flags() and flags_to_string()
924 1.154 he from the bin/ls/ sources to libutil, users doing UPDATE builds
925 1.154 he will need to do a "make cleandir" in
926 1.154 he tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
927 1.154 he bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
928 1.156 he usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
929 1.156 he as the installation images in distrib/
930 1.154 he in order to excise stale references to the old stat_flags.h header
931 1.154 he file in the ls sources -- stat_flags.h has been removed.
932 1.154 he
933 1.152 christos 20061108:
934 1.152 christos The configure script used in the src/tools/gcc compiler has been
935 1.152 christos changed to indicate that our libc has ssp support built-in and
936 1.241 wiz does not depend on -lssp and -lssp-nonshared. You'll need to
937 1.152 christos make clean in src/tools/gcc first to rebuild the compiler.
938 1.152 christos
939 1.151 rpaulo 20061009:
940 1.151 rpaulo The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
941 1.241 wiz available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
942 1.151 rpaulo
943 1.150 bjh21 20060814:
944 1.150 bjh21 The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
945 1.150 bjh21 withdrawn. Use vidcvideo and pckbd instead. See the GENERIC
946 1.150 bjh21 kernel configuration for an example. X servers from the last
947 1.150 bjh21 few years should cope.
948 1.150 bjh21
949 1.149 christos 20060703:
950 1.241 wiz MPACPI is no more. We always configure PCI interrupts using ACPI
951 1.241 wiz if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
952 1.241 wiz to ACPI_SCANPCI. Thanks to work from fvdl.
953 1.149 christos
954 1.148 dogcow 20060627:
955 1.148 dogcow socket(2) has changed, and its system call has been versioned.
956 1.148 dogcow For userlands with the old version of socket(2), make sure that
957 1.148 dogcow your kernel has 'options COMPAT_30' set, or else 'bad system call'
958 1.148 dogcow errors will result.
959 1.148 dogcow
960 1.1 abs Hints for a more successful build:
961 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
962 1.123 jmc Use build.sh, but do not use its "expert mode":
963 1.132 jmmv This will automatically build the tools in the
964 1.123 jmc correct order, and it will keep the tools and the
965 1.123 jmc new build products from interfering with the running
966 1.123 jmc system. This will allow you to ignore most of the
967 1.123 jmc other advice in this file.
968 1.2 mrg Build a new kernel first:
969 1.2 mrg This makes sure that any new system calls or features
970 1.2 mrg expected by the new userland will be present. This
971 1.2 mrg helps to avoid critical errors when upgrading.
972 1.1 abs Use object directories:
973 1.1 abs This helps to keep stale object
974 1.1 abs files from polluting the build if a Makefile "forgets"
975 1.1 abs about one. It also makes it easier to clean up after
976 1.1 abs a build. It's also necessary if you want to use the
977 1.1 abs same source tree for multiple machines.
978 1.123 jmc To use object directories with build.sh:
979 1.123 jmc a) invoke build.sh with the "-M" or "-O" options.
980 1.123 jmc To use object directories without using build.sh:
981 1.1 abs a) cd /usr/src ; make cleandir
982 1.2 mrg b) Add "OBJMACHINE=yes" to /etc/mk.conf
983 1.2 mrg c) Add "MKOBJDIRS=yes" to /etc/mk.conf
984 1.1 abs d) cd /usr/src ; make build
985 1.2 mrg Note that running "make obj" in a directory will create
986 1.2 mrg in obj.$MACHINE directory.
987 1.1 abs Build to a DESTDIR:
988 1.123 jmc This helps to keep old installed files (especially libraries)
989 1.123 jmc from interfering with the new build.
990 1.123 jmc To build to a DESTDIR with build.sh, use the "-D" option.
991 1.123 jmc To build to a DESTDIR without using build.sh, set the DESTDIR
992 1.123 jmc environment variable before running make build. It should be
993 1.123 jmc set to the pathname of an initially empty directory.
994 1.123 jmc Problems: if you do not use build.sh, you might need to
995 1.123 jmc update critical utilities without using DESTDIR since
996 1.123 jmc nothing is executed from what is installed in DESTDIR.
997 1.123 jmc (See critical utils, below.)
998 1.1 abs Build often:
999 1.1 abs This keeps critical utilities current enough to not choke
1000 1.1 abs on any other part of the source tree that depends on up to
1001 1.123 jmc date functionality. If you use build.sh, you should not have
1002 1.123 jmc this problem.
1003 1.241 wiz
1004 1.1 abs What to do if things don't work:
1005 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1006 1.230 tls When things don't work there are usually a few things that commonly
1007 1.1 abs should be done.
1008 1.1 abs 1) make includes
1009 1.1 abs This should be done automatically by make build.
1010 1.1 abs 2) cd share/mk && make install
1011 1.1 abs Again, automatically done by make build.
1012 1.1 abs
1013 1.1 abs Failsafe rebuild of a small part of the tree:
1014 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1015 1.1 abs To make sure you rebuild something correctly you want to do
1016 1.1 abs something like the following:
1017 1.1 abs 1) Make sure the includes and .mk files are up to date.
1018 1.1 abs 2) Make sure any program used to build the particular
1019 1.1 abs utility is up to date. (yacc, lex, etc...)
1020 1.1 abs 3) cd ...path/to/util...
1021 1.1 abs make cleandir
1022 1.1 abs rm ...all obj directories...
1023 1.1 abs make cleandir # yes, again
1024 1.1 abs make obj
1025 1.1 abs make depend && make
1026 1.1 abs
1027 1.1 abs Failsafe rebuild of the entire tree:
1028 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1029 1.1 abs If you really want to make sure the source tree is clean and
1030 1.2 mrg ready for a build try the following. Note that sourcing /etc/mk.conf
1031 1.2 mrg (a make(1) Makefile) in this manner is not right, and will not work
1032 1.2 mrg for anyone who uses any make(1) features in /etc/mk.conf.
1033 1.1 abs
1034 1.1 abs ---cut here---
1035 1.1 abs #!/bin/sh
1036 1.1 abs . /etc/mk.conf
1037 1.1 abs
1038 1.58 lukem if [ -z $NETBSDSRCDIR ] ; then
1039 1.58 lukem NETBSDSRCDIR=/usr/src
1040 1.1 abs fi
1041 1.58 lukem if [ \! -d $NETBSDSRCDIR ] ; then
1042 1.1 abs echo Unable to find sources
1043 1.1 abs exit 1
1044 1.1 abs fi
1045 1.58 lukem find $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
1046 1.1 abs
1047 1.1 abs if [ -z $BSDOBJDIR ] ; then
1048 1.1 abs BSDOBJDIR=/usr/obj
1049 1.1 abs fi
1050 1.1 abs if [ -d $BSDOBJDIR ] ; then
1051 1.1 abs rm -rf $BSDOBJDIR
1052 1.1 abs fi
1053 1.1 abs
1054 1.58 lukem cd $NETBSDSRCDIR && make cleandir
1055 1.1 abs
1056 1.1 abs ---cut here---
1057 1.1 abs
1058 1.1 abs Critical utilities:
1059 1.1 abs ^^^^^^^^^^^^^^^^^^^
1060 1.3 itojun usr.bin/compile_et
1061 1.1 abs usr.bin/make
1062 1.1 abs usr.bin/yacc
1063 1.1 abs usr.bin/lex
1064 1.11 lukem usr.bin/xlint
1065 1.142 drochner usr.bin/config
1066 1.1 abs
1067 1.34 simonb Other problems and possible solutions:
1068 1.1 abs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1069 1.1 abs Symptom:Complaints involving a Makefile.
1070 1.17 erh Fix: Rebuild usr.bin/make:
1071 1.17 erh cd usr.bin/make && make && make install
1072 1.111 simonb Or, a failsafe method if that doesn't work:
1073 1.17 erh cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
1074 1.17 erh
1075 1.1 abs Fix: Make sure .mk files are up to date.
1076 1.1 abs cd share/mk && make install
1077 1.2 mrg
1078 1.2 mrg Symptom:Kernel `config' fails to configure any kernel, including GENERIC.
1079 1.142 drochner Fix: Rebuild usr.bin/config
1080 1.1 abs
1081 1.1 abs Symptom:
1082 1.1 abs Fix: Rebuild usr.bin/yacc
1083 1.1 abs
1084 1.1 abs Symptom:
1085 1.1 abs Fix: Rebuild usr.bin/lex
1086 1.1 abs
1087 1.1 abs Symptom:
1088 1.1 abs Fix: rm /usr/lib/libbfd.a
1089 1.4 itojun
1090 1.4 itojun Symptom:Obsolete intermediate files are used during compilation
1091 1.4 itojun Fix: Try the following sequence of commands in the directory in question.
1092 1.4 itojun make cleandir; rm `make print-objdir`; make cleandir; make obj
1093 1.4 itojun (If you built the tree without "make obj" in the past, obsolete files
1094 1.4 itojun may remain. The command tries to clean everything up)
1095 1.5 wiz
1096 1.207 mbalmer Symptom:.../sysinst/run.c:xx: warning: initialization from incompatible
1097 1.207 mbalmer pointer type
1098 1.5 wiz Fix: Rebuild and install usr.bin/menuc
1099 1.12 itojun
1100 1.12 itojun Symptom:mklocale not found during build in share/locale/ctype
1101 1.12 itojun Fix: Build and install usr.bin/mklocale
1102 1.13 dogcow
1103 1.86 kleink Symptom:undefined reference to `__assert13' or `__unsetenv13'
1104 1.13 dogcow Fix: Rebuild and install lib/libc
1105 1.13 dogcow
1106 1.142 drochner Symptom:usr.bin/config fails to build.
1107 1.19 cgd Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
1108 1.13 dogcow
1109 1.19 cgd Symptom:undefined reference to `getprogname' or `setprogname'
1110 1.19 cgd Fix: Rebuild and install lib/libc
1111 1.24 abs
1112 1.24 abs Symptom:lint does not understand the '-X' option
1113 1.24 abs Fix: May need to build & install libs with NOLINT=1 before rebuilding lint
1114 1.223 joerg
1115 1.223 joerg Symptom:Update build fails in src/tools/gcc complaining that a variable
1116 1.223 joerg (e.g. CPPFLAGS) has changed since the previous run.
1117 1.223 joerg Fix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
1118 1.257 apb
1119 1.257 apb Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
1120 1.257 apb No such file or directory.
1121 1.257 apb Cause: If a directory is created by mistake, then it is sometimes
1122 1.257 apb deleted from the CVS repository using administrative commands
1123 1.257 apb that bypass the normal cvs access controls. If your cvs working tree
1124 1.257 apb contains references to a directory that has been deleted on the
1125 1.257 apb server in this way, then "cvs update" reports this error.
1126 1.257 apb Fix: Recursively delete the affected directory from your working tree
1127 1.257 apb and try the update again.
1128