similar to: remotetcp_chert

Displaying 20 results from an estimated 400 matches similar to: "remotetcp_chert"

2016 Dec 13
0
remotetcp_chert
On Thu, Dec 08, 2016 at 10:08:40PM +0000, Eric Lindblad wrote: > Dear Olly Betts, > > same 32 bit > > compiler version > hardware > OS > OS version > > as here (where remotetcp_chert passed and skipped 3) > > xapian-core-1.2.21.tar.xz > > http://nurmi-labs.blogspot.com/2015/10/xapian.html That's over a year old - are you really running the exact
2016 Dec 11
0
old stable configure & make_check logs
I've posted the results of 'make check' for xapian "oldstable" (xapian-core-1.2.24) compiled on Slackware-14.0 (32 bit) here: http://nurmi-labs.blogspot.com/p/xapian-linux-old-stable-sse.html xapian-linux-old-stable-sse Summary ./apitest backend none: All 58 tests passed. ./apitest backend inmemory: All 228 tests passed, 8 skipped. ./apitest backend brass: All 304 tests
2015 Oct 07
0
brass and chert compiled / xapian port to Interix
Report by Eric Lindblad 06-10-2015 http://www.ericlindblad.blogspot.com cf: http://permalink.gmane.org/gmane.comp.search.xapian.general/9885 modifications allowing for brass and chert to compile on SFU Interix 3.5 (modified) [code change not performance critical] /xapian-core-1.2.21/backends/brass/brass_check.cc /xapian-core-1.2.21/backends/chert/chert_check.cc #include <climits> +
2011 Apr 17
3
Report for http://trac.xapian.org/wiki/SupportedPlatforms
Hello :-) There was probably no good reason to do this build but the Debian 6.0 Squeeze repo version was 1.2.3, we needed 1.2.4 and I didn't think of using the package from unstable. Arch: x86_64 Platform: Linux 2.6 Debian 6.0 (Squeeze) Compiler: gcc version 4.4.5 (Debian 4.4.5-8) Version: 1.2.4 Status: no known problems Source: http://oligarchy.co.uk/xapian/1.2.4/xapian-core-1.2.4.tar.gz
2015 Feb 06
2
Fwd: Waiting for Reply regarding "TestCases Failure"
> Is that the complete output? Yes it is the complete output against "./runtest ./apitest --verbose topercent2"( after running make remove-cached-databases). I attached the snapshot of the output of commands but the size of the email got bigger than 40kb so i had to place the output as text. If I do not run "make remove-cached-databases" and run "./runtest ./apitest
2015 Jan 26
2
TestCases Failure
Please find my inline reply. On 26 January 2015 at 06:56, Olly Betts <olly at survex.com> wrote: > On Sun, Jan 25, 2015 at 06:46:26PM +0500, Saad Ahmed wrote: > > I have been able to successfully build the code. But when I run the > > existing testcases (to verify everthing is working fine), It says 3 out > of > > the six testcases fails. Here is the report of the
2015 Jan 25
2
TestCases Failure
Hi, I am a student in Pakistan willing to contribute to Xapian. I have been able to successfully build the code. But when I run the existing testcases (to verify everthing is working fine), It says 3 out of the six testcases fails. Here is the report of the test cases. "... make check-TESTS make[5]: Entering directory `/home/saad/GitProjects/xapian/build/xapian-core/tests' Running
2015 Feb 03
2
Fwd: Waiting for Reply regarding "TestCases Failure"
---------- Forwarded message ---------- From: Saad Ahmed <ch.saad.ahmed at gmail.com> Date: 3 February 2015 at 21:10 Subject: Waiting for Reply regarding "TestCases Failure" To: Xapian Development <xapian-devel at lists.xapian.org> I have been waiting for reply regarding any further steps to take. Following are the outputs of commands that you asked me to run. All these
2016 Dec 12
1
testing
If the subject of xapian-core apitests on MSYS/MINGW and MSYS2/MINGW is taken up it might be noted that the compiler version could be recorded, probably gcc 5.3.0 or newer, that closed pipes might be an issue, and also allocating for the location of xapian-tcpsrv. Not from my own tests but another man informed there was some problems with [MSYS2] python bindings. I am not knowledgeable of the
2015 Sep 15
0
xapian porting to Interix / conclusion
Report by Eric Lindblad 14-09-2015 http://www.ericlindblad.blogspot.com cf: http://permalink.gmane.org/gmane.comp.search.xapian.general/9880 The 'gmake check' compile error on xapian-core-1.2.21/tests/api_backend.cc was resolved by the modification (at the suggestion of a mailing-list member) of the offending string from "q.OP_PHRASE" to "Xapian::Query::OP_PHRASE".
2016 Dec 07
1
MSYS2 'make check' output xapian-core-1.4.1-1
System: Microsoft Windows XP Home Edition CPUs: Intel(R) Atom(TM) CPU N270 @1.60GHz setup for the 'Git for Windows' with MSYS2 gcc-6.1.0 plus utilties and libraries were added http://nurmi-labs.blogspot.com/2016/11/git.html obviously, with Home Edition, no network was setup http://nurmi-labs.blogspot.com/p/xapian-ms.html System: Slackware Linux (version 14.0) CPUs: Intel(R) Atom(TM)
2016 Dec 05
1
MSYS2 apitest.exe FAIL
MS XP SP3 (32 bit) https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/ mingw-w64-i686-xapian-core-1.4.1-1-any.pkg.tar.xz does not contain /mingw32/lib/libxapian.la. cf: http://nurmi-labs.blogspot.com/2016/11/git.html (for setup) https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/ mingw-w64-i686-libtool-2.4.6-7-any.pkg.tar.xz (added)
2015 Sep 11
1
xapian 1.0.x compiled on Interix / Eric Lindblad
Report by Eric Lindblad 11-09-2015 http://www.ericlindblad.blogspot.com I compiled xapian-core-1.0.23 today on Interix. 'gmake check' summary PASS: btreetest, quartztest, stemtest, termgentest FAIL: apitest, internaltest, queryparsertest MS XP SP3 HOME modified SFU Interix 3.5 w/ getopt.h, inttypes.h, & stdint.h copied over from SUA Interix for Vista (and newer) into
2015 Sep 11
0
xapian-core-1.0.23 compiled on Interix / Eric Lindblad
Report by Eric Lindblad 11-09-2015 http://www.ericlindblad.blogspot.com I compiled xapian-core-1.0.23 today on Interix. 'gmake check' summary PASS: btreetest, quartztest, stemtest, termgentest FAIL: apitest, internaltest, queryparsertest MS XP SP3 HOME modified SFU Interix 3.5 w/ getopt.h, inttypes.h, & stdint.h copied over from SUA Interix for Vista (and newer) into
2015 Jan 27
2
TestCases Failure
Please find my inline reply. On 27 January 2015 at 03:02, Olly Betts <olly at survex.com> wrote: > > The script which automates most of the release process runs "make > distcheck", which runs the testsuite, so these tests didn't fail for me > when I made the 1.3.2 release. > > When I run "make distcheck" in the "build" folder, it gives
2019 Mar 06
2
Problem while writing test cases for api_termgen
Excuse me, I have met some problem while writing test cases for api_termgen. I added a case for mixed CJK numbers to test_simple, as the example mentioned in #699: > { "", "2千3百", "2[1] 千[2] 3[3] 百[4]"} But it unexpectedly failed. Below are the input and output. I run test with command: > ./runtest ./apitest termgen1 And the test case output is: > Running
2007 Nov 28
1
Problem compiling SVN-HEAD
Hi guys, Quick question - I'm getting errors compiling the tests; of the form: .\apitest.cc(46) : fatal error C1083: Cannot open include file: 'api_anydb.h': No such file or directory api_anydb.cc .\api_anydb.cc(26) : fatal error C1083: Cannot open include file: 'api_anydb.h': No such file or directory These files don't seem to exist. Any hints? Cheers Charlie
2016 Dec 14
1
testing
xapian-core-1.2.24 Unclear yet about any possible use of patches, either for MSYS/MINGW and/or MSYS2/MINGW, for xapian-core versions(?), but here are sections of the 'configure' and 'make check' logs I output from a MSYS/MINGW (g++ 5.3.0) compile on XP SP3 (32 bit) Home Edition (xapian-core-1.2.24). configure log checking for setenv... no checking for _putenv_s... yes
2016 Dec 08
1
configure & make_check logs w/out '--disable-sse'
System: Slackware Linux (version 14.0) CPUs: Intel(R) Atom(TM) CPU N270 @1.60GHz xapian-core-1.4.1.tar.xz http://nurmi-labs.blogspot.com/p/xapian-linux-sse.html
2007 Feb 12
1
Build problems
I'm getting remotetest and apitest failing for me on ixion on SVN HEAD-ish. I can't find a link to tinderbox anywhere obvious (I expected it to be linked from bleeding edge, and possibly the bugzilla start page), so I don't know if it's something dumb I've done to my setup and checkout, or a genuine problem. Any ideas? J --