-
Notifications
You must be signed in to change notification settings - Fork 14
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
is gcc supported for client applications? #361
Comments
when I use a
The same seems to happen when I compile the client application with Only when I use clang15 that was found during compilation of OI for its internal jit compiler for both, the
Is this expected from your POV, i.e. does one have to use the same clang for OI JIT, |
Thanks massively @milianw for doing all this work and helping OI greatly! As @JakeHillion said to you in another issue, you are bearing the brunt of the pain being the first contributor and outside Meta user of OI. We will definitely do our utmost to make sure you get to a place where OI is as useful to you as it is to us. Please bear with us in the coming days and weeks as the team has a few big OI projects internally that we're wrestling with and we're also at CppCon in a few weeks. I don't understand what is going off in your environment and maybe What I can do though is to take a look through some debug and try to figure it from there. if you have time could you do the above clang16++ oid invocation (the failing one) as well as the clang15 one (the successful one) but add the following flags to the oid invocation: Just let me know if you have any questions. |
I'm trying to run oid for the first time, I did this:
which gives me
but when I try this on a simple example compiled with g++, I get:
these are seemingly due to the jit compiler trying to use the headers from g++, which is not a good idea, as these headers are g++ specific and not clang compatible. We have had similar issues when trying to parse C++ code in cmake projects build with g++ in kdevelop. There, we can hack around this by always using the clang provided system headers and then doing some hackery to make the rest of the code still assume it's using g++.
But with my still very limited understanding of OI, I'm unsure if that's an option. Does that mean one cannot use OI at all on code compiled with g++? That would be a pity, because while I might easily use g++ for my own code, all system libraries are compiled with g++ on most distributions...
The text was updated successfully, but these errors were encountered: