[Xapian-discuss] ucs2 build of xapian?

[Jason Witherspoon]

Hey Olly--

Again, thanks so much for your help and time.  I must now bow out red-facedly, as my entire problem seems to've been caused by an errant:

sys.path.insert(0, "/usr/lib/python2.5/site-packages/")

in my script headers.  Can't remember what I was thinking/why the heck I put that there, but needless to say, removing it solves my problems.

Thanks again!


-----Original Message-----
From: Olly Betts [mailto:olly at survex.com]
Sent: Wed 12/19/2007 6:42 PM
To: Jason Witherspoon
Cc: Xapian Discussion
Subject: Re: [Xapian-discuss] ucs2 build of xapian?
 
On Wed, Dec 19, 2007 at 03:04:08PM -0800, Jason Witherspoon wrote:
> So I have no /usr/include/python2.5/pyconfig.h file.  It seems to be
> in /usr/local/include/python2.5/pyconfig.h for whatever reason,

Did you compile it yourself?  Generally autoconf-based packages you
build yourself default to installing in /usr/local unless you specify
--prefix to configure.

But it's odd that the original error message showed that the Xapian
python bindings had installed themselves here:
    
/usr/lib/python2.5/site-packages/xapian.py
    
> it's "#define Py_UNICODE_SIZE 2"

Well, that much is good.

> However, there is a /usr/include/python2.4/pyconfig.h (not
> /usr/local/..., NB) file, which returns "#define
> Py_UNICODE_SIZE 4"
>  
> The active Python is definitely 2.5.1, but maybe Xapian is pulling the
> old 2.4 pyconfig file...?

What configure does is to find a Python interpreter and ask it where the
headers are, where extensions should be installed, etc.  So it should be
able to pick mismatching settings, but perhaps there's a flaw in how
this is done.

Let's see what configure has found - in your xapian-bindings build tree,
what does this command output?

grep -i python config.log

Cheers,
    Olly