so it seems to me that musl-gcc prints the wrong library search paths and that's why meson thinks the library exists? Why does meson not believe the result of the actual compilation with -lreadline? Or am I holding the cross file wrong somehow?
Expected behavior
The library is not found.
system parameters
Is this a cross build or just a plain native build (for the same computer)? cross
Describe the bug
Library is found when it shouldn't be found.
To Reproduce
I am using
musl-gcc
from themusl
Arch Linux package with the following cross file:Consider the following project:
Configuring the project shows:
but the log shows:
I am seeing this in the logs:
so it seems to me that
musl-gcc
prints the wrong library search paths and that's why meson thinks the library exists? Why does meson not believe the result of the actual compilation with-lreadline
? Or am I holding the cross file wrong somehow?Expected behavior
The library is not found.
system parameters
meson --version
: 1.4.0