Trying to build openssl-0.9.5 using make and its ./config instructions. Not sure what to make of this log. Thoughts?

Fails with::

make
making all in crypto...
make[1]: Entering directory '/home/___KATS___/Desktop/openssl-0.9.5/crypto'
gcc -I. -I../include -DTHREADS -D_REENTRANT -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -m16 -Wall -DSHA1_ASM -DMD5_ASM -DD160_ASM -c -o cryptlib.o cryptlib.c
In file included from cryptlib.h:69:0,
from cryptlib.c:61:
../include/openssl/e_os.h:1:1: error: expected identifier or ‘(’ before ‘.’ token
../../e_os.h
^
cryptlib.c:98:3: error: #error "Inconsistency between crypto.h and cryptlib.c"
# error "Inconsistency between crypto.h and cryptlib.c"
^~~~~
cryptlib.c:102:8: error: unknown type name ‘STACK’
static STACK *app_locks=NULL;
^~~~~
cryptlib.c:104:21: error: expected ‘)’ before ‘*’ token
static void (MS_FAR *locking_callback)(int mode,int type,
^
cryptlib.c:106:20: error: expected ‘)’ before ‘*’ token
static int (MS_FAR *add_lock_callback)(int *pointer,int amount,
^
cryptlib.c:108:30: error: expected ‘)’ before ‘*’ token
static unsigned long (MS_FAR *id_callback)(void)=NULL;
^
cryptlib.c: In function ‘CRYPTO_get_new_lockid’:
cryptlib.c:122:41: warning: implicit declaration of function ‘sk_new_null’; did you mean ‘__nonnull’? [-Wimplicit-function-declaration]
if ((app_locks == NULL) && ((app_locks=sk_new_null()) == NULL))
^~~~~~~~~~~
__nonnull
cryptlib.c:122:40: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
if ((app_locks == NULL) && ((app_locks=sk_new_null()) == NULL))
^
cryptlib.c:124:3: warning: implicit declaration of function ‘CRYPTOerr’ [-Wimplicit-function-declaration]
CRYPTOerr(CRYPTO_F_CRYPTO_GET_NEW_LOCKID,ERR_R_MALLOC_FAILURE);
^~~~~~~~~
cryptlib.c:124:13: error: ‘CRYPTO_F_CRYPTO_GET_NEW_LOCKID’ undeclared (first use in this function)
CRYPTOerr(CRYPTO_F_CRYPTO_GET_NEW_LOCKID,ERR_R_MALLOC_FAILURE);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cryptlib.c:124:13: note: each undeclared identifier is reported only once for each function it appears in
cryptlib.c:124:44: error: ‘ERR_R_MALLOC_FAILURE’ undeclared (first use in this function)
CRYPTOerr(CRYPTO_F_CRYPTO_GET_NEW_LOCKID,ERR_R_MALLOC_FAILURE);
^~~~~~~~~~~~~~~~~~~~
cryptlib.c:127:11: warning: implicit declaration of function ‘BUF_strdup’; did you mean ‘strdup’? [-Wimplicit-function-declaration]
if ((str=BUF_strdup(name)) == NULL)
^~~~~~~~~~
strdup
cryptlib.c:127:10: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
if ((str=BUF_strdup(name)) == NULL)
^
cryptlib.c:129:4: warning: implicit declaration of function ‘sk_push’ [-Wimplicit-function-declaration]
i=sk_push(app_locks,str);
^~~~~~~
cryptlib.c:131:3: warning: implicit declaration of function ‘Free’; did you mean ‘free’? [-Wimplicit-function-declaration]
Free(str);
^~~~
free
cryptlib.c:133:6: error: ‘CRYPTO_NUM_LOCKS’ undeclared (first use in this function)
i+=CRYPTO_NUM_LOCKS; /* gap of one :-) */
^~~~~~~~~~~~~~~~
cryptlib.c: In function ‘CRYPTO_num_locks’:
cryptlib.c:139:9: error: ‘CRYPTO_NUM_LOCKS’ undeclared (first use in this function); did you mean ‘CRYPTO_num_locks’?
return CRYPTO_NUM_LOCKS;
^~~~~~~~~~~~~~~~
CRYPTO_num_locks
cryptlib.c: In function ‘CRYPTO_get_locking_callback’:
cryptlib.c:145:9: error: ‘locking_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_get_locking_callback’?
return(locking_callback);
^~~~~~~~~~~~~~~~
CRYPTO_get_locking_callback
cryptlib.c: In function ‘CRYPTO_get_add_lock_callback’:
cryptlib.c:151:9: error: ‘add_lock_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_get_add_lock_callback’?
return(add_lock_callback);
^~~~~~~~~~~~~~~~~
CRYPTO_get_add_lock_callback
cryptlib.c: In function ‘CRYPTO_set_locking_callback’:
cryptlib.c:157:2: error: ‘locking_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_set_locking_callback’?
locking_callback=func;
^~~~~~~~~~~~~~~~
CRYPTO_set_locking_callback
cryptlib.c: In function ‘CRYPTO_set_add_lock_callback’:
cryptlib.c:163:2: error: ‘add_lock_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_set_add_lock_callback’?
add_lock_callback=func;
^~~~~~~~~~~~~~~~~
CRYPTO_set_add_lock_callback
cryptlib.c: In function ‘CRYPTO_get_id_callback’:
cryptlib.c:168:9: error: ‘id_callback’ undeclared (first use in this function)
return(id_callback);
^~~~~~~~~~~
cryptlib.c: In function ‘CRYPTO_set_id_callback’:
cryptlib.c:173:2: error: ‘id_callback’ undeclared (first use in this function)
id_callback=func;
^~~~~~~~~~~
cryptlib.c: In function ‘CRYPTO_thread_id’:
cryptlib.c:180:6: error: ‘id_callback’ undeclared (first use in this function)
if (id_callback == NULL)
^~~~~~~~~~~
cryptlib.c:189:22: warning: implicit declaration of function ‘getpid’; did you mean ‘getenv’? [-Wimplicit-function-declaration]
ret=(unsigned long)getpid();
^~~~~~
getenv
cryptlib.c:193:7: warning: implicit declaration of function ‘id_callback’ [-Wimplicit-function-declaration]
ret=id_callback();
^~~~~~~~~~~
cryptlib.c: In function ‘CRYPTO_lock’:
cryptlib.c:222:6: error: ‘locking_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_set_locking_callback’?
if (locking_callback != NULL)
^~~~~~~~~~~~~~~~
CRYPTO_set_locking_callback
cryptlib.c:223:3: warning: implicit declaration of function ‘locking_callback’; did you mean ‘CRYPTO_set_locking_callback’? [-Wimplicit-function-declaration]
locking_callback(mode,type,file,line);
^~~~~~~~~~~~~~~~
CRYPTO_set_locking_callback
cryptlib.c: In function ‘CRYPTO_add_lock’:
cryptlib.c:231:6: error: ‘add_lock_callback’ undeclared (first use in this function); did you mean ‘CRYPTO_set_add_lock_callback’?
if (add_lock_callback != NULL)
^~~~~~~~~~~~~~~~~
CRYPTO_set_add_lock_callback
cryptlib.c:237:7: warning: implicit declaration of function ‘add_lock_callback’; did you mean ‘CRYPTO_set_add_lock_callback’? [-Wimplicit-function-declaration]
ret=add_lock_callback(pointer,amount,type,file,line);
^~~~~~~~~~~~~~~~~
CRYPTO_set_add_lock_callback
cryptlib.c:249:15: error: ‘CRYPTO_LOCK’ undeclared (first use in this function); did you mean ‘CRYPTO_lock’?
CRYPTO_lock(CRYPTO_LOCK|CRYPTO_WRITE,type,file,line);
^~~~~~~~~~~
CRYPTO_lock
cryptlib.c:249:27: error: ‘CRYPTO_WRITE’ undeclared (first use in this function); did you mean ‘CRYPTO_LOCK’?
CRYPTO_lock(CRYPTO_LOCK|CRYPTO_WRITE,type,file,line);
^~~~~~~~~~~~
CRYPTO_LOCK
cryptlib.c:260:15: error: ‘CRYPTO_UNLOCK’ undeclared (first use in this function); did you mean ‘CRYPTO_LOCK’?
CRYPTO_lock(CRYPTO_UNLOCK|CRYPTO_WRITE,type,file,line);
^~~~~~~~~~~~~
CRYPTO_LOCK
cryptlib.c: In function ‘CRYPTO_get_lock_name’:
cryptlib.c:269:18: error: ‘CRYPTO_NUM_LOCKS’ undeclared (first use in this function); did you mean ‘CRYPTO_add_lock’?
else if (type < CRYPTO_NUM_LOCKS)
^~~~~~~~~~~~~~~~
CRYPTO_add_lock
cryptlib.c:270:10: error: ‘lock_names’ undeclared (first use in this function)
return(lock_names[type]);
^~~~~~~~~~
cryptlib.c:271:36: warning: implicit declaration of function ‘sk_num’ [-Wimplicit-function-declaration]
else if (type-CRYPTO_NUM_LOCKS >= sk_num(app_locks))
^~~~~~
cryptlib.c:274:10: warning: implicit declaration of function ‘sk_value’ [-Wimplicit-function-declaration]
return(sk_value(app_locks,type-CRYPTO_NUM_LOCKS));
^~~~~~~~
cryptlib.c: In function ‘CRYPTO_num_locks’:
cryptlib.c:140:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cryptlib.c: In function ‘CRYPTO_get_locking_callback’:
cryptlib.c:146:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cryptlib.c: In function ‘CRYPTO_get_add_lock_callback’:
cryptlib.c:152:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cryptlib.c: In function ‘CRYPTO_get_id_callback’:
cryptlib.c:169:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cryptlib.c: In function ‘CRYPTO_get_lock_name’:
cryptlib.c:275:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
<builtin>: recipe for target 'cryptlib.o' failed
make[1]: *** [cryptlib.o] Error 1
make[1]: Leaving directory '/home/___KATS___/Desktop/openssl-0.9.5/crypto'
Makefile:183: recipe for target 'all' failed
make: *** [all] Error 1

Welcome to LQ.

`openssl-0.9.5.tar.gz´ has a time stamp, Mar 11 2000, some files in crypto/ 1999.

Can be built with an old 32bits OS, e.g. CentOS 5.11 : gcc version 4.1.2 .

1 members found this post helpful.

Thanks for the welcome and quick response!

Appreciate the pointer, I'll try setting up a CentOS VM to compile on.

Any thoughts on if an executable compiled in centOS might be usable on newer 32bit Linux distros?

Re #3.

All distros come with a default contemporary and safe openssl.
The default openssl should never be changed or replaced. Just updated when security updates are available.

Openssl-0.9.5 is not supposed to be used for anything.

-

Understood, appreciate the warning, the intent here was not to use this compiled version to replace a modern openssl package. I'm looking to do some testing of other 2000's era software that seems to require openssl-0.9.5.

OK, you may need the repo file, CentOS-5.11.repo, to install gcc-c++.
https://www.dropbox.com/s/jxs1xgrvf2...5.11.repo?dl=0
... I.e. CentOS 5 is no longer supported.
Replace files in /etc/yum.repos.d/ with the new file.


-