mirror/openssl
2
0
Fork 0
mirror of https://github.com/openssl/openssl.git synced 2024-11-27 05:21:51 +08:00
Code Issues Packages Projects Releases Wiki Activity
d4443edc57
openssl/crypto/bio/Makefile.ssl

208 lines
9.5 KiB
Makefile
Raw Normal View History

Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
#
# SSLeay/crypto/bio/Makefile
#
DIR= bio
TOP= ../..
CC= cc
INCLUDES= -I.. -I../../include
CFLAG=-g
Support INSTALL_PREFIX for packagers. Submitted by: Reviewed by: PR:
1999-04-30 05:52:08 +08:00
INSTALL_PREFIX=
OPENSSLDIR= /usr/local/ssl
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
INSTALLTOP=/usr/local/ssl
MAKE= make -f Makefile.ssl
Finally lay dependencies to rest (I hope!).
1999-01-20 05:36:31 +08:00
MAKEDEPEND= $(TOP)/util/domd $(TOP)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
MAKEFILE= Makefile.ssl
AR= ar r
CFLAGS= $(INCLUDES) $(CFLAG)
GENERAL=Makefile
TEST=
APPS=
LIB=$(TOP)/libcrypto.a
Change the command line options of mkerr.pl so -static is now default and a -write option is needed to actually change anything. Second attempt at getting rid of ERR, ERRC definitions: it might even work this time :-)
1999-04-25 01:28:43 +08:00
LIBSRC= bio_lib.c bio_cb.c bio_err.c \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
bss_mem.c bss_null.c bss_fd.c \
bss_file.c bss_sock.c bss_conn.c \
bf_null.c bf_buff.c b_print.c b_dump.c \
Add syslogging BIO.
1999-02-23 05:21:08 +08:00
b_sock.c bss_acpt.c bf_nbio.c bss_log.c
Change the command line options of mkerr.pl so -static is now default and a -write option is needed to actually change anything. Second attempt at getting rid of ERR, ERRC definitions: it might even work this time :-)
1999-04-25 01:28:43 +08:00
LIBOBJ= bio_lib.o bio_cb.o bio_err.o \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
bss_mem.o bss_null.o bss_fd.o \
bss_file.o bss_sock.o bss_conn.o \
bf_null.o bf_buff.o b_print.o b_dump.o \
Add syslogging BIO.
1999-02-23 05:21:08 +08:00
b_sock.o bss_acpt.o bf_nbio.o bss_log.o
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
SRC= $(LIBSRC)
Don't install bss_file.c under PREFIX/include/. It was introduced by Eric between SSLeay 0.8 and 0.9 and just looks useless and confusing. Pointed out by: Lennart Bong <lob@kulthea.stacken.kth.se> Submitted by: Ralf S. Engelschall
1999-03-04 15:47:27 +08:00
EXHEADER= bio.h
Make Windows compilers happy. Submitted by:Tom Titchener Reviewed by: PR:
1999-04-15 05:43:02 +08:00
HEADER= bss_file.c $(EXHEADER)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
ALL= $(GENERAL) $(SRC) $(HEADER)
top:
(cd ../..; $(MAKE) DIRS=crypto SDIRS=$(DIR) sub_all)
all: lib
lib: $(LIBOBJ)
$(AR) $(LIB) $(LIBOBJ)
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(RANLIB) $(LIB)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@touch lib
files:
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(PERL) $(TOP)/util/files.pl Makefile.ssl >> $(TOP)/MINFO
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
links:
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
@$(TOP)/util/point.sh Makefile.ssl Makefile
Obey $(PERL) when running util/mklink.pl. Submitted by: Reviewed by: PR:
1999-04-29 20:46:59 +08:00
@$(PERL) $(TOP)/util/mklink.pl ../../include/openssl $(EXHEADER)
@$(PERL) $(TOP)/util/mklink.pl ../../test $(TEST)
@$(PERL) $(TOP)/util/mklink.pl ../../apps $(APPS)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
install:
Don't install bss_file.c under PREFIX/include/. It was introduced by Eric between SSLeay 0.8 and 0.9 and just looks useless and confusing. Pointed out by: Lennart Bong <lob@kulthea.stacken.kth.se> Submitted by: Ralf S. Engelschall
1999-03-04 15:47:27 +08:00
@for i in $(EXHEADER); \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
do \
Support INSTALL_PREFIX for packagers. Submitted by: Reviewed by: PR:
1999-04-30 05:52:08 +08:00
(cp $$i $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i; \
chmod 644 $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i ); \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
tags:
ctags $(SRC)
tests:
lint:
lint -DLINT $(INCLUDES) $(SRC)>fluff
depend:
New Configure option no-<cipher> (rsa, idea, rc5, ...).
1999-04-27 09:14:46 +08:00
$(MAKEDEPEND) $(INCLUDES) $(DEPFLAG) $(PROGS) $(LIBSRC)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
dclean:
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(PERL) -pe 'if (/^# DO NOT DELETE THIS LINE/) {print; exit(0);}' $(MAKEFILE) >Makefile.new
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
mv -f Makefile.new $(MAKEFILE)
clean:
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
rm -f *.o *.obj lib tags core .pure .nfs* *.old *.bak fluff
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# DO NOT DELETE THIS LINE -- make depend depends on it.
Put the dependencies back.
1999-03-06 22:32:48 +08:00
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
b_dump.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
b_dump.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
b_dump.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
b_dump.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
b_dump.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
b_print.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
b_print.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
b_print.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
b_print.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
b_print.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
b_sock.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
b_sock.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
b_sock.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
b_sock.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
b_sock.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bf_buff.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
bf_buff.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
bf_buff.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
bf_buff.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
bf_buff.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
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.
1999-05-21 19:16:48 +08:00
bf_buff.o: ../../include/openssl/e_os.h ../../include/openssl/e_os2.h
bf_buff.o: ../../include/openssl/err.h ../../include/openssl/evp.h
bf_buff.o: ../../include/openssl/idea.h ../../include/openssl/md2.h
bf_buff.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
bf_buff.o: ../../include/openssl/objects.h ../../include/openssl/opensslconf.h
bf_buff.o: ../../include/openssl/opensslv.h ../../include/openssl/rc2.h
bf_buff.o: ../../include/openssl/rc4.h ../../include/openssl/rc5.h
bf_buff.o: ../../include/openssl/ripemd.h ../../include/openssl/rsa.h
bf_buff.o: ../../include/openssl/safestack.h ../../include/openssl/sha.h
bf_buff.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bf_nbio.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
bf_nbio.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
bf_nbio.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
bf_nbio.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
bf_nbio.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
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.
1999-05-21 19:16:48 +08:00
bf_nbio.o: ../../include/openssl/e_os.h ../../include/openssl/e_os2.h
bf_nbio.o: ../../include/openssl/err.h ../../include/openssl/evp.h
bf_nbio.o: ../../include/openssl/idea.h ../../include/openssl/md2.h
bf_nbio.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
bf_nbio.o: ../../include/openssl/objects.h ../../include/openssl/opensslconf.h
bf_nbio.o: ../../include/openssl/opensslv.h ../../include/openssl/rand.h
bf_nbio.o: ../../include/openssl/rc2.h ../../include/openssl/rc4.h
bf_nbio.o: ../../include/openssl/rc5.h ../../include/openssl/ripemd.h
bf_nbio.o: ../../include/openssl/rsa.h ../../include/openssl/safestack.h
bf_nbio.o: ../../include/openssl/sha.h ../../include/openssl/stack.h
bf_nbio.o: ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bf_null.o: ../../include/openssl/asn1.h ../../include/openssl/bio.h
bf_null.o: ../../include/openssl/blowfish.h ../../include/openssl/bn.h
bf_null.o: ../../include/openssl/buffer.h ../../include/openssl/cast.h
bf_null.o: ../../include/openssl/crypto.h ../../include/openssl/des.h
bf_null.o: ../../include/openssl/dh.h ../../include/openssl/dsa.h
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.
1999-05-21 19:16:48 +08:00
bf_null.o: ../../include/openssl/e_os.h ../../include/openssl/e_os2.h
bf_null.o: ../../include/openssl/err.h ../../include/openssl/evp.h
bf_null.o: ../../include/openssl/idea.h ../../include/openssl/md2.h
bf_null.o: ../../include/openssl/md5.h ../../include/openssl/mdc2.h
bf_null.o: ../../include/openssl/objects.h ../../include/openssl/opensslconf.h
bf_null.o: ../../include/openssl/opensslv.h ../../include/openssl/rc2.h
bf_null.o: ../../include/openssl/rc4.h ../../include/openssl/rc5.h
bf_null.o: ../../include/openssl/ripemd.h ../../include/openssl/rsa.h
bf_null.o: ../../include/openssl/safestack.h ../../include/openssl/sha.h
bf_null.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bio_cb.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bio_cb.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bio_cb.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bio_cb.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
bio_cb.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bio_err.o: ../../include/openssl/bio.h ../../include/openssl/crypto.h
bio_err.o: ../../include/openssl/err.h ../../include/openssl/opensslv.h
bio_err.o: ../../include/openssl/stack.h
bio_lib.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bio_lib.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bio_lib.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bio_lib.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
bio_lib.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_acpt.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_acpt.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_acpt.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_acpt.o: ../../include/openssl/opensslconf.h
Removed traces of cryptall.h, and did a "make depend". Submitted by: Reviewed by: PR:
1999-04-25 17:21:05 +08:00
bss_acpt.o: ../../include/openssl/opensslv.h ../../include/openssl/stack.h
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.
1999-05-21 19:16:48 +08:00
bss_acpt.o: ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_conn.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_conn.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_conn.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_conn.o: ../../include/openssl/opensslconf.h
Removed traces of cryptall.h, and did a "make depend". Submitted by: Reviewed by: PR:
1999-04-25 17:21:05 +08:00
bss_conn.o: ../../include/openssl/opensslv.h ../../include/openssl/stack.h
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.
1999-05-21 19:16:48 +08:00
bss_conn.o: ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_fd.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_fd.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_fd.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_fd.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
bss_fd.o: ../../include/openssl/stack.h ../cryptlib.h bss_sock.c
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_file.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_file.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_file.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_file.o: ../../include/openssl/opensslconf.h
Removed traces of cryptall.h, and did a "make depend". Submitted by: Reviewed by: PR:
1999-04-25 17:21:05 +08:00
bss_file.o: ../../include/openssl/opensslv.h ../../include/openssl/stack.h
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.
1999-05-21 19:16:48 +08:00
bss_file.o: ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_log.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_log.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_log.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_log.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
bss_log.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_mem.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_mem.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_mem.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_mem.o: ../../include/openssl/opensslconf.h ../../include/openssl/opensslv.h
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.
1999-05-21 19:16:48 +08:00
bss_mem.o: ../../include/openssl/stack.h ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_null.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_null.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_null.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_null.o: ../../include/openssl/opensslconf.h
Removed traces of cryptall.h, and did a "make depend". Submitted by: Reviewed by: PR:
1999-04-25 17:21:05 +08:00
bss_null.o: ../../include/openssl/opensslv.h ../../include/openssl/stack.h
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.
1999-05-21 19:16:48 +08:00
bss_null.o: ../cryptlib.h
"make depend" Submitted by: Reviewed by: PR:
1999-04-24 06:50:50 +08:00
bss_sock.o: ../../include/openssl/bio.h ../../include/openssl/buffer.h
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.
1999-05-21 19:16:48 +08:00
bss_sock.o: ../../include/openssl/crypto.h ../../include/openssl/e_os.h
bss_sock.o: ../../include/openssl/e_os2.h ../../include/openssl/err.h
Add a kludge :-( There were problems with putting e_os.h just into the top directory, because the test programs are compiled within test/ in the "standard" case in in their original directories in the makefile.one case; and in the latter symlinks may not be available.
1999-05-21 06:18:49 +08:00
bss_sock.o: ../../include/openssl/opensslconf.h
Removed traces of cryptall.h, and did a "make depend". Submitted by: Reviewed by: PR:
1999-04-25 17:21:05 +08:00
bss_sock.o: ../../include/openssl/opensslv.h ../../include/openssl/stack.h
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.
1999-05-21 19:16:48 +08:00
bss_sock.o: ../cryptlib.h
Reference in New Issue Copy Permalink