• Add 32-bit powerpc patches from bdragon

In D30099#675645, @bdragon wrote:

Note: I have the bootstrap side working for 32 bit powerpc, been holding off on submitting it though because I haven't successfully gotten a full lang/rust build out of it yet (problems with linking.)

@mikael, wondering why you abandoned? I am curious if adding build-stage=2 was already enough.

In D29760#672237, @jbeich wrote:

• Switching to .crate seems OK and aligns with PkgSrc
• Converting both main and 2021Q2 (a la f90ccf6cfccc) can avoid the delay:

Any opinions on this approach?

Any further comments can happen in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254678

Please commit it. Thanks.

All ports that are affected by this are tagged with CARGO_USE_GITHUB and CARGO_USE_GITLAB. Assuming those ports all build (or alternatively if you have checked that the contents of Cargo.toml are the same before and after) then this is approved if you remove the superfluous [].

• Change approach and do it in a backwards compatible way instead

• Rebase

• devel/meson, Mk/Uses/meson.mk: Do not force color output

• Rebase
• Try to unbreak www/deno (untested)

• More missing USES=python:build fixes
• Add explicit USES=ninja:build to multimedia/handbrake (previously got it through meson but now needs the samu alias)
• Attempt to fix build order bug in x11-fonts/font-manager

• Fix x11-wm/mutter build order bug with patch from Aports
• Fix x11/brisk-menu build order bug
• Add missing USES=python:build to some ports that got it through ninja previously
• Fix lang/swi-pl build by adding missing USES=readline (previously implicit through ninja->python->readline)
• Only append -v to MAKE_ARGS when using ninja. samu already gets it via SAMUFLAGS. ninja supports GNU-style arguments (flags in any order) while samu does not and -v gets added last. This should fix the immediate error in www/chromium (build goes further but complete build untested)

• Update devel/samurai to latest master with upstream fix for the fpe bug

• Update review from the right branch...

• Add fix for floating point exception bug with NINJA_STATUS=%p

• Unbreak ninja:run

• Revert the CARGO_USE_GIT* changes

• Use the right lock file in cargo-crates

In D29353#657807, @bapt wrote:

I do like it, I would be interested in a exp-run with both to see if there is any difference, I bet ninja vs samurai itself won't bring anything, but the fact we don't need python do build samurai, will make project using ninja (well samurai here ;)) appear earlier in the build process which may have an impact.

• Also pass -v in SAMUFLAGS for ports that call ninja on their own and ignore MAKE_ARGS

• export SAMUFLAGS to make samu builds respect MAKE_JOBS_NUMBER

• sysutils/fluxengine generates broken Ninja files; fix that

• Include newly added sysutils/fluxengine

• Rebase