NetBSD on Darwin - Mac OS X Leopard - to complete successfully
hack cross-building hack on Darwin
mdate 20 July 2008
who agc
file src/distrib/common/Makefile.mdset : 1.33
descr
Darwin has problems with getopt() when used in mdsetimage -v,
due to the difference between BSD and libiberty() getopt
implementations, more fully described in
http://mail-index.netbsd.org/current-users/2008/06/27/msg003242.html
and the subsequent thread. For just now, we just have an ugly
workaround not to call mdsetimage with the -v argument on Darwin
kcah
to the CD-ROM image.
Make CDEXTRA and CDBUILDEXTRA be able to contain lists of files and directories
which are added in turn.
Add support for CDEXTRA_SKIP which contains a list of fnmatch(3) items to
skip during the copy. This is _very_ useful for skipping CVS dirs for example.
CDBUILDEXTRA and CDEXTRA_SKIP are to be used in Makefiles creating the images,
CDEXTRA remains to be used from build.sh.
Update documentation and build.sh help text to show that -C can be used to
specify a list of files and directories rather than just a single dir.
no longer use it as a copy of ${_F} in the subsequent test for
additional targets under the MDSET_SUFFIXES test.
This brings back builds of srec & bin files for evbarm and img
files for evbppc.
- allow to specify the "instkernel" directory, and allow to put multiple
kernels on the image
- allow to specify the directory where the image will be created
- only use bootxx_cd9660 if it exists
- search for second-stage boot as usr/mdec/boot.${MACHINE} in addition to
usr/mdec/boot
- make 'installboot -e' optional
- use target 'release' or 'iso_image' depending on ${CDRELEASE}
- call some MD targets, which will eventually complete the file list or
make the image bootable
'copy-releasedir' is done before doing 'image'. Failure to do so
leads to a race condition that may result in build errors on
parallel builds with '-j 4' and '-j 16'.
per floppy for a while. (The rest of the sums are ok).
Change the 'padded' size to include all the space in the last 8k block
of the tar file.
Similarly if the image doesn't fit, report the exact amount of overflow.
Recreating the makefile when the crunchgen program has changed is probably
adequate, and it allows a lot of later optimisations to still apply.
In particular:
- the final link for ramdiskbin
- the create of the embedded filesystem
- the inclusion of the ramdisk into the kernel
- compressing the kernel
Unless something else actually requires one of the above.
of 'boot' and 'netbsd'.
This makes it possible for the tar archive to end at the end of the 2.88M
floppy, instead of either 4k before, or 6k after.
Gives us a whole extra 4k.
The very observant might realise that we don't need the final 1024 bytes
of nulls written to the floppy either, so they could be deleted!
Implement MDSET_NOGZIP & MDSET_NOGZIP.${FILENAME}, to prevent the gzip
of the final image. This is useful if that image has already been
munged & gzipped by MDSET_POST* or MDSET_SUFFIXES*.
agc