`undefined reference` in boost filesystem from release 1.68 for gcc 5.2-6.3 about filesystem

[pdimov]

It might be a good idea to check 1.69 RC1 at https://dl.bintray.com/boostorg/release/1.69.0/source/

Boost.System is header-only in 1.69, so the link error in the original post should no longer be an issue.

But in general, the rule is that you have to build Boost with the same C++ standard with which you'll be using it. If you're going to use f.ex. C++14, and you're building with a compiler for which C++14 isn't default (such as gcc 5/clang 5 or earlier) you need to build with b2 cxxstd=14.

[jbeich]

Probably, duplicate of either boostorg/system#24 or boostorg/system#26. See also ABI discussion.

[wkailey]

I just installed boost 1.68, and I have the same problem. After successfully untarring, building, and installing boost, I am including <boost/regex.hpp> and linking with -lboost_regex, and it comes up with an undefined external [a function named . . . . . .match()] at line 386 of regex/v4/perl_matcher.hpp

[jcbritobr]

This also happens to me with mingw 64 builds on windows and gcc 7.x

[Lastique]

I'm tempted to close this because it looks like an ABI mismatch problem. I've added a MinGW-w64 gcc 7.3 CI job just to test this config explicitly.

[pdimov]

And it failed. -)

[Lastique]

For a different reason. :)

[jcbritobr]

It might be a good idea to check 1.69 RC1 at https://dl.bintray.com/boostorg/release/1.69.0/source/

Boost.System is header-only in 1.69, so the link error in the original post should no longer be an issue.

But in general, the rule is that you have to build Boost with the same C++ standard with which you'll be using it. If you're going to use f.ex. C++14, and you're building with a compiler for which C++14 isn't default (such as gcc 5/clang 5 or earlier) you need to build with b2 cxxstd=14.

I was using gcc 7.3, but will build it again, using b2 cxxstd=14.

Thank you guys.

[Lastique]

The tests are passing now. So either this was an ABI mismatch or it was already fixed in develop.