UPDATING revision 1.129
11.129Sjmc$NetBSD: UPDATING,v 1.129 2004/10/12 04:03:20 jmc 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.99Smrg
191.129Sjmc20041006:
201.129Sjmc
211.129Sjmc	A bug was introduced into /bin/sh (var.c rev 1.35) which causes
221.129Sjmc	variables to not export correctly to subshells in all cases. This
231.129Sjmc	will cause builds to break if that version of /bin/sh is installed
241.129Sjmc	on the system. The proper version of /bin/sh can be verified with:
251.129Sjmc
261.129Sjmc        ident /bin/sh | grep var
271.129Sjmc
281.129Sjmc	Any /bin/sh w. version 1.35 will not work and needs to be updated
291.129Sjmc	before attempting a build.
301.129Sjmc	
311.127Schristos20041001:
321.127Schristos	The ipfilter kernel sources moved from sys/netinet to
331.127Schristos	dist/sys/ipf/netinet. Due to the move some Makefile
341.127Schristos	dependencies are now dangling requiring a make cleandir
351.128She	before they work again (kdump, ktruss, rescue, ipf, and
361.128She	ftp-proxy are the victims).
371.127Schristos
381.125Satatat20040715:
391.125Satatat	The rc.d/sendmail script now uses a heuristic to determine
401.125Satatat	if sendmail should be started at boot time.  It checks the
411.125Satatat	contents of /etc/mailer.conf, /etc/mail/submit.cf, and the
421.125Satatat	owner and mode of the sendmail binary to see if any changes
431.125Satatat	to the mail infrastructure have been made.  If no changes
441.125Satatat	are detected, it will start an SMTP listener.
451.125Satatat
461.125Satatat	Setting sendmail=NO in /etc/rc.conf will override this.
471.125Satatat
481.125Satatat	If you are only using sendmail by default and only for
491.125Satatat	local delivery, it is important that you also update your
501.125Satatat	sendmail.cf so that the SMTP listener only listens on the
511.125Satatat	loopback interface.
521.125Satatat
531.125Satatat20040715:
541.125Satatat	The method by which athhal-elf.o gets pulled into i386
551.125Satatat	kernel builds has been changed again.  The latest version
561.125Satatat	of bsd.files.mk is no longer required.
571.125Satatat
581.124Sjmc20040621:
591.124Sjmc	Due to the recent rototill of tools/compat it's crucial one starts
601.124Sjmc	from a clean objdir under tools/*.
611.124Sjmc
621.124Sjmc	This is mostly due to generated files (yacc and lex sources) needing
631.125Satatat	to be generated with new rules from bsd.hostprog.mk.
641.124Sjmc
651.124Sjmc	The safest course is to rm -rf all objects under tools before building.
661.124Sjmc
671.121Slukem20040516:
681.121Slukem	The end-user modifiable X11 configuration has been moved
691.121Slukem	from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>.
701.121Slukem	Ensure that src and xsrc is up to date, and run
711.121Slukem	"make cleandir" in src/x11 before your next build.
721.121Slukem
731.126Slukem	postinstall currently doesn't migrate the files from
741.126Slukem	/usr/X11R6/lib/X11/* to /etc/X11/* although it does
751.126Slukem	detect that this needs to occur, so you'll have to
761.126Slukem	manually move these files yourself.
771.126Slukem
781.119Satatat20040426:
791.119Satatat	Support for the original dynamic sysctl node structure has
801.119Satatat	been removed in favor of the newer layout.  This affects
811.119Satatat	consumers of the create and delete interface, as well as
821.119Satatat	the dynamic discovery mechanism.  This is believed only to
831.119Satatat	be the sysctl(8) binary itself, at this point in time, so
841.119Satatat	the only effect of this should be that a sysctl binary
851.119Satatat	built from sources dated between 2003/12/04 and 2004/03/24
861.119Satatat	will not work on a kernel built from sources dated after
871.119Satatat	2004/04/25.  If you need a new sysctl binary but build.sh
881.119Satatat	does not work, make sure that your revision of
891.120Satatat	src/sys/sys/sysctl.h is 1.112 (or later), and then the
901.120Satatat	do the following:
911.119Satatat
921.120Satatat	cd /usr/src (or wherever your source tree is)
931.120Satatat	make USETOOLS=no includes
941.120Satatat	cd lib/libc
951.120Satatat	make USETOOLS=no dependall install
961.120Satatat	cd ../../sbin/sysctl
971.119Satatat	make USETOOLS=no dependall install
981.119Satatat
991.122Sitojun	If you are using older sysctl binary, GNU autoconf would fail to
1001.122Sitojun	identify your machine architecture, and tries to build binary for
1011.122Sitojun	"unknown-unknown-netbsd20F" or something like that.  if that happens,
1021.122Sitojun	make sure to follow the above steps.
1031.122Sitojun
1041.118Sdbj20040425:
1051.118Sdbj	The ffs superblock issues listed below under 20040109 and 20030402
1061.118Sdbj	are now automatically addressed by the /etc/rc.d/fixsb script or by
1071.118Sdbj	sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4
1081.118Sdbj	invocation mentioned below will continue to work and is now
1091.118Sdbj	automated by those scripts.  Note that under certain circumstances,
1101.118Sdbj	affected filesystems upgraded to a -current kernel first before
1111.118Sdbj	upgrading their userland with the fixsb and fsck_ffs fixes may
1121.118Sdbj	encounter a 'freeing free inode' panic when writing to the affected
1131.118Sdbj	filesystem, so it is a good idea to repair the filesystem as soon as
1141.118Sdbj	possible.  For more details on the fixsb script, see pr install/25138.
1151.118Sdbj
1161.115Schristos20040418:
1171.121Slukem	statfs(2) and friends have been replaced with statvfs(2). Before
1181.115Schristos	installing a newly build userland make sure that you are running
1191.115Schristos	a newly built kernel with COMPAT_20 set. In addition your libc
1201.115Schristos	build might not work (undefined SYS_statfs symbol) because make
1211.115Schristos	clean does not know how to remove files it does not know about
1221.116Schristos	anymore. Manually remove all generated .S sources and objects
1231.116Schristos	from the libc build directory.
1241.115Schristos
1251.114Sjmc20040326:
1261.114Sjmc	The method by which athhal-elf.o gets pulled into i386 kernel builds
1271.117Sjmc	has been changed. The file is now stored as a uuencoded file in CVS
1281.114Sjmc	and the generated Makefile will use the new .uue rules from bsd.file.mk
1291.114Sjmc	to build it.
1301.114Sjmc
1311.114Sjmc	This means you must have the latest bsd.files.mk installed when
1321.114Sjmc	building a kernel without USETOOLS=yes.
1331.114Sjmc
1341.113Sdan20040318:
1351.113Sdan	A bug in the cgd(4) blowfish code was corrected, without
1361.113Sdan	provision of backwards compatibility, after several public
1371.113Sdan	notices over several months. Users of cgd with blowfish cipher
1381.113Sdan	ONLY must dump their data before updating their kernels, and
1391.113Sdan	recreate cgd's and restore data using the new kernel. See
1401.113Sdan	(recent message to current-users, URL when mail-index has updated)
1411.113Sdan
1421.108Sbjh2120040313:
1431.108Sbjh21	On acorn32, the opms and qms drivers have been withdrawn, and
1441.108Sbjh21	the old wsqms driver is now called qms.  Kernel config files
1451.108Sbjh21	will need updating.  See the ones in sys/arch/acorn32/conf
1461.108Sbjh21	for examples.
1471.108Sbjh21
1481.106Sbjh2120040125:
1491.106Sbjh21	On acorn32, the beep and sysbeep devices are no longer
1501.106Sbjh21	needed, and will need to be deleted from kernel configuration
1511.106Sbjh21	files.
1521.105Sbjh21
1531.102Sdbj20040109:
1541.102Sdbj	Compatibility for old ffs superblock layouts has been
1551.102Sdbj	added, and the restrictive fsck checks have been reenabled
1561.102Sdbj	when using those layouts.  If you have been using -current
1571.102Sdbj	since 20030402, you may find that fsck again signals fatal
1581.110Sdbj	superblock mismatches.  To repair, make sure you have
1591.111Ssimonb	an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4
1601.109Sdbj	to complete the filesystem upgrade.  A message has
1611.111Ssimonb	been added to the kernel which should detect this problem.
1621.111Ssimonb	See the following discussion for more information:
1631.112Skeihan	http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html
1641.102Sdbj
1651.99Smrg20031203:
1661.100Skeihan	New binutils builds may fail due to old dependencies.
1671.99Smrg	It's necessary to "make cleandir" to ensure that
1681.99Smrg	the dependencies will be rebuilt correctly.
1691.98Swiz
1701.98Swiz20031111:
1711.98Swiz	A newer mkdep is needed.  Error noting that is
1721.98Swiz		cc: Ambiguous abbreviation --
1731.97Slukem
1741.97Slukem20031008:
1751.97Slukem	/usr/include/sys/disklabel_mbr.h was removed.
1761.97Slukem	It's necessary to "make cleandir" to ensure that
1771.97Slukem	the dependencies will be rebuilt correctly.
1781.96Schristos
1791.109Sdbj20031007:
1801.111Ssimonb	A sign exension bug was fixed which set all the high bits
1811.111Ssimonb	of our newly expanded ffs fs_flags.  This should only
1821.111Ssimonb	affect users who installed or upgraded in September of 2003.
1831.109Sdbj	A small utility program was posted to tech-kern which
1841.111Ssimonb	should fix this problem, and a warning message was added
1851.111Ssimonb	to the kernel which should discover and warn about it.  See
1861.111Ssimonb	http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html
1871.109Sdbj
1881.96Schristos20030906:
1891.96Schristos	With the addition of siginfo support the old signal trampoline
1901.96Schristos	code has been deprecated to COMPAT_16. Make sure that your running
1911.96Schristos	kernel has COMPAT_16 enabled before building userland.
1921.94Schristos
1931.94Schristos20030801:
1941.95Swiz	With the new openssl, there is some header and library shuffling.
1951.94Schristos	rm -f /usr/include/des.h /usr/include/kerberosIV/* /lib/libdes* \
1961.95Swiz	/usr/lib/libdes* before building.
1971.92Swiz
1981.92Swiz20030703:
1991.92Swiz	Texinfo was updated to 4.6.  To avoid failures when trying to
2001.92Swiz	build the included texinfo files, do:
2011.92Swiz
2021.92Swiz	cd src/gnu/usr.bin/texinfo
2031.92Swiz	make MKINFO=no dependall install
2041.90Swiz
2051.90Swiz20030630:
2061.101Sjunyoung	Groff was updated to 1.19; it's probably necessary to do
2071.91Swiz		cd share/mk && make install
2081.90Swiz		cd src/gnu/usr.bin/groff
2091.90Swiz		make MKMAN=no dependall install
2101.90Swiz	(untested).
2111.89Schristos
2121.89Schristos20030516:
2131.89Schristos	Due to bugs in the export handling code, invalid export lines
2141.89Schristos	were accepted before and caused the kernel to panic when
2151.89Schristos	mountd got restarted because it freed memory that had already
2161.89Schristos	been freed. This has been fixed and the kernel checks
2171.89Schristos	export addresses very strictly. If you upgrade your kernel,
2181.89Schristos	make sure you also upgrade mountd, because if your export
2191.89Schristos	file contains lines with an old inet4 address syntax (i.e.
2201.89Schristos	a.b.c or a.b or a), they will get rejected by the new kernel.
2211.87Sbjh21
2221.87Sbjh2120030402:
2231.87Sbjh21	The superblock layout for FFS was changed.  If you have 1.6
2241.87Sbjh21	fsck binaries, they will signal a fatal superblock mismatch
2251.87Sbjh21	with the first alternate, because they compare too many
2261.87Sbjh21	fields (even ones that aren't useful).  If possible, upgrade
2271.87Sbjh21	your fsck_ffs binary before using a new kernel.
2281.87Sbjh21	None of this signals actual filesystem damage.
2291.85Satatat
2301.85Satatat20030324:
2311.85Satatat	sendmail version 8.12.8 was imported.  Since sendmail is
2321.85Satatat	now setgid to the smmsp group, and runs in "collection"
2331.85Satatat	mode for most common activities, there is a new config
2341.85Satatat	file called submit.cf that needs to live in /etc/mail.
2351.85Satatat	The generic submit.cf sample in /usr/share/sendmail/cf
2361.85Satatat	is named netbsd-msp.cf.  Upgrading your regular sendmail
2371.85Satatat	configuration file is also strongly advised.
2381.85Satatat
2391.85Satatat	See the section named "MESSAGE SUBMISSION PROGRAM" in
2401.85Satatat	the updated /usr/share/sendmail/README file for more
2411.85Satatat	information.
2421.82Swiz
2431.82Swiz20030117:
2441.82Swiz	Texinfo was updated to 4.3.  To avoid failures when trying to
2451.82Swiz	build the included texinfo files, do:
2461.82Swiz
2471.82Swiz	cd src/gnu/usr.bin/texinfo
2481.82Swiz	make MKINFO=no dependall install
2491.81Slukem
2501.81Slukem20021223:
2511.81Slukem	The METALOG format changed slightly, to remove the leading
2521.81Slukem	"${DESTDIR}" from path names.
2531.81Slukem	This only affects people building with UNPRIVED.
2541.81Slukem	For complete safety, remove the DESTDIR entirely and
2551.81Slukem	update tools/mtree, before running make build.
2561.88Sitojun
2571.88Sitojun20021219:
2581.88Sitojun	CVS repository layout was changed.  See the following for details
2591.88Sitojun	if you are using (anonymous) cvs to update your tree.
2601.88Sitojun
2611.93Ssalo	http://mail-index.NetBSD.org/netbsd-announce/2002/12/19/0000.html
2621.80Slukem
2631.80Slukem20021219:
2641.80Slukem	install(1) had a '-N dbdir' option added, to specify an
2651.80Slukem	alternate location to look up users & groups (instead
2661.80Slukem	of the host system passwd(5) and group(5) databases).
2671.80Slukem
2681.80Slukem	The build system was modified to take advantage of
2691.80Slukem	this option (using ${NETBSDSRCDIR}/etc), so if you
2701.83Skei	use USETOOLS==no, you may have to rebuild and
2711.80Slukem	reinstall usr.bin/xinstall first.
2721.78Slukem
2731.78Slukem20021130:
2741.78Slukem	fparseln(3) moved from libutil to libc.
2751.78Slukem	If building to DESTDIR=/, reinstall the includes
2761.78Slukem	and rebuild libc:
2771.78Slukem		make includes
2781.78Slukem		make do-lib-libc
2791.78Slukem	If using build.sh, "cd tools/compat && make clean"
2801.78Slukem	before rebuilding the tools.
2811.77Slukem
2821.77Slukem20021126:
2831.77Slukem	The mk.conf(5) variable SYS_INCLUDE has been deprecated,
2841.77Slukem	including the optional "SYS_INCLUDE=symlinks" support.
2851.77Slukem	All header files, including <sys/*.h> are copied into
2861.77Slukem	/usr/include.
2871.76Sthorpej
2881.76Sthorpej20021121:
2891.76Sthorpej	The C run-time support files crtbegin.o and crtend.o
2901.76Sthorpej	(and their companions crtbeginS.o and crtendS.o) were
2911.76Sthorpej	split up, with new crti.o and crtn.o files resulting.
2921.76Sthorpej	This means that libtool needs to be rebuilt once the
2931.76Sthorpej	new libraries are installed.  The process of rebuilding
2941.76Sthorpej	libtool will cause it to automatically notice the new
2951.76Sthorpej	required files, but it *must* be rebuilt in order to
2961.76Sthorpej	do this.
2971.76Sthorpej
2981.76Sthorpej	An out-of-date libtool will result in shared libraries
2991.76Sthorpej	which lack _init() and _fini() routines, which means that
3001.76Sthorpej	their global contructors/destructors will not be invoked.
3011.75Sthorpej
3021.75Sthorpej20021121:
3031.75Sthorpej	A bug related to how ARM ELF objects were tagged has been
3041.75Sthorpej	corrected.
3051.75Sthorpej
3061.75Sthorpej	NetBSD ARM ELF uses the soft-VFP floating point model by
3071.75Sthorpej	default.  However, the assembler lacked support for marking
3081.75Sthorpej	objects as using the VFP floating point format, and the
3091.79Swiz	compiler was not properly passing the flag indicating "soft-VFP"
3101.75Sthorpej	to the assembler.
3111.75Sthorpej
3121.75Sthorpej	Unfortunately, this means that the linker will now consider
3131.75Sthorpej	old (i.e. not marked "softvfp") NetBSD ARM ELF objects to be
3141.75Sthorpej	incompatible with new (properly marked) objects.
3151.75Sthorpej
3161.75Sthorpej	The problem will only manifest itself if you attempt to compile
3171.75Sthorpej	a new program using the fixed toolchain, and link that program
3181.75Sthorpej	against old libraries which do not have the proper "softvfp"
3191.75Sthorpej	markings.  ALL OF YOUR EXISTING BINARIES AND SHARED LIBRARIES
3201.75Sthorpej	WILL CONTINUE TO WORK PROPERLY.
3211.75Sthorpej
3221.75Sthorpej	The only work-around for the problem is to recompile all of
3231.75Sthorpej	the libraries on the system.  The easiest way to do this for
3241.79Swiz	system libraries is to install a binary snapshot; they are
3251.93Ssalo	generally available on releng.NetBSD.org.  Any packages you
3261.75Sthorpej	have installed which supply libraries will have to be recompiled
3271.75Sthorpej	if you wish to link new programs against those libraries.
3281.75Sthorpej
3291.75Sthorpej	If you have questions about this matter, please contact
3301.93Ssalo	port-arm@NetBSD.org.
3311.73Sprovos
3321.73Sprovos20021011:
3331.73Sprovos	Systrace has been improved to support privilege elevation.
3341.73Sprovos	Updating the kernel requires the userland part of systrace
3351.79Swiz	to be rebuilt.
3361.72Sthorpej
3371.72Sthorpej20021010:
3381.72Sthorpej	The config(8) grammar was changed to allow options to register
3391.72Sthorpej	dependencies on attributes, as well as other options.  Users
3401.72Sthorpej	must update and reinstall usr.sbin/config before building a new
3411.72Sthorpej	kernel.
3421.70Sthorpej
3431.70Sthorpej20021009:
3441.70Sthorpej	A new attribute dependency syntax was introduced to config(8),
3451.70Sthorpej	which is now used by the SCSI configuration description.  Users
3461.71Swiz	must update and reinstall usr.sbin/config before building a new
3471.70Sthorpej	kernel.
3481.69Sthorpej
3491.69Sthorpej20021003:
3501.69Sthorpej	Several changes have been made to the autoconfiguration
3511.69Sthorpej	framework.  Users must update and reinstall usr.sbin/config
3521.69Sthorpej	before building a new kernel.
3531.74Sjschauma
3541.74Sjschauma20021001:
3551.74Sjschauma	The i386mp branch has been merged.  To compile a kernel, users
3561.74Sjschauma	will need to add the option 'cpu* at mainbus?' to their configuration
3571.74Sjschauma	file.  Multiprocessor kernels will need
3581.74Sjschauma	ioapic*		at mainbus? apid ?
3591.74Sjschauma	options		MULTIPROCESSOR
3601.74Sjschauma	options		COM_MPLOCK
3611.68Slukem
3621.68Slukem20020922:
3631.68Slukem	MKDYNAMICROOT=yes enabled by default, which means that
3641.68Slukem	certain shared libraries are installed into /lib, the shared
3651.68Slukem	linker is installed into /libexec, and all programs in /bin
3661.68Slukem	and /sbin are dynamically linked.
3671.68Slukem	If you do not use "make build", you should ensure that
3681.68Slukem	you have the libraries and shared linker in the new locations,
3691.68Slukem	with:
3701.68Slukem		make do-lib-csu do-lib-libc do-lib do-gnu-lib do-ld.elf_so
3711.67Slukem
3721.67Slukem20020917:
3731.67Slukem	USE_NEW_TOOLCHAIN has been replaced with:
3741.67Slukem	    -	TOOLCHAIN_MISSING -- set to "yes" on platforms for which
3751.67Slukem		there is no working in-tree toolchain (hppa, ns32k, sh5,
3761.67Slukem		x86_64).
3771.67Slukem	    -	EXTERNAL_TOOLCHAIN -- if defined by the user, points to the
3781.79Swiz		root of an external toolchain (e.g. /usr/local/gnu).  This
3791.67Slukem		enables the cross-build framework even for TOOLCHAIN_MISSING
3801.67Slukem		platforms.
3811.66Sgehenna
3821.66Sgehenna20020906:
3831.66Sgehenna	gehenna-devsw has been merged into the trunk. Need to update and
3841.79Swiz	reinstall usr.sbin/config before building the kernel.
3851.65Slukem
3861.65Slukem20020822:
3871.65Slukem	Crunched rescue tools (contents of /bin and /sbin, plus others)
3881.65Slukem	are now provided in /rescue.
3891.65Slukem
3901.65Slukem	To ensure that these are built statically linked (no matter
3911.65Slukem	what the setting of LDSTATIC is), use a crunchgen(1) built
3921.65Slukem	from sources newer than 20020820 (see the next entry).
3931.65Slukem
3941.65Slukem20020820:
3951.65Slukem	crunchgen(1) changed to ensure that the generated program
3961.65Slukem	is statically linked.
3971.65Slukem
3981.65Slukem	Solution: update and reinstall usr.bin/crunch
3991.84Sgrant
4001.84Sgrant20020605:
4011.84Sgrant	smmsp user/group has been added for sendmail.
4021.84Sgrant
4031.84Sgrant	Add the following into /etc/group:
4041.84Sgrant
4051.84Sgrant	smmsp:*:17:
4061.84Sgrant
4071.84Sgrant	and the following to /etc/master.passwd (via vipw):
4081.84Sgrant
4091.84Sgrant	smmsp:*:17:17::0:0:Sendmail Message Submission Program:/nonexistent:/sbin/nologin
4101.61Sitojun
4111.61Sitojun20020515:
4121.61Sitojun	sshd user/group has been added.  Need to hand add this in, or sshd
4131.61Sitojun	will not let you log in (with default, or UsePrivlegeSeparation=yes)
4141.61Sitojun
4151.61Sitojun	Add the following into /etc/group:
4161.61Sitojun
4171.61Sitojun	sshd:*:16:
4181.61Sitojun
4191.61Sitojun	and the following to /etc/master.passwd (via vipw):
4201.61Sitojun
4211.63Senami	sshd:*:16:16::0:0:& pseudo-user:/var/chroot/sshd:/sbin/nologin
4221.61Sitojun	
4231.79Swiz	Also /var/chroot/sshd directory needs to be present (digged as part of
4241.79Swiz	the build process).
4251.60Ssommerfe
4261.60Ssommerfe20020426:
4271.60Ssommerfe	NBUILDJOBS obsoleted in favor of just using -j.
4281.59Slukem
4291.59Slukem20020426:
4301.59Slukem	etc/postinstall added, which performs various checks for 
4311.59Slukem	configuration file updates and changes, and can fix most of
4321.59Slukem	the problems identified.
4331.59Slukem	This should make it much easier to upgrade a system's
4341.59Slukem	configuration from earlier systems (as far back as NetBSD 1.5).
4351.56Slukem
4361.56Slukem20020320:
4371.79Swiz	<bsd.lib.mk> needs a new install(1) for its "-a cmd" support.
4381.79Swiz	Build and install at usr.bin/xinstall before the build.
4391.56Slukem
4401.55Sitojun20020319:
4411.79Swiz	Raw IPv6 socket now makes strict checking for sa_family and sa_len
4421.79Swiz	on send(2) operation.  Be sure to have sbin/rtsol and usr.sbin/rtsold
4431.55Sitojun	newer than November 2001 when you upgrade the kernel.
4441.55Sitojun
4451.54Sitojun20020311:
4461.54Sitojun	ssh configuration files were moved from /etc to /etc/ssh.  Beware
4471.54Sitojun	if you restart your machine from remote.  Note that sshd.conf needs
4481.54Sitojun	to be changed (due to the use of "/etc" inside).
4491.54Sitojun
4501.54Sitojun20020223:
4511.53Smatt	Users of the VAX port will need to rebuild and install gas
4521.53Smatt	so it deal with the now present register prefix used in all
4531.53Smatt	the VAX assembly files.
4541.53Smatt
4551.50Sitojun20020118:
4561.50Sitojun	ntpd user/group has been added.  Need to hand add this in or builds
4571.50Sitojun	will break as mtree aborts early.
4581.50Sitojun
4591.50Sitojun	Add the following into /etc/group:
4601.50Sitojun
4611.50Sitojun	ntpd:*:15:
4621.50Sitojun
4631.50Sitojun	and the following to /etc/master.passwd (via vipw):
4641.50Sitojun
4651.50Sitojun	ntpd:*:15:15::0:0:Ntpd pseudo-user:/var/chroot/ntpd:/sbin/nologin
4661.50Sitojun
4671.49Sjmc20011207:
4681.49Sjmc	If you're attempting to build a snapshot on sparc64 and are getting
4691.49Sjmc	reloc errors from the toolchain groff binary this means your native
4701.49Sjmc	toolchain has some broken C++ bits.
4711.49Sjmc
4721.49Sjmc	To fix:
4731.49Sjmc
4741.49Sjmc	Build a new toolchain (i.e. build.sh -t)
4751.49Sjmc	Use the new toolchain to build and install natively (i.e. /usr/lib)
4761.49Sjmc
4771.49Sjmc	gnu/lib/libgcc
4781.51Spooka	gnu/lib/libstdc++
4791.49Sjmc
4801.49Sjmc	After this a snapshot will be able to be built.
4811.49Sjmc
4821.47Sjmc20011201:
4831.47Sjmc	In order for a sparc64 build to work you must have a working awk. If
4841.47Sjmc	you've built and installed a system with the new toolchain up to this
4851.52Swiz	point you do not have a working awk as its ability to do floating
4861.47Sjmc	point is broken. 
4871.47Sjmc
4881.47Sjmc	To build:
4891.47Sjmc
4901.47Sjmc	remake and install gnu/lib/libgcc
4911.47Sjmc	remake and install gnu/usr.bin/gawk into /usr/bin (make sure it links
4921.48Sjmc	against the new libgcc.a)
4931.47Sjmc
4941.46Sthorpej20011128:
4951.46Sthorpej	Kernel config information was changed to use defflag in
4961.46Sthorpej	the various "files" files.  Bug fixes to config(8) are
4971.46Sthorpej	required in order for this to work properly.  Make sure
4981.46Sthorpej	to build and install in usr.sbin/config before attempting
4991.46Sthorpej	to build a new kernel.
5001.46Sthorpej
5011.45Syamt20011030:
5021.45Syamt	libc/locale/wcstod.c now needs new lint(1). Update lint(1)
5031.45Syamt	before building libc.
5041.43Smason
5051.44Stv20011029:
5061.44Stv	The new document BUILDING.mdoc (view with nroff | more, or
5071.44Stv	see pre-generated .txt and .html versions) describes the build
5081.44Stv	procedure in great detail.  BUILDING, and the USE_NEW_TOOLCHAIN
5091.44Stv	build process, are intended in the long run to replace this
5101.44Stv	manual update log.
5111.44Stv
5121.44Stv	Users building a USE_NEW_TOOLCHAIN system should read the
5131.44Stv	BUILDING document for caveats.  Generally, BUILDING supersedes
5141.44Stv	UPDATING for these systems, as tool updating is taken care of
5151.44Stv	by the new build system.
5161.42Sperry
5171.42Sperry20011028:
5181.42Sperry	src/etc/Makefile now needs install to be able to handle
5191.42Sperry	symlinks that point to nowhere. A bug in install that
5201.42Sperry	prevented this was corrected.
5211.42Sperry
5221.42Sperry	Solution: update and reinstall usr.bin/xinstall
5231.42Sperry	Better Solution: Use the new toolchain and it will just work
5241.42Sperry	for you.
5251.40Slukem
5261.40Slukem20011006:
5271.40Slukem	/etc/mtree/NetBSD.dist has been updated to take advantage of
5281.40Slukem	absolute path support added to mtree(8). Older mtree(8)s don't
5291.40Slukem	understand the format.
5301.40Slukem
5311.40Slukem	Solution: update and reinstall usr.sbin/mtree
5321.39Sjmc
5331.39Sjmc20011004:
5341.39Sjmc	Crunchgen has been updated to work via reach-over makefiles. Updating
5351.39Sjmc	is suggested before running a snapshot build
5361.36Stv
5371.35Sthorpej20010915:
5381.35Sthorpej	The new "ubcperf" code committed by Chuck Silvers removed
5391.35Sthorpej	a header file, uvm/uvm_vnode.h.  There may be stale .depend
5401.35Sthorpej	files that still reference this file.
5411.35Sthorpej
5421.35Sthorpej	Solution: "make cleandir && make dependall" in affected
5431.35Sthorpej	directories.
5441.31Senami
5451.31Senami20010803:
5461.31Senami	grep.info is now built from grep.texi using makeinfo.  Since it
5471.31Senami	requires makeinfo v4.0, you need to install new texinfo before
5481.31Senami	building gnu/usr.bin/grep.  To install new texinfo, please follow
5491.31Senami	the instruction described in 20010726 entry.
5501.30Senami
5511.64Ssommerfe20010803: 
5521.41Swiz	(i386 only): i386 kernel now uses new instructions like
5531.111Ssimonb	`fxsave' which old gas doesn't understand.  To build the
5541.64Ssommerfe	kernel successfully, you need to build and install a new toolchain, 
5551.64Ssommerfe	(i.e., build.sh -t) or 	(temporarily) comment out "options I686_CPU" 
5561.64Ssommerfe	from your kernel configuration until you rebuild your userland.
5571.64Ssommerfe	See 20011029 above and BUILDING file in this directory for more information.
5581.64Ssommerfe	[updated 20020630 since i386 gas moved when USE_NEW_TOOLCHAIN enabled]
5591.29Sbjh21
5601.29Sbjh2120010731:
5611.29Sbjh21	Bootloader update on ELF platforms.  DDB in kernels from before
5621.29Sbjh21	this will be unable to read symbol tables provided by newer
5631.29Sbjh21	bootloaders.
5641.27Sassar
5651.27Sassar20010726:
5661.27Sassar	Texinfo was updated to 4.0.  To avoid failures when trying to
5671.28Sassar	build the included texinfo files, do:
5681.28Sassar
5691.28Sassar	cd src/gnu/usr.bin/texinfo
5701.28Sassar	make MKINFO=no dependall install
5711.25Sthorpej
5721.25Sthorpej20010718:
5731.25Sthorpej	Enabled correct .init/.fini processing in crt0.  The way this
5741.25Sthorpej	was done was to change a -I directive to cc(1), which means
5751.25Sthorpej	make(1) will have a stale dependency (it will be checking the
5761.25Sthorpej	timestamp on the wrong "dot_init.h").
5771.25Sthorpej
5781.25Sthorpej	The symptom you will see is that new programs die with SIGSEGV
5791.25Sthorpej	if you have a stale dependency.
5801.25Sthorpej
5811.25Sthorpej	Solution: "make cleandir" in both lib/csu and libexec/ld.elf_so
5821.25Sthorpej	before starting your build.
5831.26Sthorpej
5841.26Sthorpej20010628:
5851.26Sthorpej	A construct was added to uvm_page.h that uncovered a bug
5861.26Sthorpej	in lint(1).  If you get a warning/error about a non-portable
5871.26Sthorpej	bitfield, update your lint(1) before proceeding.
5881.21Sjmc
5891.21Sjmc20010226:
5901.22Sjmc	Added named user/group to system. Need to hand add this in or builds
5911.21Sjmc	will break as mtree aborts early.
5921.21Sjmc
5931.21Sjmc	To work around add by hand:
5941.21Sjmc
5951.21Sjmc	named:*:14:
5961.21Sjmc
5971.22Sjmc	to /etc/group and add:
5981.22Sjmc
5991.22Sjmc	named:*:14:14::0:0:Named pseudo-user:/var/named:/sbin/nologin
6001.22Sjmc
6011.22Sjmc	to master.passwd (use vipw for instance if doing by hand).
6021.22Sjmc
6031.22Sjmc	Now a make build should progress.
6041.18Sjmc
6051.18Sjmc20010219:
6061.52Swiz	get/setprogname() added. Any hostprogs that may use this will need
6071.111Ssimonb	to be bootstrapped manually until the host system is current.
6081.18Sjmc
6091.111Ssimonb	Known problems: sys/arch/macppc/stand/fixcoff
6101.19Scgd			usr.sbin/config (adding -DMAKE_BOOTSTRAP to
6111.19Scgd			  CFLAGS and rebuilding should work)
6121.20Sjmc			usr.sbin/mdsetimage - Build a static copy if
6131.111Ssimonb			  building a snapshot before fully bootstrapped.
6141.15Schristos
6151.15Schristos20010204:
6161.15Schristos	prepare the code to compile with stricter gcc flags. in
6171.15Schristos	particular start eliminating redundant declarations. Yacc
6181.15Schristos	needs to be installed before make build.
6191.10Schristos
6201.10Schristos20010114:
6211.10Schristos	introduce .if commands(target) in make(1). You need to
6221.10Schristos	bring everything up-to-date first, then without installing
6231.23Stron	anything make and install in usr.bin/make, then proceed
6241.10Schristos	with make build.
6251.9Ssommerfe
6261.9Ssommerfe20010101:
6271.9Ssommerfe	bsd.subdir.mk committed 20001230 had a bug which caused
6281.9Ssommerfe	afterinstall targets to run too soon; update again.
6291.8Ssommerfe
6301.8Ssommerfe20001230:
6311.8Ssommerfe	New share/mk files needed to support .WAIT in SUBDIR variables.
6321.8Ssommerfe	If you get make errors, 
6331.8Ssommerfe		(cd share/mk; make install)
6341.8Ssommerfe	Also, PRINTOBJDIR has changed and is now used more heavily.
6351.6Sad
6361.6Sad20001019:
6371.7Sad	The `ca' device driver has been replaced by `ld'; although the
6381.6Sad	major and minor numbers haven't changed, you should update your /dev
6391.6Sad	directory.
6401.1Sabs
6411.4Sitojun20000929:
6421.4Sitojun	The following make directives are obsoleted.
6431.4Sitojun	MKCRYPTO_RSA NOCRYPTO_RSA NOCRYPTO_RC5 NOCRYPTO_IDEA 
6441.4Sitojun	By default, RSA is built into libcrypto.  IDEA and RC5 will not be
6451.16Swiz	built into libcrypto.  By using MKCRYPTO_{RC5,IDEA}, you can build
6461.4Sitojun	additional library libcrypto_{idea,rc5}.
6471.1Sabs
6481.1Sabs
6491.1SabsHints for a more successful build:
6501.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6511.123Sjmc    Use build.sh, but do not use its "expert mode":
6521.123Sjmc	This will will automatically build the tools in the
6531.123Sjmc	   correct order, and it will keep the tools and the
6541.123Sjmc	   new build products from interfering with the running
6551.123Sjmc	   system.  This will allow you to ignore most of the
6561.123Sjmc	   other advice in this file.
6571.2Smrg    Build a new kernel first:
6581.2Smrg	This makes sure that any new system calls or features
6591.2Smrg	   expected by the new userland will be present.  This
6601.2Smrg	   helps to avoid critical errors when upgrading.
6611.1Sabs    Use object directories:
6621.1Sabs	This helps to keep stale object
6631.1Sabs	   files from polluting the build if a Makefile "forgets"
6641.1Sabs	   about one.  It also makes it easier to clean up after
6651.1Sabs	   a build.  It's also necessary if you want to use the
6661.1Sabs	   same source tree for multiple machines.
6671.123Sjmc	   To use object directories with build.sh:
6681.123Sjmc	    a) invoke build.sh with the "-M" or "-O" options.
6691.123Sjmc	   To use object directories without using build.sh:
6701.1Sabs	    a) cd /usr/src ; make cleandir
6711.2Smrg	    b) Add "OBJMACHINE=yes" to /etc/mk.conf
6721.2Smrg	    c) Add "MKOBJDIRS=yes" to /etc/mk.conf
6731.1Sabs	    d) cd /usr/src ; make build
6741.2Smrg	   Note that running "make obj" in a directory will create
6751.2Smrg	   in obj.$MACHINE directory.
6761.1Sabs    Build to a DESTDIR:
6771.123Sjmc	This helps to keep old installed files (especially libraries)
6781.123Sjmc	   from interfering with the new build.
6791.123Sjmc	   To build to a DESTDIR with build.sh, use the "-D" option.
6801.123Sjmc	   To build to a DESTDIR without using build.sh, set the DESTDIR
6811.123Sjmc	   environment variable before running make build.  It should be
6821.123Sjmc	   set to the pathname of an initially empty directory.
6831.123Sjmc	   Problems: if you do not use build.sh, you might need to
6841.123Sjmc		update critical utilities without using DESTDIR since
6851.123Sjmc		nothing is executed from what is installed in DESTDIR.
6861.123Sjmc		(See critical utils, below.)
6871.1Sabs    Build often:
6881.1Sabs	This keeps critical utilities current enough to not choke
6891.1Sabs	on any other part of the source tree that depends on up to
6901.123Sjmc	date functionality.  If you use build.sh, you should not have
6911.123Sjmc	this problem.
6921.1Sabs 
6931.1SabsWhat to do if things don't work:
6941.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6951.1SabsWhen things don't work there is usually a few things that commonly
6961.1Sabsshould be done.
6971.1Sabs    1)	make includes
6981.1Sabs	This should be done automatically by make build.
6991.1Sabs    2)  cd share/mk && make install
7001.1Sabs	Again, automatically done by make build.
7011.1Sabs
7021.1SabsFailsafe rebuild of a small part of the tree:
7031.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7041.1SabsTo make sure you rebuild something correctly you want to do
7051.1Sabssomething like the following:
7061.1Sabs    1)  Make sure the includes and .mk files are up to date.
7071.1Sabs    2)  Make sure any program used to build the particular
7081.1Sabs	utility is up to date.  (yacc, lex, etc...)
7091.1Sabs    3)  cd ...path/to/util...
7101.1Sabs	make cleandir
7111.1Sabs	rm ...all obj directories...
7121.1Sabs	make cleandir			# yes, again
7131.1Sabs	make obj
7141.1Sabs	make depend && make
7151.1Sabs
7161.1SabsFailsafe rebuild of the entire tree:
7171.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7181.1SabsIf you really want to make sure the source tree is clean and
7191.2Smrgready for a build try the following.  Note that sourcing /etc/mk.conf
7201.2Smrg(a make(1) Makefile) in this manner is not right, and will not work
7211.2Smrgfor anyone who uses any make(1) features in /etc/mk.conf.
7221.1Sabs
7231.1Sabs---cut here---
7241.1Sabs#!/bin/sh
7251.1Sabs. /etc/mk.conf
7261.1Sabs
7271.58Slukemif [ -z $NETBSDSRCDIR ] ; then
7281.58Slukem    NETBSDSRCDIR=/usr/src
7291.1Sabsfi
7301.58Slukemif [ \! -d $NETBSDSRCDIR ] ; then
7311.1Sabs    echo Unable to find sources
7321.1Sabs    exit 1
7331.1Sabsfi
7341.58Slukemfind $NETBSDSRCDIR -name \*.o -o -name obj.\* -o -name obj -exec rm \{\} \;
7351.1Sabs
7361.1Sabsif [ -z $BSDOBJDIR ] ; then
7371.1Sabs    BSDOBJDIR=/usr/obj
7381.1Sabsfi
7391.1Sabsif [ -d $BSDOBJDIR ] ; then
7401.1Sabs    rm -rf $BSDOBJDIR
7411.1Sabsfi
7421.1Sabs
7431.58Slukemcd $NETBSDSRCDIR && make cleandir
7441.1Sabs
7451.1Sabs---cut here---
7461.1Sabs
7471.1SabsCritical utilities:
7481.1Sabs^^^^^^^^^^^^^^^^^^^
7491.1Sabs	gnu/usr.bin/egcs
7501.3Sitojun	usr.bin/compile_et
7511.1Sabs	usr.bin/make
7521.1Sabs	usr.bin/yacc
7531.1Sabs	usr.bin/lex
7541.11Slukem	usr.bin/xlint
7551.2Smrg	usr.sbin/config
7561.1Sabs
7571.34SsimonbOther problems and possible solutions:
7581.1Sabs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7591.1SabsSymptom:Unreasonable compiler errors.
7601.1SabsFix:	Rebuild gnu/usr.bin/egcs
7611.1Sabs
7621.1SabsSymptom:Complaints involving a Makefile.
7631.17SerhFix:	Rebuild usr.bin/make:
7641.17Serh	cd usr.bin/make && make && make install
7651.111Ssimonb	Or, a failsafe method if that doesn't work:
7661.17Serh	cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin
7671.17Serh
7681.1SabsFix:	Make sure .mk files are up to date.
7691.1Sabs	cd share/mk && make install
7701.2Smrg
7711.2SmrgSymptom:Kernel `config' fails to configure any kernel, including GENERIC.
7721.2SmrgFix:	Rebuild usr.sbin/config
7731.1Sabs
7741.1SabsSymptom:
7751.1SabsFix:	Rebuild usr.bin/yacc
7761.1Sabs
7771.1SabsSymptom:
7781.1SabsFix:	Rebuild usr.bin/lex
7791.1Sabs
7801.1SabsSymptom:
7811.1SabsFix:	rm /usr/lib/libbfd.a
7821.4Sitojun
7831.4SitojunSymptom:Obsolete intermediate files are used during compilation
7841.4SitojunFix:	Try the following sequence of commands in the directory in question.
7851.4Sitojun	make cleandir; rm `make print-objdir`; make cleandir; make obj
7861.4Sitojun	(If you built the tree without "make obj" in the past, obsolete files
7871.4Sitojun	may remain.  The command tries to clean everything up)
7881.5Swiz
7891.5SwizSymptom:.../sysinst/run.c:xx: warning: initialization from incompatible pointer type
7901.5SwizFix:	Rebuild and install usr.bin/menuc
7911.12Sitojun
7921.12SitojunSymptom:mklocale not found during build in share/locale/ctype
7931.12SitojunFix:	Build and install usr.bin/mklocale
7941.13Sdogcow
7951.86SkleinkSymptom:undefined reference to `__assert13' or `__unsetenv13'
7961.13SdogcowFix:    Rebuild and install lib/libc
7971.13Sdogcow
7981.19ScgdSymptom:usr.sbin/config fails to build.
7991.19ScgdFix:	Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile.
8001.13Sdogcow
8011.19ScgdSymptom:undefined reference to `getprogname' or `setprogname'
8021.19ScgdFix:    Rebuild and install lib/libc
8031.24Sabs
8041.24SabsSymptom:lint does not understand the '-X' option
8051.24SabsFix:    May need to build & install libs with NOLINT=1 before rebuilding lint
806