-
Notifications
You must be signed in to change notification settings - Fork 595
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
Compilation failed on macOS Sonoma, Apple Silicon #12920
Comments
Can you post the full log here?
Don't know if it's because Apple introduced a new linker in xcode 15.
…On Tue, Oct 17, 2023 at 8:24 PM laofan ***@***.***> wrote:
Describe the bug
Environment:
Homebrew clang version 17.0.2
Target: arm64-apple-darwin23.0.0
Thread model: posix
InstalledDir: /opt/homebrew/opt/llvm/bin
Error message/log
ld: warning: -bind_at_load is deprecated on macOS
ld: warning: -bind_at_load is deprecated on macOS
ld: multiple errors: archive member '/' not a mach-o file in '~/risingwave/target/debug/build/protobuf-src-d9b7156dc4fddede/out/install/build/src/.libs/libprotobuf.a'; archive member '/' not a mach-o file in '~/risingwave/target/debug/build/protobuf-src-d9b7156dc4fddede/out/install/build/src/.libs/libprotobuf.a'; archive member '/' not a mach-o file in '~/risingwave/target/debug/build/protobuf-src-d9b7156dc4fddede/out/install/build/src/.libs/libprotoc.a'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [protoc] Error 1
make: *** [install-recursive] Error 1
thread 'main' panicked at ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/autotools-0.2.6/src/lib.rs:781:5:
command did not execute successfully, got: exit status: 2
build script failed, must exit now
stack backtrace:
0: rust_begin_unwind
at /rustc/62ebe3a2b177d50ec664798d731b8a8d1a9120d1/library/std/src/panicking.rs:619:5
1: core::panicking::panic_fmt
at /rustc/62ebe3a2b177d50ec664798d731b8a8d1a9120d1/library/core/src/panicking.rs:72:14
2: autotools::fail
3: autotools::Config::build
4: build_script_build::main
5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[cargo-make] ERROR - Unable to execute script.
[cargo-make] WARN - Build Failed.
To Reproduce
*No response*
Expected behavior
*No response*
How did you deploy RisingWave?
*No response*
The version of RisingWave
*No response*
Additional context
*No response*
—
Reply to this email directly, view it on GitHub
<#12920>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJBQZNM44SI2N6WDKZF23LDX7Z2G5AVCNFSM6AAAAAA6DYDIQGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DOMRYHAZDKMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi, here are all log
|
"archive member '/' not a mach-o file" - I have the same error when building some small project, seems that macos issue |
Cannot reproduce locally. We also develop RisingWave on M1 mac. Googled and found similar issues on other projects, such as https://stackoverflow.com/a/74335326 There may be some bugs in Rust macos-arm64 target. |
@fuyufjh I've reproduced issue on minimal build example, https://stackoverflow.com/q/77444892/11335766 |
I cannot reproduce on Sonoma. Did you have any config in |
Close for now since no updates and not reproducible. Feel free to leave new comments or create a new issue if there's update! |
Describe the bug
Environment:
Homebrew clang version 17.0.2
Target: arm64-apple-darwin23.0.0
Thread model: posix
InstalledDir: /opt/homebrew/opt/llvm/bin
Error message/log
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: