New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/issues/27437#issuecomment-751384475

Comment:
The culprit seems to be the `INTROSPECTION_GIRDIR` and `INTROSPECTION_TYPELIBDIR` variables in every `Makefile` which are set using the pkg-config-wrapper in `configure` via:
```
INTROSPECTION_GIRDIR=`$PKG_CONFIG --define-variable=datadir="${_GI_EXP_DATADIR}" --variable=girdir gobject-introspection-1.0`
INTROSPECTION_TYPELIBDIR="$($PKG_CONFIG --define-variable=libdir="${_GI_EXP_LIBDIR}" --variable=typelibdir gobject-introspection-1.0)"
```
which adds `$XBPS_CROSS_BASE`.

I don’t really have a solution, just a different hack: run
```
sed -e "s,^\(INTROSPECTION_GIRDIR\s*=\s*\)${XBPS_CROSS_BASE}\(.*\),\1\2," -i $(find . -name Makefile)
sed -e "s,^\(INTROSPECTION_TYPELIBDIR\s*=\s*\)${XBPS_CROSS_BASE}\(.*\),\1\2," -i $(find . -name Makefile)
```
between the `build` and `install` phase; either by replacing the hack in the `98-fixup-gir-path.sh`-hook or e.g. in a custom `pre_install()` (and removing the hook).

I haven’t tested if these variables are relevant for building the package, yet; if not then a clean solution could be adjusting the pkg-config-wrapper to not add `$XBPS_CROSS_BASE` to `girdir` and `typelibdir` queries.