version 1.104, 2004/01/12 16:19:19 |
version 1.122, 2004/05/31 00:18:58 |
Line 8 For a more detailed description see Make |
|
Line 8 For a more detailed description see Make |
|
Recent changes: |
Recent changes: |
^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^ |
|
|
|
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: |
|
A bug in the cgd(4) blowfish code was corrected, without |
|
provision of backwards compatibility, after several public |
|
notices over several months. Users of cgd with blowfish cipher |
|
ONLY must dump their data before updating their kernels, and |
|
recreate cgd's and restore data using the new kernel. See |
|
(recent message to current-users, URL when mail-index has updated) |
|
|
|
20040313: |
|
On acorn32, the opms and qms drivers have been withdrawn, and |
|
the old wsqms driver is now called qms. Kernel config files |
|
will need updating. See the ones in sys/arch/acorn32/conf |
|
for examples. |
|
|
|
20040125: |
|
On acorn32, the beep and sysbeep devices are no longer |
|
needed, and will need to be deleted from kernel configuration |
|
files. |
|
|
20040109: |
20040109: |
Compatibility for old ffs superblock layouts has been |
Compatibility for old ffs superblock layouts has been |
added, and the restrictive fsck checks have been reenabled |
added, and the restrictive fsck checks have been reenabled |
when using those layouts. If you have been using -current |
when using those layouts. If you have been using -current |
since 20030402, you may find that fsck again signals fatal |
since 20030402, you may find that fsck again signals fatal |
superblock mismatches. To work around, you can use |
superblock mismatches. To repair, make sure you have |
fsck_ffs -b 32 -c 4 to restore an alternate superblock |
an updated fsck_ffs and then you can use fsck_ffs -b 16 -c 4 |
and complete the filesystem upgrade. |
to complete the filesystem upgrade. A message has |
|
been added to the kernel which should detect this problem. |
|
See the following discussion for more information: |
|
http://mail-index.NetBSD.org/current-users/2004/01/11/0022.html |
|
|
20031203: |
20031203: |
New binutils builds may fail due to old dependencies. |
New binutils builds may fail due to old dependencies. |
|
|
It's necessary to "make cleandir" to ensure that |
It's necessary to "make cleandir" to ensure that |
the dependencies will be rebuilt correctly. |
the dependencies will be rebuilt correctly. |
|
|
|
20031007: |
|
A sign exension bug was fixed which set all the high bits |
|
of our newly expanded ffs fs_flags. This should only |
|
affect users who installed or upgraded in September of 2003. |
|
A small utility program was posted to tech-kern which |
|
should fix this problem, and a warning message was added |
|
to the kernel which should discover and warn about it. See |
|
http://mail-index.NetBSD.org/tech-kern/2003/10/07/0005.html |
|
|
20030906: |
20030906: |
With the addition of siginfo support the old signal trampoline |
With the addition of siginfo support the old signal trampoline |
code has been deprecated to COMPAT_16. Make sure that your running |
code has been deprecated to COMPAT_16. Make sure that your running |
|
|
|
|
20010803: |
20010803: |
(i386 only): i386 kernel now uses new instructions like |
(i386 only): i386 kernel now uses new instructions like |
`fxsave' which old gas doesn't understand. To build the |
`fxsave' which old gas doesn't understand. To build the |
kernel successfully, you need to build and install a new toolchain, |
kernel successfully, you need to build and install a new toolchain, |
(i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" |
(i.e., build.sh -t) or (temporarily) comment out "options I686_CPU" |
from your kernel configuration until you rebuild your userland. |
from your kernel configuration until you rebuild your userland. |
|
|
|
|
20010219: |
20010219: |
get/setprogname() added. Any hostprogs that may use this will need |
get/setprogname() added. Any hostprogs that may use this will need |
to be bootstrapped manually until the host system is current. |
to be bootstrapped manually until the host system is current. |
|
|
Known problems: sys/arch/macppc/stand/fixcoff |
Known problems: sys/arch/macppc/stand/fixcoff |
usr.sbin/config (adding -DMAKE_BOOTSTRAP to |
usr.sbin/config (adding -DMAKE_BOOTSTRAP to |
CFLAGS and rebuilding should work) |
CFLAGS and rebuilding should work) |
usr.sbin/mdsetimage - Build a static copy if |
usr.sbin/mdsetimage - Build a static copy if |
building a snapshot before fully bootstrapped. |
building a snapshot before fully bootstrapped. |
|
|
20010204: |
20010204: |
prepare the code to compile with stricter gcc flags. in |
prepare the code to compile with stricter gcc flags. in |
Line 599 Fix: Rebuild gnu/usr.bin/egcs |
|
Line 692 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 |
Or, a failsafe method if that doesn't work: |
Or, a failsafe method if that doesn't work: |
cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin |
cd usr.bin/make && cc *.c */*.c -I . -o make && mv make /usr/bin |
|
|
Fix: Make sure .mk files are up to date. |
Fix: Make sure .mk files are up to date. |