-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
clang not found #3521
Comments
@karl-cardenas-coding thank you for creating the issue, if someone else faces the same problem, this'll be helpful. |
@mrinalwadhwa happy to help. I have some ideas on how we can get around this issue all together with containers. A really quick and easy way is to have people use the latest Rust container and do all exercises inside the container. That's what I did and it worked great. Long-term, using a platform like Instruqt would probably be the best user experience. That way the user don't have to install anything and can simply go through all exercises in a provided environment. Anyway just some ideas, happy to help explore them. |
Good ideas, there is container image currently that has all our build tools. Give it a try:
|
Oooo that's even better. Adding some introductory text to each lesson wouldn't be to bad of a task. @mrinalwadhwa would you be okay if I opened a PR that provided instructions on how to use the docker image for each lesson? |
@karl-cardenas-coding not at all, we would love to get a PR. |
fixed with #3523 |
When attempting to go through the hello work example on my Mac (M1 Monterey 12.6) I keep getting the same error of
clang not found
. Regardless of the number of times I try to install clang through the automated prompt, the software is not found.Below is a snipped out of the error output:
This error occurs when the
cargo build
command is invoked.Solution
I am sharing the solution here in case others stumble into this error when getting started. It seems like every time the OS version is upgraded, Xtools preference location is not linked to the latest. You can read more about this issue in this thread.
Issue the following command in your Terminal session to resolve the issue:
The text was updated successfully, but these errors were encountered: