nrpe-2.0b2 on FreeBSD

[Subhendu Ghosh]

Mark - what version of gcc is in use?

I compile on NetBSD without any problems.

-sg

On Wed, 16 Apr 2003, mark wrote:

> Has anyone managed to compile nrpe-2.0b2 on FreeBSD with command args 
> enabled? I'm trying to compile it on FreeBSD-4.8, here is what I get:
> 
> ./configure --enable-ssl --enable-command-args
> [config works fine]
> <snip>
> 
> # make all
> cd ./src/; make ; cd ..
> gcc -g -O2 -I/usr/local/include/openssl -DHAVE_CONFIG_H -L/usr/local/lib  
> -lssl -lcrypto -o nrpe  nrpe.c utils.c
> nrpe.c: In function `validate_request':
> nrpe.c:1327: `x' undeclared (first use in this function)
> nrpe.c:1327: (Each undeclared identifier is reported only once
> nrpe.c:1327: for each function it appears in.)
> *** Error code 1
> 
> Stop in /usr/local/src/nrpe-2.0b2/src.
> *** Error code 1
> 
> Stop in /usr/local/src/nrpe-2.0b2.
> #
> 
> It's definitly in the "arguments" part of the code. I defined x in nrpe.c 
> and while it compiled, nrpe didn't work then. I'm sure I just defined it 
> wrong. Anyone know how it should be defined and where in nrpe.c it should 
> be defined? 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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
> 

-- 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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