I was tempted to try that, but thought I'd break it. That error has gone away. I am attempting to install KinoSearch (seems you are a maintainer). Can I continue that conversation here? I'm getting many failed tests. I haven't looked at it enough to know where I should be focusing, but any help is much appreciated.
cars: ./Build test
t/000-load.t .................. ok
t/001-build_invindexes.t ...... Failed 2/4 subtests
t/002-kinosearch.t ............ ok
t/010-verify_args.t ........... ok
t/011-class.t ................. ok
t/012-priority_queue.t ........ ok
t/013-bit_vector.t ............ ok
t/015-sort_external.t ......... ok
t/101-simple_template_io.t .... ok
t/102-strings_template_io.t ... ok
t/103-repeats_template_io.t ... ok
t/104-parse_template_io.t ..... ok
t/105-invindex.t .............. 1/22 Insecure dependency in unlink while running with -T switch at /tmp/KinoSearch-0.165/blib/lib/KinoSearch/Store/FSInvIndex.pm line 45.
# Looks like you planned 22 tests but ran 3.
# Looks like your test exited with 2 just after 3.
t/105-invindex.t .............. Dubious, test returned 2 (wstat 512, 0x200)
Failed 19/22 subtests
t/106-locking.t ............... 1/3 Lockfile looks dead - removing at /tmp/KinoSearch-0.165/blib/lib/KinoSearch/Store/FSLock.pm line 40.
t/106-locking.t ............... ok
t/150-polyanalyzer.t .......... ok
t/152-token_batch.t ........... ok
t/153-lc_normalizer.t ......... ok
t/154-tokenizer.t ............. ok
t/155-stopalizer.t ............ ok
t/201-field_infos.t ........... Failed 3/7 subtests
t/202-term.t .................. ok
t/203-compound_file_reader.t .. Failed 3/5 subtests
t/204-fields_reader.t ......... Failed 17/22 subtests
t/205-seg_reader.t ............ Failed 6/8 subtests
t/206-seg_infos.t ............. All 1 subtests passed
t/207-seg_term_enum.t ......... Failed 4/9 subtests
t/208-terminfo.t .............. ok
t/209-term_infos_reader.t ..... Failed 2/6 subtests
t/210-deldocs.t ............... Failed 11/12 subtests
t/211-seg_term_docs.t ......... Failed 5/7 subtests
t/212-multi_term_docs.t ....... Failed 4/10 subtests
t/213-segment_merging.t ....... Failed 6/10 subtests
t/214-spec_field.t ............ Failed 12/12 subtests
t/302-many_fields.t ........... No subtests run
t/303-highlighter.t ........... Failed 6/9 subtests
t/501-termquery.t ............. Failed 4/7 subtests
t/502-phrasequery.t ........... Failed 4/5 subtests
t/503-booleanquery.t .......... Failed 4/6 subtests
t/504-similarity.t ............ Failed 1/5 subtests
t/505-hit_queue.t ............. ok
t/506-hit_collector.t ......... ok
t/507-query_filter.t .......... Failed 1/2 subtests
t/508-hits.t .................. Failed 3/4 subtests
t/509-multi_searcher.t ........ Failed 3/4 subtests
t/510-remote_search.t ......... skipped: Can't get a socket: Connection refused
t/601-queryparser.t ........... Failed 216/217 subtests
t/602-boosts.t ................ No subtests run
t/603-query_boosts.t .......... Failed 2/2 subtests
t/604-simple_search.t ......... Failed 12/12 subtests
t/701-uscon.t ................. 1/10 Can't call method "create_weight" on an undefined value at /tmp/KinoSearch-0.165/blib/lib/KinoSearch/Search/BooleanQuery.pm line 91.
# Looks like you planned 10 tests but ran 2.
# Looks like your test exited with 255 just after 2.
t/701-uscon.t ................. Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 8/10 subtests
t/999-remove_invindexes.t ..... ok
t/pod-coverage.t .............. skipped: Test::Pod::Coverage 1.04 required for testing POD coverage
t/pod.t ....................... ok
Test Summary Report
-------------------
t/001-build_invindexes.t (Wstat: 138 Tests: 2 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 4 tests but ran 2.
t/105-invindex.t (Wstat: 512 Tests: 3 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan. You planned 22 tests but ran 3.
t/201-field_infos.t (Wstat: 138 Tests: 4 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 7 tests but ran 4.
t/203-compound_file_reader.t (Wstat: 138 Tests: 2 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 5 tests but ran 2.
t/204-fields_reader.t (Wstat: 138 Tests: 5 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 22 tests but ran 5.
t/205-seg_reader.t (Wstat: 138 Tests: 2 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 8 tests but ran 2.
t/206-seg_infos.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
t/207-seg_term_enum.t (Wstat: 138 Tests: 5 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 9 tests but ran 5.
t/209-term_infos_reader.t (Wstat: 138 Tests: 4 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 6 tests but ran 4.
t/210-deldocs.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 12 tests but ran 1.
t/211-seg_term_docs.t (Wstat: 138 Tests: 2 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 7 tests but ran 2.
t/212-multi_term_docs.t (Wstat: 138 Tests: 6 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 10 tests but ran 6.
t/213-segment_merging.t (Wstat: 138 Tests: 4 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 10 tests but ran 4.
t/214-spec_field.t (Wstat: 138 Tests: 0 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 12 tests but ran 0.
t/302-many_fields.t (Wstat: 138 Tests: 0 Failed: 0)
Non-zero wait status: 138
Parse errors: No plan found in TAP output
t/303-highlighter.t (Wstat: 138 Tests: 3 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 9 tests but ran 3.
t/501-termquery.t (Wstat: 138 Tests: 3 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 7 tests but ran 3.
t/502-phrasequery.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 5 tests but ran 1.
t/503-booleanquery.t (Wstat: 138 Tests: 2 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 6 tests but ran 2.
t/504-similarity.t (Wstat: 138 Tests: 4 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 5 tests but ran 4.
t/507-query_filter.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 2 tests but ran 1.
t/508-hits.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 4 tests but ran 1.
t/509-multi_searcher.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 4 tests but ran 1.
t/601-queryparser.t (Wstat: 138 Tests: 1 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 217 tests but ran 1.
t/602-boosts.t (Wstat: 138 Tests: 0 Failed: 0)
Non-zero wait status: 138
Parse errors: No plan found in TAP output
t/603-query_boosts.t (Wstat: 138 Tests: 0 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 2 tests but ran 0.
t/604-simple_search.t (Wstat: 138 Tests: 0 Failed: 0)
Non-zero wait status: 138
Parse errors: Bad plan. You planned 12 tests but ran 0.
t/701-uscon.t (Wstat: 65280 Tests: 2 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 10 tests but ran 2.
Files=53, Tests=376, 37 wallclock secs ( 0.49 usr 0.27 sys + 16.97 cusr 3.35 csys = 21.08 CPU)
Result: FAIL
Failed 28/53 test programs. 0/376 subtests failed.
Show quoted text-----Original Message-----
From: Marvin Humphrey via RT [mailto:bug-Lingua-Stem-Snowball@rt.cpan.org]
Sent: Tuesday, June 29, 2010 4:09 PM
To: Thompson, John
Subject: [rt.cpan.org #58959] HP-UX
<URL:
https://rt.cpan.org/Ticket/Display.html?id=58959 >
These errors are related to exporting C symbols which are needed by the
dev branch of KinoSearch (0.3x). However, since they are coming from
Dynaloader, they may be related to what is now dead code. Try removing
the following lines from Snowball.pm:
# Ensure that C symbols are exported so that other shared libaries (e.g.
# KinoSearch) can use them. See Dynaloader docs.
sub dl_load_flags {0x01}
