aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/scripts/gettext.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2022-05-26 14:36:03 -0400
committerEli Schwartz <eschwartz@archlinux.org>2022-05-29 11:41:55 -0400
commit6757e4f07c9f780ed33b21ac15f5f5727a6a10f3 (patch)
tree88102ab96194388207b3d462c700175dd782f654 /mesonbuild/scripts/gettext.py
parent704cd1a79d69c3619b0e26bda6b52c11d0da3674 (diff)
downloadmeson-6757e4f07c9f780ed33b21ac15f5f5727a6a10f3.zip
meson-6757e4f07c9f780ed33b21ac15f5f5727a6a10f3.tar.gz
meson-6757e4f07c9f780ed33b21ac15f5f5727a6a10f3.tar.bz2
linkers: try a bit harder to autodetect the correct linker id
mingw GCC using ld.bfd emits diagnostics that include "-plugin-opt=-pass-through=-lmoldname" and this triggers a match for mold when it should not. Instead, always check the very beginning of the output for the linker id. This is pretty consistent: - it is always on stdout - GCC may put additional things on stderr we don't care about - swift is bizarre and on some OSes redirects the linker stdout to swiftc's stderr, but it will still be the only stderr; we didn't even check stderr at all until commit 712cbe056811ebdf0d7358ba07a874717a1c736f For gold/bfd linkers, the linker id is always the *second* word, after the legally mandated "GNU" we already check for.
Diffstat (limited to 'mesonbuild/scripts/gettext.py')
0 files changed, 0 insertions, 0 deletions