Ruby

Now it turned out the build fails even -j 1 is specified. Any value to -j option will fail.
Not giving -j option goes fine.

Further information from Yuichiro NAITO:

最初にレースコンディションと言っていたのは誤りで
-j の有無で shell に渡すコマンドの範囲が異なるのが原因でした。
基本的にはビルド手順を1行づつ shell に渡すのが本来の make の実装なのですが、
BSD make は -j オプションをつけると、ビルド手順が複数行ある場合にまとめて shell に渡すようになります。
そうすると、途中で exec があった場合、残りのコマンドが実行されなくなります。
Ruby の Makefile では行の最後のコマンドに exec 使うことで、
最後の fork(2) 実行を省略しようという意図のように見えます。

結局のところ BSD make の互換性問題のように思います。

Applied in changeset git|faa4f4f23fbb6b48b158cc38d9b509fd00838976.

Get rid of FreeBSD make incompatibility [Bug #16331]

FreeBSD make works differently with -j option.

-j max_jobs
Specify the maximum number of jobs that make may have running
at any one time. The value is saved in .MAKE.JOBS. Turns
compatibility mode off, unless the B flag is also specified.
When compatibility mode is off, all commands associated with a
target are executed in a single shell invocation as opposed to
the traditional one shell invocation per line. This can break
traditional scripts which change directories on each command
invocation and then expect to start with a fresh environment on
the next line. It is more efficient to correct the scripts
rather than turn backwards compatibility on.

Stop using exit, cd, exec in middle of commands.

I executed following shell script on my FreeBSD test environment and got attached log file.

#!/bin/sh LANG=C ( echo System Information: echo ---------------------------------------------------------------------- dmesg echo ---------------------------------------------------------------------- echo Package Information: echo ---------------------------------------------------------------------- pkg info -aq echo ---------------------------------------------------------------------- cd /tmp for ver in 2.6.5 2.7.0-rc2 do echo Test build of ${ver}: tar xfpJ /net/freebsd/ports/distfiles/ruby/ruby-${ver}.tar.xz cd ruby-${ver} echo Configure: echo ---------------------------------------------------------------------- ./configure echo ---------------------------------------------------------------------- echo Build: echo ---------------------------------------------------------------------- make -j $(sysctl -n kern.smp.cpus) echo ---------------------------------------------------------------------- cd .. rm -rf ruby-${ver} done ) | 2>&1 tee buildtest-with-bmake-and-j-option.log 

As you can see, make -j works fine with 2.6.5 but fails with 2.7.0-rc2.

It is not fixed yet for me, too.

I attach ruby-{2.6.5,2.7.0} build result with {BSD,GNU} make.

Applied in changeset git|53adb53c9aea5da98ed3e470983b2cbfe367cb7d.

Ignore expected errors on compiling C++ source [Bug #16331]

BSD make can run parallel more aggressively than GNU make. It communicate
with other make process through -J option in MAKEFLAGS environment variable
to notify a build failure happend in an other pararell make process.
https://www.freebsd.org/cgi/man.cgi?make

It usually works well but ext/-test-/cxxanyargs/Makefile has two targets
which are expected to fail (failure.o and failurem1.o).

Additional note:
To test and debug this issue, following command will speed up it.
make -f exts.mk -j8 clean all

ruby_2_7 a930174d798b58ee10493bf192d277ffe08518a7.