FS#61056 - [lib32-mesa] Use meson cross-compile file instead of env variables
Attached to Project:
Community Packages
Opened by Alexandre Demers (oxalin) - Thursday, 13 December 2018, 07:01 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 13 December 2018, 07:34 GMT
Opened by Alexandre Demers (oxalin) - Thursday, 13 December 2018, 07:01 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 13 December 2018, 07:34 GMT
|
Details
Description:
PKGBUILD uses the following before calling meson: " build() { export CC="gcc -m32" export CXX="g++ -m32" export PKG_CONFIG_PATH="/usr/lib32/pkgconfig" export LLVM_CONFIG="/usr/bin/llvm-config32" [...] " Instead, when using meson, a cross-compilation file should be used with the option "--cross-compile". For cross-compiling on x86_64 to x86, you could use the file provided by AUR package meson-cross-x86-linux-gnu or create a new one from it. Additional info: * package version(s): 18.3.1 * config and/or log files etc.: see AUR package meson-cross-x86-linux-gnu for cross-compilation |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 13 December 2018, 07:34 GMT
Reason for closing: Works for me
Additional comments about closing: No explanation why we should care, especially given the package apparently works fine.
It's certainly a very pathetic build system that doesn't support such common environment variables as CC, which I guess is why meson supports it...
Thursday, 13 December 2018, 07:34 GMT
Reason for closing: Works for me
Additional comments about closing: No explanation why we should care, especially given the package apparently works fine.
It's certainly a very pathetic build system that doesn't support such common environment variables as CC, which I guess is why meson supports it...