boost::asio::execution::bad_executor needs an explicit BOOST_ASIO_DECL

[jcelerier]

When linking with lld (from clang-64 MinGW) on windows, with BOOST_ASIO_DYN_LINK:

 ld.lld: error: undefined symbol: vtable for boost::asio::execution::bad_executor

Every other symbol is correct, but since the type boost::asio::execution::bad_executor itself is not marked BOOST_ASIO_DECL, then the implicit dtor won't be marked as exported.

[jcelerier]

hmm.. actually I'm still getting the same link error despite marking everything:

class BOOST_ASIO_DECL bad_executor : public std::exception
{
public:
  /// Constructor.
  BOOST_ASIO_DECL bad_executor() noexcept;
  BOOST_ASIO_DECL virtual ~bad_executor() noexcept;

  /// Obtain message associated with exception.
  BOOST_ASIO_DECL virtual const char* what() const noexcept;
};

BOOST_ASIO_DECL bad_executor::bad_executor() noexcept { }
BOOST_ASIO_DECL bad_executor::~bad_executor() noexcept { }

BOOST_ASIO_DECL const char* bad_executor::what() const noexcept
{
  return "bad executor";
}

[inetic]

I had the same problem

with BOOST_ASIO_DYN_LINK:

Just for context, we achieved the above by patching asio to include defined(__MINGW32__) detail/config.hpp. Without it the linker spits out thousands of lines of undefined references

With the above, only the undefined reference to bad_executor() and vtable errors remained. I was unable to fix it with BOOST_ASIO_DECL and non inlined functions (I did not have a minimal reproducible example and testing with the main project took too long). At the end inlining the constructor, destructor and what + removing noexcept from the constructor helped.