checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in /var/lib/gems/1.9.1/gems/xapian-full-1.2.3/xapian-core-1.2.3': configure: error: C compiler cannot create executables Seeconfig.log' for more details.
/var/lib/gems/1.9.1/gems/xapian-full-1.2.3/xapian-core-1.2.3': configure: error: C compiler cannot create executables See
Tasks: TOP => default
(See full trace by running task with --trace)
Gem files will remain installed in /var/lib/gems/1.9.1/gems/xapian-full-1.2.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/xapian-full-1.2.3/./gem_make.out
An error occurred while installing xapian-full (1.2.3), and Bundler cannot continue.
Make sure that gem install xapian-full -v '1.2.3' succeeds before bundling.
gem install xapian-full -v '1.2.3'
There appears to be something wrong with this gem. There is a fork with a newer build that does compile correctly.
I would really like to enable and use the full text search option however it appears that without xapian-full installed this is impossible.
The objective map I have drawn up here is not necessarily to deprecate xapian support however to gradually offer a wider range of support for file indexing engines. 1.5.0 will see it move into a rather rigid structure where as some point after that (before 1.6.0) there will be options to support varying indexing options through a standardised class design. What Gem is it that compiles?
@jeick I have encountered the same issue as you described here, then I search and found a post that works for me:
Hope this helps.
Thanks! That does help. How can I test that full text search actually works? I should be able to put a text file in dmsf, run the indexing command, then locate said file using some keyword in the file correct?
Jeick there are some outstanding patches that are to be done to current release that have been identified to inhibit some of the fulltext search; however yes that's correct.
We're using your plugin with https://rubygems.org/gems/xapian-full-alaveteli as it does not rely on system below. Works like charm.