It was a very bad idea to use #include "../e_os.h" -- when this occurs
authorBodo Möller <bodo@openssl.org>
Fri, 21 May 1999 11:16:48 +0000 (11:16 +0000)
committerBodo Möller <bodo@openssl.org>
Fri, 21 May 1999 11:16:48 +0000 (11:16 +0000)
commit7e701817234ff2be2a745fc63f32ccb5e874854c
tree9fabfb74c7cfdd98d897ce0f0f43efe42996b9d9
parentd76c85a301f0ab5ff74b54f841cf5db70916dbba
It was a very bad idea to use #include "../e_os.h" -- when this occurs
in cryptlib.h (which is often included as "../cryptlib.h"), then the
question remains relative to which directory this is to be interpreted.
gcc went one further directory up, as intended; but makedepend thinks
differently, and so probably do some C compilers.  So the ../ must go away;
thus e_os.h goes back into include/openssl (but I now use
#include "openssl/e_os.h" instead of <openssl/e_os.h> to make the point) --
and we have another huge bunch of dependency changes.  Argh.
40 files changed:
Makefile.org
apps/Makefile.ssl
apps/apps.h
apps/eay.c
crypto/Makefile.ssl
crypto/asn1/Makefile.ssl
crypto/bio/Makefile.ssl
crypto/bn/Makefile.ssl
crypto/bn/bntest.c
crypto/buffer/Makefile.ssl
crypto/cast/Makefile.ssl
crypto/cast/cast_lcl.h
crypto/conf/Makefile.ssl
crypto/cryptlib.h
crypto/des/Makefile.ssl
crypto/dh/Makefile.ssl
crypto/dsa/Makefile.ssl
crypto/err/Makefile.ssl
crypto/evp/Makefile.ssl
crypto/lhash/Makefile.ssl
crypto/md2/Makefile.ssl
crypto/mdc2/Makefile.ssl
crypto/objects/Makefile.ssl
crypto/pem/Makefile.ssl
crypto/pkcs12/Makefile.ssl
crypto/pkcs7/Makefile.ssl
crypto/rand/Makefile.ssl
crypto/rand/md_rand.c
crypto/rand/randfile.c
crypto/rsa/Makefile.ssl
crypto/rsa/rsa_oaep_test.c
crypto/stack/Makefile.ssl
crypto/txt_db/Makefile.ssl
crypto/x509/Makefile.ssl
crypto/x509v3/Makefile.ssl
rsaref/Makefile.ssl
ssl/Makefile.ssl
ssl/ssl_locl.h
ssl/ssltest.c
test/Makefile.ssl