Christian Groessler <[email protected]> wrote: >On 05/24/17 17:35, Robert Swindells wrote: >> Christian Groessler <[email protected]> wrote: >>> with "old way" I mean not using build.sh. >> [snip] >> >> I don't use build.sh to build kernels but use a workflow inbetween >> it and the old way that you describe. >> >> I cross build the tools for whatever target architecture I want using >> build.sh. >> >> Then: >> >> % cd src/sys/arch/macppc/conf >> % /path/to/macppc-tools/bin/nbconfig GENERIC >> % cd ../compile/GENERIC >> % /path/to/macppc-tools/bin/nbmake-macppc depend >> % /path/to/macppc-tools/bin/nbmake-macppc >> >> You could probably look in the nbmake-macppc shell script to work out what >> extra environment variables you need to set in order to get your way to >> work but I think there is still the chance of a mismatch between the host >> tools and the -current source tree. > >I'm not cross-compiling here. I'm trying to build a macppc kernel on a >macppc host.
I know, you could still build the tools on the macppc host though. >But now I just want to compile a modified kernel to check something out. >But the nice, simple, way I was using >in older times doesn't work anymore :-( The answer will be in nbmake-macppc.
