similar to: Re: [Xapian-commits] 8181: trunk/xapian-bindings/ trunk/xapian-bindings/python/

Hi all, I'm getting an error in the smoketest. I'm using latest Swig and Python bindings from SVN-HEAD: File "smoketest.py", line 23, in <module> import xapian File "C:\work\xapian\xapian-SVN\xapian-core\win32\Release\Python\xapian.py", line 2099, in <module> ValueRangeProcessor.__call__ = ValueRangeProcessor.__call AttributeError: type

Dear Xapian developers, I am happy to announce that the Xapian-Ruby bindings now pass all tests defined in smoketest.rb. (These tests are mostly drawn from smoketest.py; a few tests that are not applicable to the Ruby version have been removed.) I have also added Olly's patch to integrate the Ruby bindings into the automake/configure scripts. The latest version is available by anonymous

I'm posting this here to help others who might be having the same issue. I maintain xapian-core ruby gem. I was trying to upgrade to 1.4.2 and had some issues. The generated makefile doesn’t work because of the following: docs/rdocs/index.html: docs/xapian.rb rm -rf docs/rdocs $(MKDIR_P) docs cd docs && $(RDOC) --op rdocs `test -f xapian.rb||echo '$(abs_srcdir)/'`xapian.rb

Hello, I am attempting to run the smoketest.php file from my devserver and am getting nothing but errors. It looks like it did not install correctly. Yesterday I compiled the source on os x and it appeared to install just fine, but now it is not working at all. I tried to replace the location of the xapian.php file with a hardcoded located and got a different set of errors. Here are

Hi Olly and co, On an Ubuntu 15.10, following the docs at https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package When running debuild -e PHP_VERSIONS=5 -us -uc I get (sorry for the French): " dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: paquet source xapian-bindings dpkg-buildpackage: version source 1.2.21-2.1 dpkg-buildpackage: distribution source unstable

Oh, by the way, just running `make all` works fine too, which is what I am now doing in the gem.. but fixing the makefile would retain the existing working behaviour of `make clean all` which was fine in 1.2.x On 16 January 2017 at 14:21, Samuel Williams <space.ship.traveller at gmail.com> wrote: > I'm posting this here to help others who might be having the same issue. > > I

Hi all, There's been a odd bug reported to us by Daniel Menard while working on the PHP bindings: "I then tried to run the dotest target...All tests passed, except the one about get_matching_terms (smoketest.php line 94). I added this line before the exit: for ($i=0; $i<strlen($terms); $i++) echo $c=ord($terms[$i]), ' ', ($c>31?$terms[$i]:''), "\n";

I thought that I installed all the bindings but seems to me that I am missing xapian.so when I try to run smoketest.php Warning: dl(): Unable to load dynamic library '/usr/lib/php/extensions/xapian.so' - /usr/lib/php/extensions/xapian.so: cannot open shared object file: No such file or directory Can somebody send me the link to the module that I need to install? Thanks, Kevin

Dear Xapian community, We've been looking for a search engine to integrate with our Rails applications. Xapian seems to be the most robust and mature of any open source solution out there. But, there were no Ruby bindings. So... I've started work on Ruby SWIG bindings for Xapian. My work is still alpha-quality; expect bugs and expect API changes before we're done. It's

Le 26/03/16 18:04, Olly Betts a ?crit : > On Sat, Mar 26, 2016 at 04:51:35PM -0500, Yannick Warnier wrote: >> On an Ubuntu 15.10, following the docs at >> https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package >> >> When >> >> running debuild -e PHP_VERSIONS=5 -us -uc >> >> I get (sorry for the French): >> >> >> "

Hi - I've been fixing up the bindings to match the latest API. Should be able to commit later today or tomorrow. The smoketest on PHP isn't working any more, apparently because the inmemory backend isn't accessible (I haven't looked in detail - I fixed them for something I was doing). (Also some more magic iterators for the Python bindings.) J --

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

On Tue, May 11, 2004 at 06:11:36PM +0100, Richard Boulton wrote: > "xapian-config --cxxflags" assumes that it doesn't need to emit > -I/usr/include in this situation (presumably on the basis that > any sane C compiler will already have that on its path). Worse, passing -I/usr/include causes problems with some versions of GCC on some platforms as GCC generates

There are various other situations where we create symlinks instead of copying, and as some of these are used in libtool I've given up trying to build in the way I was doing. It's a little unfortunate, but as it's probably a bug in the linux NFS server, which isn't the best in the world anyway, let's just ignore everything there for the time being. However ``make

On Thu, Oct 21, 2004 at 05:45:42PM +0100, Olly Betts wrote: > Log message: > python/docs/bindings.html: Remove documentation explicitly saying > how we wrap Xapian::QueryParser and Xapian::Stem since we wrap them > exactly as we wrap everything else we don't mention! Also mention > simpleexpand example. The point of this comment was to highlight that they exist within the

On Sat, Mar 26, 2016 at 04:51:35PM -0500, Yannick Warnier wrote: > On an Ubuntu 15.10, following the docs at > https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package > > When > > running debuild -e PHP_VERSIONS=5 -us -uc > > I get (sorry for the French): > > > " > dpkg-buildpackage -rfakeroot -D -us -uc > dpkg-buildpackage: paquet source

On Thu, Apr 12, 2007 at 05:57:27PM +0100, richard wrote: > xapian.i: Parse the visibility support header file, so we don't > get errors when we %include other xapian headers. Fixes error > reported by python/except.i, which has a line saying > %include "xapian/error.h" That part is easy enough, but does "make check" now pass for you? My build is failing to

Le 26/03/16 18:44, Yannick Warnier a ?crit : > Le 26/03/16 18:04, Olly Betts a ?crit : >> On Sat, Mar 26, 2016 at 04:51:35PM -0500, Yannick Warnier wrote: >>> On an Ubuntu 15.10, following the docs at >>> https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package >>> >>> When >>> >>> running debuild -e PHP_VERSIONS=5 -us -uc

I'm cc:-ing my reply to xapian-devel, since others may have an opinion. In particular, James has probably done most work on the python bindings. On Fri, Jan 27, 2006 at 03:56:23PM -0800, Jason Toffaletti wrote: > I'm curious if boost::python has been considered for creating more > pythonic bindings to Xapian. I've used it to wrap several C++ libraries > and found the

Yesterday I updated the deprecation.rst document such that I think it contains all the items which are slated for deprecation (and also contains full details of the upgrade suggestions, as Olly suggested). I've marked several things which have been deprecated for a long period of time (ie, since 0.9.0 or earlier) for removal in 1.0.0, in line with the policy outlined in the document. If