Skip to content
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

vector failed to execute when target musl #877

Closed
xcaptain opened this issue Sep 17, 2019 · 4 comments

Comments

@xcaptain
Copy link

@xcaptain xcaptain commented Sep 17, 2019

I'm using to cargo build --release --target=x86_64-unknown-linux-musl to build the project but the result won't execute, but the default target works

图片

@mre

This comment has been minimized.

Copy link
Contributor

@mre mre commented Sep 17, 2019

Hum... that doesn't look like a problem with vector, though.
It seems to build just fine so I wonder where it was copying the binary into.
You can try a cargo clean which will remove the target folder and then another build.
Then you can inspect your target folder and see which subfolders it created.

You can verify that you have the correct toolchains with

rustc --print target-list
@binarylogic

This comment has been minimized.

Copy link
Member

@binarylogic binarylogic commented Sep 17, 2019

Hi @xcaptain , is there any reason our pre-built binary won't work for you?

https://packages.timber.io/vector/nightly/vector-nightly-x86_64-unknown-linux-musl.tar.gz

That should be the latest musl build ^

@xcaptain

This comment has been minimized.

Copy link
Author

@xcaptain xcaptain commented Sep 17, 2019

@mre Can you build with cargo build --release --target=x86_64-unknown-linux-musl and run the binary using rustc 1.37 stable? I will check again to see if it's related to my build environment

@xcaptain xcaptain closed this Sep 19, 2019
@mre

This comment has been minimized.

Copy link
Contributor

@mre mre commented Sep 20, 2019

@xcaptain, sorry that I didn't report back.
Maybe this could help you: #826.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.