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