Double your dating the reference manual for how to

The data to be indexed can generally come from very different sources: SQL databases, plain text files, HTML files, mailboxes, and so on.

From Sphinx point of view, the data it indexes is a set of structured .

this means that some compile-time type size check failed.

The most probable reason is that off_t type is less than 64-bit on your system.

As a quick hack, you can edit sphinx.h and replace off_t with DWORD in a typedef for Sph Offset_t, but note that this will prohibit you from using full-text indexes larger than 2 GB.

Even if the hack helps, please report such issues, providing the exact error message and compiler/OS details, so I could properly fix them in next releases.

Currently known systems Sphinx has been successfully running on are: CPU architectures known to work include i386 (aka x86), amd64 (aka x86_64), SPARC64, and ARM.

Chances are good that Sphinx should work on other Unix platforms and/or CPU architectures just as well.

In 2.2.1-beta a tsvpipe (Tab Separated Values) and csvpipe (Comma Separated Values) data source was added.

You can get more information here Section 3.10, “tsvpipe\csvpipe (Tab\Comma Separated Values) data source”.

Official native Sphinx API implementations for PHP, Perl, Python, Ruby and Java are included within the distribution package.

API is very lightweight so porting it to a new language is known to take a few hours or days.

Actually, each and every important aspect was a problem: Despite the amount of time passed and numerous improvements made in the other solutions, there's still no solution which I personally would be eager to migrate to.