version 1.113, 2004/03/18 11:03:57 |
version 1.125, 2004/07/22 03:55:33 |
|
|
$NetBSD$ |
$NetBSD$ |
|
|
This file is intended to be a brief introduction to the build |
This file (UPDATING) is intended to be a brief reference to recent |
process and a reference on what to do if something doesn't work. |
changes that might cause problems in the build process, and a guide for |
|
what to do if something doesn't work. |
|
|
|
For a more detailed description of the recommended way to build NetBSD |
|
using build.sh, see the BUILDING file. |
|
|
|
Note that much of the advice in this UPDATING file was written before |
|
build.sh existed. Nevertheless, the advice here may be useful for |
|
working around specific problems with build.sh. |
|
|
For a more detailed description see Makefile. |
See also: BUILDING, build.sh, Makefile. |
|
|
Recent changes: |
Recent changes: |
^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^ |
|
|
|
20040715: |
|
The rc.d/sendmail script now uses a heuristic to determine |
|
if sendmail should be started at boot time. It checks the |
|
contents of /etc/mailer.conf, /etc/mail/submit.cf, and the |
|
owner and mode of the sendmail binary to see if any changes |
|
to the mail infrastructure have been made. If no changes |
|
are detected, it will start an SMTP listener. |
|
|
|
Setting sendmail=NO in /etc/rc.conf will override this. |
|
|
|
If you are only using sendmail by default and only for |
|
local delivery, it is important that you also update your |
|
sendmail.cf so that the SMTP listener only listens on the |
|
loopback interface. |
|
|
|
20040715: |
|
The method by which athhal-elf.o gets pulled into i386 |
|
kernel builds has been changed again. The latest version |
|
of bsd.files.mk is no longer required. |
|
|
|
20040621: |
|
Due to the recent rototill of tools/compat it's crucial one starts |
|
from a clean objdir under tools/*. |
|
|
|
This is mostly due to generated files (yacc and lex sources) needing |
|
to be generated with new rules from bsd.hostprog.mk. |
|
|
|
The safest course is to rm -rf all objects under tools before building. |
|
|
|
20040516: |
|
The end-user modifiable X11 configuration has been moved |
|
from /usr/X11R6/lib/X11/<dir> to /etc/X11/<dir>. |
|
Ensure that src and xsrc is up to date, and run |
|
"make cleandir" in src/x11 before your next build. |
|
|
|
20040426: |
|
Support for the original dynamic sysctl node structure has |
|
been removed in favor of the newer layout. This affects |
|
consumers of the create and delete interface, as well as |
|
the dynamic discovery mechanism. This is believed only to |
|
be the sysctl(8) binary itself, at this point in time, so |
|
the only effect of this should be that a sysctl binary |
|
built from sources dated between 2003/12/04 and 2004/03/24 |
|
will not work on a kernel built from sources dated after |
|
2004/04/25. If you need a new sysctl binary but build.sh |
|
does not work, make sure that your revision of |
|
src/sys/sys/sysctl.h is 1.112 (or later), and then the |
|
do the following: |
|
|
|
cd /usr/src (or wherever your source tree is) |
|
make USETOOLS=no includes |
|
cd lib/libc |
|
make USETOOLS=no dependall install |
|
cd ../../sbin/sysctl |
|
make USETOOLS=no dependall install |
|
|
|
If you are using older sysctl binary, GNU autoconf would fail to |
|
identify your machine architecture, and tries to build binary for |
|
"unknown-unknown-netbsd20F" or something like that. if that happens, |
|
make sure to follow the above steps. |
|
|
|
20040425: |
|
The ffs superblock issues listed below under 20040109 and 20030402 |
|
are now automatically addressed by the /etc/rc.d/fixsb script or by |
|
sysinst when it checks a a filesystem. The manual fsck_ffs -b16 -c4 |
|
invocation mentioned below will continue to work and is now |
|
automated by those scripts. Note that under certain circumstances, |
|
affected filesystems upgraded to a -current kernel first before |
|
upgrading their userland with the fixsb and fsck_ffs fixes may |
|
encounter a 'freeing free inode' panic when writing to the affected |
|
filesystem, so it is a good idea to repair the filesystem as soon as |
|
possible. For more details on the fixsb script, see pr install/25138. |
|
|
|
20040418: |
|
statfs(2) and friends have been replaced with statvfs(2). Before |
|
installing a newly build userland make sure that you are running |
|
a newly built kernel with COMPAT_20 set. In addition your libc |
|
build might not work (undefined SYS_statfs symbol) because make |
|
clean does not know how to remove files it does not know about |
|
anymore. Manually remove all generated .S sources and objects |
|
from the libc build directory. |
|
|
|
20040326: |
|
The method by which athhal-elf.o gets pulled into i386 kernel builds |
|
has been changed. The file is now stored as a uuencoded file in CVS |
|
and the generated Makefile will use the new .uue rules from bsd.file.mk |
|
to build it. |
|
|
|
This means you must have the latest bsd.files.mk installed when |
|
building a kernel without USETOOLS=yes. |
|
|
20040318: |
20040318: |
A bug in the cgd(4) blowfish code was corrected, without |
A bug in the cgd(4) blowfish code was corrected, without |
provision of backwards compatibility, after several public |
provision of backwards compatibility, after several public |
|
|
|
|
Hints for a more successful build: |
Hints for a more successful build: |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
|
Use build.sh, but do not use its "expert mode": |
|
This will will automatically build the tools in the |
|
correct order, and it will keep the tools and the |
|
new build products from interfering with the running |
|
system. This will allow you to ignore most of the |
|
other advice in this file. |
Build a new kernel first: |
Build a new kernel first: |
This makes sure that any new system calls or features |
This makes sure that any new system calls or features |
expected by the new userland will be present. This |
expected by the new userland will be present. This |
Line 535 Hints for a more successful build: |
|
Line 640 Hints for a more successful build: |
|
about one. It also makes it easier to clean up after |
about one. It also makes it easier to clean up after |
a build. It's also necessary if you want to use the |
a build. It's also necessary if you want to use the |
same source tree for multiple machines. |
same source tree for multiple machines. |
To use object directories: |
To use object directories with build.sh: |
|
a) invoke build.sh with the "-M" or "-O" options. |
|
To use object directories without using build.sh: |
a) cd /usr/src ; make cleandir |
a) cd /usr/src ; make cleandir |
b) Add "OBJMACHINE=yes" to /etc/mk.conf |
b) Add "OBJMACHINE=yes" to /etc/mk.conf |
c) Add "MKOBJDIRS=yes" to /etc/mk.conf |
c) Add "MKOBJDIRS=yes" to /etc/mk.conf |
Line 543 Hints for a more successful build: |
|
Line 650 Hints for a more successful build: |
|
Note that running "make obj" in a directory will create |
Note that running "make obj" in a directory will create |
in obj.$MACHINE directory. |
in obj.$MACHINE directory. |
Build to a DESTDIR: |
Build to a DESTDIR: |
This helps to keep old |
This helps to keep old installed files (especially libraries) |
installed files (especially libraries) from interfering |
from interfering with the new build. |
with the new build. |
To build to a DESTDIR with build.sh, use the "-D" option. |
To build to a DESTDIR, set the DESTDIR environment |
To build to a DESTDIR without using build.sh, set the DESTDIR |
variable before running make build. It should be set to |
environment variable before running make build. It should be |
the pathname of an initially empty directory. |
set to the pathname of an initially empty directory. |
Problems: you might need to update critical utilities |
Problems: if you do not use build.sh, you might need to |
without using DESTDIR since nothing is executed |
update critical utilities without using DESTDIR since |
from what is installed in DESTDIR. |
nothing is executed from what is installed in DESTDIR. |
(See critical utils, below) |
(See critical utils, below.) |
Build often: |
Build often: |
This keeps critical utilities current enough to not choke |
This keeps critical utilities current enough to not choke |
on any other part of the source tree that depends on up to |
on any other part of the source tree that depends on up to |
date functionality. |
date functionality. If you use build.sh, you should not have |
|
this problem. |
|
|
What to do if things don't work: |
What to do if things don't work: |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |