lucene++ is built using the custom allocator configuration

[James Henstridge]

To build the media scanner, we need lucene++ to be built using the standard allocator, which doesn't seem to be the case with the 3.4.0-0ubuntu1 package:

   $ grep LPP_USE_ALLOCATOR /usr/include/lucene++/Config.h
   #define LPP_USE_ALLOCATOR

The problem is in the debian/rules file, where it passes the flag "-DLPP_USE_ALLOCATOR:BOOL=OFF" to cmake. The actual flag that luene++'s cmake configuration expects to control this is "-DENABLE_STANDARD_ALLOCATOR:BOOL=ON".

[James Henstridge (jamesh)]

I built a test package using this change, and was able to successfully build the media scanner with it.

[Łukasz Zemczak (sil2100)]

This is being worked on. I fixed it in the pre-ubuntu2 version, just I'm encountering issues with other features we want to add, like multiarch.

[Łukasz Zemczak (sil2100)]

I have officially encountered a problem when building the final package with -DENABLE_STANDARD_ALLOCATOR:BOOL=ON. I am getting lots of undefined reference to `Lucene::Analyzer::getPreviousTokenStream()' etc. during linking of ../../bin/lucene++-tester. The same source passes without any problems with the same flag passed as OFF. Strange!

[James Henstridge (jamesh)]

I still haven't managed to reproduce the problem you ran into. I did another test build of the package, and also built it successfully in my PPA with the following diff to the current Saucy package:

https://launchpad.net/~jamesh/+archive/ppa/+files/lucene%2B%2B_3.0.4-0ubuntu1_3.0.4-0ubuntu1%2Bjh1.diff.gz

[Łukasz Zemczak (sil2100)]

Released in latest lucene++.