Bug 111127 - MESA_GIT_SHA1_OVERRIDE is ignored upon Mesa build
Summary: MESA_GIT_SHA1_OVERRIDE is ignored upon Mesa build
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: Other All
: medium minor
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-14 09:49 UTC by network723
Modified: 2019-07-14 16:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description network723 2019-07-14 09:49:40 UTC
I'm not sure when it happened, but in older Mesa versions, it would include short git commit number into OpenGL profile string if you set MESA_GIT_SHA1_OVERRIDE environment variable during boot (I strip git data to save disk space and make things faster on build VM). But it looks like more recent Mesa git ignores that variable, so it would show up just like "Mesa 19.2.0-devel", no git commit number. Has something changed about that? I couldn't find this in documentation.
Comment 1 Eric Engestrom 2019-07-14 13:39:51 UTC
Nothings changed here. You can check the script yourself, it's really small:
https://gitlab.freedesktop.org/mesa/mesa/blob/master/bin/git_sha1_gen.py#L46

Maybe double check that you didn't make a typo or that it was somehow unset?
Btw, you don't need to set the env var during boot, only for the build, but maybe that was just a typo in your original message.
Comment 2 network723 2019-07-14 16:02:13 UTC
(In reply to Eric Engestrom from comment #1)
> Nothings changed here. You can check the script yourself, it's really small:
> https://gitlab.freedesktop.org/mesa/mesa/blob/master/bin/git_sha1_gen.py#L46

I've checked scripts, export MESA_GIT_SHA1_OVERRIDE is called right before meson invocation, but still no revision number in glxinfo output. Is it possible that meson itself unsets environment?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.