rooneg at electricjellyfish
Jul 25, 2005, 4:57 PM
Views: 6172
Permalink
|
|
Re: bad liblucene4c.la while building lucene4c
[In reply to]
|
|
steve johnson wrote:
> I really don't mean to be obtuse but as I previously
> mentioned I've never used libtool (of any variant). I
> suspect I have to hack the generated Makefile to link
> against the .so but damned if I can even find the
> correct section. A pointer to the Makefile section to
> hack would be greatly appreciated.
Actually, I'm not sure if you'll have to hack the makefile or not...
I'd try just removing the .la file and running make, and seeing if it
does anything useful. If it doesn't, I don't think I can really be much
help to you, since I don't actually have a copy the mod_mbox makefile,
since I don't work on mod_mbox, and I suspect if hand-hacking is needed
that's where it would be.
Another thing to think about is the fact that when building mod_mbox you
might want to try making it use jlibtool, just like Lucene4C does. I
mean Lucene4C manages to get at least one binary (the lcn command line
tool) to link against its library, so jlibtool does apparently manage to
do it in at least some circumstances. If the libtool you're using with
mod_mbox can't seem to do the same thing, it could be that it's GNU
libtool, not jlibtool.
-garrett
|
