-
-
Notifications
You must be signed in to change notification settings - Fork 547
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
'atomic' header not found when comiling Odin #3376
Comments
Looks like a typo on the "Getting Started" page. The package you're actually looking for is |
this package is already installed on my system but it still doesn't work :( |
I've had the same issue on Mint. I fix it by installing |
Looking into it some more it seems you should run
Note that this is indeed gcc-12 and not g++-12 as I don't have g++-12 installed on my system and I can build the compiler just fine. |
clang++ -v returned this :
I installed libstdc++-14-dev, and now it works, thank you !! |
Hello, In Linux OpenSuse Tumbleweed with LLVM 18, if it gives us the following error:
We have to issue the following command
We then see that it is the gcc 14 that is in use by clang++ and then we have to install the corresponding gcc version of the libstdc++ : OpenSuse Tumbleweed compilation of Odin with llvm 18 I had to install: libstdc++6-devel-gcc14 do:
then do again:
Note: This was made ( solved ) according the current thread and from the help of Jason and Layton: 'atomic' header not found when comiling Odin #3376 Thank you very much Jason, Best regards, |
Context
I can't manage to compile Odin on Debian testing (Trixie), on a x86_64. But when I compile it inside a docker image (based on the same distribution) it works.
I've tried with llvm-17 and llvm-14, still the same. I've also installed libx32stdc++-12-dev, as stated on the Getting Started page.
odin report
output:generated from the version i built with the docker image :
Expected Behavior
It should compile.
Current Behavior
It doesn't find the "atomic" c++ header.
Failure Information (for bugs)
Steps to Reproduce
I can't reproduce it since it works inside docker, with the same distribution.
Dockerfile used :
Dockerfile.txt
Failure Logs
The text was updated successfully, but these errors were encountered: