Hi Manuela,

It means that your os does not know where to look for the rrd library, 
this is probably caused by rrdtool's slightly odd default instalation 
location (/usr/local/rrdtool). If you compile rrdtool with 'configure 
--prefix=/usr/local', it will be installed in a more standard location, 
which means that the library is automaticaly in your library search path.

Or if you really want rrdtool to be in /usr/local/rrdtool, on Linux you 
can add this path to /etc/ld.so.conf and then run ldconfig. On Freebsd 
you can change the ldconfig_paths in /etc/rc.conf.

Regards,
Werner

Manuela Lima schreef:
> Hi everyone,
>
> I'm still getting problems during the ./configure from nfdump. Now, appears to
> me the message in the end of the ./ configure commmand:
>
> $ ./configure LDFLAGS='-L /usr/X11R6/lib -L /opt/csw/lib -L /opt/csw/include' 
> >
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for _LARGE_FILES value needed for large files... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ANSI C... (cached) none needed
> checking whether we are using SunPro C... no
> checking for bison... no
> checking for byacc... no
> checking for flex... flex
> checking for yywrap in -lfl... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for rrd_update in -lrrd... yes
> checking rrd.h usability... yes
> checking rrd.h presence... yes
> checking for rrd.h... yes
> configure: error: Can not load rrd library. Not in loader search path!
>
> What could possibly be now?
>
> Thanks in advance!
> --
> Abs,
>
> Manuela Lima
> Bolsista CAT/CBPF
>
> ------------------------------------------
> CBPF WebMail -  http://www.cbpf.br 
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Nfdump-discuss mailing list
> Nfdump-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfdump-discuss
>   


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Nfdump-discuss mailing list
Nfdump-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfdump-discuss

Reply via email to