https://bugs.freedesktop.org/show_bug.cgi?id=96516
--- Comment #3 from Alexandre Demers <[email protected]> ---
(In reply to Emil Velikov from comment #2)
> Vedran friendly advice - changing assignee to yourself, limits notifications
> to others as the bug evolves. Some people just state that they're working on
> it, without changing the status. Feel free to proceed as you wish.
>
> Alexandre, I take it that things were working just before that patch ? Are
> you using git checkouts, git archive or any other means to get (and build)
> mesa ?
Building mesa from git through git checkout, pull, and so on. Bisected in no
time because I had just built mesa (64bit) (from culprit commit's parent) when
I saw there was a new commit in the tree once I moved to build the 32 bit
version. Previous commit was building without problem (and is still, I just
tested it). It happened that I had made a clean up of the repo to build against
an updated LLVM and I was lucky to find there was a missing git_sha1.h file.
If needed, I can provide my build script and/or autogen.sh command, but
building from a clean repo should be enough to reproduce the problem.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
