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
make_check log
I../../xapian-core-1.2.24/common -I../../xapian-core-1.2.24/include -I../include
-I../../xapian-core-1.2.24/tests/harness -fshow-column -Wall -W
-Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wformat-security -fno-gnu-keywords -Wundef -Woverloaded-virtual
-Wstrict-null-sentinel -Wshadow -Wstrict-overflow=1 -Wlogical-op
-Wmissing-declarations -Wdouble-promotion -Winit-self -fvisibility=hidden
-mfpmath=sse -msse2 -mtune=generic -g -O2 -c -o api_replicate.o
../../xapian-core-1.2.24/tests/api_replicate.cc
../../xapian-core-1.2.24/tests/api_replicate.cc: In destructor
'unset_max_changesets_helper_::~unset_max_changesets_helper_()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:262:39: note: in expansion of
macro 'set_max_changesets'
~unset_max_changesets_helper_() { set_max_changesets(0); }
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate1()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:279:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(10);
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate2()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:353:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(10);
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate3()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:491:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(10);
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate4()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:539:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(1);
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate5()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:632:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(2);
^
../../xapian-core-1.2.24/tests/api_replicate.cc: In function 'bool
test_replicate6()':
../../xapian-core-1.2.24/tests/api_replicate.cc:253:69: error:
'_putenv_s' was not declared in this scope
# define set_max_changesets(N) _putenv_s("XAPIAN_MAX_CHANGESETS", #N)
^
../../xapian-core-1.2.24/tests/api_replicate.cc:760:5: note: in expansion of
macro 'set_max_changesets'
set_max_changesets(10);
^
make[4]: *** [api_replicate.o] Error 1
make[4]: Leaving directory `/c/WORK/build-i686/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/c/WORK/build-i686/tests'
make[2]: *** [check] Error 2
make[2]: Leaving directory `/c/WORK/build-i686/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/c/WORK/build-i686'
make: *** [check] Error 2
--------------------------------------------
On Tue, 12/13/16, Olly Betts <olly at survex.com> wrote:
Subject: Re: testing
To: "Eric Lindblad" <geirfuglaps at yahoo.com>
Cc: xapian-discuss at lists.xapian.org
Date: Tuesday, December 13, 2016, 11:48 PM
On Mon, Dec 12, 2016 at
05:00:36PM +0000, Eric Lindblad wrote:
>
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.
That's unhelpfully vague,
but perhaps this patch helps with "closed
pipes"?
https://github.com/ojwb/xapian/commit/43af24c4a39819463621e9f8494cf7fdd30736e4.patch
If so, let me know and
I'll apply it to git master.
> I am not knowledgeable of the packages
and/or files utilised with MSYS/MINGW
>
and/or MSYS2/MINGW to resolve a hostname, however, maybe a
xapian-core
> compile and run of
'make check' under MSYS/MINGW would provide more
output
> than (as below) under
MSYS2/MINGW, which merely printed "FAIL:
apitest.exe".
You
ought to see the failing tests - if you aren't, I'm
not sure why not.
Perhaps
try:
make VERBOSE=1
If not that, perhaps
you've somehow managed to enable automake's TAP
test
harness, in which case the actual
output will probably be in "*.log"
files.
> If
there is any usefulness in MSYS/MINGW output in getting
MSYS2/MINGW to
> pass the apitest I can
not say, neither will forward I an assessment as to
> whether in this direction old stable
(1.2.24) might be looked at before
>
current (1.4.1) as pertains to MSYS/MINGW and/or
MSYS2/MINGW.
1.2.x is
now firmly in maintenance mode. If people provide clean
patches
for portability issues, they're
very likely to get applied, but my focus
is
very much on 1.4.x and git master.
Cheers,
Olly