* Gregor Zattler <telegr...@gmx.net> [2016-10-11 23:07 +0200]:

> Hi Elimar,
> * Elimar Riesebieter <riese...@lxtec.de> [07. Okt. 2016]:
> > * Gregor Zattler <telegr...@gmx.net> [2016-10-07 00:18 +0200]:
> >> * Elimar Riesebieter <riese...@lxtec.de> [06. Okt. 2016]:
> > [...]
> >>> What tells
> >>> $ ldd $(which mutt) | grep xapian?
> >> 
> >> libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 
> >> (0x00007f7f4d900000)
> > 
> > On my systems mutt 1.7.0-6 should have been build against
> > libxapian-dev 1.4 which let mutt point to:
> > 
> > libxapian.so.30 => /usr/lib/i386-linux-gnu/sse2/libxapian.so.30 (0xb680e000)
> > libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
> > (0x00007f9790569000)
> > 
> > From where did you get the mutt package? Did you compiled it by
> > your self?
> 
> This is mutt-1.70-6 from testing repository but I compiled
> notmuch myself and this was the reason fro the wrong library
> version (don't ask me why.  Since I updated notmuch
> 
> $ ldd $(which mutt) | grep xapian
>         libxapian.so.30 =>
>         /usr/lib/x86_64-linux-gnu/libxapian.so.30
>         (0x00007fad41a27000)

So bug closed hereby.

Thanks
Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

Attachment: signature.asc
Description: PGP signature

Reply via email to