I think you are judging to fast. For instance on my Solaris 11 Sparc
system, there is a local OpenSSL installation under
/lib/64/libcrypto.so.1.0.0 which does have the RAND_egd symbol. The
local file /usr/include/openssl/opensslconf.h does not define
OPENSSL_NO_EGD and /usr/include/openssl/rand.h declares RAND_egd.
So in my case the system installation of openssl does support RAND_egd.
To make sure, that httpd finds all info for your custom openssl - header
files and libs - before the ones from the operating system, the include
and linker paths need to be set up correctly during configure and build.
Since during the configure check on your system the gcc flags are:
gcc -std=gnu99 -o conftest -m32 -DSOLARIS2=10
-D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE
-I/var/opt/sun/xvm/uce/opt/server/include -L/usr/sfw//lib
-L/var/opt/sun/xvm/uce/opt/server/lib conftest.c -lssl -lcrypto -luuid
-lsendfile -lrt -lsocket -lnsl -lpthread
we can see, that it would eg. use libs from /usr/sfw/lib before your own
openssl libs.
Therefore I think iit makes sense to do the litlle investigation that I
suggested.
In addition: what are your configure flags plus additional env vars you set?
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
