Open gillesgui opened 1 year ago
Hi @gillesgui
This seems an issue related to the GCC recipe and not to the Conan client, so let me transfer it to the conan-center-index repository.
Hi @gillesgui - Thanks again for reporting the issue.
Just a follow-up to get more context about your use case, and to know if you're completely stuck with this failure. Is it not possible to install directly the GCC 11.3.0 compiler in your system via apt
or something similar? Or do you need to use this recipe for another reason?
Hi,
Sorry I didn't follow-up on this, lots of things going on in October.
I found the solution to my issue, and can't really figure out the logic behind.
For gcc 11.3.0 to build properly, I need the compiler.cppstd
statement to be removed from the profile I use. I tried keeping it with several values (11, gnu11, 14, etc.), nothing worked. The only final solution was to remove it in a specific profile I use for building gcc.
If someone knows the reason why, I would be interested.
What is your question?
HI,
I am trying to compile GCC using the official recipe and Conan 2.0.13. My target is 11.3.0 but I have also tried 12.2.0 with the same result.
My build environement is a Alma 8 docker image, fully up to date. I am using stock GCC version and a failry simple profile (only specific thing is I set cppstd to 11 to comply with gcc request):
Every build attempt ends up with the same error:
For some reason only /lib is used as a system path for shared libs. No search is done in /lib64. I've tried a few tricks (with no result) but I have to admit I am a bit confused. Shouldn't there be an easy way to make sure /lib64 is used for resolving those libs (especially when we are not cross-compiling)?
I hope I haven't missed the piece of documentation covering this.
Thankq for your help!
Have you read the CONTRIBUTING guide?