ld: 0711-317 ERROR: Undefined symbol: .VA_COPY <-- Can anyone tell me how to fix this????

[Andreas Ericsson]

Kenneth Klein wrote:
> I finally got nagios to "make all" and make etc. Then I dl.ed the source 
> for the plugins, I grabbed the latest stable verson.
> 
> I got this error when I ran make all.
> 
> ar: Creating an archive file libsnprintf.a.
>        gcc  -g -O2  -L. -L/lib -o check_disk  check_disk.o utils.o 
> ../lib/libnagiosplug.a popen.o -lsnprintf -lsnprintf
> ld: 0711-317 ERROR: Undefined symbol: .VA_COPY
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more 
> information.
> collect2: ld returned 8 exit status
> make: 1254-004 The error code from the last command is 1.
> 

The configure script seems to not have picked up that your system can't 
handle the VA_COPY macro properly. There are macros for it in 
lib/snprintf.c which can circumvent this. Adding
#undef HAVE_VA_COPY
#undef HAVE__VA_COPY
to the top of the file should at least make the plugins compile, 
although I can't guarantee they won't segfault en masse. That will 
depend on your systems vsprintf() implementation.

If it's at all possible, you should try running Nagios on either Linux 
or *BSD. Older systems doesn't have the asprintf() function and the 
current plugin distribution sadly relies heavily on it being there.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
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_id=7477&alloc_id=16492&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