mesa: 9075823c17280d36ca2ba2e98ec93fb097801593 (master 10.5.0-devel)
OpenBSD build error
checking for PTHREAD_PRIO_INHERIT... yes
checking for SHA1Init... yes
checking for CC_SHA1_Init... no
checking for wincrypt.h... no
checking for SHA1Init in -lmd... no
checking for LIBSHA1... no
checking for nettle_sha1_init in -lnettle... no
checking for gcry_md_open in -lgcrypt... no
checking for SHA1_Init in -lcrypto... yes
checking for OPENSSL... yes
checking for SHA1 implementation... libc
checking for LIBDRM... yes
sha1.c: In function '_mesa_sha1_init':
sha1.c:37: error: 'SHA1_CTX' undeclared (first use in this function)
sha1.c:37: error: (Each undeclared identifier is reported only once
sha1.c:37: error: for each function it appears in.)
sha1.c:37: error: 'ctx' undeclared (first use in this function)
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?
SHA1_CTX is defined in sha1.h
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
- or we always include the directory name
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".
Author: Carl Worth <firstname.lastname@example.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).
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.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.