thor0505%comcast.net@localhost writes: >>If you want to pass different mk.conf files and have different paths, >>that should be pretty easy. The basic hint is to not insist on passing >>one argument, and accept that you will set multiple options. > That's fine. I just wanted to make sure this was the "best practice", > so I don't run into cross-arch or cross-mk.conf errors later on. The > only way I've seen to set different mk.confs is to set the variable on > the command line either prior to (and export) or when invoking > ./build.sh. Is this correct, or is there an undocumented option to set > it on the command line? I think environment is the right way; that's what the docs say and reading build.sh source code does not suggest otherwise. >>./build.sh -m i386 -j8 -x -u -U -O /usr/obj/gdt-current/i386 -T >> /usr/obj/gdt-current/tools -D /usr/obj/gdt-current/destdir/i386 -R >> /usr/obj/gdt->current/>releasedir -X /u0/n0/gdt/NetBSD-current/xsrc >> release > Do you set the kernel in mk.conf, or is this just an example where you > skip building the kernel/it's already built? I am doing a release build, so all the kernels in the release are built. If you run GENERIC, this makes sense. When I first ran NetBSD I made custom kernels, but now tend to run GENERIC, because memory is not so precious (usually) and because part of the problem was probing odd ISA devices.
Attachment:
pgpFKmOYxkRgH.pgp
Description: PGP signature