Red Hat Bugzilla – Bug 153228
opensslconf.h uses include "", even though it's a system header
Last modified: 2007-11-30 17:11:03 EST
Description of problem:
If you compile an openssl using application (for MD5/SHA1) using just
pkg-config to get the CFLAGS you get...
In file included from /usr/include/openssl/e_os2.h:56,
/usr/include/openssl/opensslconf.h:13:30: opensslconf-i386.h: No such file or
This is because pkg-config --cflags doesn't produce -I/usr/include/openssl as
an option. Adding this to the .pc file makes everything work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Compile application
vstr-1.0.14 (see freshmeat) shows this problem.
No, this wouldn't be right. Normally everything works as it should, because the
opensslconf-i386.h is included by #include "opensslconf-i386.h" from
opensslconf.h which lies in the same directory. You can try that by simple
compiling any test.c which has #include <openssl/sha.h> without any -I options
Is it possible that you have -I- option on the gcc command line?
Yes, you are corrrect, on both counts.
For some reason, I just saw the error message and didn't check how I was
including the header.
So can we get the file opensslconf.h changed from...
No, this would mean exactly that the #includes wouldn't work.
It would work if it was changed to #include <openssl/opensslconf-i386.h> however
I don't want to change it as the current situation works well and I'm not sure
if some other obscure cases wouldn't break.
"""It would work if it was changed to #include <openssl/opensslconf-i386.h>
however I don't want to change it as the current situation works well and I'm
not sure if some other obscure cases wouldn't break."""
By "works well" I assume you meant "doesn't work at all", if you use -I-. I
can't see what could possibly break ... but I guess I'm forced to work around it
if you refuse to fix it.