version 1.113, 2004/03/18 11:03:57 |
version 1.152, 2006/11/09 18:20:59 |
|
|
$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: |
^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^ |
|
|
|
20061108: |
|
The configure script used in the src/tools/gcc compiler has been |
|
changed to indicate that our libc has ssp support built-in and |
|
does not depend on -lssp and -lssp-nonshared. You'll need to |
|
make clean in src/tools/gcc first to rebuild the compiler. |
|
|
|
20061009: |
|
The sysctl variables net.inet{,6}.tcp{,6}.newreno are no longer |
|
available. Use net.inet{,6}.tcp{,6}.congctl.selected instead. |
|
|
|
20060814: |
|
The vt, vidcconsole, kbd, and rpckbd drivers on acorn32 have been |
|
withdrawn. Use vidcvideo and pckbd instead. See the GENERIC |
|
kernel configuration for an example. X servers from the last |
|
few years should cope. |
|
|
|
20060703: |
|
MPACPI is no more. We always configure PCI interrupts using ACPI |
|
if we have an ACPI kernel. The option MPACPI_SCANPCI has been renamed |
|
to ACPI_SCANPCI. Thanks to work from fvdl. |
|
|
|
20060627: |
|
socket(2) has changed, and its system call has been versioned. |
|
For userlands with the old version of socket(2), make sure that |
|
your kernel has 'options COMPAT_30' set, or else 'bad system call' |
|
errors will result. |
|
|
|
20060526: |
|
The kernel linker scripts for i386 and xen |
|
(sys/arch/i386/conf/kern.ldscript*) were changed to set the |
|
load address correctly, for the benefit of MULTIBOOT boot loaders |
|
(like Grub). If you use a linker (ld) older than from 2006/04/17, it |
|
will be unable to link the kernel because of a bug and ld will fail |
|
with an error like: |
|
../../../../arch/i386/conf/kern.ldscript:45 \ |
|
non constant expression for load base |
|
You need to update at least src/gnu/dist/binutils/ld and recompile |
|
and install the linker. If using the build.sh script, the easiest |
|
way is with a "build.sh tools" command, with any other options |
|
that you use normally. When using build.sh, the linker binary is |
|
installed as ${TOOLDIR}/bin/i386--netbsdelf-ld. |
|
|
|
20060131: |
|
the protocol between the sparc64 bootloader (ofwboot) and |
|
the kernel was changed. Before installing a new kernel, |
|
you need to update ofwboot. After a full build, just copy |
|
/usr/mdec/ofwboot to /, or do a rebuild of |
|
src/sys/arch/sparc/stand/ofwboot and install the result to /. |
|
|
|
20050917: |
|
arch/*/conf/std.* was changed to include conf/std, which |
|
contains MI options previously enabled by default. |
|
If you have kernel config files which doesn't include |
|
arch/*/conf/std.*, you need to edit them to include conf/std |
|
to get the previous configuration. |
|
|
|
20050830: |
|
named.conf was moved from /etc/namedb to /etc. |
|
postinstall(8) migrates this during interactive use. |
|
Users of MKUPDATE=yes will need to manually rectify |
|
this in their DESTDIR. |
|
|
|
20050825: |
|
Some data structures in sys/device.h, related to interface |
|
attributes and locator names, were changed. config(1) was |
|
modified to emit the new data structures. |
|
Thus usr.bin/config must be updated (and run on the kernel |
|
configuration file) before a new kernel can be built. |
|
|
|
20050531: |
|
genassym.sh(8) was moved to genassym(1). You need to either build |
|
tools first or install the version of genassym from /usr/bin before |
|
you can build a kernel again. |
|
|
|
20050520: |
|
Because a kernfs bug which xentools relies on was fixed, |
|
xentools up to xentools20-2.0.3nb4 won't work with new kernel. |
|
|
|
20050417: |
|
postinstall(8) was moved from /etc to /usr/sbin and made part |
|
of the "base" set, to make it easier to invoke after an |
|
upgrade. |
|
|
|
20050325: |
|
pcppi(4) was separated in two devices, adding attimer(4). Be sure |
|
to add a config line for an attimer(4) device in your kernel |
|
configuration, or you won't be able to set the pitch of the beep |
|
with wsconsctl. Depending on the default value for the pitch, you |
|
might even not hear any more beep. Also, it is advised to attach both |
|
devices the same way (i.e., both on isa or both on acpi) or the |
|
pcppi(4) device may fail to find the attimer(4) one. |
|
|
|
20050211: |
|
Fixes to tools/Makefile.gnuhost may cause UPDATE=1 builds in |
|
some of the cross tools to fail if they use configure. Some configure's |
|
cache the environment passed in and notice the new environment is |
|
different and abort. Doing a clean in tools/ should be enough to |
|
make a build continue. |
|
|
|
20050109: |
|
Since su is using pam by default now, make sure that you have |
|
/etc/pam.d populated (postinstall will do that automatically |
|
for you). Otherwise su will fail open (i.e. will not require |
|
a password). |
|
|
|
20041229: |
|
Make had a path resolution bug that manifested itself as not |
|
being able to install openpam.3. This bug has been fixed, but |
|
you might need to rebuild make manually first to get through |
|
the build. |
|
|
|
20041201: |
|
Userland programs have been changed to use /dev/bpf instead of |
|
/dev/bpfX. You need to create that device by installing a new |
|
MAKEDEV and running it, or mv /dev/bpf0 /dev/bpf && rm /dev/bpf[0-9]* |
|
|
|
20041006: |
|
|
|
A bug was introduced into /bin/sh (var.c rev 1.35) which causes |
|
variables to not export correctly to subshells in all cases. This |
|
will cause builds to break if that version of /bin/sh is installed |
|
on the system. The proper version of /bin/sh can be verified with: |
|
|
|
ident /bin/sh | grep var |
|
|
|
Any /bin/sh w. version 1.35 will not work and needs to be updated |
|
before attempting a build. |
|
|
|
20041001: |
|
The ipfilter kernel sources moved from sys/netinet to |
|
dist/sys/ipf/netinet. Due to the move some Makefile |
|
dependencies are now dangling requiring a make cleandir |
|
before they work again (kdump, ktruss, rescue, ipf, and |
|
ftp-proxy are the victims). |
|
|
|
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. |
|
|
|
postinstall currently doesn't migrate the files from |
|
/usr/X11R6/lib/X11/* to /etc/X11/* although it does |
|
detect that this needs to occur, so you'll have to |
|
manually move these files yourself. |
|
|
|
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 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 780 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 790 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: |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
Line 614 cd $NETBSDSRCDIR && make cleandir |
|
Line 862 cd $NETBSDSRCDIR && make cleandir |
|
|
|
Critical utilities: |
Critical utilities: |
^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^ |
gnu/usr.bin/egcs |
|
usr.bin/compile_et |
usr.bin/compile_et |
usr.bin/make |
usr.bin/make |
usr.bin/yacc |
usr.bin/yacc |
usr.bin/lex |
usr.bin/lex |
usr.bin/xlint |
usr.bin/xlint |
usr.sbin/config |
usr.bin/config |
|
|
Other problems and possible solutions: |
Other problems and possible solutions: |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
Symptom:Unreasonable compiler errors. |
|
Fix: Rebuild gnu/usr.bin/egcs |
|
|
|
Symptom:Complaints involving a Makefile. |
Symptom:Complaints involving a Makefile. |
Fix: Rebuild usr.bin/make: |
Fix: Rebuild usr.bin/make: |
cd usr.bin/make && make && make install |
cd usr.bin/make && make && make install |
Line 637 Fix: Make sure .mk files are up to date. |
|
Line 881 Fix: Make sure .mk files are up to date. |
|
cd share/mk && make install |
cd share/mk && make install |
|
|
Symptom:Kernel `config' fails to configure any kernel, including GENERIC. |
Symptom:Kernel `config' fails to configure any kernel, including GENERIC. |
Fix: Rebuild usr.sbin/config |
Fix: Rebuild usr.bin/config |
|
|
Symptom: |
Symptom: |
Fix: Rebuild usr.bin/yacc |
Fix: Rebuild usr.bin/yacc |
Line 663 Fix: Build and install usr.bin/mklocale |
|
Line 907 Fix: Build and install usr.bin/mklocale |
|
Symptom:undefined reference to `__assert13' or `__unsetenv13' |
Symptom:undefined reference to `__assert13' or `__unsetenv13' |
Fix: Rebuild and install lib/libc |
Fix: Rebuild and install lib/libc |
|
|
Symptom:usr.sbin/config fails to build. |
Symptom:usr.bin/config fails to build. |
Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. |
Fix: Try building with -DMAKE_BOOTSTRAP added to CFLAGS in Makefile. |
|
|
Symptom:undefined reference to `getprogname' or `setprogname' |
Symptom:undefined reference to `getprogname' or `setprogname' |