meson: 'meson scan-build' is broken

Describe the bug From #8707, meson scan-build is broken since https://github.com/mesonbuild/meson/commit/e81acbd6069e8c1ae8e3be7bb83ddc239009d42d. ~~This commit should be reverted.~~ Sorry, I see the regression from that commit was already fixed, and the real commit that introduced this bug is hidden by that one…

To Reproduce See #8707

Expected behavior See #8707

system parameters See #8707

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 22 (5 by maintainers)

Commits related to this issue

backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to dcbaker/meson by dcbaker 3 years ago
backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to mesonbuild/meson by dcbaker 3 years ago
backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to bonzini/meson by dcbaker 3 years ago
backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to mesonbuild/meson by dcbaker 3 years ago
backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to mesonbuild/meson by dcbaker 3 years ago
backends/ninja: only pass project specific arguments to scan-build Currently all arguments are being passed to scan-build as part of the refactoring of how Meson internally handles arguments, but tha... — committed to mesonbuild/meson by dcbaker 3 years ago

Most upvoted comments

Seems I wasted a lot of time typing up this intro to fenv, but that’s fine.

It’s alright, I am going to steal this for docs!

alatiera on Jul 1, 2021

Please note that if not fixed soon, freedesktop-sdk 21.08 (and therefore both GNOME 41 and GNOME 42) will likely ship with meson 0.56 instead of the latest and greatest.

does this contain enough information for Meson upstream to debug further or is a more fine-grained reproducer necessary?

I can explain how to test things under flatpak if needed, but nothing else should be necessary as the reproducer is simply meson scan-build with any project.

mcatanzaro on Jun 30, 2021

it shows -Dbuild.c_link_args=['"'"'-l/app/lib'"'"']' at the end there in your first paste. Where is this coming from? It has absolutely crazy amount of quoting in addition to having clearly wrong flag.

That is coming from meson itself. After the bad revision, it adds that nonsense flag when it internally invokes itself to run scan-build. There are no changes to my environment between the logs I’ve shown above other than meson version.

mcatanzaro on Jun 17, 2021

Let me see how hard it is to do a bisect between e81acbd and f31ffaa, with e81acbd reverted to avoid hitting the “invalid literal for int() with base 8: ‘18’” issue. If there aren’t difficult conflicts, then that should reveal which commit is to blame…

Too many conflicts. I will leave this for meson developers, sorry.

mcatanzaro on Jun 2, 2021