Does anyone know why, when the version of protobuf from ports matches the internal protobuf version, MySQL links to the port-installed protobuf instead of the bundled one?
Build scripts often pickup dependencies when they happen to be installed, even if you tell the build script to "disable" them. This is one of the reasons why packages are build in a "clean room" environment. It prevents this kind of issue.
Yes, the issue was resolved after updating the protobuf version in the port. I hope MySQL doesn't use the latest protobuf version for some time so it doesn't happen again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
