Nagios Plugins build under SPARC Solaris8 with SUNWspro CC fails

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Ralph.Grothe at itdz-berlin.de
> Sent: Tuesday, July 19, 2005 7:00 AM
> To: nagiosplug-help-admin at lists.sourceforge.net; nagios-
> users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios Plugins build under SPARC Solaris8 with
> SUNWspro CC fails
> 
> Hello again,
> 
> . -I../lib -I../intl   -I/usr/local/ssl/include/openssl  -g -c
> check_http.c
> "check_http.c", line 50: cannot find include file:
> <openssl/rsa.h>
> "check_http.c", line 51: cannot find include file:
> <openssl/crypto.h>

[snip]

> cc: acomp failed for check_http.c
> *** Error code 2
> dmake: Fatal error: Command failed for target `check_http.o'
> Waiting for 1 job to finish
> 
> 
> 
> Which is daft as I can find the complained about header files,
> just in the path I separately supplied.
> 

> # ll
> /usr/local/ssl/include/openssl/{rsa,crypto,x509,pem,ssl,err,rand}
> .h
> -rw-r--r--   1 bin      bin        15804 Jan 25 14:23
> /usr/local/ssl/include/openssl/crypto.h

[snip]

> 
> 
> Isn't Forte cc honouring CPPFLAGS in the end?

It looks like it is but you're specifying the wrong path to openssl.
Notice that it's looking for 'openssl/crypto.h', which in your case
would be in the path '/usr/local/ssl/include/openssl/openssl/crypto.h'.

Try using 'CPPFLAGS=-I/usr/local/ssl/include/'.

--
Marc




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null