[crypto] Skip platform linux_amd64_musl #262
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem is currently: ``` -- Found Rust: /root/.rustup/toolchains/stable-x86_64-unknown-linux-musl/bin/rustc (found version "1.83.0") CMake Error at /duckdb_build_dir/corrosion/cmake/Corrosion.cmake:79 (message): Target x86_64-unknown-linux-gnu is not installed for toolchain stable-x86_64-unknown-linux-musl. Help: Run `rustup target add --toolchain stable-x86_64-unknown-linux-musl x86_64-unknown-linux-gnu` to install the missing target. Call Stack (most recent call first): /duckdb_build_dir/corrosion/CMakeLists.txt:73 (include) ``` Needs to be likely solved at the toolchain level, possibly in the dockerfile for musl in duckdb/extension-ci-tools.
carlopi
force-pushed
the
no_musl_crypto
branch
from
6836658 to
6ab2fb2
Compare
carlopi
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem is currently:
Needs to be likely solved at the toolchain level, possibly in the dockerfile for musl in duckdb/extension-ci-tools.
@rustyconover