Summary: | MESA_GIT_SHA1_OVERRIDE is ignored upon Mesa build | ||
---|---|---|---|
Product: | Mesa | Reporter: | network723 |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
Severity: | minor | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
network723
2019-07-14 09:49:40 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. (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? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/943. |
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.