And here's the ticket for meson where this issue originates:
https://github.com/mesonbuild/meson/issues/11043
Apparently llvm-config is not the only, or even the recommended way to
get settings, it's just that meson is using it instead of relying
entirely on cmake configs.
Alex
On Mon, 14 Nov 20
Can also confirm that patch worked for me
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173248):
https://lists.openembedded.org/g/openembedded-core/message/173248
Mute This Topic: https://lists.openembedded.org/mt/95018621/21656
Group Owner: opene
Anyway. I filed an upstream ticket:
https://github.com/llvm/llvm-project/issues/58984
Alex
On Mon, 14 Nov 2022 at 14:50, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> On Mon, 14 Nov 2022 at 14:41, Richard Purdie
> wrote:
>
> > The trouble is how many people are ever going to check whe
On Mon, 14 Nov 2022 at 14:41, Richard Purdie
wrote:
> The trouble is how many people are ever going to check whether the
> output of llvm-config changes? We really need to work with upstream to
> make this util cross safe...
Yes, by making it a thin wrapper over pkg-config. I am completely
baffl
On Mon, 2022-11-14 at 14:35 +0100, Alexander Kanavin wrote:
> Sadly the magic is not perfect: llvm-config contains a hardcoded
> value for the libdir from the native configuration, and things will
> break if the target build installs libraries somewhere else (e.g. lib64).
>
> llvm-config in target
Sadly the magic is not perfect: llvm-config contains a hardcoded
value for the libdir from the native configuration, and things will
break if the target build installs libraries somewhere else (e.g. lib64).
llvm-config in target bindir also needs a rpath adjustment,
otherwise it simply won't even
