version 1.129, 2004/10/12 04:03:20 |
version 1.137, 2005/04/11 15:36:46 |
Line 15 See also: BUILDING, build.sh, Makefile. |
|
Line 15 See also: BUILDING, build.sh, Makefile. |
|
|
|
Recent changes: |
Recent changes: |
^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^ |
|
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: |
20041006: |
|
|
|
|
Hints for a more successful build: |
Hints for a more successful build: |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
Use build.sh, but do not use its "expert mode": |
Use build.sh, but do not use its "expert mode": |
This will will automatically build the tools in the |
This will automatically build the tools in the |
correct order, and it will keep the tools and the |
correct order, and it will keep the tools and the |
new build products from interfering with the running |
new build products from interfering with the running |
system. This will allow you to ignore most of the |
system. This will allow you to ignore most of the |