UPDATING revision 1.158
11.158Sdbj$NetBSD: UPDATING,v 1.158 2007/03/10 00:10:15 dbj Exp $
21.1Sabs
31.123SjmcThis file (UPDATING) is intended to be a brief reference to recent
41.123Sjmcchanges that might cause problems in the build process, and a guide for
51.123Sjmcwhat to do if something doesn't work.
61.1Sabs
71.123SjmcFor a more detailed description of the recommended way to build NetBSD
81.123Sjmcusing build.sh, see the BUILDING file.
91.123Sjmc
101.123SjmcNote that much of the advice in this UPDATING file was written before
111.123Sjmcbuild.sh existed.  Nevertheless, the advice here may be useful for
121.123Sjmcworking around specific problems with build.sh.
131.123Sjmc
141.123SjmcSee also: BUILDING, build.sh, Makefile.
151.1Sabs
161.1SabsRecent changes:
171.1Sabs^^^^^^^^^^^^^^^
181.138Slukem
191.158Sdbj20070210: 
201.158Sdbj        src/sys/sys/{sa.h,savar.h} were removed.
211.158Sdbj          find ${OBJDIR} \( -name .depend -o -name '*.d' \) -print \
221.158Sdbj              | xargs egrep -l '/sa.h|/savar.h' | xargs rm
231.158Sdbj        will allow dependencies on those files to get get rebuilt
241.158Sdbj
251.157Sapb20070209:
261.157Sapb        The threading model was changed when the newlock2 branch
271.157Sapb        was merged to NetBSD-current.  If you boot with a new
281.157Sapb        kernel (version 4.99.10), then you also need a new pthread
291.157Sapb        library (/usr/lib/libpthread.so.0.7).  If you boot with
301.157Sapb        an old kernel, then you need the old pthread library
311.157Sapb        (/usr/lib/libpthread.so.0.6).  Provided you keep the kernel and
321.157Sapb        the pthread library in sync, old threaded applications should
331.157Sapb        continue to work with an old or new kernel.  Note that named(8)
341.157Sapb	is the only threaded application in the base system.
351.157Sapb
361.154She20061214:
371.154She	Following the move of string_to_flags() and flags_to_string()
381.154She	from the bin/ls/ sources to libutil, users doing UPDATE builds
391.154She	will need to do a "make cleandir" in
401.154She		tools/mtree/, tools/makefs/, tools/binstall/, tools/pax/,
411.154She		bin/pax/, bin/ls/, usr.sbin/mtree/, usr.sbin/makefs/,
421.156She		usr.bin/xinstall/, libexec/ftpd/, rescue/, as well
431.156She		as the installation images in distrib/
441.154She	in order to excise stale references to the old stat_flags.h header
451.154She	file in the ls sources -- stat_flags.h has been removed.
461.154She
471.152Schristos20061108:
481.152Schristos	The configure script used in the src/tools/gcc compiler has been
491.152Schristos	changed to indicate that our libc has ssp support built-in and
501.152Schristos	does not depend on -lssp and -lssp-nonshared. You'll need to
511.152Schristos	make clean in src/tools/gcc first to rebuild the compiler.
521.152Schristos
531.151Srpaulo20061009:
541.151Srpaulo	The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer
551.151Srpaulo	available. Use net.inet{,6}.tcp{,6}.congctl.selected instead.
561.151Srpaulo
571.150Sbjh2120060814:
581.150Sbjh21	The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been
591.150Sbjh21	withdrawn.  Use vidcvideo and pckbd instead.  See the GENERIC
601.150Sbjh21	kernel configuration for an example.  X servers from the last
611.150Sbjh21	few years should cope.
621.150Sbjh21
631.149Schristos20060703:
641.149Schristos	MPACPI is no more. We always configure PCI interrupts using ACPI
651.149Schristos	if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed
661.149Schristos	to ACPI_SCANPCI. Thanks to work from fvdl.
671.149Schristos
681.148Sdogcow20060627:
691.148Sdogcow	socket(2) has changed, and its system call has been versioned.
701.148Sdogcow	For userlands with the old version of socket(2), make sure that
711.148Sdogcow	your kernel has 'options COMPAT_30' set, or else 'bad system call'
721.148Sdogcow	errors will result.
731.148Sdogcow
741.146Spavel20060526:
751.147Schristos	The kernel linker scripts for i386 and xen 
761.147Schristos	(sys/arch/i386/conf/kern.ldscript*) were changed to set the
771.146Spavel	load address correctly, for the benefit of MULTIBOOT boot loaders
781.146Spavel	(like Grub). If you use a linker (ld) older than from 2006/04/17, it
791.147Schristos	will be unable to link the kernel because of a bug and ld will fail
801.147Schristos	with an error like:
811.147Schristos	    ../../../../arch/i386/conf/kern.ldscript:45 \
821.147Schristos		non constant expression for load base
831.147Schristos	You need to update at least src/gnu/dist/binutils/ld and recompile
841.147Schristos	and install the linker. If using the build.sh script, the easiest
851.147Schristos	way is with a "build.sh tools" command, with any other options
861.147Schristos	that you use normally. When using build.sh, the linker binary is
871.147Schristos	installed as ${TOOLDIR}/bin/i386--netbsdelf-ld.
881.147Schristos
891.145Smartin20060131:
901.145Smartin	the protocol between the sparc64 bootloader (ofwboot) and
911.145Smartin	the kernel was changed. Before installing a new kernel,
921.145Smartin	you need to update ofwboot. After a full build, just copy
931.145Smartin	/usr/mdec/ofwboot to /, or do a rebuild of
941.145Smartin	src/sys/arch/sparc/stand/ofwboot and install the result to /.
951.145Smartin
961.144Syamt20050917:
971.144Syamt	arch/*/conf/std.* was changed to include conf/std, which
981.144Syamt	contains MI options previously enabled by default.
991.144Syamt	If you have kernel config files which doesn't include
1001.144Syamt	arch/*/conf/std.*, you need to edit them to include conf/std
1011.144Syamt	to get the previous configuration.
1021.144Syamt
1031.143Slukem20050830:
1041.143Slukem	named.conf was moved from /etc/namedb to /etc.
1051.143Slukem	postinstall(8) migrates this during interactive use.
1061.143Slukem	Users of MKUPDATE=yes will need to manually rectify
1071.143Slukem	this in their DESTDIR.
1081.143Slukem
1091.142Sdrochner20050825:
1101.142Sdrochner	Some data structures in sys/device.h, related to interface
1111.142Sdrochner	attributes and locator names, were changed. config(1) was
1121.142Sdrochner	modified to emit the new data structures.
1131.142Sdrochner	Thus usr.bin/config must be updated (and run on the kernel
1141.142Sdrochner	configuration file) before a new kernel can be built.
1151.142Sdrochner
1161.139Schristos20050531:
1171.141Saugustss	genassym.sh(8) was moved to genassym(1). You need to either build
1181.141Saugustss	tools first or install the version of genassym from /usr/bin before
1191.139Schristos	you can build a kernel again.
1201.139Schristos
1211.140Syamt20050520:
1221.140Syamt	Because a kernfs bug which xentools relies on was fixed,
1231.140Syamt	xentools up to xentools20-2.0.3nb4 won't work with new kernel.
1241.140Syamt
1251.138Slukem20050417:
1261.138Slukem	postinstall(8) was moved from /etc to /usr/sbin and made part
1271.138Slukem	of the "base" set, to make it easier to invoke after an
1281.138Slukem	upgrade.
1291.138Slukem
1301.136Scube20050325:
1311.136Scube	pcppi(4) was separated in two devices, adding attimer(4).  Be sure
1321.136Scube	to add a config line for an attimer(4) device in your kernel
1331.136Scube	configuration, or you won't be able to set the pitch of the beep
1341.137Scube	with wsconsctl.  Depending on the default value for the pitch, you
1351.137Scube	might even not hear any more beep.  Also, it is advised to attach both
1361.137Scube	devices the same way (i.e., both on isa or both on acpi) or the
1371.137Scube	pcppi(4) device may fail to find the attimer(4) one.
1381.136Scube
1391.135Sjmc20050211:
1401.135Sjmc	Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in
1411.135Sjmc	some of the cross tools to fail if they use configure. Some configure's
1421.135Sjmc	cache the environment passed in and notice the new environment is
1431.135Sjmc	different and abort. Doing a clean in tools/ should be enough to
1441.135Sjmc	make a build continue.
1451.135Sjmc
1461.134Schristos20050109:
1471.134Schristos	Since su is using pam by default now, make sure that you have
1481.134Schristos	/etc/pam.d populated (postinstall will do that automatically
1491.134Schristos	for you). Otherwise su will fail open (i.e. will not require
1501.134Schristos	a password).
1511.134Schristos
1521.133Schristos20041229:
1531.133Schristos	Make had a path resolution bug that manifested itself as not
1541.133Schristos	being able to install openpam.3. This bug has been fixed, but
1551.133Schristos	you might need to rebuild make manually first to get through
1561.133Schristos	the build.
1571.133Schristos
1581.130Schristos20041201:
1591.130Schristos	Userland programs have been changed to use /dev/bpf instead of
1601.130Schristos	/dev/bpfX. You need to create that device by installing a new
1611.131Swiz	MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]*
1621.99Smrg
1631.129Sjmc20041006:
1641.129Sjmc
1651.129Sjmc	A bug was introduced into /bin/sh (var.c rev 1.35) which causes
1661.129Sjmc	variables to not export correctly to subshells in all cases. This
1671.129Sjmc	will cause builds to break if that version of /bin/sh is installed
1681.129Sjmc	on the system. The proper version of /bin/sh can be verified with:
1691.129Sjmc
1701.129Sjmc        ident /bin/sh | grep var
1711.129Sjmc
1721.129Sjmc	Any /bin/sh w. version 1.35 will not work and needs to be updated
1731.129Sjmc	before attempting a build.
1741.129Sjmc	
1751.127Schristos20041001:
1761.127Schristos	The ipfilter kernel sources moved from sys/netinet to
1771.127Schristos	dist/sys/ipf/netinet. Due to the move some Makefile
1781.127Schristos	dependencies are now dangling requiring a make cleandir
1791.128She	before they work again (kdump, ktruss, rescue, ipf, and
1801.128She	ftp-proxy are the victims).
1811.127Schristos
1821.125Satatat20040715:
1831.125Satatat	The rc.d/sendmail script now uses a heuristic to determine
1841.125Satatat	if sendmail should be started at boot time.  It checks the
1851.125Satatat	contents of /etc/mailer.conf, /etc/mail/submit.cf, and the
1861.125Satatat	owner and mode of the sendmail binary to see if any changes
1871.125Satatat	to the mail infrastructure have been made.  If no changes
1881.125Satatat	are detected, it will start an SMTP listener.
1891.125Satatat
1901.125Satatat	Setting sendmail=NO in /etc/rc.conf will override this.
1911.125Satatat
1921.125Satatat	If you are only using sendmail by default and only for
1931.125Satatat	local delivery, it is important that you also update your
1941.125Satatat	sendmail.cf so that the SMTP listener only listens on the
1951.125Satatat	loopback interface.
1961.125Satatat
1971.125Satatat20040715:
1981.125Satatat	The method by which athhal-elf.o gets pulled into i386
1991.125Satatat	kernel builds has been changed again.  The latest version
2001.125Satatat	of bsd.files.mk is no longer required.
2011.125Satatat
2021.124Sjmc20040621:
2031.124Sjmc	Due to the recent rototill of tools/compat it's crucial one starts
2041.124Sjmc	from a clean objdir under tools/*.
2051.124Sjmc
2061.124Sjmc	This is mostly due to generated files (yacc and lex sources) needing
2071.125Satatat	to be generated with new rules from bsd.hostprog.mk.
2081.124Sjmc
2091.124Sjmc	The safest course is to rm -rf all objects under tools before building.
2101.124Sjmc
2111.121Slukem20040516:
2121.121Slukem	The end-user modifiable X11 configuration has been moved
2131.121Slukem	from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.
2141.121Slukem	Ensure that src and xsrc is up to date, and run
2151.121Slukem	"make cleandir" in src/x11 before your next build.
2161.121Slukem
2171.126Slukem	postinstall currently doesn't migrate the files from
2181.126Slukem	/usr/X11R6/lib/X11/* to /etc/X11/* although it does
2191.126Slukem	detect that this needs to occur, so you'll have to
2201.126Slukem	manually move these files yourself.
2211.126Slukem
2221.119Satatat20040426:
2231.119Satatat	Support for the original dynamic sysctl node structure has
2241.119Satatat	been removed in favor of the newer layout.  This affects
2251.119Satatat	consumers of the create and delete interface, as well as
2261.119Satatat	the dynamic discovery mechanism.  This is believed only to
2271.119Satatat	be the sysctl(8) binary itself, at this point in time, so
2281.119Satatat	the only effect of this should be that a sysctl binary
2291.119Satatat	built from sources dated between 2003/12/04 and 2004/03/24
2301.119Satatat	will not work on a kernel built from sources dated after
2311.119Satatat	2004/04/25.  If you need a new sysctl binary but build.sh
2321.119Satatat	does not work, make sure that your revision of
2331.120Satatat	src/sys/sys/sysctl.h is 1.112 (or later), and then the
2341.120Satatat	do the following:
2351.119Satatat
2361.120Satatat	cd /usr/src (or wherever your source tree is)
2371.120Satatat	make USETOOLS=no includes
2381.120Satatat	cd lib/libc
2391.120Satatat	make USETOOLS=no dependall install
2401.120Satatat	cd ../../sbin/sysctl
2411.119Satatat	make USETOOLS=no dependall install
2421.119Satatat
2431.122Sitojun	If you are using older sysctl binary, GNU autoconf would fail to
2441.122Sitojun	identify your machine architecture, and tries to build binary for
2451.122Sitojun	"unknown-unknown-netbsd20F" or something like that.  if that happens,
2461.122Sitojun	make sure to follow the above steps.
2471.122Sitojun
2481.118Sdbj20040425:
2491.118Sdbj	The ffs superblock issues listed below under 20040109 and 20030402
2501.118Sdbj	are now automatically addressed by the /etc/rc.d/fixsb script or by
2511.118Sdbj	sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4
2521.118Sdbj	invocation mentioned below will continue to work and is now
2531.118Sdbj	automated by those scripts.  Note that under certain circumstances,
2541.118Sdbj	affected filesystems upgraded to a -current kernel first before
2551.118Sdbj	upgrading their userland with the fixsb and fsck_ffs fixes may
2561.118Sdbj	encounter a 'freeing free inode' panic when writing to the affected
2571.118Sdbj	filesystem, so it is a good idea to repair the filesystem as soon as
2581.118Sdbj	possible.  For more details on the fixsb script, see pr install/25138.
2591.118Sdbj
2601.115Schristos20040418:
2611.121Slukem	statfs(2) and friends have been replaced with statvfs(2). Before
2621.115Schristos	installing a newly build userland make sure that you are running
2631.115Schristos	a newly built kernel with COMPAT_20 set. In addition your libc
2641.115Schristos	build might not work (undefined SYS_statfs symbol) because make
2651.115Schristos	clean does not know how to remove files it does not know about
2661.116Schristos	anymore. Manually remove all generated .S sources and objects
2671.116Schristos	from the libc build directory.
2681.115Schristos
2691.114Sjmc20040326:
2701.114Sjmc	The method by which athhal-elf.o gets pulled into i386 kernel builds
2711.117Sjmc	has been changed. The file is now stored as a uuencoded file in CVS
2721.114Sjmc	and the generated Makefile will use the new .uue rules from bsd.file.mk
2731.114Sjmc	to build it.
2741.114Sjmc
2751.114Sjmc	This means you must have the latest bsd.files.mk installed when
2761.114Sjmc	building a kernel without USETOOLS=yes.
2771.114Sjmc
2781.113Sdan20040318:
2791.113Sdan	A bug in the cgd(4) blowfish code was corrected, without
2801.113Sdan	provision of backwards compatibility, after several public
2811.113Sdan	notices over several months. Users of cgd with blowfish cipher
2821.113Sdan	ONLY must dump their data before updating their kernels, and
2831.113Sdan	recreate cgd's and restore data using the new kernel. See
2841.113Sdan	(recent message to current-users, URL when mail-index has updated)
2851.113Sdan
2861.108Sbjh2120040313:
2871.108Sbjh21	On acorn32, the opms and qms drivers have been withdrawn, and
2881.108Sbjh21	the old wsqms driver is now called qms.  Kernel config files
2891.108Sbjh21	will need updating.  See the ones in sys/arch/acorn32/conf
2901.108Sbjh21	for examples.
2911.108Sbjh21
2921.106Sbjh2120040125:
2931.106Sbjh21	On acorn32, the beep and sysbeep devices are no longer
2941.106Sbjh21	needed, and will need to be deleted from kernel configuration
2951.106Sbjh21	files.
2961.105Sbjh21
2971.102Sdbj20040109:
2981.102Sdbj	Compatibility for old ffs superblock layouts has been
2991.102Sdbj	added, and the restrictive fsck checks have been reenabled
3001.102Sdbj	when using those layouts.  If you have been using -current
3011.102Sdbj	since 20030402, you may find that fsck again signals fatal
3021.110Sdbj	superblock mismatches.  To repair, make sure you have
3031.111Ssimonb	an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4
3041.109Sdbj	to complete the filesystem upgrade.  A message has
3051.111Ssimonb	been added to the kernel which should detect this problem.
3061.111Ssimonb	See the following discussion for more information:
3071.112Skeihan	http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
3081.102Sdbj
3091.99Smrg20031203:
3101.100Skeihan	New binutils builds may fail due to old dependencies.
3111.99Smrg	It's necessary to "make cleandir" to ensure that
3121.99Smrg	the dependencies will be rebuilt correctly.
3131.98Swiz
3141.98Swiz20031111:
3151.98Swiz	A newer mkdep is needed.  Error noting that is
3161.98Swiz		cc: Ambiguous abbreviation --
3171.97Slukem
3181.97Slukem20031008:
3191.97Slukem	/usr/include/sys/disklabel_mbr.h was removed.
3201.97Slukem	It's necessary to "make cleandir" to ensure that
3211.97Slukem	the dependencies will be rebuilt correctly.
3221.96Schristos
3231.109Sdbj20031007:
3241.153Sreed	A sign extension bug was fixed which set all the high bits
3251.111Ssimonb	of our newly expanded ffs fs_flags.  This should only
3261.111Ssimonb	affect users who installed or upgraded in September of 2003.
3271.109Sdbj	A small utility program was posted to tech-kern which
3281.111Ssimonb	should fix this problem, and a warning message was added
3291.111Ssimonb	to the kernel which should discover and warn about it.  See
3301.111Ssimonb	http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html
3311.109Sdbj
3321.96Schristos20030906:
3331.96Schristos	With the addition of siginfo support the old signal trampoline
3341.96Schristos	code has been deprecated to COMPAT_16. Make sure that your running
3351.96Schristos	kernel has COMPAT_16 enabled before building userland.
3361.94Schristos
3371.94Schristos20030801:
3381.95Swiz	With the new openssl, there is some header and library shuffling.
3391.94Schristos	rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \
3401.95Swiz	/usr/lib/libdes* before building.
3411.92Swiz
3421.92Swiz20030703:
3431.92Swiz	Texinfo was updated to 4.6.  To avoid failures when trying to
3441.92Swiz	build the included texinfo files, do:
3451.92Swiz
3461.92Swiz	cd src/gnu/usr.bin/texinfo
3471.92Swiz	make MKINFO=no dependall install
3481.90Swiz
3491.90Swiz20030630:
3501.101Sjunyoung	Groff was updated to 1.19; it's probably necessary to do
3511.91Swiz		cd share/mk && make install
3521.90Swiz		cd src/gnu/usr.bin/groff
3531.90Swiz		make MKMAN=no dependall install
3541.90Swiz	(untested).
3551.89Schristos
3561.89Schristos20030516:
3571.89Schristos	Due to bugs in the export handling code, invalid export lines
3581.89Schristos	were accepted before and caused the kernel to panic when
3591.89Schristos	mountd got restarted because it freed memory that had already
3601.89Schristos	been freed. This has been fixed and the kernel checks
3611.89Schristos	export addresses very strictly. If you upgrade your kernel,
3621.89Schristos	make sure you also upgrade mountd, because if your export
3631.89Schristos	file contains lines with an old inet4 address syntax (i.e.
3641.89Schristos	a.b.c or a.b or a), they will get rejected by the new kernel.
3651.87Sbjh21
3661.87Sbjh2120030402:
3671.87Sbjh21	The superblock layout for FFS was changed.  If you have 1.6
3681.87Sbjh21	fsck binaries, they will signal a fatal superblock mismatch
3691.87Sbjh21	with the first alternate, because they compare too many
3701.87Sbjh21	fields (even ones that aren't useful).  If possible, upgrade
3711.87Sbjh21	your fsck_ffs binary before using a new kernel.
3721.87Sbjh21	None of this signals actual filesystem damage.
3731.85Satatat
3741.85Satatat20030324:
3751.85Satatat	sendmail version 8.12.8 was imported.  Since sendmail is
3761.85Satatat	now setgid to the smmsp group, and runs in "collection"
3771.85Satatat	mode for most common activities, there is a new config
3781.85Satatat	file called submit.cf that needs to live in /etc/mail.
3791.85Satatat	The generic submit.cf sample in /usr/share/sendmail/cf
3801.85Satatat	is named netbsd-msp.cf.  Upgrading your regular sendmail
3811.85Satatat	configuration file is also strongly advised.
3821.85Satatat
3831.85Satatat	See the section named "MESSAGE SUBMISSION PROGRAM" in
3841.85Satatat	the updated /usr/share/sendmail/README file for more
3851.85Satatat	information.
3861.82Swiz
3871.82Swiz20030117:
3881.82Swiz	Texinfo was updated to 4.3.  To avoid failures when trying to
3891.82Swiz	build the included texinfo files, do:
3901.82Swiz
3911.82Swiz	cd src/gnu/usr.bin/texinfo
3921.82Swiz	make MKINFO=no dependall install
3931.81Slukem
3941.81Slukem20021223:
3951.81Slukem	The METALOG format changed slightly, to remove the leading
3961.81Slukem	"${DESTDIR}" from path names.
3971.81Slukem	This only affects people building with UNPRIVED.
3981.81Slukem	For complete safety, remove the DESTDIR entirely and
3991.81Slukem	update tools/mtree, before running make build.
4001.88Sitojun
4011.88Sitojun20021219:
4021.88Sitojun	CVS repository layout was changed.  See the following for details
4031.88Sitojun	if you are using (anonymous) cvs to update your tree.
4041.88Sitojun
4051.93Ssalo	http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html
4061.80Slukem
4071.80Slukem20021219:
4081.80Slukem	install(1) had a '-N dbdir' option added, to specify an
4091.80Slukem	alternate location to look up users & groups (instead
4101.80Slukem	of the host system passwd(5) and group(5) databases).
4111.80Slukem
4121.80Slukem	The build system was modified to take advantage of
4131.80Slukem	this option (using ${NETBSDSRCDIR}/etc), so if you
4141.83Skei	use USETOOLS==no, you may have to rebuild and
4151.80Slukem	reinstall usr.bin/xinstall first.
4161.78Slukem
4171.78Slukem20021130:
4181.78Slukem	fparseln(3) moved from libutil to libc.
4191.78Slukem	If building to DESTDIR=/, reinstall the includes
4201.78Slukem	and rebuild libc:
4211.78Slukem		make includes
4221.78Slukem		make do-lib-libc
4231.78Slukem	If using build.sh, "cd tools/compat && make clean"
4241.78Slukem	before rebuilding the tools.
4251.77Slukem
4261.77Slukem20021126:
4271.77Slukem	The mk.conf(5) variable SYS_INCLUDE has been deprecated,
4281.77Slukem	including the optional "SYS_INCLUDE=symlinks" support.
4291.77Slukem	All header files, including <sys/*.h> are copied into
4301.77Slukem	/usr/include.
4311.76Sthorpej
4321.76Sthorpej20021121:
4331.76Sthorpej	The C run-time support files crtbegin.o and crtend.o
4341.76Sthorpej	(and their companions crtbeginS.o and crtendS.o) were
4351.76Sthorpej	split up, with new crti.o and crtn.o files resulting.
4361.76Sthorpej	This means that libtool needs to be rebuilt once the
4371.76Sthorpej	new libraries are installed.  The process of rebuilding
4381.76Sthorpej	libtool will cause it to automatically notice the new
4391.76Sthorpej	required files, but it *must* be rebuilt in order to
4401.76Sthorpej	do this.
4411.76Sthorpej
4421.76Sthorpej	An out-of-date libtool will result in shared libraries
4431.76Sthorpej	which lack _init() and _fini() routines, which means that
4441.153Sreed	their global constructors/destructors will not be invoked.
4451.75Sthorpej
4461.75Sthorpej20021121:
4471.75Sthorpej	A bug related to how ARM ELF objects were tagged has been
4481.75Sthorpej	corrected.
4491.75Sthorpej
4501.75Sthorpej	NetBSD ARM ELF uses the soft-VFP floating point model by
4511.75Sthorpej	default.  However, the assembler lacked support for marking
4521.75Sthorpej	objects as using the VFP floating point format, and the
4531.79Swiz	compiler was not properly passing the flag indicating "soft-VFP"
4541.75Sthorpej	to the assembler.
4551.75Sthorpej
4561.75Sthorpej	Unfortunately, this means that the linker will now consider
4571.75Sthorpej	old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be
4581.75Sthorpej	incompatible with new (properly marked) objects.
4591.75Sthorpej
4601.75Sthorpej	The problem will only manifest itself if you attempt to compile
4611.75Sthorpej	a new program using the fixed toolchain, and link that program
4621.75Sthorpej	against old libraries which do not have the proper "softvfp"
4631.75Sthorpej	markings.  ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES
4641.75Sthorpej	WILL CONTINUE TO WORK PROPERLY.
4651.75Sthorpej
4661.75Sthorpej	The only work-around for the problem is to recompile all of
4671.75Sthorpej	the libraries on the system.  The easiest way to do this for
4681.79Swiz	system libraries is to install a binary snapshot; they are
4691.93Ssalo	generally available on releng.NetBSD.org.  Any packages you
4701.75Sthorpej	have installed which supply libraries will have to be recompiled
4711.75Sthorpej	if you wish to link new programs against those libraries.
4721.75Sthorpej
4731.75Sthorpej	If you have questions about this matter, please contact
4741.93Ssalo	port-arm@NetBSD.org.
4751.73Sprovos
4761.73Sprovos20021011:
4771.73Sprovos	Systrace has been improved to support privilege elevation.
4781.73Sprovos	Updating the kernel requires the userland part of systrace
4791.79Swiz	to be rebuilt.
4801.72Sthorpej
4811.72Sthorpej20021010:
4821.72Sthorpej	The config(8) grammar was changed to allow options to register
4831.72Sthorpej	dependencies on attributes, as well as other options.  Users
4841.72Sthorpej	must update and reinstall usr.sbin/config before building a new
4851.72Sthorpej	kernel.
4861.70Sthorpej
4871.70Sthorpej20021009:
4881.70Sthorpej	A new attribute dependency syntax was introduced to config(8),
4891.70Sthorpej	which is now used by the SCSI configuration description.  Users
4901.71Swiz	must update and reinstall usr.sbin/config before building a new
4911.70Sthorpej	kernel.
4921.69Sthorpej
4931.69Sthorpej20021003:
4941.69Sthorpej	Several changes have been made to the autoconfiguration
4951.69Sthorpej	framework.  Users must update and reinstall usr.sbin/config
4961.69Sthorpej	before building a new kernel.
4971.74Sjschauma
4981.74Sjschauma20021001:
4991.74Sjschauma	The i386mp branch has been merged.  To compile a kernel, users
5001.74Sjschauma	will need to add the option 'cpu* at mainbus?' to their configuration
5011.74Sjschauma	file.  Multiprocessor kernels will need
5021.74Sjschauma	ioapic*		at mainbus? apid ?
5031.74Sjschauma	options		MULTIPROCESSOR
5041.74Sjschauma	options		COM_MPLOCK
5051.68Slukem
5061.68Slukem20020922:
5071.68Slukem	MKDYNAMICROOT=yes enabled by default, which means that
5081.68Slukem	certain shared libraries are installed into /lib, the shared
5091.68Slukem	linker is installed into /libexec, and all programs in /bin
5101.68Slukem	and /sbin are dynamically linked.
5111.68Slukem	If you do not use "make build", you should ensure that
5121.68Slukem	you have the libraries and shared linker in the new locations,
5131.68Slukem	with:
5141.68Slukem		make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so
5151.67Slukem
5161.67Slukem20020917:
5171.67Slukem	USE_NEW_TOOLCHAIN has been replaced with:
5181.67Slukem	    -	TOOLCHAIN_MISSING -- set to "yes" on platforms for which
5191.67Slukem		there is no working in-tree toolchain (hppa, ns32k, sh5,
5201.67Slukem		x86_64).
5211.67Slukem	    -	EXTERNAL_TOOLCHAIN -- if defined by the user, points to the
5221.79Swiz		root of an external toolchain (e.g. /usr/local/gnu).  This
5231.67Slukem		enables the cross-build framework even for TOOLCHAIN_MISSING
5241.67Slukem		platforms.
5251.66Sgehenna
5261.66Sgehenna20020906:
5271.66Sgehenna	gehenna-devsw has been merged into the trunk. Need to update and
5281.79Swiz	reinstall usr.sbin/config before building the kernel.
5291.65Slukem
5301.65Slukem20020822:
5311.65Slukem	Crunched rescue tools (contents of /bin and /sbin, plus others)
5321.65Slukem	are now provided in /rescue.
5331.65Slukem
5341.65Slukem	To ensure that these are built statically linked (no matter
5351.65Slukem	what the setting of LDSTATIC is), use a crunchgen(1) built
5361.65Slukem	from sources newer than 20020820 (see the next entry).
5371.65Slukem
5381.65Slukem20020820:
5391.65Slukem	crunchgen(1) changed to ensure that the generated program
5401.65Slukem	is statically linked.
5411.65Slukem
5421.65Slukem	Solution: update and reinstall usr.bin/crunch
5431.84Sgrant
5441.84Sgrant20020605:
5451.84Sgrant	smmsp user/group has been added for sendmail.
5461.84Sgrant
5471.84Sgrant	Add the following into /etc/group:
5481.84Sgrant
5491.84Sgrant	smmsp:*:17:
5501.84Sgrant
5511.84Sgrant	and the following to /etc/master.passwd (via vipw):
5521.84Sgrant
5531.84Sgrant	smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin
5541.61Sitojun
5551.61Sitojun20020515:
5561.61Sitojun	sshd user/group has been added.  Need to hand add this in, or sshd
5571.153Sreed	will not let you log in (with default, or UsePrivilegeSeparation=yes)
5581.61Sitojun
5591.61Sitojun	Add the following into /etc/group:
5601.61Sitojun
5611.61Sitojun	sshd:*:16:
5621.61Sitojun
5631.61Sitojun	and the following to /etc/master.passwd (via vipw):
5641.61Sitojun
5651.63Senami	sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin
5661.61Sitojun	
5671.79Swiz	Also /var/chroot/sshd directory needs to be present (digged as part of
5681.79Swiz	the build process).
5691.60Ssommerfe
5701.60Ssommerfe20020426:
5711.60Ssommerfe	NBUILDJOBS obsoleted in favor of just using -j.
5721.59Slukem
5731.59Slukem20020426:
5741.59Slukem	etc/postinstall added, which performs various checks for 
5751.59Slukem	configuration file updates and changes, and can fix most of
5761.59Slukem	the problems identified.
5771.59Slukem	This should make it much easier to upgrade a system's
5781.59Slukem	configuration from earlier systems (as far back as NetBSD 1.5).
5791.56Slukem
5801.56Slukem20020320:
5811.79Swiz	<bsd.lib.mk> needs a new install(1) for its "-a cmd" support.
5821.79Swiz	Build and install at usr.bin/xinstall before the build.
5831.56Slukem
5841.55Sitojun20020319:
5851.79Swiz	Raw IPv6 socket now makes strict checking for sa_family and sa_len
5861.79Swiz	on send(2) operation.  Be sure to have sbin/rtsol and usr.sbin/rtsold
5871.55Sitojun	newer than November 2001 when you upgrade the kernel.
5881.55Sitojun
5891.54Sitojun20020311:
5901.54Sitojun	ssh configuration files were moved from /etc to /etc/ssh.  Beware
5911.54Sitojun	if you restart your machine from remote.  Note that sshd.conf needs
5921.54Sitojun	to be changed (due to the use of "/etc" inside).
5931.54Sitojun
5941.54Sitojun20020223:
5951.53Smatt	Users of the VAX port will need to rebuild and install gas
5961.53Smatt	so it deal with the now present register prefix used in all
5971.53Smatt	the VAX assembly files.
5981.53Smatt
5991.50Sitojun20020118:
6001.50Sitojun	ntpd user/group has been added.  Need to hand add this in or builds
6011.50Sitojun	will break as mtree aborts early.
6021.50Sitojun
6031.50Sitojun	Add the following into /etc/group:
6041.50Sitojun
6051.50Sitojun	ntpd:*:15:
6061.50Sitojun
6071.50Sitojun	and the following to /etc/master.passwd (via vipw):
6081.50Sitojun
6091.50Sitojun	ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin
6101.50Sitojun
6111.49Sjmc20011207:
6121.49Sjmc	If you're attempting to build a snapshot on sparc64 and are getting
6131.49Sjmc	reloc errors from the toolchain groff binary this means your native
6141.49Sjmc	toolchain has some broken C++ bits.
6151.49Sjmc
6161.49Sjmc	To fix:
6171.49Sjmc
6181.49Sjmc	Build a new toolchain (i.e. build.sh -t)
6191.49Sjmc	Use the new toolchain to build and install natively (i.e. /usr/lib)
6201.49Sjmc
6211.49Sjmc	gnu/lib/libgcc
6221.51Spooka	gnu/lib/libstdc++
6231.49Sjmc
6241.49Sjmc	After this a snapshot will be able to be built.
6251.49Sjmc
6261.47Sjmc20011201:
6271.47Sjmc	In order for a sparc64 build to work you must have a working awk. If
6281.47Sjmc	you've built and installed a system with the new toolchain up to this
6291.52Swiz	point you do not have a working awk as its ability to do floating
6301.47Sjmc	point is broken. 
6311.47Sjmc
6321.47Sjmc	To build:
6331.47Sjmc
6341.47Sjmc	remake and install gnu/lib/libgcc
6351.47Sjmc	remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links
6361.48Sjmc	against the new libgcc.a)
6371.47Sjmc
6381.46Sthorpej20011128:
6391.46Sthorpej	Kernel config information was changed to use defflag in
6401.46Sthorpej	the various "files" files.  Bug fixes to config(8) are
6411.46Sthorpej	required in order for this to work properly.  Make sure
6421.46Sthorpej	to build and install in usr.sbin/config before attempting
6431.46Sthorpej	to build a new kernel.
6441.46Sthorpej
6451.45Syamt20011030:
6461.45Syamt	libc/locale/wcstod.c now needs new lint(1). Update lint(1)
6471.45Syamt	before building libc.
6481.43Smason
6491.44Stv20011029:
6501.44Stv	The new document BUILDING.mdoc (view with nroff | more, or
6511.44Stv	see pre-generated .txt and .html versions) describes the build
6521.44Stv	procedure in great detail.  BUILDING, and the USE_NEW_TOOLCHAIN
6531.44Stv	build process, are intended in the long run to replace this
6541.44Stv	manual update log.
6551.44Stv
6561.44Stv	Users building a USE_NEW_TOOLCHAIN system should read the
6571.44Stv	BUILDING document for caveats.  Generally, BUILDING supersedes
6581.44Stv	UPDATING for these systems, as tool updating is taken care of
6591.44Stv	by the new build system.
6601.42Sperry
6611.42Sperry20011028:
6621.42Sperry	src/etc/Makefile now needs install to be able to handle
6631.42Sperry	symlinks that point to nowhere. A bug in install that
6641.42Sperry	prevented this was corrected.
6651.42Sperry
6661.42Sperry	Solution: update and reinstall usr.bin/xinstall
6671.42Sperry	Better Solution: Use the new toolchain and it will just work
6681.42Sperry	for you.
6691.40Slukem
6701.40Slukem20011006:
6711.40Slukem	/etc/mtree/NetBSD.dist has been updated to take advantage of
6721.40Slukem	absolute path support added to mtree(8). Older mtree(8)s don't
6731.40Slukem	understand the format.
6741.40Slukem
6751.40Slukem	Solution: update and reinstall usr.sbin/mtree
6761.39Sjmc
6771.39Sjmc20011004:
6781.39Sjmc	Crunchgen has been updated to work via reach-over makefiles. Updating
6791.39Sjmc	is suggested before running a snapshot build
6801.36Stv
6811.35Sthorpej20010915:
6821.35Sthorpej	The new "ubcperf" code committed by Chuck Silvers removed
6831.35Sthorpej	a header file, uvm/uvm_vnode.h.  There may be stale .depend
6841.35Sthorpej	files that still reference this file.
6851.35Sthorpej
6861.35Sthorpej	Solution: "make cleandir && make dependall" in affected
6871.35Sthorpej	directories.
6881.31Senami
6891.31Senami20010803:
6901.31Senami	grep.info is now built from grep.texi using makeinfo.  Since it
6911.31Senami	requires makeinfo v4.0, you need to install new texinfo before
6921.31Senami	building gnu/usr.bin/grep.  To install new texinfo, please follow
6931.31Senami	the instruction described in 20010726 entry.
6941.30Senami
6951.64Ssommerfe20010803: 
6961.41Swiz	(i386 only): i386 kernel now uses new instructions like
6971.111Ssimonb	`fxsave' which old gas doesn't understand.  To build the
6981.64Ssommerfe	kernel successfully, you need to build and install a new toolchain, 
6991.64Ssommerfe	(i.e., build.sh -t) or 	(temporarily) comment out "options I686_CPU" 
7001.64Ssommerfe	from your kernel configuration until you rebuild your userland.
7011.64Ssommerfe	See 20011029 above and BUILDING file in this directory for more information.
7021.64Ssommerfe	[updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled]
7031.29Sbjh21
7041.29Sbjh2120010731:
7051.29Sbjh21	Bootloader update on ELF platforms.  DDB in kernels from before
7061.29Sbjh21	this will be unable to read symbol tables provided by newer
7071.29Sbjh21	bootloaders.
7081.27Sassar
7091.27Sassar20010726:
7101.27Sassar	Texinfo was updated to 4.0.  To avoid failures when trying to
7111.28Sassar	build the included texinfo files, do:
7121.28Sassar
7131.28Sassar	cd src/gnu/usr.bin/texinfo
7141.28Sassar	make MKINFO=no dependall install
7151.25Sthorpej
7161.25Sthorpej20010718:
7171.25Sthorpej	Enabled correct .init/.fini processing in crt0.  The way this
7181.25Sthorpej	was done was to change a -I directive to cc(1), which means
7191.25Sthorpej	make(1) will have a stale dependency (it will be checking the
7201.25Sthorpej	timestamp on the wrong "dot_init.h").
7211.25Sthorpej
7221.25Sthorpej	The symptom you will see is that new programs die with SIGSEGV
7231.25Sthorpej	if you have a stale dependency.
7241.25Sthorpej
7251.25Sthorpej	Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so
7261.25Sthorpej	before starting your build.
7271.26Sthorpej
7281.26Sthorpej20010628:
7291.26Sthorpej	A construct was added to uvm_page.h that uncovered a bug
7301.26Sthorpej	in lint(1).  If you get a warning/error about a non-portable
7311.26Sthorpej	bitfield, update your lint(1) before proceeding.
7321.21Sjmc
7331.21Sjmc20010226:
7341.22Sjmc	Added named user/group to system. Need to hand add this in or builds
7351.21Sjmc	will break as mtree aborts early.
7361.21Sjmc
7371.21Sjmc	To work around add by hand:
7381.21Sjmc
7391.21Sjmc	named:*:14:
7401.21Sjmc
7411.22Sjmc	to /etc/group and add:
7421.22Sjmc
7431.22Sjmc	named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin
7441.22Sjmc
7451.22Sjmc	to master.passwd (use vipw for instance if doing by hand).
7461.22Sjmc
7471.22Sjmc	Now a make build should progress.
7481.18Sjmc
7491.18Sjmc20010219:
7501.52Swiz	get/setprogname() added. Any hostprogs that may use this will need
7511.111Ssimonb	to be bootstrapped manually until the host system is current.
7521.18Sjmc
7531.111Ssimonb	Known problems: sys/arch/macppc/stand/fixcoff
7541.19Scgd			usr.sbin/config (adding -DMAKE_BOOTSTRAP to
7551.19Scgd			  CFLAGS and rebuilding should work)
7561.20Sjmc			usr.sbin/mdsetimage - Build a static copy if
7571.111Ssimonb			  building a snapshot before fully bootstrapped.
7581.15Schristos
7591.15Schristos20010204:
7601.15Schristos	prepare the code to compile with stricter gcc flags. in
7611.15Schristos	particular start eliminating redundant declarations. Yacc
7621.15Schristos	needs to be installed before make build.
7631.10Schristos
7641.10Schristos20010114:
7651.10Schristos	introduce .if commands(target) in make(1). You need to
7661.10Schristos	bring everything up-to-date first, then without installing
7671.23Stron	anything make and install in usr.bin/make, then proceed
7681.10Schristos	with make build.
7691.9Ssommerfe
7701.9Ssommerfe20010101:
7711.9Ssommerfe	bsd.subdir.mk committed 20001230 had a bug which caused
7721.9Ssommerfe	afterinstall targets to run too soon; update again.
7731.8Ssommerfe
7741.8Ssommerfe20001230:
7751.8Ssommerfe	New share/mk files needed to support .WAIT in SUBDIR variables.
7761.8Ssommerfe	If you get make errors, 
7771.8Ssommerfe		(cd share/mk; make install)
7781.8Ssommerfe	Also, PRINTOBJDIR has changed and is now used more heavily.
7791.6Sad
7801.6Sad20001019:
7811.7Sad	The `ca' device driver has been replaced by `ld'; although the
7821.6Sad	major and minor numbers haven't changed, you should update your /dev
7831.6Sad	directory.
7841.1Sabs
7851.4Sitojun20000929:
7861.4Sitojun	The following make directives are obsoleted.
7871.4Sitojun	MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 
7881.4Sitojun	By default, RSA is built into libcrypto.  IDEA and RC5 will not be
7891.16Swiz	built into libcrypto.  By using MKCRYPTO_{RC5,IDEA}, you can build
7901.4Sitojun	additional library libcrypto_{idea,rc5}.
7911.1Sabs
7921.1Sabs
7931.1SabsHints for a more successful build:
7941.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7951.123Sjmc    Use build.sh, but do not use its "expert mode":
7961.132Sjmmv	This will automatically build the tools in the
7971.123Sjmc	   correct order, and it will keep the tools and the
7981.123Sjmc	   new build products from interfering with the running
7991.123Sjmc	   system.  This will allow you to ignore most of the
8001.123Sjmc	   other advice in this file.
8011.2Smrg    Build a new kernel first:
8021.2Smrg	This makes sure that any new system calls or features
8031.2Smrg	   expected by the new userland will be present.  This
8041.2Smrg	   helps to avoid critical errors when upgrading.
8051.1Sabs    Use object directories:
8061.1Sabs	This helps to keep stale object
8071.1Sabs	   files from polluting the build if a Makefile "forgets"
8081.1Sabs	   about one.  It also makes it easier to clean up after
8091.1Sabs	   a build.  It's also necessary if you want to use the
8101.1Sabs	   same source tree for multiple machines.
8111.123Sjmc	   To use object directories with build.sh:
8121.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
8131.123Sjmc	   To use object directories without using build.sh:
8141.1Sabs	    a) cd /usr/src ; make cleandir
8151.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
8161.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
8171.1Sabs	    d) cd /usr/src ; make build
8181.2Smrg	   Note that running "make obj" in a directory will create
8191.2Smrg	   in obj.$MACHINE directory.
8201.1Sabs    Build to a DESTDIR:
8211.123Sjmc	This helps to keep old installed files (especially libraries)
8221.123Sjmc	   from interfering with the new build.
8231.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
8241.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
8251.123Sjmc	   environment variable before running make build.  It should be
8261.123Sjmc	   set to the pathname of an initially empty directory.
8271.123Sjmc	   Problems: if you do not use build.sh, you might need to
8281.123Sjmc		update critical utilities without using DESTDIR since
8291.123Sjmc		nothing is executed from what is installed in DESTDIR.
8301.123Sjmc		(See critical utils, below.)
8311.1Sabs    Build often:
8321.1Sabs	This keeps critical utilities current enough to not choke
8331.1Sabs	on any other part of the source tree that depends on up to
8341.123Sjmc	date functionality.  If you use build.sh, you should not have
8351.123Sjmc	this problem.
8361.1Sabs 
8371.1SabsWhat to do if things don't work:
8381.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8391.1SabsWhen things don't work there is usually a few things that commonly
8401.1Sabsshould be done.
8411.1Sabs    1)	make includes
8421.1Sabs	This should be done automatically by make build.
8431.1Sabs    2)  cd share/mk && make install
8441.1Sabs	Again, automatically done by make build.
8451.1Sabs
8461.1SabsFailsafe rebuild of a small part of the tree:
8471.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8481.1SabsTo make sure you rebuild something correctly you want to do
8491.1Sabssomething like the following:
8501.1Sabs    1)  Make sure the includes and .mk files are up to date.
8511.1Sabs    2)  Make sure any program used to build the particular
8521.1Sabs	utility is up to date.  (yacc, lex, etc...)
8531.1Sabs    3)  cd ...path/to/util...
8541.1Sabs	make cleandir
8551.1Sabs	rm ...all obj directories...
8561.1Sabs	make cleandir			# yes, again
8571.1Sabs	make obj
8581.1Sabs	make depend && make
8591.1Sabs
8601.1SabsFailsafe rebuild of the entire tree:
8611.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
8621.1SabsIf you really want to make sure the source tree is clean and
8631.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
8641.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
8651.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
8661.1Sabs
8671.1Sabs---cut here---
8681.1Sabs#!/bin/sh
8691.1Sabs. /etc/mk.conf
8701.1Sabs
8711.58Slukemif [ -z $NETBSDSRCDIR ] ; then
8721.58Slukem    NETBSDSRCDIR=/usr/src
8731.1Sabsfi
8741.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
8751.1Sabs    echo Unable to find sources
8761.1Sabs    exit 1
8771.1Sabsfi
8781.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
8791.1Sabs
8801.1Sabsif [ -z $BSDOBJDIR ] ; then
8811.1Sabs    BSDOBJDIR=/usr/obj
8821.1Sabsfi
8831.1Sabsif [ -d $BSDOBJDIR ] ; then
8841.1Sabs    rm -rf $BSDOBJDIR
8851.1Sabsfi
8861.1Sabs
8871.58Slukemcd $NETBSDSRCDIR && make cleandir
8881.1Sabs
8891.1Sabs---cut here---
8901.1Sabs
8911.1SabsCritical utilities:
8921.1Sabs^^^^^^^^^^^^^^^^^^^
8931.3Sitojun	usr.bin/compile_et
8941.1Sabs	usr.bin/make
8951.1Sabs	usr.bin/yacc
8961.1Sabs	usr.bin/lex
8971.11Slukem	usr.bin/xlint
8981.142Sdrochner	usr.bin/config
8991.1Sabs
9001.34SsimonbOther problems and possible solutions:
9011.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9021.1SabsSymptom:Complaints involving a Makefile.
9031.17SerhFix:	Rebuild usr.bin/make:
9041.17Serh	cd usr.bin/make && make && make install
9051.111Ssimonb	Or, a failsafe method if that doesn't work:
9061.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
9071.17Serh
9081.1SabsFix:	Make sure .mk files are up to date.
9091.1Sabs	cd share/mk && make install
9101.2Smrg
9111.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
9121.142SdrochnerFix:	Rebuild usr.bin/config
9131.1Sabs
9141.1SabsSymptom:
9151.1SabsFix:	Rebuild usr.bin/yacc
9161.1Sabs
9171.1SabsSymptom:
9181.1SabsFix:	Rebuild usr.bin/lex
9191.1Sabs
9201.1SabsSymptom:
9211.1SabsFix:	rm /usr/lib/libbfd.a
9221.4Sitojun
9231.4SitojunSymptom:Obsolete intermediate files are used during compilation
9241.4SitojunFix:	Try the following sequence of commands in the directory in question.
9251.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
9261.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
9271.4Sitojun	may remain.  The command tries to clean everything up)
9281.5Swiz
9291.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
9301.5SwizFix:	Rebuild and install usr.bin/menuc
9311.12Sitojun
9321.12SitojunSymptom:mklocale not found during build in share/locale/ctype
9331.12SitojunFix:	Build and install usr.bin/mklocale
9341.13Sdogcow
9351.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
9361.13SdogcowFix:    Rebuild and install lib/libc
9371.13Sdogcow
9381.142SdrochnerSymptom:usr.bin/config fails to build.
9391.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
9401.13Sdogcow
9411.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
9421.19ScgdFix:    Rebuild and install lib/libc
9431.24Sabs
9441.24SabsSymptom:lint does not understand the '-X' option
9451.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
946