FreeBSD builds in CI about b2

[grafikrobot]

Not sure I'm going to be able to help much. What I can see from the logs you linked:

• B2 is being built with gcc-11 (the first g++ in the path?).
• When loading b2 it's trying to dynamic link to glibcxx that is different than what it was built with.
• Perhaps the dynamic loader path is different when linking vs. running.
• Generally smells like a badly configured set of compilers.
• Almost certainly not a b2 problem. But a general system set up problem.

Closing as I'm 99% sure it's not a b2 problem. Reopen if you find otherwise.

[sdarwin]

@grafikrobot

More info:

When installing gcc11 on FreeBSD it says:

To ensure binaries built with this toolchain find appropriate versions
of the necessary run-time libraries, you may want to link using

  -Wl,-rpath=/usr/local/lib/gcc11

For ports leveraging USE_GCC, USES=compiler, or USES=fortran this happens
transparently.

That's right! So, for specific CI jobs we are adding something like export B2_LINKFLAGS='-Wl,-rpath=/usr/local/lib/gcc11' and those jobs are building successfully.

What would be the best way to add similar link flags to bootstrap.sh? The problem is occurring at this stage of the process:

./bootstrap.sh
./b2 headers

In other words. it only involves b2 before getting to any specific CI jobs.

I have avoided the problem by removing the "default" gcc. In the absence of /usr/local/bin/gcc b2 compiles with /usr/bin/clang++.