-
Notifications
You must be signed in to change notification settings - Fork 335
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
GLIBC not found while building against Amazon Linux 2 - x86_64 #467
Comments
I think you've bumped into this issue: ziglang/zig#9485 I'm trying to find a way to mitigate that. @messense documented that as one of the caveats of using Zig: https://github.com/messense/cargo-zigbuild#caveats |
@calavera I think the problem is that cargo-lambda disables zig linker when compiling from x86_64 to x86_64: https://github.com/cargo-lambda/cargo-lambda/blob/b9b6a1993ad7ae5563d8c1a82b023396bfaf2a31/crates/cargo-lambda-build/src/lib.rs#L72 |
oh yeah, you might be right. And the problem is that if we don't disable it, you need to use a nightly build, is that still the case @messense?
|
@calavera I'm working on a hack to enable that feature on stable Rust: rust-cross/cargo-zigbuild#32 |
Released in v0.8.5. |
Thanks @messense I'll test it today. @fancywriter, as a "workaround" until I release a new version of cargo-lambda, you can also build and deploy using ARM as the architecture if your code is not dependent on X86_64 in any way.
|
I just published cargo-lambda 0.7 that mitigates this problem. |
Hello!
I am trying to build example from README. It is said it's recommended to use Amazon Linux 2 runtime because it's "easier to build", that's what I am trying to do.
My Cargo.toml:
src/main.rs
is the same as in README.Building with command (from the Linux laptop with the same x86_64 architecture,
uname -m
gives mex86_64
)Success. Than deploying with command
Also success.
But later when I am trying to invoke this function
, it doesn't work, it gives
When trying to search some logs, I found three lines
I am using rust-1.59.0.
What did I do wrong?
The text was updated successfully, but these errors were encountered: