similar to: Xapian Binding compile error in Windows XP using CygWin

Hi all. I have problem compiling xapian php bindings. I am using debian sarge. I have installed php4-dev before compilation. I am getting the following errors: boomer:~/xapian/xapian-bindings-0.9.0# make make all-recursive make[1]: Entering directory `/root/xapian/xapian-bindings-0.9.0' Making all in php4 make[2]: Entering directory `/root/xapian/xapian-bindings-0.9.0/php4' make

Hi, I'm on a Ubuntu 18.04 server, trying to use django-haystack with xapian in a python3.6 virtualenv. The virtualenv is set up not to use system packages, meaning that I can't just install python3-xapian-haystack with apt, and instead have to manually build xapian-core and xapian-bindings within the virtualenv. This works with xapian-core and the --prefix argument to configure. When I

Hi? I am a beginer. And I want to try this searcher. When I configure and building Xapian-bingdings, I met this problem. I type "make" then got some error info: That appear like this: jack at jack-desktop:~/SE/xapian-bindings-1.2.5$ make make all-recursive make[1]: ?????? `/home/jack/SE/xapian-bindings-1.2.5' Making all in python make[2]: ??????

Hello, Compiling xapian-core-0.9.2 worked fine, and make check reported that the tests ran without problems (although it skipped some near the end). Now I'm trying to compile xapian-bindings-0.9.2 on OpenBSD 3.7 but have run into a problem. After hours of searching the net I haven't found a solution. For reference gcc -v gives the following output: Configured with: Thread model: single

With the new "stamp" rules for running SWIG, things don't seem to get rebuilt when I expect them to, e.g.: olly at ixion:~/svn/xapian/xapian-bindings/python $ make modern/xapian_wrap.cc make: Nothing to be done for `modern/xapian_wrap.cc'. olly at ixion:~/svn/xapian/xapian-bindings/python $ ls -l modern/xapian_wrap.cc ls: modern/xapian_wrap.cc: No such file or directory Problem

This is the output of the 'make' command for the python bindings (0.9.2). xapian-core compiles fine. aiolia:~/Desktop/2005-08-01/xapian-bindings-0.9.2 dialtone$ make make all-recursive Making all in python make all-recursive Making all in docs Making all in examples make[5]: Nothing to be done for `all'. make[5]: Nothing to be done for `all-am'. /bin/sh ../libtool --tag=CXX

I'm having a problem compiling the python 2.1 packages for release 0.9.1 - I get many errors along the lines of: ../../python/olde/xapian_wrap.cc: In function `PyObject* PySwigObject_repr(PySwigObject*)': ../../python/olde/xapian_wrap.cc:664: error: `PyString_FromFormat' undeclared (first use this function) On further investigation, the copies of xapian_wrap.cc in the olde and

Questions are threaded into the output: ******************** #./configure --without-python checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking

As discussed on IRC. The naming conventions aren't ideal, but the intent feels right and it works for me. J -- /--------------------------------------------------------------------------\ James Aylett xapian.org james at tartarus.org uncertaintydivision.org -------------- next part -------------- Index:

I've uploaded Xapian 1.2.6 (including Search::Xapian 1.2.6.0). As usual you can download from: http://xapian.org/download You can read an overview of the release here: http://trac.xapian.org/wiki/ReleaseOverview/1.2.6 The full lists of user-visible changes are linked to from there, and also from the "[news]" links on the download page. As always, if you encounter problems,

On Tue, Oct 02, 2018 at 04:13:14PM -0700, Eric Abrahamsen wrote: > ./configure --prefix=$venv --with-python3 > > The configure process looks fine: xapian-config is found correctly, as > is my virtualenv python installation. Then I export LD_LIBRARY_PATH as > $venv/lib. You shouldn't need to set LD_LIBRARY_PATH - libtool should set rpath when linking against a library outside

hi i?m trying to build the ruby bindings in xapian 1.1.2 on win xp. i?ve 1. pulled the tags/1.1.2 revision from svn 2. built SWIG from repo via MinGW and MSYS (swig -help works, so build seems ok to me) 3. built xapian-core following readme in ...\win32msvc, apitest doesn?t give errors now if i try to build: "...\ruby>nmake SWIGBUILD=1 Microsoft (R) Program

Message body follows: Hi, I'm interested in Xapian as a possible search engine for a Python project I'm developing. The reason why I write to you, is that I saw that you've been fixing bugs... so please excuse me if I'm bothering you: I saw no other contact on the xapian.org web pages. I've been spending the last two days trying to set up Python bindings for the library

Message body follows: Hi, I'm interested in Xapian as a possible search engine for a Python project I'm developing. The reason why I write to you, is that I saw that you've been fixing bugs... so please excuse me if I'm bothering you: I saw no other contact on the xapian.org web pages. I've been spending the last two days trying to set up Python bindings for the library

Carrying on this conversation: http://lists.tartarus.org/pipermail/xapian-discuss/2007-March/003513.html void TermGenerator::set_stopper(stopper) Stopper * stopper CODE: // FIXME: no corresponding SvREFCNT_dec(), but a leak seems better than // a SEGV! SvREFCNT_inc(ST(1)); THIS->set_stopper(stopper); It would be good to fix these FIXMEs. A class-level HASH could be

Hi, I have been experimenting with simpleindex.php in the php4 examples. However, the command seems to crash on exit: $ php simpleindex.php h < simpleindex.php Segmentation fault I ran it through gdb to get a stack trace (see below). It looks to me as if the WritableDatabase may be getting deleted twice. Can this be fixed, or alternatively is there any work around? I'd have a look at

A short note: this message comes as a public reply to a discussion about xapian-bindings, that is why it can look a little bit incomplete... however the problem for now was to modify the xapian-core distribution so that there are symbols #defined (or maybe #undefined) to reflect what backends were available in the library. As I said to Olly, I'm a complete newbie at Autotools (and SWIG), so

(following my mail in xapian-discuss on 11.06) I revisited my resource file and came up with a much simpler solution. I'm now using the new version.h file (no need to duplicate version strings) and add php-src to the include path given to rc.exe so I can get the precise php version. On my windows, the resulting dll appears as "Xapian 1.0.1 bindings for PHP 5.2.2" Here is what I

Hi All Is there any reason why someone could not build a regular PHP extension (not using SWIG) for Xapian? Same as mnoGoSearch has. The extension itself would be released under the PHP license. Is there anything on either side of the pond that would prevent this from being legal? Alec

Hello, this is a question that could be answered by collaborators of the Ruby bindings. Today I've played around with the Xapian::MultiValueSorter class. I've set everything up and then I tried following on an instance of Xapian::Enquire: : enquire = Xapian::Enquire.new(database) enquire.query = options[:query] : sorter = Xapian::MultiValueSorter.new sorter.add(0, true) sorter.add(1,