-
Notifications
You must be signed in to change notification settings - Fork 85
Cannot compile rust-htslib with x86_64-unknown-linux-musl (needed for AWS Lambda runtimes) #179
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
Comments
I think there are issues even before you get to
|
True to all you said. I'll be digging on the |
Back to this after a while... that was a not-so-INVALID issue, the path for MUSL + C bindings in Rust is pretty tortuous these days, see: I'm planning to file an idea/pre-RFC to Rust internals, inquiring why Thanks @luizirber for reviewing this back in January ;) |
Hello rust-htslib,
I'm currently using this crate to simply read a BAM header. My crate builds fine on my machine (running OSX Catalina, also tested on a regular Linux machine):
The problem comes when I try to cross-compile it to run on AWS Lambda... it looks like the linking phase fails for the few rust-htslib functions I need to parse that BAM header:
Here's the full output while using serverless.com (lambda) deployment tool:
I don't have much experience with the rust-htslib approach to cbindgen & co, but if you could provide some pointers on what you think could be wrong here, I'd be happy to investigate further.
In order to reproduce this issue, assuming you are on Linux:
If something fails on your machine, please take a look at this blogpost which contains additional directions should you encounter some difficulty with the cross-compiling toolchain.
I would like to fix this before jumping into another rust implementation to just read the first BGZF block of a BAM file to get the header :-S
The text was updated successfully, but these errors were encountered: