Xapian discuss - Jan 2006 - Compiling xapian on Ubuntu Breezy

It's not hard to compile the normal xapian stuff but if you download
svn it can be tricky to compile the complete release.

1)   Get swig 1.3.26 or higher from swig.org.  The Breezy packages are too old.

The rest is only needed for cvssearch.

2)  `apt-get install libdb4.1++-dev`
3)   Download the recent pstream.h from pstreams.sf.net
      Replace cvssearch/db/pstream.h and cvssearch/map/process/pstream.h
4)  I couldn't figure out where uint_to_string() came from so I
rewrote it, and there was another typo in that same file.  The patch
is attached.

regards,
dan carpenter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff-alignment
Type: application/octet-stream
Size: 1283 bytes
Desc: not available
Url :
http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20060112/f8fac9c8/diff-alignment-0001.obj

On Thu, Jan 12, 2006 at 09:48:17PM -0800, Dan Carpenter
wrote:
> It's not hard to compile the normal xapian stuff but if you download
> svn it can be tricky to compile the complete release.
> 
> 1)   Get swig 1.3.26 or higher from swig.org.  The Breezy packages are too
old.
Unless you're actually wanting to do development work on Xapian, I'd
generally recommend using the SVN snapshots from here:

http://www.oligarchy.co.uk/xapian/trunk/

They're already bootstrapped so you don't need the right versions of the
autotools or SWIG installed.  Plus they aren't generated if SVN trunk is
too broken to bootstrap, which is rare, but annoying if you're just
wanting to try out something newer than the last release.

The only real downside is that you need to download a whole new set of
tarballs, rather than being able to incrementally update using SVN.
> The rest is only needed for cvssearch.
> 
> 2)  `apt-get install libdb4.1++-dev`
> 3)   Download the recent pstream.h from pstreams.sf.net
>       Replace cvssearch/db/pstream.h and cvssearch/map/process/pstream.h
Why's this needed?  Is the older pstream.h not usable with modern C++
compilers or something like that?
> 4)  I couldn't figure out where uint_to_string() came from so I
> rewrote it, and there was another typo in that same file.  The patch
> is attached.
Thanks, I'll apply it.

Beware that cvssearch isn't really release quality at present (as you
may have guessed...)

Cheers,
    Olly

On Thu, Jan 12, 2006 at 09:48:17PM -0800, Dan Carpenter
wrote:
> 4)  I couldn't figure out where uint_to_string() came from so I
> rewrote it, and there was another typo in that same file.  The patch
> is attached.
It's in db/util.h, but that's not included by the alignment code.
I think I must have been in the middle of working on this and got
distracted.

Anyhow, I've fixed everything you reported.

Cheers,
    Olly