similar to: Re: [Xapian-commits] 7938: trunk/xapian-maintainer-tools/win32msvc/

On Thu, Apr 12, 2007 at 12:52:03PM +0100, richard wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: richard > Revision: 8196 > Date: 2007-04-12 12:52:02 +0100 (Thu, 12 Apr 2007) > > Log message (1 line): > Fix rules for generating .pl files from .pl.in files. > > Modified files: > U

On Tue, Jan 02, 2007 at 03:55:59PM +0000, richard wrote: > * backends/quartz/btree.cc,backends/flint/flint_io.h: Patches from > Charlie Hull to allow 2GB+ index files work when compiled using > Visual C++. I suspect that xapian-compact.cc (and quartzcompact.cc if you can be bothered) will also need fixing since they use off_t. You need to make sure that the stat() function called

On Wed, Mar 07, 2007 at 11:22:36PM +0000, olly wrote: > docs/Makefile.am: Stop shipping docs/apidoc/latex/* in the > xapian-core tarballs since it's just useless bloat. Removing it > more than halves the size of the tarball (55% reduction!) Hmm, this is very odd. I tried unpacking the last xapian-core snapshot tarball, deleting the junk files, and rebuilding the tarball, and I got

I spotted recently that since we switched to git, commit notifications haven't been sent to the xapian-commits list. We can probably install a hook for git to get them flowing again, but given that none of the ~20 subscribers to the list has complained, I'm wondering if a list for commits is still useful. Perhaps with a decentralised version control system it isn't, though the

On Mon, Oct 01, 2007 at 01:13:07PM +0100, richard wrote: > Log message (3 lines): > net/remoteconnection.cc: After calling read(), check for received > == 0 after checking for errors, so that if an EINTR occurs in > read, we don't report EOF instead of retrying. > [...] > http://xapian.org/C?9389?trunk/xapian-core/net/remoteconnection.cc I don't think this change is

On Wed, Dec 13, 2006 at 06:09:49PM +0000, richard wrote: > Improve documentation comment for Document::get_value(). Further to this improvement, I wonder if the "must be >= 0" should be dropped. Xapian::valueno is an unsigned type, so you effectively can't pass a negative value in (if you do it'll be converted to a large positive value and would work if used

On Wed, Oct 04, 2006 at 01:27:20PM +0100, richard wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: richard > Revision: 7283 > Date: 2006-10-04 13:27:17 +0100 (Wed, 04 Oct 2006) > > Log message (2 lines): > Use "unsigned char" instead of "char" when serialising lengths, to avoid > problems on platforms where char is

On Mon, Apr 09, 2007 at 11:26:44AM +0100, richard wrote: > backends/flint/flint_database.cc: Fix bug with document lengths > in replace document. Was using doclens.insert() to set the new > document length, but this has no effect if the entry already > exists. Argh! That issue has bitten us at least once before. I'll audit all uses of insert to see if there are any other

On Fri, Oct 06, 2006 at 05:36:47PM +0100, richard wrote: > tests/runtest.in: Cache result of test for $VG_LOG_FD if we find the new > option. Saves 2 seconds for each invocation on my machine, which is half the > time when running just a single simple test. Nice speed up, although we might as well just remove the option and send valgrind's output to /dev/null as things currently

On Thu, Mar 01, 2007 at 03:29:26PM +0000, richard wrote: > * common/utils.c,common/utils.h: For windows, add an om_tostring()function for > 64 bit integers: time() and GetProcessId() return these, and without this, > backends/quartz/quartz_log.cc reports an error. This change generates a new warning in the mingw cross-build: common/utils.cc:82: warning: int format, different type

On Wed, Apr 11, 2007 at 10:31:39AM +0100, richard wrote: > python/smoketest.py: Replace cut-and-pasted test checking code > with functions, to simplify tests. It might be simpler, but mostly because functionality has gone - you've thrown away all my carefully written failure messages! Now if a test fails, the message is very generic and you have to read the code to find out what's

On Thu, Mar 29, 2007 at 03:39:01PM +0100, richard wrote: > bin/xapian-tcpsrv.cc,tests/harness/testsuite.cc: First of many > parts of a large patch from Mark Hammond working towards enabling > remote databases on windows. When displaying errors which might > be socket errors, display the error number as well as the output > of strerror - on windows, strerror doesn't display

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

On Tue, Mar 06, 2007 at 09:07:04AM +0000, richard wrote: > * HACKING: Note on running preautoreconf and autoreconf to keep SVN > builds working. What's the scenario in which you have to run them by hand? I'd rather fix this to just work automatically than document deficiencies in the build system. I fixed a problem a few weeks ago with removed files which were listed in

On Wed, Apr 18, 2007 at 02:59:19PM +0100, richard wrote: > HACKING: Minimal changes to make this into valid restructured > text. It's cute that minimal changes are required to do that, but is this really useful? Now when I load HACKING into vim it displays the last 100+ lines in inverse video, which it didn't do before. That actually makes this document harder to read for probably

On Sun, Mar 03, 2019 at 05:13:09PM +0000, James Aylett wrote: > On 3 Mar 2019, at 17:01, Olly Betts <olly at survex.com> wrote: > > > I suspect what's going on here is that bootstrap will by default > > download, build and install (into a subdirectory of the build tree) any > > of the autotools for which suitable versions aren't already installed. > >

I've uploaded Xapian 1.0.7, which as usual you can download from: http://xapian.org/download This release fixes an assortment of bugs, and improves efficiency in a few cases. It's intended to be a relatively safe incremental update over 1.0.6. For a more detailed overview see: http://trac.xapian.org/wiki/ReleaseOverview/1.0.7 The full lists of user-visible changes are linked to from

hi, I'm using Xapian on Windows with large files. My index directory is about 65 607 466 693 bytes: 2007-01-30 09:28 17 position_baseA 2007-01-30 10:06 17 position_baseB 2007-01-23 14:18 0 position_DB 2007-01-30 10:06 360 496 postlist_baseB 2007-01-30 10:06 23 623 852 032 postlist_DB 2007-01-30 10:06 88 432

On Wed, Mar 07, 2007 at 11:45:13AM +0000, richard wrote: > * configure.ac: Add -D_FORTIFY_SOURCE to AM_CXXFLAGS for GCC > builds. According to glibc CVS support for this was added in > October 2004, but it doesn't seem to be documented very well, > other than in features.h. I'd not come across this before, so I had a quick poke around. It's hardly documented *well* in

On Thu, 18 Apr 2024 at 06:24, Olly Betts <olly at survex.com> wrote: [ ... ] > Yes - it's in the xapian-omega package you already have installed: > > /usr/lib/cgi-bin/omega/omega Thank you, Mr. Betts. for your replying to my questions. Please consider me a novice and elaborate further, Mr. Betts. > You may need to configure apache to tell it to use this for a URL on