Created attachment 602946 [details] meson-bisect.sh Building any meson project produces the above error message (`ERROR: Unable to determine linker`). I bisected meson using the attached script as follows: > git clone https://github.com/mesonbuild/meson.git meson > cd meson > git checkout 0.53.0 > git bisect bad > git bisect good 0.52.1 > git bisect run ~/meson-bisect.sh That came back with the following: > > ef9aeb188ea2bc7353e59916c18901cde90fa2b3 is the first bad commit > commit ef9aeb188ea2bc7353e59916c18901cde90fa2b3 > Author: Dylan Baker <dylan@REDACTED> > Date: Tue Nov 19 09:30:46 2019 -0800 > > Allow selecting the dynamic linker > > This uses the normal meson mechanisms, an LD environment variable or via > cross/native files. > > Fixes: #6057 > > docs/markdown/snippets/linker_override.md | 17 +++ > mesonbuild/compilers/compilers.py | 6 + > mesonbuild/compilers/mixins/gnu.py | 4 + > mesonbuild/compilers/mixins/visualstudio.py | 4 + > mesonbuild/compilers/rust.py | 6 +- > mesonbuild/envconfig.py | 2 + > mesonbuild/environment.py | 206 +++++++++++++++++----------- > mesonbuild/linkers.py | 28 ++-- > run_unittests.py | 4 +- > 9 files changed, 182 insertions(+), 95 deletions(-) > create mode 100644 docs/markdown/snippets/linker_override.md > bisect run success
This may be related? https://github.com/mesonbuild/meson/issues/6442
I already p.masked it on these basis and upstream information. Guess the p.mask information could be updated with this bug number now :)
*** Bug 705208 has been marked as a duplicate of this bug. ***
*** Bug 705210 has been marked as a duplicate of this bug. ***
0.53.1 is now in the tree. Let me know if this is still an issue.