flowistry: Prebuilt Flowistry binaries have incorrect rustc library paths on ARM targets

Hi,

The extension seems to install fine (there’s the Flowistry context menu), but choosing any action opens the pane with:

Flowistry could not run because your project failed to build with error:
error: failed to run `rustc` to learn about target-specific information

Caused by:
process didn't exit successfully: `/Users/me/.cargo/bin/flowistry-driver rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (signal: 6, SIGABRT: process abort signal)
--- stderr
dyld: Library not loaded: @rpath/librustc_driver-ac2715475dad8249.dylib
    Referenced from: /Users/me/.cargo/bin/flowistry-driver
    Reason: image not found

OS: macOS 11.6 (Darwin arm64 20.6.0) VSCode: 1.62.0-insider

I searched through closed isues and couldn’t find one like this. Thanks in advance!

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 22 (11 by maintainers)

Most upvoted comments

Ah ok I think I see the issue. The M1 build is happening on a Github Actions runner that’s x86_64. So the actual compiler itself is built for x86_64. Flowistry is getting cross-compiled to ARM, but Rustc is still inserting the dylib paths as if the binary is being run on x86_64 and not ARM.

I will investigate a solution, thank you both for your patience and support.

willcrichton on Feb 23, 2022

that did the trick, thanks @willcrichton!

scullionw on Feb 23, 2022