Unless your team is still writing C and C++ programs, all they will need are the C runtimes (libgcc) of the particular version that their apps were compiled against and whatever libraries it needs. You could install the compiler to a new location and compile from there, just make sure whatever library path you make to hold the runtimes you update the registered paths on the system (use crle). As far as using the Sun C compiler (what is now known as part of Developer studio), that would probably not work due to certain libraries, includes, etc that are not part of that compiler suite. Could you make it work? Yes. But you would have to obviously know C or C++ well enough to translate certain pieces of code and includes to Sun's libraries. You would also have to compile any dependancies that ossec has against the Sun C compiler as well. (Linkage doesn't hold from Sun's C compiler to Gcc). If I am to understand you correctly, you are abandoning the attempt for a Solaris 8 install, so I will not mess with it.
Haz On Wed, May 20, 2009 at 2:47 PM, <patrick.swa...@firstdata.com> wrote: > > Wanted to update the list with what has been discovered. The version > of gcc on this Solaris 8 box is rather old (gcc version 2.95.1 > 19990816 -- understatement, I know). > > The team that owns the Solaris 8 box is hesitant to change gcc > versions, and have asked if there is a way to use the Sun c compiler > in /opt/SUNWspro/bin/cc? I am not a programmer, and not quite what to > change in the install.sh script in order to use the Sun c compiler > instead of gcc. > > Is it even possible to use the Sun C compiler? > > Thanks again for any and all input as we have solidified on using > OSSEC as our FIM solution for our Distributed Platforms (AIX, Solaris, > Linux, and Windows) and are under the gun to get it rolled out as > quick as possible. > > Patrick > > On May 18, 3:37 pm, patrick.swa...@firstdata.com wrote: > > Hi All, > > I am trying to compile on a Solaris 8 server: > > SunOS sun3n 5.8 Generic_117350-52 sun4u sparc SUNW,Sun-Fire-15000 > > pkginfo |grep gcc > > application SMCgcc gcc > > application SMClgcc libgcc > > > > But when it gets to the "Making monitord" it fails w/: > > > > *** Making monitord *** > > > > gcc -g -Wall -I../ -I../headers -DDEFAULTDIR=\"/opt/ossec\" -DCLIENT > > -DSOLARIS -DHIGHFIRST -DARGV0=\"ossec-monitord\" -DXML_VAR=\"var\" - > > DOSSECHIDS -lsocket -lnsl -lresolv compress_log.c main.c > > manage_files.c monitor_agents.c monitord.c sign_log.c ../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 -o ossec-monitord > > gcc -g -Wall -I../ -I../headers -DDEFAULTDIR=\"/opt/ossec\" -DCLIENT > > -DSOLARIS -DHIGHFIRST -DARGV0=\"ossec-monitord\" -DXML_VAR=\"var\" - > > DOSSECHIDS -lsocket -lnsl -lresolv -UARGV0 -DARGV0=\"ossec-reportd\" > > report.c ../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 -o ossec-reportd > > *Initialization*:1: warning: `ARGV0' redefined > > *Initialization*:1: warning: this is the location of the previous > > definition > > report.c: In function `report_help': > > report.c:20: `ARGV0' undeclared (first use in this function) > > report.c:20: (Each undeclared identifier is reported only once > > report.c:20: for each function it appears in.) > > report.c: In function `main': > > report.c:53: `ARGV0' undeclared (first use in this function) > > *Initialization*:1: warning: `ARGV0' redefined > > *Initialization*:1: warning: this is the location of the previous > > definition > > *** Error code 1 > > make: Fatal error: Command failed for target `mmonitor' > > Current working directory /export/home/phswartz/ossec-hids-2.0/src/ > > monitord > > > > Error Making monitord > > *** Error code 1 > > make: Fatal error: Command failed for target `all' > > > > All of the previous subsections didn't have a problem ( syscheckd, > > rootcheck, util, addagent, client-agent, remoted, logcollector). > > Is there something else I should be checking? What are my options at > > this point? > > > > Thanks so much in advance! > > Patrick >
