At 2:47 AM -0800 2/17/01, Joe R. Jah wrote:
>___Flags used in configuration:
>
>CFLAGS="-O2"
>CXXFLAGS="-O2"
>CPPFLAGS="-I/usr/local/GCC/include/g++-3 -L/usr/local/GCC/lib"
>CC="/usr/local/bin/egcs"
>CXX="/usr/local/bin/egcs++"
>export CFLAGS CXXFLAGS CPPFLAGS CC CXX C++
>
>___Rundig results:
>
>htdig: can't load library 'libstdc++-2.so.3'
>htpurge: can't load library 'libstdc++-2.so.3'
>htnotify: can't load library 'libstdc++-2.so.3'
>htfuzzy: can't load library 'libstdc++-2.so.3'
>htfuzzy: can't load library 'libstdc++-2.so.3'
This is a different matter entirely--it's saying that the runtime
loader can't find the library. At this point it's very
platform-dependent and I've never used BSDI, so I can't offer a
specific fix. I'll re-outline my comments from yesterday:
Read the man page for ld and/or ld.so. Look to see if it supports the
LD_RUN_PATH environment variable (which sets the loader paths during
compile-time). If so, see <http://www.htdig.org/FAQ.html#q3.6>. If
not, you may have a Linux-like dynamic loader, in which case you'll
need to set a config file with the paths for libraries.
--
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
Information: http://lists.sourceforge.net/lists/listinfo/htdig-general
FAQ: http://htdig.sourceforge.net/FAQ.html
