htdig-dev — Developer Discussion for the ht://Dig project

[htdig-dev] "Last call" for patches in 3.2.0b6

[Gabriele B. <an...@ti...>]

Hi guys,

    I invite you to point the last changes you would like to be applied 
before 3.2.0b6 is out. I intend to release it tomorrow indeed. Sounds good?

Ciao,
-Gabriele
--
Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check 
maintainer
Current Location: Prato, Toscana, Italia
an...@ti... | http://www.prato.linux.it/~gbartolini | ICQ#129221447
 > "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The 
Inferno

Re: [htdig-dev] Re: Accents, endings and chaining

[Neal R. <ne...@ri...>]

> Greetings Dominiqu,
>
> I have tried to reproduce your problem (as I understood it), but
> can't.  Several possibilities come to mind:
>   1. You are (as Gilles suggested) relying on the fuzzy rule "accents"
>      rather than explicitly entering the accent into the query.  In
>      this case, you are out of luck.
>   2. Your  endings_dictionary  file doesn't contain the words with
>      actual accents.
>   3. Your  endings_dictionary  has the accents, but encoded as
>      multi-byte unicode sequences.  Currently, ht://Dig doesn't
>      support unicode.
> In either case 2 or case 3, the solution is to replace the entries in
> your  endings_dictionary  file with the single-byte latin1 (not
> unicode) accents.

  Here are two possible approaches:

1) Strip accents from all stored words & queries.  This is a fairly common
practice in search engines & NLP systems.  The obvious dissadvantage is
that a user can't restrict results to contain that specific accent... they
get back results with all of the different accents for a 'base letter'.

2) Store BOTH the accented word & unaccented/stripped word in the
db.words.db.  Silently augment each search query with the stripped version
of each word.
  This steps around the dissadvantage of #1 and still get the
'generalization' of stripped accents.

Thanks

Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485

Re: [htdig-dev] Accents, endings and chaining

[Neal R. <ne...@ri...>]

FYI:
=09I have written accent stripping code that I'd be happy to add....

=09We'll also have a Unicode version soon ;-)

Thanks


On Sat, 5 Jun 2004, Lachlan Andrew wrote:

> Greetings Gilles,
>
> As I understand Dominique's problem, it is not an issue of chaining
> the "accents" fuzzy rule with the "endings" fuzzy rule.  He is
> searching for a word with an accent.  If it matches a word in the
> database with an accent, then it should not need a fuzzy algorithm to
> register a match.  I thought that "accents" causes "acouph=E8ne" to
> match "acouphene" (without the accend).
>
> Dominique, could you confirm that both the document and the query have
> an accent?  If that is the case, then we *may* be able to fix this
> problem without needing to chain fuzzy rules.
>
> Cheers,
> Lachlan
>
> On Thu, 3 Jun 2004 02:07 am, Gilles Detillieux wrote:
> > Dominique had written:
> > > > 3- I have a problem with the accent and plurials.
> > > >
> > > > If a search for "herbe" or "herbes", no problems.  But, if the
> > > > works have an accent, like "acouph=E8ne", htdig have a problem to
> > > > find the plural.
> > > >
> > > > herbe: 136 results
> > > > herbes: 136 results
> > > >
> > > > acouph=E8ne:   6 results
> > > > acouph=E8nes:  25 results
> > > >
> > > >
> > > > search_algorithm:       exact:1 endings:1 prefix:1 accent:1
> > > > synonyms:0,5
> >
> > htsearch does not yet support chaining of fuzzy match algorithms,
> > so the results of the accents algorithms don't have the endings
> > algorithm applied to them (nor vice-versa).
>
> --
> lh...@us...
> ht://Dig developer DownUnder  (http://www.htdig.org)
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>

Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485

RE: [htdig-dev] htsearch => wrapper script

[Rupert J. <ru...@sa...>]

Hi Ted,

I'm sorry, this isn't making any sense to me.

As I understand it, the path to the config file is compiled in to htsearch
as a security precaution, so that when you specify which config file to use
as a parameter when invoking htsearch from the webpage you are not exposing
the directory location of ht://dig.

Why do you feel that compiling in the location of the conf files is a
drawback?

I personally feel that adding an additional perl script is creating an
unnecessary step in the processing of form data to htsearch, for the sake of
convenience. I would assume that all ht://dig users are webmasters of some
degree, and compiling htsearch with the location of the conf files shouldn't
be a major task for most ht://dig users.

Not to mention the issues faced by users who would then need to reconfigure
their implementations of ht://dig in order to incorporate the new script.

Kind regards,

Rupert Jones


-----Original Message-----
From: htd...@li...
[mailto:htd...@li...] On Behalf Of Ted
Stresen-Reuter
Sent: 03 June 2004 23:55
To: //Dig - Dev
Subject: [htdig-dev] htsearch => wrapper script

You know, in setting up my package, I realized that it seems like a 
real drawback to have to compile in the location of the conf files into 
htsearch (rather than having it look in it's own directory, for 
example, for cases in which the location is not compiled in).

Maybe, instead of putting htsearch in cgi-bin, we could put htsearch in 
--prefix/bin and drop a perl script into cgi-bin that simply passes the 
request on to htsearch (and htsearch sends the response). That way, we 
could keep all the htdig binaries together in one place.

Does this make sense to anyone else or just to me?

Ted Stresen-Reuter



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
ht://Dig Developer mailing list:
htd...@li...
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

