the assembler/Makefile will build & execute intel-gen4asm using the target compiler. that means you can't cross-compile it as there's no guarantee the target is producing code that is executable on the current build host. i could post a pathological example (building x86 code on an arm system), but a more realistic one is where you have a kernel running x86_64 and it only supports x86_64 (so 64-bit, not x86/32-bit or x32). when it attempts to execute the assembler, it fails with: intel-gpu-tools-1.7: make[3]: ../../assembler/intel-gen4asm: Command not found i guess assembler/Makefile.am needs some hacking so it uses BUILD_CC/BUILD_CFLAGS/etc... instead of the default CC/CFLAGS/etc...
I guess Thomas could fix this pretty easily...
The assembler location can be set by overriding the value of the GEN4ASM variable when running make. During cross compilation, this should be set to the location of intel-gen4asm that will execute on the build host.
this is not how packages generally work to support cross-compiling. it should build a local copy for its local one-off usage using BUILD_CC. intel-gen4asm is not a standard tool that is reasonable to expect people build & install ahead of time a matching copy.
Assigning to Daniela to check this issue with Marius
Marius, Daniela, is there any update here?
To reflect reality: RESOLVED WONTFIX. Upstream now also has meson build as an alternative to autotools. Might help, might not.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.