similar to: Compiling xapian-bindings-0.9.2 on OpenBSD 3.7

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]: ??????

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

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

Resurrecting an old thread from 2012! Finally got back to working on this. I have been stuck in JavaScript land for too long. Come to find out, on windows, perl does indeed define open to be win32_open and close to be win32_close. This is done in perl/lib/CORE/win3iop.h. So, to get past this problem, I had to modify Xapian.xs to do an #undef of open and close if WIN32 is defined. Also, I had

Hi All, I am compiling the development code of xapian ( http://trac.xapian.org/browser/trunk) and while doing *'make*' it will give following error PYTHONPATH="xapian:$PYTHONPATH" /usr/bin/python -c "import _xapian" Traceback (most recent call last): File "<string>", line 1, in <module> ImportError:

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

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

On Tue, May 23, 2023 at 03:06:50AM +0000, nebulaaksum wrote: > You said, " Generally xapian-bindings with a newer xapian-core (within > the same stable release series) should work." > But it is the newer xapian-core-1.4.22 which is installed in my system > already that is having Xapian library version 1.4.18, So the > xapian-bindings-1.4.22 is saying the core an older

Hi Compilation of 1.3.7 dies with the following configuration: ==================================== ./configure --enable-shared --enable-static --disable-sse --disable-backend-inmemory --disable-backend-remote ==================================== During the compilation I get the following error: ==================================== /bin/bash ./libtool --tag=CXX --mode=link g++ -fshow-column

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

Hello I'm new with the Xapian and I'm trying to install it in Windows XP SP2. I'm using CygWin (the full version). Have already compiled the xapian-core, using a change found in gmane for the file safewindows.h In cygwin path usr/local/ have the xapian lib etc. For the binding the ./configure command passes ok. when the make starts I get the folowing : .... MANY ERRORS at

Oh Olly, you are so kind. Thank you so much. I think you pinned out my problem. I have installed the xapian-core-1.4.22 at /usr/local/xapian-core-1.4.22 to avoid cluttering. I will try to do what you have given me. if that does not work, I will try to remove the older xapian-core-1.4.18 library wherever it is if I can locate it. Then I will give the path for the new one. GTK is just one of the

I posted this message first. But it was missing so I post again. I think there is a some bug in build configration files. Can you check up the following errors and fix it? The error has no concern with UTF-8 patch. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- [root at saturn xapian-core-0.9.4_svn6707]# make ... ... mkdir .libs/libxapian.lax/libqueryparser.a

On Wed, Feb 12, 2014 at 10:32:03PM +0800, Hurricane Tong wrote: > I seem to run into some trouble. > I succeeded in building the source code of Xapian in ubuntu, > but when I write a demo c++ application > > [snip] > I can't get it built. > > > hurricanetong at hurricanetong-VirtualBox:~/workspace$ g++ -L/usr/local/lib -lxapian-1.3 BuildIndexDemo.cpp Hmmm,

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

The disclaimer automatically added and is not intended to limit legitimate discourse, and any code I write for this is expected to be licensed under whatever license the original work is using. I haven't tried compiling latest code under visual studio yet (is this possible?). I wonder if there is a way to tell gcc to not mangle the names during cross compile. I was able to successfully

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

I uninstall xapian1.3 and install xapian-1.2.17 but i still failed hurricanetong at hurricanetong-VirtualBox:~/workspace$ g++ `xapian-config --cxxflags --libs` demo2.cc /tmp/cc2wsfDJ.o: In function `main': demo2.cc:(.text+0x4a): undefined reference to `Xapian::WritableDatabase::WritableDatabase(std::basic_string<char, std::char_traits<char>, std::allocator<char> >

Thank you very much,It works! And some Q&A I meet,may help somebody: 1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat'; 2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7"; 3. If Somebody write a demo in VS2017 3.1 change libxapian.a's name to libxapian.lib; 3.2 make sure the