David Welton wrote:
ok, I changed it by hand. 'svn diff' produces a patch quite similar
to the one you passed me. I compiled and restarted apache
Cannot load /home/manghi/Projects/rivet/1_0/src/.libs/mod_rivet.so
into server:
/home/manghi/Projects/rivet/1_0/src/.libs/mod_rivet.so: undefined
symbol: Rivet_Init
I'm not an expert of the autotools galaxy, but Makefile.am in src
is quite simple. The only thing I can say is that I don't see
a clear connection between mod_rivet.so and librivet.so expressed
in this file. Therefore I don't know if it's correct to expect the
2 library to link up dynamically. As someone wrote in src/Makefile.am,
autotools are 'weird and magic' and being a magician is not everybody's
art, so i can be missing totally the point.
Hrm... bizarre. I'll see if I can take a look at that some time this
week.
Hi David, I'm getting out of a really busy time (lectures, kids flue etc)
I made Rivet work again by statically linking the libraries into the module.
This is obtained simply appending $(lib_libexec_LTLIBRARIES) to
mod_rivet_la_LIBADD in src/Makefile.am. No fancy autotools macros.
'configure' complains about the non portability of the method,
but at least I got the module into apache again with the commands I
wanted to have.
the question now is: where mod_rivet.so expects to find librivet.so and
librivetparser.so? /usr/lib didn't work and lib_libexecdir didn't
work either... the latter is evaluated as /usr/share/rivet0.7.0
any hint?
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
