Re: Linking a privately built -lxapian

[David Bremner]

Matt Armstrong  writes:

> I've got a privately built xapian 4.0 in my $HOME/opt/xapian-core-1.4.0
> dir, and its bin dir in my path.
>
> xapian-config is working like this:
>
> % xapian-config --libs
> -L/usr/local/google/home/marmstrong/opt/xapian-core-1.4.0/lib -lxapian

I don't think the notmuch configure script is very well set up for "one
package per hierarchy". That could probably improved, but a simple
workaround would be to install xapian and notmuch into the same
${foo}/{lib,bin} hierarchy, where foo=${HOME} and foo=/usr/local are
both reasonably well tested, I believe (although not by me).

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Linking a privately built -lxapian

[Matt Armstrong]

I've got a privately built xapian 4.0 in my $HOME/opt/xapian-core-1.4.0
dir, and its bin dir in my path.

xapian-config is working like this:

% xapian-config --libs
-L/usr/local/google/home/marmstrong/opt/xapian-core-1.4.0/lib -lxapian

Then "./configure; make" doesn't produce a functioning build unless I
run notmuch's make one of these two ways:

1) make LDFLAGS=-Wl,-rpath-link,$HOME/opt/xapian-core-1.4.0/lib
2) LD_RUN_PATH=$HOME/opt/xapian-core-1.4.0/lib make

I can live with that, but it brings back decade old memories.  Is there
a better way?

(I don't want to get into packaging up a xapian 1.4 .deb and installing
it on my box just to build notmuch)
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch