Pav Lucistnik <p...@freebsd.org> wrote: > Ports framework now systematically supports building ports on > multiple processing cores. It is achieved by passing -jX flag to make(1) > running on vendor code. Of course not all ports handle this well,
A word of caution: It is quite possible for a port to build fine with -jN and still fail with -jM, where N < M. If it builds fine on a 64-core sparc64, it will build anywhere, but I expect some ports will work fine for, say, -j2 and fail for -j4. Or only fail *sometimes* due to a race. > If you are FreeBSD port maintainer: > > Nothing changes for you, if you don't want. If you want to enable the > use of multiple cores in your port, add MAKE_JOBS_SAFE=yes to a block > somewhere below dependency declarations. What is the goal here? Should all ports that can be safely built in parallel eventually have MAKE_JOBS_SAFE=yes? Or should we not bother with ports where the gain is likely to be minimal? -- Christian "naddy" Weisgerber na...@mips.inka.de _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
