-
Notifications
You must be signed in to change notification settings - Fork 37
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
Build duckdb_java linux-amd64-musl #120
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main question: can we get away from static linking the libc++ ?
I see that working with, question is if we can manage without.
I think in general this will not work because the standard alpine distribution doesn't include these libraries. Not linking it means requiring users to always install them in their Alpine containers when they want to use duckdb. This error happened trying to run duckdb (libstdc++ and libgcc linked) in the standard Metabase container which uses alpine, and loading httpfs (no libstdc++ and libgcc linked). Also this does mean the extensions need to have statically linked libstdc++ and libgcc. Idk if there's a better solution here. |
But I think the problem here is that v1.1.2 has no concept (yet) of musl. Would it be possible to run the same workflow again using a recent duckdb commit (such as 09cef57892 the one currently backed in duckdb-java) |
I tried this again on this branch and it still fails |
Build duckdb_java for Alpine linux on amd64
(arm64 is possible but takes 4+ hours on the default GHA runner, so skipping for now)