of course you were right, Dan!
I had to export CC to point to where GCC is installed (in my case in 
/opt/csw/bin/gcc)

worked perfectly, until I ran in yet another problem. but this time I think 
something's wrong with my ssl.h in /usr/include/openssl/ssl.h

 *** Making os_auth ***

/opt/csw/bin/gcc -g -Wall -I../ -I../headers  -DDEFAULTDIR=\"/var/ossec\" 
-DCLIENT -DUSE_OPENSSL -DSOLARIS -DHIGHFIRST      -DARGV0=\"ossec-authd\" 
-DOSSECHIDS -lsocket -lnsl -lresolv main-server.c ssl.c 
../addagent/validate.c ../config/lib_config.a ../shared/lib_shared.a 
../os_net/os_net.a ../os_regex/os_regex.a ../os_crypto/os_crypto.a 
../os_zlib/os_zlib.c ../external/libz.a -lssl -lcrypto -o ossec-authd
main-server.c: In function 'ssl_error':
main-server.c:53:31: warning: passing argument 1 of 'SSL_get_error' 
discards 'const' qualifier from pointer target type
         switch (SSL_get_error(ssl, ret))
                               ^
In file included from auth.h:45:0,
                 from main-server.c:29:
/usr/include/openssl/ssl.h:1408:5: note: expected 'struct SSL *' but 
argument is of type 'const struct SSL *'
 int SSL_get_error(SSL *s,int ret_code);
     ^
