10-22-2020, 03:10 AM
(10-21-2020, 06:54 PM)carlosqueso Wrote:(10-21-2020, 03:02 AM)icecream95 Wrote: Hint to everyone here: This issue isn't going to automatically fix itself.I'm happy to put some time in helping with this, but while I'm fully capable of running commands and determining if something is broken, I'm not a developer. I tried to run the meson command and got asked for a directory. Do I need to navigate somewhere, or should a specify a directory?
I haven't been able to reproduce this myself, so someone here who has the problem will have to help find the problem by bisecting.
You'll have to use git bisect on Mesa, with a "good" commit of ac6b8e42ce2 and a "bad" commit of 20a4235c4c9 (man git-bisect for docs).
Configure Mesa from the build directory like this:
Code:meson -Dgallium-drivers=panfrost,kmsro -Dvulkan-drivers= -Db_ndebug=false --buildtype=plain
Compile and install with `ninja; sudo ninja install`
Install ccache beforehand to speed up the bisect process significantly.
Once an issue is narrowed down to a specific commit, it's usually pretty easy to find what the problem is and fix it.
With a new enough meson, the command should work as is if you're in a 'build' subdirectory of the root Mesa directory.
You should add -Dlibunwind=false to the meson command, though, as on ARM libunwind is broken for many distros.
Note that `git bisect` needs to be run from the root directory of the repository, but you can pass `-C build` to ninja to avoid having to go back into the build directory. You shouldn't have to re-run meson at all while bisecting.