boost: install fails with +openmpi: bootstrap compilation fails for `b2`

[Epoxid2 (Stephan Schmidt)]

The various Boost ports fail to install with +openmpi, on Monterey 12.5.1.

Appears to be an issue with bootstrap compilation of b2:

:info:configure Building B2 engine..
1421	:info:configure > cpp -DNDEBUG builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp execnt.cpp execunix.cpp filesys.cpp filent.cpp fileunix.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam_strings.cpp jam.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathnt.cpp pathsys.cpp pathunix.cpp regexp.cpp rules.cpp scan.cpp search.cpp startup.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp -o b2
1422	:info:configure cpp: fatal error: too many input files
1423	:info:configure compilation terminated.
1424	:info:configure > cp b2 bjam
1425	:info:configure cp: b2: No such file or directory
1426	:info:configure Failed to build B2 build engine

[ds283 (David Seery)]

Wondering whether there was any outcome from this.

I'm not certain whether I should log this under a second ticket, but I am having a similar issue when trying to build at least boost176 or boost180 with +openmpi. boost171 and boost173 build and install correctly.

The problem is again with building b2, but the cause of the error is different (or at least appears different to me):

:info:configure Could not find a suitable toolset.
:info:configure You can specify the toolset as the argument, i.e.:
:info:configure     ./build.sh [options] gcc
:info:configure Toolsets supported by this script are:
:info:configure     acc, clang, como, gcc, intel-darwin, intel-linux, kcc, kylix, mipspro,
:info:configure     pathscale, pgi, qcc, sun, sunpro, tru64cxx, vacpp

Moving into the build directly and trying to run ./bootstrap.sh myself with a --with-toolset argument does better, but then build.sh complains that the C compiler does not appear to undertstand C++11

% ./bootstrap.sh --prefix=/opt/local --with-icu=/opt/local --with-python=/opt/local/bin/python3.10 --with-python-root=/opt/local/bin/python3.10 --with-toolset=gcc
Building B2 engine..

A C++11 capable compiler is required for building the B2 engine.
Toolset 'gcc' does not appear to support C++11.

> g++ -x c++ -std=c++11  check_cxx11.cpp
clang: error: no such file or directory: 'check_cxx11.cpp'
> g++ -x c++ -std=c++11 -D_GNU_SOURCE  check_cxx11.cpp
clang: error: no such file or directory: 'check_cxx11.cpp'
> g++ -x c++ -std=c++11 -pthread  check_cxx11.cpp
clang: error: no such file or directory: 'check_cxx11.cpp'

To be clear, this only happens with the +openmpi variant. Trying to build without +openmpi works fine.

[ds283 (David Seery)]

Build log with boost180 with failure caused by +openmpi