[Bug 1207584] Re: lucene++ is built using the custom allocator configuration

2013-08-16 Thread Łukasz Zemczak
Released in latest lucene++. ** Changed in: lucene++ (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207584 Title: lucene++ is built using the

[Bug 1207584] Re: lucene++ is built using the custom allocator configuration

2013-08-04 Thread James Henstridge
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:

[Bug 1207584] Re: lucene++ is built using the custom allocator configuration

2013-08-02 Thread James Henstridge
I built a test package using this change, and was able to successfully build the media scanner with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207584 Title: lucene++ is built using the

[Bug 1207584] Re: lucene++ is built using the custom allocator configuration

2013-08-02 Thread Łukasz Zemczak
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. ** Changed in: lucene++ (Ubuntu) Assignee: (unassigned) = Łukasz Zemczak (sil2100) ** Changed in: lucene++ (Ubuntu) Status: New = In

[Bug 1207584] Re: lucene++ is built using the custom allocator configuration

2013-08-02 Thread Łukasz Zemczak
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