-- 
Incoming mail is certified Virus Free.
Checked by AVG Anti-Virus (http://www.grisoft.com).
Version: 7.0.245 / Virus Database: 263.1.1 - Release Date: 06/06/2004
 

-- 
Outgoing mail is certified Virus Free.
Checked by AVG Anti-Virus (http://www.grisoft.com).
Version: 7.0.245 / Virus Database: 263.1.1 - Release Date: 06/06/2004
 

[htdig-dev] Current Status as of snapshot 3.2.0b6-20040606

[Geoff H. <ghu...@us...>]

STATUS of ht://Dig branch 3-2-x

RELEASES:
   3.2.0b6: Scheduled: 31 May 2004.
   3.2.0b5: Released:  10 Nov 2003.
   3.2.0b4: Cancelled.
   3.2.0b3: Released:  22 Feb 2001.
   3.2.0b2: Released:  11 Apr 2000.
   3.2.0b1: Released:   4 Feb 2000.

(Please note that everything added here should have a tracker PR# so
we can be sure they're fixed. Geoff is currently trying to add PR#s for
what's currently here.)

SHOWSTOPPERS:

KNOWN BUGS:
(none serious.
See <http://sourceforge.net/tracker/?atid=104593&group_id=4593&func=browse>.)

PENDING PATCHES (available but need work):
* Gilles's configuration parsing patches need testing before committing.
* Memory improvements to htmerge. (Backed out b/c htword API changed.)
* Mifluz merge.  (Is this still pending??)

NEEDED FEATURES:
* Quim's new htsearch/qtest query parser framework.
* File/Database locking. PR#405764.

TESTING:
* httools programs: 
  (htload a test file, check a few characteristics, htdump and compare)
* Tests for new config file parser
* Duplicate document detection while indexing
* Major revisions to ExternalParser.cc, including fork/exec instead of popen,
  argument handling for parser/converter, allowing binary output from an
  external converter.
* ExternalTransport needs testing of changes similar to ExternalParser.

DOCUMENTATION:
* List of supported platforms/compilers is ancient. (PR#405279)
* Document all of htsearch's mappings of input parameters to config attributes
   to template variables. (Relates to PR#405278.)
  Should we make sure these config attributes are all documented in
  defaults.cc, even if they're only set by input parameters and never
  in the config file?
* Split attrs.html into categories for faster loading.
* Turn defaults.cc into an XML file for generating documentation and 
  defaults.cc.
* require.html is not updated to list new features and disk space
   requirements of 3.2.x (e.g. regex matching, database compression.)
   PRs# 405280 #405281.
* Htfuzzy could use more documentation on what each fuzzy algorithm
   does. PR#405714.
* Document the list of all installed files and default
   locations. PR#405715.

OTHER ISSUES:
* Can htsearch actually search while an index is being created?
* The code needs a security audit, esp. htsearch. PR#405765.

[htdig-dev] Making ht://Dig more user friendly

[Lachlan A. <lh...@us...>]

Greetings Ted,

As I understand it, -i *should* remove all files before it starts 
digging.  In particular, it removes  doc_db, doc_index, doc_excerpt, 
word_db (plus word_db+"_weakcmpr"), md5_db, url_log, doc_list and 
word_dump.  Do you know which files were not being deleted?

Cheers,
Lachlan

On Mon, 31 May 2004 09:47 pm, Ted Stresen-Reuter wrote:
> I had to modify rundig
> to delete existing databases if -a was not used, otherwise, it
> didn't seem to be creating genuinely new databases (please correct
> me if I'm wrong).

-- 
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

[htdig-dev] Re: Accents, endings and chaining

[Lachlan A. <lh...@us...>]

Greetings Dominiqu,

I have tried to reproduce your problem (as I understood it), but=20
can't.  Several possibilities come to mind:
  1. You are (as Gilles suggested) relying on the fuzzy rule "accents"
     rather than explicitly entering the accent into the query.  In
     this case, you are out of luck.
  2. Your  endings_dictionary  file doesn't contain the words with
     actual accents.
  3. Your  endings_dictionary  has the accents, but encoded as
     multi-byte unicode sequences.  Currently, ht://Dig doesn't
     support unicode.
In either case 2 or case 3, the solution is to replace the entries in=20
your  endings_dictionary  file with the single-byte latin1 (not=20
unicode) accents.

Do any of these cases apply?

Cheers,
Lachlan

On Sat, 5 Jun 2004 02:43 pm, Lachlan Andrew wrote:
>
> As I understand Dominique's problem, it is not an issue of chaining
> the "accents" fuzzy rule with the "endings" fuzzy rule.  He is
> searching for a word with an accent.  If it matches a word in the
> database with an accent, then it should not need a fuzzy algorithm
> to register a match.  I thought that "accents" causes "acouph=E8ne"
> to match "acouphene" (without the accend).
>
> Dominique, could you confirm that both the document and the query
> have an accent?  If that is the case, then we *may* be able to fix
> this problem without needing to chain fuzzy rules.
>
> Cheers,
> Lachlan
>
> On Thu, 3 Jun 2004 02:07 am, Gilles Detillieux wrote:
> > Dominique had written:
> > > > 3- I have a problem with the accent and plurials.
> > > >
> > > > If a search for "herbe" or "herbes", no problems.  But, if
> > > > the works have an accent, like "acouph=E8ne", htdig have a
> > > > problem to find the plural.
> > > >
> > > > herbe: 136 results
> > > > herbes: 136 results
> > > >
> > > > acouph=E8ne:   6 results
> > > > acouph=E8nes:  25 results
> > > >
> > > >
> > > > search_algorithm:       exact:1 endings:1 prefix:1 accent:1
> > > > synonyms:0,5
> >
> > htsearch does not yet support chaining of fuzzy match algorithms,
> > so the results of the accents algorithms don't have the endings
> > algorithm applied to them (nor vice-versa).

=2D-=20
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

Re: [htdig-dev] On HP-UX 10.20 [3.2.0b6 almost there]

[Lachlan A. <lh...@us...>]

Greetings Ted,

If you copy the attached files to .../test/ then it should fix the 
problem with t_htdig, and the spurious warnings for t_factors.  The 
other two seem to suggest that HP-UX doesn't like 8-bit characters.  
Do you know if that is the case?

Cheers,
Lachlan

On Thu, 3 Jun 2004 09:38 pm, Ted Stresen-Reuter wrote:
> I did now...
>
> tedsr% make check
> running htdig: expected
> http://localhost:7400/set1/
 [delete]
> but got
>
> FAIL: t_htdig
> awk: empty regular expression
>   input record number 61, file
>   source line number 1
> PASS: t_factors
> Output doesn't match "1 matches"
> ../htsearch/htsearch -c
> /Users/tedsr/Desktop/htdig-3.2.0b6/test/conf/htdig.conf.tmp
> 'words=francais;search_algorithm=accents:0.1' >>
> /tmp/t_htsearch24106 --
>                    Search for 'francais' with
> search_algorithm=accents
> FAIL: t_fuzzy
> Output doesn't match "1 matches"
> ../htsearch/htsearch -c
> /Users/tedsr/Desktop/htdig-3.2.0b6/test/conf/htdig.conf.tmp
> 'words=fran?ais' >> /tmp/t_htsearch25328 --
>                    Search for 'fran?ais' without translate_latin1
> FAIL: t_validwords
> ====================
> 3 of 19 tests failed
> ====================

-- 
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

[htdig-dev] Gilles' patch for configuration

[Lachlan A. <lh...@us...>]

Greetigns Gilles,

Are you sure that Neal committed the last *.cxx builds?  There's 
hardly a sign of him when browsing CVS.

In particular, the  #ifdef _WIN32  lines in conf_lexer.cxx appeared on 
July 21 when Gabriele applied the patch by Marco Nenciarini.

$0.02
Lachlan

On Fri, 4 Jun 2004 06:52 am, Gilles Detillieux wrote:
> I really wanted feedback from Neal about Win32 compatibility in the
> config parser. Neal had committed the last *.cxx builds, and I'm
> not sure if he had built them himself with flex/bison, or had
> manually patched them.  In any case, I'm running an older version
> of bison than whoever last built these, so I'm a bit reluctant to
> override the ones in CVS with my build. Could whoever built the
> last ones please come forward, grab my April 22 config parser patch
> (which I can repost to htdig-dev if needed), and rebuild them. 
> Then Neal can make any other changes that are needed for Win32.

-- 
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

[htdig-dev] Accents, endings and chaining

[Lachlan A. <lh...@us...>]

Greetings Gilles,

As I understand Dominique's problem, it is not an issue of chaining=20
the "accents" fuzzy rule with the "endings" fuzzy rule.  He is=20
searching for a word with an accent.  If it matches a word in the=20
database with an accent, then it should not need a fuzzy algorithm to=20
register a match.  I thought that "accents" causes "acouph=E8ne" to=20
match "acouphene" (without the accend).

Dominique, could you confirm that both the document and the query have=20
an accent?  If that is the case, then we *may* be able to fix this=20
problem without needing to chain fuzzy rules.

Cheers,
Lachlan

On Thu, 3 Jun 2004 02:07 am, Gilles Detillieux wrote:
> Dominique had written:
> > > 3- I have a problem with the accent and plurials.
> > >
> > > If a search for "herbe" or "herbes", no problems.  But, if the
> > > works have an accent, like "acouph=E8ne", htdig have a problem to
> > > find the plural.
> > >
> > > herbe: 136 results
> > > herbes: 136 results
> > >
> > > acouph=E8ne:   6 results
> > > acouph=E8nes:  25 results
> > >
> > >
> > > search_algorithm:       exact:1 endings:1 prefix:1 accent:1
> > > synonyms:0,5
>
> htsearch does not yet support chaining of fuzzy match algorithms,
> so the results of the accents algorithms don't have the endings
> algorithm applied to them (nor vice-versa).

=2D-=20
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

Re: [htdig-dev] Re: Role/Purpose of db files

[Lachlan A. <lh...@us...>]

Greetings all,

Before anyone points out max_description_length, I'll quietly go and 
put my other foot in my mouth...

Lachlan :)

On Sat, 5 Jun 2004 12:39 pm, Lachlan Andrew wrote:
> Meanwhile, it seems that
> meta-descriptions etc also get put into the excerpts file *despite*
> max_head_length.

-- 
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

[htdig-dev] Re: Role/Purpose of db files

[Lachlan A. <lh...@us...>]

Greetings all,

Setting  max_head_length  to 0 doesn't cause a crash, but it seems to 
break things.  I'll look into that.  Meanwhile, it seems that 
meta-descriptions etc also get put into the excerpts file *despite* 
max_head_length.  Should we
 - ignore this
 - limit meta-descriptions to max_head_length too
 - limit (head text + meta-descriptions) to max_head_length?

Thoughts?
Lachlan

On Wed, 2 Jun 2004 09:03 pm, Lachlan Andrew wrote:

> db.excerpts stores the bit of text...
> If you're worried by its size, you
> are better off setting  max_head_length  very small (ideally zero,
> but I'm not sure if that will cause a crash -- could you check?).

-- 
lh...@us...
ht://Dig developer DownUnder  (http://www.htdig.org)

Re: [htdig-dev] htdig-3.2.0b6's ready

[Gabriele B. <g.b...@co...>]

Hi guys,

   the release of ht://Dig 3.2.0b6 will be delayed by a couple of days.
It is reasonable to wait for Gilles to include at least his patch
regarding DC meta data.

   If possible, his patch regarding the config parser will be included
too; in case there are some conflicts with Neal's Win32 code this patch
won't be included in this release.

   I have already included the patch regarding space in URLs, which
makes the spider more flexible, as suggested by Joe in the members list.
I have also updated the tarball in the files directory.

   It goes without saying that until the release process has finished,
the tarball in the files directory will be updated.

   It is important, as Gilles notes, to provide all the small bug fixes
and contributed patches in this release. And it's only a matter of a few
days.

Ciao,
-Gabriele

Il gio, 2004-06-03 alle 10:44, Gabriele Bartolini ha scritto:
> Hi guys,
> 
>    I've followed the checklist (http://www.htdig.org/dev/), created the
> packages using the 'htdig-release.sh' script on sf.net and uploaded the
> files in the /files/ directory of the website.
> 
>    Sorry Lachlan, I've overriden your files, as I had made some changes
> in the meantime.
> 
>    Please test them.
> 
>    Also, please have a look at the RELEASE.html file with the changes I
> have detailed.
> 
>    I am not sure about how to make the diff file from the 3.2.0b5
> release:
> 
> 1) export the 3.2.0b5 in a directory
> 2) untar the 3.2.0b6 in a parallel directory
> 3) run: diff -c3p -r 3.2.0b5 3.2.0b6
> 4) compress the file
> 
>    Is that all?
> 
>    Once done that I will go on with the release process (tomorrow?).
> 
> Ciao,
> -Gabriele
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev

[htdig-dev] Re: [htdig-members] Lack of Progress in 3.2-final

[<lac...@ip...>]

Greetings all,

Sorry, that is my fault -- I was trying too hard to meet the deadline we
had set.  I had meant to include at least the file space patch, but forgot
even that in the rush.  You're right that it will be better to wait a bit
and get these patches tested and applied first.

Cheers,
Lachlan

>From: Gilles Detillieux <gr...@sc...>
>However, I did suggest that we
>get b6 out "with all the bug fixes we have at hand, and an honest attempt
>to fix any other known bugs."  To my knowledge, the b6 code does not yet
>have my config parser patch of over a month ago yet (never got any real
>feedback from anyone), and my little fix for meta date tag recognition
>to avoid inappropriate DC date tags (like expiration).  Any other pending
>patches/fixes that should go in b6?

Re: [htdig-dev] Re: On HP-UX 10.20

[<lac...@ip...>]

Greetings Gabriele,

You're right that some of the tests are a bit old, but a lot of them are
new.  In doing Neal's testing checklist, I have added a test to exercise
each of the config attributes that I have crossed off the list.  That slows
down a  make check  quite a bit, but I think having a thorough test suite
is worthwhile.

I'd be happy to purge the old tests, but most of them are quite quick to
run.

Cheers,
Lachlan

>From: Gabriele Bartolini <g.b...@co...>

>   I haven't been able to look at the tests properly. However, I guess
>after 3.2.0b6 is out we should really have a deeper look at them. Some
>of them are really old (Loic made them) and I don't know if they are
>still useful.
>
>   Does anyone have a better understanding of the current situation of
>tests?

[htdig-dev] RE: Package Installer for htdig on Mac OS X (3.2.0b6) - please test

[<lac...@ip...>]

Good work, Ted!  (Unfortunately I don't have a Mac to test it on...)

Lachlan

>From: Ted Stresen-Reuter <ted...@ma...>
>
>I spent the better part of yesterday and today learning how to use it 
>and believe I have a reasonable package of the most recent htdig beta 
>(http://www.htdig.org/) ready for use/distribution.

Re: [htdig-dev] Re: On HP-UX 10.20

[Gabriele B. <g.b...@co...>]

Hi guys,

   I haven't been able to look at the tests properly. However, I guess
after 3.2.0b6 is out we should really have a deeper look at them. Some
of them are really old (Loic made them) and I don't know if they are
still useful.

   Does anyone have a better understanding of the current situation of
tests?

Ciao,
-Gabriele

Il gio, 2004-06-03 alle 11:18, lac...@ip... ha scritto:
> Greetings Jesse,
> 
> It's not urgent, but I'd be interested to experiment on this...
> 
> What is the output from
>   nm htword/.libs/libhtword.a | grep instance
> ?
> 
> What happens if, in .../test/, you type
> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o testnet testnet.o  \
>   -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a \
>   ../htcommon/.libs/libcommon.a ../htword/.libs/libhtword.a \
>   ../db/.libs/libhtdb.a ../htlib/.libs/libht.a -lz \
>   ../htword/.libs/libhtword.a
> ?
> 
> What happens if you
>   cp /bin/true test/testnet
>   make check
> ?
> 
> Thanks,
> Lachlan
> 
> >From: "J. op den Brouw" <ht...@op...>
> 
> >it's the WordType::instance thing again...........
> >g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o testnet testnet.o  
> >-L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../htcomm
> >on/.libs/libcommon.a ../htword/.libs/libhtword.a ../db/.libs/libhtdb.a 
> >../htlib/.libs/libht.a -lz
> >collect2: ld returned 1 exit status
> >/usr/ccs/bin/ld: Unsatisfied symbols:
> >   WordType::instance  (data)
> >make[2]: *** [testnet] Error 1
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev

[htdig-dev] htsearch => wrapper script

[Ted Stresen-R. <ted...@ma...>]

You know, in setting up my package, I realized that it seems like a 
real drawback to have to compile in the location of the conf files into 
htsearch (rather than having it look in it's own directory, for 
example, for cases in which the location is not compiled in).

Maybe, instead of putting htsearch in cgi-bin, we could put htsearch in 
--prefix/bin and drop a perl script into cgi-bin that simply passes the 
request on to htsearch (and htsearch sends the response). That way, we 
could keep all the htdig binaries together in one place.

Does this make sense to anyone else or just to me?

Ted Stresen-Reuter

[htdig-dev] Package Installer for htdig on Mac OS X (3.2.0b6) - please test

[Ted Stresen-R. <ted...@ma...>]

Hi,

One of the things on my long list of things to do when I really had 
time for it was to learn how to use the Mac OS X PackageMaker to aid in 
the distribution/installation of open source projects such as htdig.

I spent the better part of yesterday and today learning how to use it 
and believe I have a reasonable package of the most recent htdig beta 
(http://www.htdig.org/) ready for use/distribution.

Could those of you running OS X (10.2 or higher) please give this 
package installer a whirl (try it out) and let me know if it works.

Please note, this installer may over write files with the same name in 
the default locations. In particular, it installs 
/Library/WebServer/CGI-Executables/htsearch right where your existing 
htsearch file is without renaming the original first. More detailed 
info on where things end up is in the ReadMe viewable during 
installation.

The temporary location for the package is here:
http://www.tedmasterweb.com/htdig-3.2.0b6.dmg.sit
13 MB (any ideas on how to make it smaller would be greatly appreciated)

I look forward to hearing from you.

Ted Stresen-Reuter

Re: [htdig-dev] bug or config problem

[Gilles D. <gr...@sc...>]

According to lac...@ip...:
> Perhaps my email was ambiguous.  What I was planning to do is make the default
> value of "no_next_page_text" "$(next_page_text)", instead of "next".  That
> still gives people the option to make them different if they want to, but
> means that customising them both to be the same value only requires customising
> one value.
> 
> I can't see that this will break anything.  People who have set no_next_page_text
> to something specific in the htdig.conf file won't be affected, and people
> who haven't changed  next_page_text  won't be affected.  The only people
> affected are those who have changed  next_page_text, but still have "next"
> when there is no next, which is presumably an oversight of theirs.
> 
> If you see a problem that I don't, then let me know...

No problems that I can see.  Carry on, and don't mind me.  :-)
Actually, this sounds like just the right way to handle this.

Cheers,
Gilles

-- 
Gilles R. Detillieux              E-mail: <gr...@sc...>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)

Re: [htdig-dev] On HP-UX 10.20 [3.2.0b6 almost there]

[Ted Stresen-R. <ted...@ma...>]

I did now...

tedsr% make check
Making check in db
Making check in htlib
make[1]: Nothing to be done for `check'.
Making check in htword
make[1]: Nothing to be done for `check'.
Making check in htcommon
Making check in htnet
make[1]: Nothing to be done for `check'.
Making check in htfuzzy
make[1]: Nothing to be done for `check'.
Making check in htdb
make[1]: Nothing to be done for `check'.
Making check in htdig
make[1]: Nothing to be done for `check'.
Making check in htsearch
make[1]: Nothing to be done for `check'.
Making check in httools
make[1]: Nothing to be done for `check'.
Making check in installdir
make[1]: Nothing to be done for `check'.
Making check in include
Making check in htdoc
make[1]: Nothing to be done for `check'.
Making check in test
make MAKE="make" word dbbench txt2mifluz search testnet document url
make[2]: `word' is up to date.
make[2]: `dbbench' is up to date.
make[2]: `txt2mifluz' is up to date.
make[2]: `search' is up to date.
make[2]: `testnet' is up to date.
make[2]: `document' is up to date.
make[2]: `url' is up to date.
make MAKE="make" check-TESTS
PASS: t_wordkey
PASS: t_wordlist
PASS: t_wordskip
PASS: t_wordbitstream
PASS: t_search
PASS: t_htdb
PASS: t_rdonly
PASS: t_trunc
PASS: t_url
running htdig: expected
http://localhost:7400/set1/
http://localhost:7400/set1/bad_local.htm
http://localhost:7400/set1/script.html
http://localhost:7400/set1/site%201.html
http://localhost:7400/set1/site2.html
http://localhost:7400/set1/site3.html
http://localhost:7400/set1/site4.html
http://localhost:7400/set1/sub%2520dir/
http://localhost:7400/set1/sub%2520dir/empty%20file.html
http://localhost:7400/set1/title.html
but got

FAIL: t_htdig
PASS: t_htsearch
PASS: t_htmerge
PASS: t_htnet
PASS: t_htdig_local
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 61, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 46, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 10, file
  source line number 1
awk: empty regular expression
  input record number 51, file
  source line number 1
awk: empty regular expression
  input record number 51, file
  source line number 1
awk: empty regular expression
  input record number 51, file
  source line number 1
awk: empty regular expression
  input record number 51, file
  source line number 1
PASS: t_factors
tempWords: 'francais:0 '
Boolean: 'francais:0 '
Adding algorithm accents
initial: ''
Fuzzy on: francais
    accents
searchWords: 'francais:0 '
LogicalWords: francais
Pattern: francais
Highlight Pattern: francais
perform_push @0: francais
score: empty list, push 0 @0
term:factor
Output doesn't match "1 matches"
../htsearch/htsearch -c 
/Users/tedsr/Desktop/htdig-3.2.0b6/test/conf/htdig.conf.tmp 
'words=francais;search_algorithm=accents:0.1' >> /tmp/t_htsearch24106 
--
                   Search for 'francais' with search_algorithm=accents
FAIL: t_fuzzy
PASS: t_parsing
PASS: t_templates
tempWords: 'fran?ais:0 '
Boolean: 'fran?ais:0 '
Adding algorithm exact
initial: ''
Fuzzy on: fran?ais
    exact fran?ais
searchWords: 'fran?ais:0 '
LogicalWords: fran?ais
Pattern: fran?ais
Highlight Pattern: fran?ais
perform_push @0: fran?ais
score: empty list, push 0 @0
term:factor
Output doesn't match "1 matches"
../htsearch/htsearch -c 
/Users/tedsr/Desktop/htdig-3.2.0b6/test/conf/htdig.conf.tmp 
'words=fran?ais' >> /tmp/t_htsearch25328 --
                   Search for 'fran?ais' without translate_latin1
FAIL: t_validwords
====================
3 of 19 tests failed
====================
make[2]: *** [check-TESTS] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

On Jun 3, 2004, at 11:30 AM, Gabriele Bartolini wrote:

> Il gio, 2004-06-03 alle 12:07, Ted Stresen-Reuter ha scritto:
>> I just did ./configure, make, make check, and make install with b6.
>> make check said there was nothing to be done for anything. Is that
>> normal? I thought it ran a bunch of tests...
>
> Sorry Ted. Did you run configure with 'enable-tests'?
>
> -Gabriele
>

Re: [htdig-dev] On HP-UX 10.20 [3.2.0b6 almost there]

[Gabriele B. <g.b...@co...>]

Il gio, 2004-06-03 alle 12:07, Ted Stresen-Reuter ha scritto:
> I just did ./configure, make, make check, and make install with b6. 
> make check said there was nothing to be done for anything. Is that 
> normal? I thought it ran a bunch of tests...

Sorry Ted. Did you run configure with 'enable-tests'?

-Gabriele

Re: [htdig-dev] Re: 3.1.6 vs. 3.2.0b5 speed test results

[Ted Stresen-R. <ted...@ma...>]

Ok, using Lachlan's "time" suggestion, here are the results:

3.1.6 Start time: Thu Jun 3 11:07:37 WEST 2004
PDF::parse: cannot find pdf parser /usr/local/bin/acroread

real    3m19.448s
user    1m16.690s
sys     0m42.660s
Done Digging: Thu Jun 3 11:10:57 WEST 2004

3.2.0b5 Start time: Thu Jun 3 11:10:57 WEST 2004

real    7m39.478s
user    4m49.470s
sys     0m27.640s
Done Digging: Thu Jun 3 11:18:36 WEST 2004

3.2.0b6 Start time: Thu Jun 3 11:18:36 WEST 2004

real    7m2.774s
user    4m39.720s
sys     0m24.490s
Done Digging: Thu Jun 3 11:25:39 WEST 2004

Some of the local sites that I'm indexing serve PDFs but I do not have 
htdig configured to do anything with them. I don't know where that 
error is coming from in version 3.1.6. Remember, I am using the default 
htdig.conf file for these tests with the one exception that I'm 
changing the start_url to be a handful of sites I have on my local 
machine.

I hope this helps too...

Ted

On Jun 3, 2004, at 8:47 AM, lac...@ip... wrote:

>> From: Ted Stresen-Reuter <ted...@ma...>
>>
>> Contradictory results when run against the same machine.
>>
>> 3.1.6
>> Start time: Wed Jun 2 13:20:41 WEST 2004
>> PDF::parse: cannot find pdf parser /usr/local/bin/acroread
>> Done Digging: Wed Jun 2 13:22:47 WEST 2004
>> Total: 2:06
>>
>> 3.2
>> Start time: Wed Jun 2 13:22:47 WEST 2004
>> Done Digging: Wed Jun 2 13:27:39 WEST 2004
>> Total: 4:52
>>
>> I haven't been following the whole thread on what's at issue here, but
>> if someone can give me an indication of what we want to test, maybe I
>> could set up a site that tests specifically that issue.
>
> Greetigns Ted,
>
> One simple thing to try is running
> % time rundig
> which should tell us how much time is spent running code, and how much 
> is
> spent waiting for I/O (disk or network).
>
> I also notice that 3.1.6 wasn't indexing .pdf files.  Was 3.2.0?
>
>> Let me know... (back to painting)
>
> *grin*
>
> Lachlan
>

Re: [htdig-dev] On HP-UX 10.20 [3.2.0b6 almost there]

[Gabriele B. <g.b...@co...>]

Hi Ted,

   thank you very much. I tried the configure/make/make install triad
and it worked fine. However, 'make check' had some problems, due to a
particular apache installation (I have apache 2.0 and tests can't find
mod_env.so).

Il gio, 2004-06-03 alle 12:07, Ted Stresen-Reuter ha scritto:
> After doing the install (with prefix set to /Library/htdig-3.2.0b6) 
> everything, including man pages and all, ended up in the install 
> directory. For some reason, these additional goodies weren't getting 
> installed with b5. I don't know what you've done, but good work on 
> that!

I included them into the automake files (they should be automatically
handled); then Lachlan did a great job in customisation of the man pages
content.

Regarding man pages, I also want to thank Robert for his contribution.

Ciao,
-Gabriele

Re: [htdig-dev] On HP-UX 10.20 [3.2.0b6 almost there]

[Ted Stresen-R. <ted...@ma...>]

Hi Gabriele,

I just did ./configure, make, make check, and make install with b6. 
make check said there was nothing to be done for anything. Is that 
normal? I thought it ran a bunch of tests...

After doing the install (with prefix set to /Library/htdig-3.2.0b6) 
everything, including man pages and all, ended up in the install 
directory. For some reason, these additional goodies weren't getting 
installed with b5. I don't know what you've done, but good work on 
that!

I'm not going to test the digging in my speed tests using Lachlan's 
suggestion for using "time".

Back later with some test results.

Ted Stresen-Reuter

My system:
Mac OS X (10.3.4), 768 MB RAM

On Jun 3, 2004, at 9:57 AM, Gabriele Bartolini wrote:

> Hi Jesse,
>
>    I slightly changed Lachlan's release, updating also the configure
> scripts. You can find the new files here: http://www.htdig.org/files/
>
>    Sorry, but I believe that updating autotools scripts would be more
> appropriate for a new release.
>
> Ciao,
> -Gabriele
>
>    I have upgraded the configure scripts
> Il gio, 2004-06-03 alle 10:02, J. op den Brouw ha scritto:
>> AFIAK, b5 had the same problem with make check and some issue about 
>> select()
>> but I can't remember. b6 definitely doesn't have the select() problem.
>> zlib not used is historical, dated back in the b4 series (it didn't 
>> work
>> then).
>> it's the WordType::instance thing again...........
>>
>> [msql@chaos htdig-3.2.0b6]$ make check
>> Making check in db
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/db'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/db'
>> Making check in htlib
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htlib'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htlib'
>> Making check in htword
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htword'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htword'
>> Making check in htcommon
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htcommon'
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htcommon'
>> Making check in htnet
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htnet'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htnet'
>> Making check in htfuzzy
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htfuzzy'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htfuzzy'
>> Making check in htdb
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdb'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdb'
>> Making check in htdig
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdig'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdig'
>> Making check in htsearch
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htsearch'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htsearch'
>> Making check in httools
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/httools'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/httools'
>> Making check in installdir
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/installdir'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/installdir'
>> Making check in include
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/include'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/include'
>> Making check in htdoc
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdoc'
>> make[1]: Nothing to be done for `check'.
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/htdoc'
>> Making check in test
>> make[1]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/test'
>> make MAKE="make" word dbbench txt2mifluz search testnet document url
>> make[2]: Entering directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/test'
>> g++ -DHAVE_CONFIG_H -I. -I. -I../include
>> -DDEFAULT_CONFIG_FILE=\"/opt/htdig/htdig32/conf/htdig.conf\"
>> -I../include -I../htlib
>> -I../htnet -I../htcommon -I../htword -I../db -I../db -I../db -I../db
>> -I/opt/htdig/lib/zlib/include  -g -O2 -Wall -fno-rtti
>> -fno-exceptions -c -o word.o `test -f 'word.cc' || echo './'`word.cc
>> /bin/sh ../libtool --mode=link g++  -g -O2 -Wall -fno-rtti
>> -fno-exceptions  -L/opt/htdig/lib/zlib/lib -o word   word.o ../htne
>> t/libhtnet.la ../htcommon/libcommon.la ../htword/libhtword.la
>> ../htlib/libht.la ../htcommon/libcommon.la ../htword/libhtword.l
>> a ../db/libhtdb.la ../htlib/libht.la -lz
>> mkdir .libs
>> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o word word.o
>> -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../htcommon/.li
>> bs/libcommon.a ../htword/.libs/libhtword.a ../db/.libs/libhtdb.a
>> ../htlib/.libs/libht.a -lz
>> g++ -DHAVE_CONFIG_H -I. -I. -I../include
>> -DDEFAULT_CONFIG_FILE=\"/opt/htdig/htdig32/conf/htdig.conf\"
>> -I../include -I../htlib
>> -I../htnet -I../htcommon -I../htword -I../db -I../db -I../db -I../db
>> -I/opt/htdig/lib/zlib/include  -g -O2 -Wall -fno-rtti
>> -fno-exceptions -c -o dbbench.o `test -f 'dbbench.cc' || echo
>> './'`dbbench.cc
>> /bin/sh ../libtool --mode=link g++  -g -O2 -Wall -fno-rtti
>> -fno-exceptions  -L/opt/htdig/lib/zlib/lib -o dbbench   dbbench.o .
>> ./htnet/libhtnet.la ../htcommon/libcommon.la ../htword/libhtword.la
>> ../htlib/libht.la ../htcommon/libcommon.la ../htword/libht
>> word.la ../db/libhtdb.la ../htlib/libht.la -lz
>> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o dbbench dbbench.o
>> -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../htcomm
>> on/.libs/libcommon.a ../htword/.libs/libhtword.a ../db/.libs/libhtdb.a
>> ../htlib/.libs/libht.a -lz
>> g++ -DHAVE_CONFIG_H -I. -I. -I../include
>> -DDEFAULT_CONFIG_FILE=\"/opt/htdig/htdig32/conf/htdig.conf\"
>> -I../include -I../htlib
>> -I../htnet -I../htcommon -I../htword -I../db -I../db -I../db -I../db
>> -I/opt/htdig/lib/zlib/include  -g -O2 -Wall -fno-rtti
>> -fno-exceptions -c -o txt2mifluz.o `test -f 'txt2mifluz.cc' || echo
>> './'`txt2mifluz.cc
>> /bin/sh ../libtool --mode=link g++  -g -O2 -Wall -fno-rtti
>> -fno-exceptions  -L/opt/htdig/lib/zlib/lib -o txt2mifluz   txt2mifl
>> uz.o ../htnet/libhtnet.la ../htcommon/libcommon.la
>> ../htword/libhtword.la ../htlib/libht.la ../htcommon/libcommon.la 
>> ../htword
>> /libhtword.la ../db/libhtdb.la ../htlib/libht.la -lz
>> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o txt2mifluz txt2mifluz.o
>> -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../
>> htcommon/.libs/libcommon.a ../htword/.libs/libhtword.a
>> ../db/.libs/libhtdb.a ../htlib/.libs/libht.a -lz
>> g++ -DHAVE_CONFIG_H -I. -I. -I../include
>> -DDEFAULT_CONFIG_FILE=\"/opt/htdig/htdig32/conf/htdig.conf\"
>> -I../include -I../htlib
>> -I../htnet -I../htcommon -I../htword -I../db -I../db -I../db -I../db
>> -I/opt/htdig/lib/zlib/include  -g -O2 -Wall -fno-rtti
>> -fno-exceptions -c -o search.o `test -f 'search.cc' || echo 
>> './'`search.cc
>> /bin/sh ../libtool --mode=link g++  -g -O2 -Wall -fno-rtti
>> -fno-exceptions  -L/opt/htdig/lib/zlib/lib -o search   search.o ../
>> htnet/libhtnet.la ../htcommon/libcommon.la ../htword/libhtword.la
>> ../htlib/libht.la ../htcommon/libcommon.la ../htword/libhtwo
>> rd.la ../db/libhtdb.la ../htlib/libht.la -lz
>> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o search search.o
>> -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../htcommon
>> /.libs/libcommon.a ../htword/.libs/libhtword.a ../db/.libs/libhtdb.a
>> ../htlib/.libs/libht.a -lz
>> g++ -DHAVE_CONFIG_H -I. -I. -I../include
>> -DDEFAULT_CONFIG_FILE=\"/opt/htdig/htdig32/conf/htdig.conf\"
>> -I../include -I../htlib
>> -I../htnet -I../htcommon -I../htword -I../db -I../db -I../db -I../db
>> -I/opt/htdig/lib/zlib/include  -g -O2 -Wall -fno-rtti
>> -fno-exceptions -c -o testnet.o `test -f 'testnet.cc' || echo
>> './'`testnet.cc
>> /bin/sh ../libtool --mode=link g++  -g -O2 -Wall -fno-rtti
>> -fno-exceptions  -L/opt/htdig/lib/zlib/lib -o testnet   testnet.o .
>> ./htnet/libhtnet.la ../htcommon/libcommon.la ../htword/libhtword.la
>> ../htlib/libht.la ../htcommon/libcommon.la ../htword/libht
>> word.la ../db/libhtdb.la ../htlib/libht.la -lz
>> g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o testnet testnet.o
>> -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a ../htcomm
>> on/.libs/libcommon.a ../htword/.libs/libhtword.a ../db/.libs/libhtdb.a
>> ../htlib/.libs/libht.a -lz
>> collect2: ld returned 1 exit status
>> /usr/ccs/bin/ld: Unsatisfied symbols:
>>    WordType::instance  (data)
>> make[2]: *** [testnet] Error 1
>> make[2]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/test'
>> make[1]: *** [check-am] Error 2
>> make[1]: Leaving directory
>> `/pers/www/msql/Projects/Htdig/BUILD320/htdig-3.2.0b6/test'
>> make: *** [check-recursive] Error 1
>>
>> lac...@ip... wrote:
>>
>>> Greetings Jesse,
>>>
>>> Thanks for that.  Is this the system that had problems with 3.2.0b5? 
>>>  If
>>> so, it is very good to hear that it runs b6!  Is there a reason for 
>>> not using
>>> zlib compression?
>>>
>>> Could you post the results from  make check ?
>>>
>>> Thanks again,
>>> Lachlan
>>>
>>>
>>>
>>>> From: "J. op den Brouw" <ht...@op...>
>>>>
>>>>
>>>
>>>
>>>
>>>> HP-UX chaos B.10.20 U 9000/800 2004964319 unlimited-user license
>>>> hppa2.0-hp-hpux10.20
>>>> gcc 2.8.1
>>>> make 3.78
>>>> bash 2.03
>>>>
>>>> configure works, zlib compression compiled, but not used and no 
>>>> shared libs
>>>> make works
>>>> make check fails (!!)
>>>> make install works
>>>> rundig works (only 1000 pages tested), no external parsers 
>>>> configured
>>>> htsearch works
>>>>
>>>> builld and rundig log available.
>>>>
>>>> --jesse
>>>>
>>>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by the new InstallShield X.
>>> From Windows to Linux, servers to mobile, InstallShield X is the one
>> installation-authoring solution that does it all. Learn more and
>> evaluate today! http://www.installshield.com/Dev2Dev/0504
>> _______________________________________________
>> ht://Dig Developer mailing list:
>> htd...@li...
>> List information (subscribe/unsubscribe, etc.)
>> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>