ld: fatal: library -lssl: not found
ld: fatal: library -lcrypto: not found
ld: fatal: file processing errors. No output written to ossec-authd
*** Error code 1
make: Fatal error: Command failed for target `auth1'
Current working directory /root/ossec-hids-2.8.2/src/os_auth



Am Donnerstag, 24. September 2015 14:57:08 UTC+2 schrieb dan (ddpbsd):
>
>
> On Sep 24, 2015 8:46 AM, "theresa mic-snare" <rockpr...@gmail.com 
> <javascript:>> wrote:
> >
> > it was indeed in a different location :)
> > i symlinked it to the other location where it should supposedly be 
> /usr/include/openssl/opensslconf.h
> >
> > and ran the installation script again.
> > but now i'm running into a different error....
> >
> >  *** Making os_crypto *** 
> >  
> > cc -g -Wall -I../../ -I../../headers  -DDEFAULTDIR=\"/var/ossec\" 
> -DCLIENT -DUSE_OPENSSL -DSOLARIS -DHIGHFIRST      -DARGV0=\"blowfish_op\" 
> -DOSSECHIDS -c bf_op.c bf_skey.c bf_enc.c 
> > cc: -W option with unknown program all 
>
> That right there makes me think it isn't using gcc as the compiler (-Wall 
> has been around for a while now).
>
> > *** Error code 1 
> > make: Fatal error: Command failed for target `bf' 
> > Current working directory /root/ossec-hids-2.8.2/src/os_crypto/blowfish 
> > *** Error code 1 
> > The following command caused the error: 
> > cd blowfish; make 
> > make: Fatal error: Command failed for target `os_crypto' 
> > Current working directory /root/ossec-hids-2.8.2/src/os_crypto 
> >  
> > Error Making os_crypto 
> > *** Error code 1 
> > The following command caused the error: 
> > /bin/bash ./Makeall all 
> > make: Fatal error: Command failed for target `all' 
> >  
> >  Error 0x5. 
> >  Building error. Unable to finish the installation.
> >
> >
> >
> > Am Donnerstag, 24. September 2015 14:28:14 UTC+2 schrieb dan (ddpbsd):
> >>
> >>
> >> On Sep 24, 2015 8:23 AM, "theresa mic-snare" <rockpr...@gmail.com> 
> wrote:
> >> >
> >> > hmm I see.
> >> > but I managed to build it on a Solaris 11 machine without any 
> problems.... without having to modify any Make or any other file. Hmm...
> >> >
> >>
> >> Was opensslconf.h in a different location on solaris 11?
> >>
> >> >
> >> > Am Donnerstag, 24. September 2015 14:18:27 UTC+2 schrieb dan (ddpbsd):
> >> >>
> >> >> On Thu, Sep 24, 2015 at 8:14 AM, theresa mic-snare 
> >> >> <rockpr...@gmail.com> wrote: 
> >> >> > Dan, do you currently have OSSEC installed on a Solaris machine? 
> >> >> > if so, could you please tell me where the opensslconf.h is located 
> on your 
> >> >> > system? 
> >> >> > 
> >> >>
> >> >> No, sorry. I can't afford Oracle machines, and I doubt my wife would 
> >> >> appreciate the noise. :P 
> >> >>
> >> >> I'm guessing you would need "-I/usr/sfw/include" in the build 
> command 
> >> >> for os_crypto. You might be able to add it to the CFLAGS or LDFLAGS 
> in 
> >> >> the Config.Make, but I haven't tried any of this. 
> >> >>
> >> >> > thanks, 
> >> >> > theresa 
> >> >> > 
> >> >> > Am Mittwoch, 23. September 2015 15:02:25 UTC+2 schrieb dan 
> (ddpbsd): 
> >> >> >> 
> >> >> >> 
> >> >> >> On Sep 23, 2015 8:59 AM, "theresa mic-snare" <rockpr...@gmail.com> 
> wrote: 
> >> >> >> > 
> >> >> >> > by the way: 
> >> >> >> > 
> >> >> >> > I have found the file opensslconf.h that is allegedly missing 
> on my 
> >> >> >> > server... 
> >> >> >> > it's located under: 
> >> >> >> > /usr/sfw/include/openssl/opensslconf.h 
> >> >> >> > 
> >> >> >> > is the path maybe somewhere hardcoded, so that it's maybe 
> looking in the 
> >> >> >> > wrong place? 
> >> >> >> > 
> >> >> >> 
> >> >> >> That would be my guess. 
> >> >> >> 
> >> >> >> > cheers, 
> >> >> >> > theresa 
> >> >> >> > 
> >> >> >> > 
> >> >> >> > Am Mittwoch, 23. September 2015 14:45:05 UTC+2 schrieb theresa 
> >> >> >> > mic-snare: 
> >> >> >> >> 
> >> >> >> >> Hi everyone, 
> >> >> >> >> 
> >> >> >> >> I was just trying to compile OSSEC 2.8.2 on a Solaris 10 
> (SPARC) 
> >> >> >> >> server, and got the following error: 
> >> >> >> >> 
> >> >> >> >>  *** Making os_crypto *** 
> >> >> >> >> 
> >> >> >> >> /opt/csw/bin/gcc -g -Wall -I../../ -I../../headers 
> >> >> >> >> -DDEFAULTDIR=\"/var/ossec\" -DCLIENT -DUSE_OPENSSL -DSOLARIS 
> -DHIGHFIRST 
> >> >> >> >> -DARGV0=\"blowfish_op\" -DOSSECHIDS -c bf_op.c bf_skey.c 
> bf_enc.c 
> >> >> >> >> In file included from bf_skey.c:62:0: 
> >> >> >> >> bf_locl.h:69:55: fatal error: openssl/opensslconf.h: No such 
> file or 
> >> >> >> >> directory 
> >> >> >> >>  #include <openssl/opensslconf.h> /* BF_PTR, BF_PTR2 */ 
> >> >> >> >>                                                        ^ 
> >> >> >> >> compilation terminated. 
> >> >> >> >> In file included from bf_enc.c:60:0: 
> >> >> >> >> bf_locl.h:69:55: fatal error: openssl/opensslconf.h: No such 
> file or 
> >> >> >> >> directory 
> >> >> >> >>  #include <openssl/opensslconf.h> /* BF_PTR, BF_PTR2 */ 
> >> >> >> >>                                                        ^ 
> >> >> >> >> compilation terminated. 
> >> >> >> >> *** Error code 1 
> >> >> >> >> make: Fatal error: Command failed for target `bf' 
> >> >> >> >> Current working directory 
> /root/ossec-hids-2.8.2/src/os_crypto/blowfish 
> >> >> >> >> *** Error code 1 
> >> >> >> >> The following command caused the error: 
> >> >> >> >> cd blowfish; make 
> >> >> >> >> make: Fatal error: Command failed for target `os_crypto' 
> >> >> >> >> Current working directory /root/ossec-hids-2.8.2/src/os_crypto 
> >> >> >> >> 
> >> >> >> >> Error Making os_crypto 
> >> >> >> >> *** Error code 1 
> >> >> >> >> The following command caused the error: 
> >> >> >> >> /bin/bash ./Makeall all 
> >> >> >> >> make: Fatal error: Command failed for target `all' 
> >> >> >> >> 
> >> >> >> >>  Error 0x5. 
> >> >> >> >>  Building error. Unable to finish the installation. 
> >> >> >> >> 
> >> >> >> >> 
> >> >> >> >> 
> >> >> >> >> I think there seems to be some kind of OpenSSL dependency 
> issue... 
> >> >> >> >> I have also added the following lines in the install.sh script 
> (to make 
> >> >> >> >> sure the OpenSSL libraries get linked) 
> >> >> >> >> echo "DEXTRA=-DUSE_OPENSSL" >> ./src/Config.OS 
> >> >> >> >> echo "OPENSSLCMD=-lssl -lcrypto" >> ./src/Config.OS 
> >> >> >> >> 
> >> >> >> >> 
> >> >> >> >> I'm using the following OpenSSL version: 
> >> >> >> >> OpenSSL 0.9.7d 17 Mar 2004 (+ security fixes for: 
> CVE-2005-2969 
> >> >> >> >> CVE-2006-2937 CVE-2006-2940 CVE-2006-3738 CVE-2006-4339 
> CVE-2006-4343 
> >> >> >> >> CVE-2006-7250 CVE-2007-5135 CVE-2007-3108 CVE-2008-5077 
> CVE-2008-7270 
> >> >> >> >> CVE-2009-0590 CVE-2009-2409 CVE-2009-3555 CVE-2010-4180 
> CVE-2011-4576 
> >> >> >> >> CVE-2011-4619 CVE-2012-0884 CVE-2012-1165 CVE-2012-2110 
> CVE-2012-2131 
> >> >> >> >> CVE-2012-2333 CVE-2013-0166 CVE-2013-0169) 
> >> >> >> >> 
> >> >> >> >> anyone come across the same problem? 
> >> >> >> >> 
> >> >> >> >> cheers, 
> >> >> >> >> theresa 
> >> >> >> > 
> >> >> >> > -- 
> >> >> >> > 
> >> >> >> > --- 
> >> >> >> > You received this message because you are subscribed to the 
> Google 
> >> >> >> > Groups "ossec-list" group. 
> >> >> >> > To unsubscribe from this group and stop receiving emails from 
> it, send 
> >> >> >> > an email to ossec-list+...@googlegroups.com. 
> >> >> >> > For more options, visit https://groups.google.com/d/optout. 
> >> >> > 
> >> >> > -- 
> >> >> > 
> >> >> > --- 
> >> >> > You received this message because you are subscribed to the Google 
> Groups 
> >> >> > "ossec-list" group. 
> >> >> > To unsubscribe from this group and stop receiving emails from it, 
> send an 
> >> >> > email to ossec-list+...@googlegroups.com. 
> >> >> > For more options, visit https://groups.google.com/d/optout. 
> >> >
> >> > -- 
> >> >
> >> > --- 
> >> > You received this message because you are subscribed to the Google 
> Groups "ossec-list" group.
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send an email to ossec-list+...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/d/optout.
> >
> > -- 
> >
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "ossec-list" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to ossec-list+...@googlegroups.com <javascript:>.
> > For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to