-
Notifications
You must be signed in to change notification settings - Fork 50
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
Issues lurking with gobject-introspection
#196
Comments
Urgh, this may not be an easy fix mesonbuild/meson#6662 |
I don't see how we can give a full path to a linker: https://github.com/mesonbuild/meson/blob/master/mesonbuild/compilers/mixins/gnu.py#L311-L316 |
Ah, you are meant to set the linker flavour with the environment variables...not sure if that means the problem is something else or not |
This may be a false flag, I think introspection is up to something, disabling that with
allowed the package to install |
It is worth noting though that EasyBuild does not currently create compiler wrappers for |
The environment variable tries to map If you want to set a linker that GCC doesn't specifically know about, you probably want |
ld
wrapper used by EasyBuildgobject-introspection
The full error with
specifically, we probably need to take a look inside the python script |
I think this has something to do with the use of |
@ocaisa Can you check if you see the same problem when using |
@boegel It didn't help, and I checked the bash shell at the time the build command is called:
so I'm not sure where exactly things go wrong. |
see also #428 (comment), which suggests that As discussing during today's support meeting, we should check whether the hardcoded The problem here seems to be that Any ideas here @amadio? Possible workaround could be:
|
What is setting |
Sorry for the late reply, I was on vacations during the end of year break. |
The issue pops up at the installation of |
There are a few places in glibc where the shebang is set and that's not prefixified. You will probably observe similar behavior when calling
It only ever showed to be a problem in some very specific testing setups for me, so it was not that high priority... |
So, just to be sure, in principle it would be safe if we would just patch our |
I'm reopening this issue, as we're now seeing similar issues for Pango (#644) and Paraver (#570). We should really fix this in GObject-Introspection itself, maybe using something like the proposed fix in #570 (comment). |
Also GTK3/3.24.39-GCCcore-13.2.0 has the same issue, see #644 (comment). |
I like your fix at the end of #570 (comment), it's simple and can be EESSI-specific if we do it via a hook |
To make it easier to fix via |
Maybe we can test this in a single PR? A hook to patch |
Yep, good idea, I'll try to do that. |
Also fixed for A64FX now via #683 |
With something that was using Meson I was seeing
which I'm guessing meant it was picking the host
ld
and not the EasyBuild wrapper. Looking at the configure step I sawwhich would imply it is using the ld.gold used by gcc (which seems right since it reports 2.37, the version in the prefix, not 2.30 the version in the host).
Anyway, it seemed like a good idea to set the linker directly (as per the docs) with
but actually this throws an error
The text was updated successfully, but these errors were encountered: