Cocoon wrote:
> Can you write me exactly what I have to do "syntax" I will do it no
> problem...
Just run the commands in a terminal.
For instance here's the result in one Sparc/Solaris 8 machine:
--- --- --- ---
-bash-3.00$ gcc -print-prog-name=ld
/usr/ccs/bin/ld
-bash-3.00$ crle -v
Configuration file [3]: /var/ld/ld.config
Default Library Path (ELF):
/usr/local/lib:/opt/gnu/lib:/usr/lib:/usr/local/ssl/lib:/opt/ActiveTcl/lib:/export/home/apache2/lib:/export/home/apache2/modules
Trusted Directories (ELF): /usr/lib:/usr/local/ssl/lib:/usr/local/lib
Command line:
crle -c /var/ld/ld.config \
-l
/usr/local/lib:/opt/gnu/lib:/usr/lib:/usr/local/ssl/lib:/opt/ActiveTcl/lib:/export/home/apache2/lib:/export/home/apache2/modules
\
-s /usr/lib:/usr/local/ssl/lib:/usr/local/lib
--- --- --- ---
The first command (gcc -print-prog-name=ld) shows which ld is used by gcc, in my
case is the linker that comes with Solaris dev. tools.
The second command (crle -v) shows the default path used to search for
libraries, similar to setting LD_LIBRARY_PATH but with different paths for 32/64
bit libraries if applicable, the "trusted" path for libraries like SSL that need
access to restricted resources.
The existence of the required libraries is something configure takes care of, so
if you didn't see any complaint from configure you already have all the
requirements. But it's strange that ld complains while building the clamav
library, so I was asking what messages appeared just before the ones you showed
in the original message; there should be some names listing what is missing...
the cause could be as simple as having an old version of some library.
Hope this helps.
--
René Berber
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
