-
Notifications
You must be signed in to change notification settings - Fork 717
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
Unable to detect compiler error on armv7 build #2189
Comments
I thin the "detect_compiler_family.c" stuff is cc-rs intentionally causing a compilation failure so it can read the compiler's name from the error output. Even successful builds' logs are littered with that, unfortunately. |
It shouldn't fail though, we only run the pre-process stage to expand the macro and then check for keywords.
I think there's some issues with your gcc installation on macOS? |
How can I check? It seems to run OK when I invoke manually. |
Probably can try manually running the command, the c file can be found in cc-rs |
You mean, manually execute this:
right? I imagine it's this method: detect_family_inner() that does this, and that this:
creates the file and writes the contents into it |
In cc-rs root dir:
So, not sure how to figure out what's wrong with that |
you just need to run arm-linux-gnueabihf-gcc -E src/detect_compiler_family.c we run the compiler with |
Same result. |
you can try https://stackoverflow.com/questions/31045575/how-to-trace-system-calls-of-a-program-in-mac-os-x to trace the syscalls like |
These are all the "cc1"s I can find on my mac:
Trying from here |
Using
I was able to get armv7 working! Now musl fails, but it's a step in the right direction. I'll close this issue now. |
When trying to build ring on my mac, for armv7, with armv gcc tools installed I get this error:
There seems to kind of be two separate possible causes when I dig in a bit:
Investigating the armv7 tools I have installed:
So it's installed.
It's a x86_64 binary on my Apple Silicon Mac.
I haven't been able to force homebrew to install arm64 version of those tools yet.
But it seems to run just fine (rosetta...):
The file that it is trying to compile doesn't exist (I think even generated files should remain after a build fail?):
I'm not sure about the " error trying to exec 'cc1': execvp: No such file or directory" error, if it's for real and how I can investigate it more.
Any ideas?
The text was updated successfully, but these errors were encountered: