[Mesa-dev] Trouble with missing git_sha1.h when building from a fresh tree
emil.l.velikov at gmail.com
Thu Jun 16 19:43:00 UTC 2016
Hi Haixia Shi,
On 16 June 2016 at 19:46, Haixia Shi <hshi at chromium.org> wrote:
> Posting a question in case someone already know the issue.
> I'm observing "missing git_sha1.h" errors sometime after Emil's git_sha1.h
> patches by May 31st. This is not fixed at TOT with the latest patches on
> The problem only happens if src/git_sha1.h doesn't exist already. I just
> need to put a dummy git_sha1.h file there to work around the error.
> There's a similar bug filed
> (https://bugs.freedesktop.org/show_bug.cgi?id=50976) but the fix for that
> one patches src/Makefile directly, whereas my build flow only requires
The bug report in question is ancient and doesn't reflect what we have atm.
I'd imagine that you're using one of the following two:
- git archive tarballs, or
- you don't have access to the 'git' executable after the checkout
(using chroot and//or other).
In case of the latter I have a patch that I'm testing atm. Sadly it
won't 'fix' the issue, as that is a deliberate change.
Namely: one should _really_ be using either a proper git checkout
(with the .git folder) or a tarball produced by `make dist' (like the
In the case that you use one of the top two, I'd suggest adding the
following or one that produces similar result.
echo '#define MESA_GIT_SHA1 "git-$mesa-checkout-sha1"' > mesa/src/git_sha1.h
Obviously you should already know the actual sha (mesa-checkout-sha1).
P.S. What exactly does TOT mean ?
More information about the mesa-dev