-
-
Notifications
You must be signed in to change notification settings - Fork 14k
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
meson support for clang broken #39936
Comments
On closer examination I see that what's happening is that the meson package hardcodes the stdenv it's built with, therefore breaking use targeting any other stdenv. Was this intended? |
Not necessarily intended, but not sure the nicest solution either. Maybe a way to bundle meson with a particular stdenv? @Ericson2314 , thoughts? |
Can we just not set those vars? The environment should already have them. |
There was definitely a real case where this was needed (cross systemd maybe?) but I don't remember the symptoms. |
I can't even find where Coincidentally I also opened mesonbuild/meson#3282, a while back, which I'm guessing would be a better solution to whatever prompted @shlevy to add those vars. |
I assume |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
This was fixed in 3c00ca0#diff-6b138c4aaf5164baf820a221e2d6dd93 :) |
@Ericson2314 Thanks, that was sorely needed. Fixes my non-cross C++ builds with Meson. |
I can't seem to use
|
Made a new issue, since it only seems to be mesa? |
meson's setup-hook.sh sets
CC=@cc@/bin/cc CXX=@cc@/bin/c++
, clobbering the values provided by the stdenv. This (silently?) breaksclangStdenv
and, because gcc doesn't support-stdlib=libc++
, noisily breakslibcxxStdenv
.This was introduced by 284f75a (cc @shlevy). Never having touched the crosscompilation infrastructure before, I'm not sure what the intended behavior here is, let alone the correct way to do it, but it probably shouldn't be forcing everything to use some arbitrary gcc.
The text was updated successfully, but these errors were encountered: