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

Circular dependency errors and root module errors should not block the rest of tach check #488

Open
emdoyle opened this issue Dec 19, 2024 · 5 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@emdoyle
Copy link
Member

emdoyle commented Dec 19, 2024

Right now, when we build the 'module tree' from the tach.toml configuration, we validate against circular dependencies and the expected root module treatment (if necessary). However, when these checks fail, we immediately return an error and render it in the CLI.

Instead, the tach check command should continue with a full scan for errors even when these validations fail. The validation errors can be displayed in their own segment of the error output.

@emdoyle emdoyle added enhancement New feature or request good first issue Good for newcomers labels Dec 19, 2024
@tiluckdave
Copy link
Contributor

Hey @emdoyle
I can take this up.

@emdoyle
Copy link
Member Author

emdoyle commented Feb 6, 2025

Great, thanks! Some pretty significant changes merged recently, so make sure you are branched off of the latest main.

@tiluckdave
Copy link
Contributor

yes sure!

@tiluckdave
Copy link
Contributor

Hi @emdoyle

error: linking with `cc` failed: exit status: 1
  |
  = note: env -u IPHONEOS_DEPLOYMENT_TARGET -u TVOS_DEPLOYMENT_TARGET -u XROS_DEPLOYMENT_TARGET LC_ALL="C" PATH="/opt/homebrew/Cellar/rust/1.84.1/lib/rustlib/aarch64-apple-darwin/bin....
...
...

ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I am getting this error. I assumed it should be fixed after updating rust but still there. Can you please help?

@emdoyle
Copy link
Member Author

emdoyle commented Feb 7, 2025

@tiluckdave I am not an Apple Silicon so I won't be able to reproduce your situation, but my guess is that you are likely missing some system libraries. Unfortunately I don't know the full list that you'll need, but generally the linker output should reference specific symbols which you can then brew install.

For what it's worth, we build wheels for Apple Silicon using this runner image, so the software listed there must be sufficient (openssl and pkg-config, plus xcode development tools are all likely required).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants