Dear Rodrigo
What command is printing this error? It looks like it's a problem with
the build process not a problem with rivet itself. Rivet autotools don't
have any explicit references to that particular library, library names
and locations are poked into the Makefile by the autotools collection of
scripts, which use data fetched from various sources, including
tclConfig.sh. Would you please tell us what your ./configure command
line looks like?
-- Massimo
On 09/27/2015 11:02 PM, Rodrigo Readi wrote:
Dear Sirs!
I compiled httpd-2.4.16, tcl8.6.4, rivet-2.2.3 on OpenBSD 4.8.
When compiling rivet I get the warning:
*** Warning: linker path does not have real file for library -ltclstub86.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libtclstub86 and none of the candidates passed a file format test
*** using a regex pattern. Last file checked: /usr/opt/tcl864/lib/libtclstub86.a
*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module librivetlib. Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.
<<
By the way, I never saw something like libtclstub86.so in Tcl.
I cannot start httpd with this module, I get in err_log:
[Sun Sep 27 15:48:51.459452 2015] [:error] [pid 8003:tid 2347695104] (20014)
Internal error (specific information not available): mod_rivet: Error
loading rivetlib package: can't find package rivetlib exactly 2.2.3
<<
Any Hint, how to solve this problem?
I would try to link mod_rivet and httpd statically, but I did not find
instruction of
how to do it.
Thanks
Rodrigo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
