On Fri, 20 Dec 2002, Lutz Jaenicke via RT wrote:

> ...
> There are several issues in your report, so I have redirected this thread
> into the request tracker.
> 
> > * lots of messages during 'make depend' apparently from the pre-processor:
> > ../util/domd .. -MD makedepend -- -DOPENSSL_THREADS -D_REENTRANT -DDSO_DL 
>-DOPENSSL_NO_KRB5 -DOPENSSL_NO_IDEA -DOPENSSL_NO_ASM +DA2.0 +DS2.0 +O3 
>+Optrs_strongly_typed +Olibcalls -Ae +ESlit -DB_ENDIAN -DMD32_XARRAY -I. -I.. 
>-I../include -DOPENSSL_NO_IDEA  --  cryptlib.c mem.c mem_clr.c mem_dbg.c cversion.c 
>ex_data.c tmdiff.c cpt_err.c ebcdic.c uid.c o_time.c
> > "cryptlib.c":433:  !defined(_POSIX_C_SOURCE) || (_POSIX_C_SOURCE < 199309L)
> 
> Don't know about this one... Do you have "makedepend" on your system,
> otherwise gcc is being used. Maybe some flag is missing.

yes, makedepend is installed on the system (it comes with the HP Ansi C
Developer's Bundle, in the imake package).

i tried configuring OpenSSL v0.9.7-beta6 also with the default target
(hpux-parisc-gcc) using config (with only --prefix argument) but i still
get the above messages with 'gmake depend'. i think i found the cause for
this problem:

--- crypto/Makefile.ssl 2002-12-20 15:01:01.000000000 +0200
+++ crypto/Makefile.ssl.new     2002-12-20 15:04:47.000000000 +0200
@@ -141,7 +141,7 @@
        @for i in $(SDIRS) ;\
        do \
        (cd $$i && echo "making depend in crypto/$$i..." && \
-       $(MAKE) MAKEFILE='${MAKEFILE}' INCLUDES='${INCLUDES}' CFLAG='${CFLAG}' 
DEPFLAG='${DEPFLAG}' PERL='${PERL}' depend ); \
+       $(MAKE) MAKEFILE='${MAKEFILE}' INCLUDES='${INCLUDES}' CFLAG='${CFLAG}' 
+DEPFLAG='${DEPFLAG}' MAKEDEPPROG='${MAKEDEPPROG}' PERL='${PERL}' depend ); \
        done;
 
 clean:

best regards,
-- 
        aspa



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to