My apologies for posting w/o a subject line... Patrick Swartz
-----Original Message----- From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On Behalf Of Swartz, Patrick H Sent: Thursday, February 16, 2012 4:59 PM To: ossec-list@googlegroups.com Subject: [ossec-list] Hi All, Another Solaris compile issue. This time with Solaris 8 (yes, I know it is old and unsupported). We modified the Makeall file to point to the openssl headers, but it still fails. This is with Ossec 2.6. root# find /usr/local -name opensslconf.h /usr/local/ssl/include/openssl/opensslconf.h root# grep opensslconf.h src/Makeall #ls /usr/include/openssl/opensslconf.h > /dev/null 2>&1 ls /usr/local/ssl/include/openssl/opensslconf.h > /dev/null 2>&1 root# /usr/local/ssl/bin/openssl version OpenSSL 1.0.0c 2 Dec 2010 *** Making os_crypto *** gcc -g -Wall -I../../ -I../../headers -DDEFAULTDIR=\"/opt/ossec\" -DCLIENT -DUSE_OPENSSL -DSOLARIS -DHIGHFIRST -DARGV0=\"blowfish_op\" -DXML_VAR=\"var\" -DOSSECHIDS -c bf_op.c bf_skey.c bf_enc.c In file included from bf_skey.c:62: bf_locl.h:69:55: openssl/opensslconf.h: No such file or directory In file included from bf_enc.c:60: bf_locl.h:69:55: openssl/opensslconf.h: No such file or directory *** Error code 1 make: Fatal error: Command failed for target `bf' Current working directory /var/tmp/ossec/ossec-hids-2.6/src/os_crypto/blowfish *** Error code 1 make: Fatal error: Command failed for target `os_crypto' Current working directory /var/tmp/ossec/ossec-hids-2.6/src/os_crypto Error Making os_crypto *** Error code 1 make: Fatal error: Command failed for target `all' Any and all help would be greatly appreciated! Thanks, Patrick Swartz ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
