From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Building mesa on arm and aarch64 platforms fail
Date: Fri, 03 Nov 2023 19:59:16 +0100 [thread overview]
Message-ID: <20231103185916.biIqK9FrDCEmXSzRa5qmqYM7D50UyVCrJm0GdjP7izI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46674@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2780 bytes --]
Closed issue by SpidFightFR on void-packages repository
https://github.com/void-linux/void-packages/issues/46674
Description:
Discussed here https://github.com/void-linux/void-packages/pull/46635
Now mesa builds work for both musl and glibc, even i686, yet it seems the modifications have brought a new issue to #46172:
<details><summary>Error when building for arm and aarch64 platforms</summary>
```
[2474/2653] Linking target src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0
FAILED: src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0
aarch64-linux-gnu-c++ -o src/gallium/targets/opencl/libMesaOpenCL.so.1.0.0 -L/usr/aarch64-linux-gnu/usr/lib -I/usr/aarch64-linux-gnu/usr/include -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libMesaOpenCL.so.1 -Wl,--whole-archive src/gallium/frontends/clover/libclover.a -Wl,--no-whole-archive -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv8-a -ffile-prefix-map=/builddir/mesa-23.1.9/build=. -Wl,-rpath,/usr/aarch64-linux-gnu/usr/lib64:/usr/lib -Wl,-rpath-link,/usr/aarch64-linux-gnu/usr/lib64 -Wl,-rpath-link,/usr/lib src/gallium/auxiliary/pipe-loader/libpipe_loader_dynamic.a src/loader/libloader.a src/util/libxmlconfig.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/util/libmesa_util_sse41.a src/c11/impl/libmesa_util_c11.a src/gallium/auxiliary/libgallium.a src/compiler/nir/libnir.a src/compiler/libcompiler.a src/gallium/frontends/clover/libclllvm.a src/gallium/frontends/clover/libclspirv.a src/gallium/frontends/clover/libclnir.a -Wl,--gc-sections -Wl,--version-script /builddir/mesa-23.1.9/src/gallium/targets/opencl/opencl.sym /usr/aarch64-linux-gnu/usr/lib/libz.so -pthread -lm /usr/aarch64-linux-gnu/usr/lib/libzstd.so /usr/aarch64-linux-gnu/usr/lib64/libelf.so /usr/lib/libclang-cpp.so /usr/aarch64-linux-gnu/usr/lib64/libdrm.so /usr/aarch64-linux-gnu/usr/lib64/libexpat.so /usr/aarch64-linux-gnu/usr/lib64/libxcb-randr.so -L/usr/lib -lLLVM-15 -lsensors -L/usr/lib -lLLVM-15 /usr/aarch64-linux-gnu/usr/lib/libLLVMSPIRVLib.so /usr/aarch64-linux-gnu/usr/lib64/libSPIRV-Tools-opt.a /usr/aarch64-linux-gnu/usr/lib64/libSPIRV-Tools.a /usr/aarch64-linux-gnu/usr/lib64/libSPIRV-Tools-link.a -Wl,--end-group
[cc-wrapper] ignoring -L/usr/lib
[cc-wrapper] ignoring -L/usr/lib
/usr/lib/gcc/aarch64-linux-gnu/12.2.0/../../../../aarch64-linux-gnu/bin/ld: /usr/lib/libclang-cpp.so: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
[2475/2653] Generating src/gallium/frontends/rusticl/rustmod-bindgen-rusticl_opencl_bindings.h with a custom command
ninja: build stopped: subcommand failed.
```
</details>
Is there some kind of patch i can try to make for it to work ?
next prev parent reply other threads:[~2023-11-03 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 8:02 [ISSUE] Building mesa on arm and aarch64 platforms fail since wrappers/cross-cc modifications SpidFightFR
2023-10-14 8:04 ` classabbyamp
2023-10-14 8:05 ` SpidFightFR
2023-10-14 8:34 ` sgn
2023-10-14 10:08 ` Johnnynator
2023-10-14 11:27 ` SpidFightFR
2023-10-14 11:27 ` SpidFightFR
2023-10-16 12:21 ` SpidFightFR
2023-10-16 19:43 ` Building mesa on arm and aarch64 platforms fail SpidFightFR
2023-10-24 2:02 ` zlice
2023-10-26 13:03 ` SpidFightFR
2023-11-03 16:10 ` mhmdanas
2023-11-03 18:59 ` SpidFightFR [this message]
2023-11-03 18:59 ` SpidFightFR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231103185916.biIqK9FrDCEmXSzRa5qmqYM7D50UyVCrJm0GdjP7izI@z \
--to=spidfightfr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).