aces4me at yahoo
Jul 25, 2005, 4:56 PM
Views: 6193
Permalink
|
|
Re: bad liblucene4c.la while building lucene4c
[In reply to]
|
|
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.
Steve
Who is starting to miss the bad old days when I had to
write the Makefile myself.
--- Garrett Rooney <rooneg [at] electricjellyfish>
wrote:
> steve johnson wrote:
> > I am trying to build lucene4c to use with mod_mbox
> for
> > a SoC project. I have checked out the gcj-backend
> > branch of lucene4c, checked out the trunk version
> of
> > apr and built it with the experimental library
> > enabled, and built lucene4c with gcj4. The
> resultant
> > liblucene4c.la file looks like this:
> >
> > /usr/local/lib
> >
> >
> > I have never used libtool before but that .la
> doesn't
> > look like any others I have seen and mod_mbox
> doesn't
> > like it either:
> >
> > libtool: link: `/usr/local/lib/liblucene4c.la' is
> not
> > a valid libtool archive
> >
> > Anyone have a suggestion?
>
> Try removing liblucene4c.la and just linking
> directly against
> liblucene4c.so? I imagine this is a problem with
> jlibtool, and enough
> peopl ehave mentioned it at this point that I guess
> we're going to have
> to do something about it sooner rather than later...
>
> -garrett
>
|
