Summary: | sha1.c:37: error: 'SHA1_CTX' undeclared (first use in this function) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | medium | CC: | cworth, jfonseca, jsg |
Version: | git | Keywords: | regression |
Hardware: | x86-64 (AMD64) | ||
OS: | OpenBSD | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vinson Lee
2015-01-17 01:16:16 UTC
Thanks for the bug report. I don't have access to an OpenBSD system. Can you look into <sha1.h> and see what type is expected by SHA1Init() and friends? -Carl SHA1_CTX is defined in sha1.h http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/include/sha1.h?rev=HEAD&content-type=text/plain The xserver code this was based off builds fine so there must be a Mesa specific problem here. If I rename util/sha1.h to util/xsha1.h matching the xserver name the correct sha1.h is picked up. Otherwise <sha1.h> picks up util/sha1.h I think that for src/util either we: - name headers as prefix_foo.h and include them as include "prefix_foo.h" - or we always include the directory name include "util/foo.h" Naming headers as foo.h and including as "foo.h" is bound to cause conflicts. I also think that util might not be a good prefix for this. I'd suggest we rename src/util to for exmaple src/cgr -- for "common graphics runtime". commit 3b8ccca8a3b5e03829fba7cdb57b49fc10917954 Author: Carl Worth <cworth@cworth.org> Date: Mon Jan 19 10:49:41 2015 -0800 Rename sha1.c and sha1.h to mesa-sha1.c and mesa-sha1.h The filename of sha1.h was conflicting with the system-provided sha1.h, (and in some confiurations, our sha1.c was unsuccessfully attemping to include "sha1.h" and <sha1.h> as two different files). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=88523 I just pushed the commit mentioned above and I believe it will fix this bug. Please feel free to re-open the bug report if there is still any problem. -Carl |
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.