-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot open shared library. #322
Comments
Does the solution here work for you #246 |
Unfortunately that method is not currently working.
I also tried to reconfigure the solution posted in [#246 ] using the guides: The same errors persisted when I tried to build 10.5 or 10.4 aws_key_management. The same problem also occurred when trying to build on a non docker environment. Building with autobake-deb.sh doesnt seem to yield aws_key_management.so |
There are no open bugs upstream on this compile failure. I recommend you create one. In the mean time this compile error looks like the C++ standards/implementations evolved ahead of the code base being compiled. extra/aws_sdk/CMakeList.txt change GIT_TAG to a later release - https://github.com/aws/aws-sdk-cpp/releases Edit: This is what was required to compile the aws plugin on 10.5
An upstream bug report and confirmation of the functional test of this build patch would be appreciated. |
Your patch worked perfectly. Thank you for your effort. I will make sure to put in a bug report upstream. Here is a temporary solution based on #246 and the patch you created.
|
Thanks for writing https://jira.mariadb.org/browse/MDEV-23539. Pushing bugs shows MariaDB the parts of the code that is still being used and cared about. The final solution will probably include a not-null flush implementation and some check to ensure that we haven't broken the build for < cmake-3.0 (which sadly still exists). |
I've fixed the rebuilding of the AWS plugin the upstream source code as of releases 10.4.16 and 10.5.7 |
MDEV-23539 fixed in 10.4.16, 10.5.7 |
Versions:
Docker Compose used to create the issue
When trying to load aws_key_management.so in the logs I received one error line stating
I then used docker exec -it mariadb bash and accessed the database as root and entered
INSTALL PLUGIN aws_key_management SONAME 'aws_key_management.so';
This returned the same error code above.
After some research I installed the package libcurl4 in the container. This allowed me to add the plugin with the INSTALL PLUGIN command.
After the container is removed for an update this change is reverted and displays a new error.
This is caused because mariadb is trying to access the plugin from its mysql:plugin table since we were able to add it to the table in the previous step. This is just the same problem in a different location and is solve by way by updating libcurl in the container again.
I am hoping to use the aws plugin in the container.
The text was updated successfully, but these errors were encountered: