-
Notifications
You must be signed in to change notification settings - Fork 357
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
Segfault on cross compiling to musl #914
Comments
I confirm the problem. I have got the same. |
Im having same issue, but i'm using postgres instead of sqlite. I've not tried the workaround yet. |
I think this comes from a dynamic/static C runtime mismatch, but am not 100% certain. |
It may be helpful to automagically add the "bundled" feature when compiling for musl target - or a similar condition? |
see rusqlite/rusqlite#914 sha256: 684ebc4b8c270fc63beba185f6c54ceeb98734f13aa7aeca9b64acb33432a21c
Potentially related: tonarino/innernet#228 (comment) |
I've also stumbled into a segfault: #1290 (comment). |
Setup
Versions
Feature Flags
Problem Description
When cross compiling to
x86_64-unknown-linux-musl
target diesel segfaults immediately in line: https://github.com/diesel-rs/diesel/blob/bec389a1ea329c161fc7a8fb8df8bea29a3432bf/diesel/src/sqlite/connection/raw.rs#L23Workaround
In #musl IRC I was given the workaround to add:
to
Cargo.toml
solves this issue.So somehow even when cross compiling the libsqlite3-sys is not bundled but dynamically linked which fails.
What are you trying to accomplish?
I want to use musl builds to have a standalone binary of my actix-web app.
Steps to reproduce
I created a minimal example: https://github.com/enaut/musl-segfault-sample
compile and run on linux with:
cargo run --target x86_64-unknown-linux-musl
The text was updated successfully, but these errors were encountered: