[Xapian-discuss] Xapian 0.9.5, Cygwin and xapian-config - Solved
Patrick Mézard
pmezard at gmail.com
Tue May 9 09:15:22 BST 2006
Olly Betts wrote:
> On Mon, May 08, 2006 at 06:47:04PM +0200, Patrick M?zard wrote:
>
>> The "make" command failed when trying to build "xapian-config". "make"
>> outputs:
>> """
>> cd . && /bin/sh ./config.status xapian-config
>> config.status: creating xapian-config
>> """
>> then seems to never terminate (I let it run for twenty minutes before
>> killing it). The task manager shows that "sed" is taking all the
>> processing time and FileMon does not show any specific filesystem
>> activity. I am stuck at this point. I tried to comment the library
>> dependency tracking function added since xapian 0.9.2 to no avail.
>>
>
> I think the problem is with generating xapian-config, not trying to
> run it (especially since it doesn't get run at all during the
> xapian-core build!)
>
> Can you find out what arguments the sed was passed? If "ps" works in
> cygwin, the output of "ps wux|grep sed" should say. If not, can you
> see if "config.status" is still running?
>
As you may have guessed, the previous thread was a dead-end: removing
the comma between the -Wl option and the linkage directive just hide the
issue deeper in the compilation sequence. When I tried to build the
python bindings, it fails for the same reason the examples failed,
linkage options were incorrect. So, instead of losing my time fixing
what is likely a shell bug I just upgraded my cygwin setup. To compare
with the former one:
GNU bash, version 3.1.17(6)-release (i686-pc-cygwin)
GNU sed version 4.1.5
And restarted the build from scratch (only keeping the libtool
dependendency patch).
I quickly got a new error:
"""
g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../common -I../include -I../include
-I../lan
guages -Wall -W -Wredundant-decls -Wundef -Wpointer-arith -Wcast-qual
-Wcast-ali
gn -Wno-multichar -Wno-long-long -fno-gnu-keywords -g -O2 -MT version.lo
-MD -MP
-MF .deps/version.Tpo -c version.cc -DPIC -o .libs/version.o
In file included from version.cc:19:
../include/xapian/version.h:25:62: operator ',' has no right operand
version.cc: In function `const char* Xapian::xapian_version_string()':
version.cc:23: error: expected primary-expression before ';' token
version.cc: In function `int Xapian::xapian_major_version()':
version.cc:25: error: expected primary-expression before ';' token
version.cc: In function `int Xapian::xapian_minor_version()':
version.cc:27: error: expected primary-expression before ';' token
version.cc: In function `int Xapian::xapian_revision()':
version.cc:29: error: expected primary-expression before ';' token
make[2]: *** [version.lo] Error 1
make[2]: Leaving directory `/c/dev/mz/libs/xapian/xapian-core-0.9.5/api'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/dev/mz/libs/xapian/xapian-core-0.9.5'
make: *** [all] Error 2
"""
For some reason, api/version.h contains the following:
"""
#if !defined(__GXX_ABI_VERSION) || __GXX_ABI_VERSION != 1002,
"""
and
"""
#define XAPIAN_VERSION "0.9.5",
#define XAPIAN_MAJOR_VERSION 0,
#define XAPIAN_MINOR_VERSION 9,
#define XAPIAN_REVISION 5,
"""
I do not know where the trailing commas come from, but once removed
xapian-core build terminates correctly.
And python bindings compile as well with the previous installation
issues still there (once everything is setup manually, the extension
works correctly).
Sorry for stealing your time with such stupid problems, next time I will
upgrade before doing anything about xapian.
Cheers,
--
Patrick Mézard
More information about the Xapian-discuss
mailing list