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

Re: [htdig-dev] powered by ... notice

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

On Sun, 13 Mar 2005, Manuel Domke wrote:

> Hi,
> 
> Am I allowed to delete your "powered by" Notice when  will use the
> ht://DIG for my search engine

  Yes.. you can customize the UI to your hearts content.  Of course we 
would still appreciate a back-link to htdig.org or some form of 
recognition.

> and what am i allowed to do with the script ?

  You can do just about anything you want with all source code that obeys 
the license conditions in the LICENSE file (and the db/LICENSE file if you 
are using 3.2.x).

  Basically you can't claim it as your own.  If you make changes that 
you then redistribute, you must make those changes avail to those people 
that you distribute to.
 
  Thanks.

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

[htdig-dev] powered by ... notice

[Manuel D. <web...@no...>]

Hi,

Am I allowed to delete your "powered by" Notice when  will use the
ht://DIG for my search engine

and what am i allowed to do with the script ?

mfg

manuel Domke

Re: [htdig-dev] Re: HTML Parser and start of CLucene conversion

[Olly B. <ol...@su...>]

On Wed, Mar 09, 2005 at 10:46:12AM -0700, Neal Richter wrote:
>   Yep, this is one of the problems with Open Source.  It would be smart 
> for all licenses to have a 'time horizon' on them where if the copyright 
> is not updated in 5-10 years it becomes either public-domain or the 
> copyright is assigned to some third party.

A nice idea, though I suspect it might be hard to sell such a licence to
corporate types.  As it was BrightStation wanted to roll their own
licence rather than use the GPL.  There are already too many mutually
incompatible "open source" licences.

Sadly copyright law has been moving towards longer copyright periods
rather than shorter.

> > I figured a better use of the time would be to simply rewrite any code
> > we couldn't convince the author to relicence.  It's certainly not my
> > major focus right now, but it's slowly happening naturally.
> 
>   Here's a proposal for you:
> 
>   Could you break down what portions of Xapian that are 'ownership clean' 
> and able to be changed into the LGPL?

It's pretty easy actually.  If the copyright notices on a file include
BrightStation or Ananova (I believe the latter is a strict subset of the
former) then it can't simply be relicensed.  Some time ago I informally
asked all the other copyright holders, and they're probably OK with it.

We use an autoptr implementation taken from the GNU ISO C++ library,
which is GPL + a library exception.  But that could easily be replaced
by something from boost.

We replaced the original stemming code with code from snowball, which is
new-style BSD.  The queryparser has recently been rewritten from
scratch.  The Java bindings are new-style BSD, and the Perl bindings are
the same licence as Perl (your choice of GPL or Perl's Artistic
licence).  Some of the other binding code is OK too.  Some of the
examples have been written from scratch, so they're OK.  And we use GNU
getopt (which is LGPL).

I've probably missed some, but that's a rough idea.

Not all code needs to be relicensed actually.  Having a GPL testsuite
isn't really a problem, and the muscat36 backend could be dropped (or
left GPL so you'd be able to use the library under the GPL with the
muscat36 backend to convert your old databases to Xapian ones).
Similarly, the examples and utility programs could be left as GPL too.

Cheers,
    Olly

Re: [htdig-dev] Re: HTML Parser and start of CLucene conversion

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

Hey Olly,

	We traded emails a while back Re:Snowball stemmers.	

> Ideally I'd prefer Xapian to be LGPL licenced (or perhaps something less
> restrictive even).  But the current developers don't own all the
> copyrights, so we can't just pick another licence.
> 
> Xapian is derived from software which was released under the GPL by
> BrightStation plc.  BrightStation's plan was to sell licences to those
> wanting to use the code but unwilling to GPL their own code.
>
> I tried to negotiate a relicensing with those who now own the
> BrightStation copyright (or at least claim to), but it seemed to just be
> an infinite timesink.

  Yep, this is one of the problems with Open Source.  It would be smart 
for all licenses to have a 'time horizon' on them where if the copyright 
is not updated in 5-10 years it becomes either public-domain or the 
copyright is assigned to some third party.
 
> I figured a better use of the time would be to simply rewrite any code
> we couldn't convince the author to relicence.  It's certainly not my
> major focus right now, but it's slowly happening naturally.

  Here's a proposal for you:

  Could you break down what portions of Xapian that are 'ownership clean' 
and able to be changed into the LGPL?

  We're solving a lot of the same problems and it seems like we could be 
sharing code a bit.

  Thanks!

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

Re: [htdig-dev] Release this code! 3.2 is done!??

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

> Do we have anyone for Linux... any Linux?

 I can do the RPMs for RedHat.

 Just Curious:
  Is everyone else getting hit by the flu?  A big chunk of my office was 
in the last few days.

Thanks

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

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 9 Mar 2005 at 11:06, Geoff Hutchison wrote:

> On Mar 8, 2005, at 6:44 AM, Dan Langille wrote:
> 
> > If the "Pre-Release Checklist" has not been done, I have no clues
> > about LeakTester, checker, purify, gprof.  Anyone?
> 
> I can vouch that essentially everything in the pre-release checklist 
> has been done. The utilities you mention are used for finding memory 
> leaks and generating profiling/performance data.

OK, so we can skip the pre-release stage.  That's a huge set of tasks 
gone from the process.

> Yes, I think it'd be helpful to know that some Linux packages would be 
> available around the same time as the release.

What I need (or rather, our clients need) is packages from from their 
vendor (in this case, RedHat).  ;)

cheers
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Geoff H. <ge...@ge...>]

On Mar 8, 2005, at 6:44 AM, Dan Langille wrote:

> If the "Pre-Release Checklist" has not been done, I have no clues
> about LeakTester, checker, purify, gprof.  Anyone?

I can vouch that essentially everything in the pre-release checklist 
has been done. The utilities you mention are used for finding memory 
leaks and generating profiling/performance data.

Yes, I think it'd be helpful to know that some Linux packages would be 
available around the same time as the release.

-Geoff

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 9 Mar 2005 at 13:16, Ted Stresen-Reuter wrote:

> Mac OS X (10.3.8) here... I'll also make a package installer for this 
> platform as well.
> 
> http://xoops.tedmasterweb.com/modules/mydownloads/viewcat.php?cid=1
> 
> Ted Stresen-Reuter
> (Yes, I'm still here, still reading, and still trying to support this 
> project)

That's great!

Do we have anyone for Linux... any Linux?


> On Mar 8, 2005, at 11:44 AM, Dan Langille wrote:
> 
> > On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:
> >
> >>> 	Geoff: could you create a release tarball (and maybe create a
> >>> document detailed how you generaly do this)
> >>
> >> Such a document already exists. It's a little out-of-date (since it's
> >> back in the days before SourceForge), but it's still pretty much
> >> correct:
> >>
> >> http://htdig.org/dev/checklist.html
> >
> > I can do some of that, mostly test compiling on FreeBSD.  Do I have
> > volunteers for other platforms?
> >
> > From that list, there is a "Pre-Release Checklist" and a "Release
> > Checklist".  Has the former been done yet?
> >
> > If the "Pre-Release Checklist" has not been done, I have no clues
> > about LeakTester, checker, purify, gprof.  Anyone?
> >
> >> I'd also add (before tagging the CVS release)
> >> * Check copyright dates in maindocs/ README, and code to ensure they
> >> include the current year.
> >>
> >> And after adding the tar and diff to the /files directory, you'll also
> >> need to:
> >> * Add tar and diff to SF.net release manager
> >> * Add NEWS item to SF.net project page
> >>
> >> I think that's pretty much complete.
> >>
> >> I'd be glad to help anyone going through the process to make sure
> >> there's accurate, up-to-date documentation of what to do. But I
> >> *really* think the more people who go through it, the better for the
> >> project. If I'm the only one who does it and I'm hit by a bus or fall
> >> off the map tomorrow, we're in trouble. :-)
> >
> > cheers
> > -- 
> > Dan Langille : http://www.langille.org/
> > BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
> >
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real 
> > users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > ht://Dig Developer mailing list:
> > htd...@li...
> > List information (subscribe/unsubscribe, etc.)
> > https://lists.sourceforge.net/lists/listinfo/htdig-dev
> >
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
> 
> 


-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

Re: [htdig-dev] Release this code! 3.2 is done!??!

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

Mac OS X (10.3.8) here... I'll also make a package installer for this 
platform as well.

http://xoops.tedmasterweb.com/modules/mydownloads/viewcat.php?cid=1

Ted Stresen-Reuter
(Yes, I'm still here, still reading, and still trying to support this 
project)

On Mar 8, 2005, at 11:44 AM, Dan Langille wrote:

> On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:
>
>>> 	Geoff: could you create a release tarball (and maybe create a
>>> document detailed how you generaly do this)
>>
>> Such a document already exists. It's a little out-of-date (since it's
>> back in the days before SourceForge), but it's still pretty much
>> correct:
>>
>> http://htdig.org/dev/checklist.html
>
> I can do some of that, mostly test compiling on FreeBSD.  Do I have
> volunteers for other platforms?
>
> From that list, there is a "Pre-Release Checklist" and a "Release
> Checklist".  Has the former been done yet?
>
> If the "Pre-Release Checklist" has not been done, I have no clues
> about LeakTester, checker, purify, gprof.  Anyone?
>
>> I'd also add (before tagging the CVS release)
>> * Check copyright dates in maindocs/ README, and code to ensure they
>> include the current year.
>>
>> And after adding the tar and diff to the /files directory, you'll also
>> need to:
>> * Add tar and diff to SF.net release manager
>> * Add NEWS item to SF.net project page
>>
>> I think that's pretty much complete.
>>
>> I'd be glad to help anyone going through the process to make sure
>> there's accurate, up-to-date documentation of what to do. But I
>> *really* think the more people who go through it, the better for the
>> project. If I'm the only one who does it and I'm hit by a bus or fall
>> off the map tomorrow, we're in trouble. :-)
>
> cheers
> -- 
> Dan Langille : http://www.langille.org/
> BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:

> > 	Geoff: could you create a release tarball (and maybe create a 
> > document detailed how you generaly do this)
> 
> Such a document already exists. It's a little out-of-date (since it's 
> back in the days before SourceForge), but it's still pretty much 
> correct:
> 
> http://htdig.org/dev/checklist.html

I can do some of that, mostly test compiling on FreeBSD.  Do I have 
volunteers for other platforms?

From that list, there is a "Pre-Release Checklist" and a "Release 
Checklist".  Has the former been done yet?

If the "Pre-Release Checklist" has not been done, I have no clues 
about LeakTester, checker, purify, gprof.  Anyone?

> I'd also add (before tagging the CVS release)
> * Check copyright dates in maindocs/ README, and code to ensure they 
> include the current year.
> 
> And after adding the tar and diff to the /files directory, you'll also 
> need to:
> * Add tar and diff to SF.net release manager
> * Add NEWS item to SF.net project page
> 
> I think that's pretty much complete.
> 
> I'd be glad to help anyone going through the process to make sure 
> there's accurate, up-to-date documentation of what to do. But I 
> *really* think the more people who go through it, the better for the 
> project. If I'm the only one who does it and I'm hit by a bus or fall 
> off the map tomorrow, we're in trouble. :-)

cheers
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

[htdig-dev] Re: HTML Parser and start of CLucene conversion

[Olly B. <ol...@su...>]

On 2005-02-02, Neal Richter <ne...@ri...> wrote:
>    Xapian is GPL, Lucene/CLucene is LGPL.  Evidently the Xapian people 
> didn't read the 4th paragraph of http://www.gnu.org/philosophy/why-not-lgpl.html
>
> "Using the ordinary GPL is not advantageous for every library. There are
> reasons that can make it better to use the Library GPL in certain cases. 
> The most common case is when a free library's features are readily 
> available for proprietary software through other alternative
> libraries. In that case, the library cannot give free software any
> particular advantage, so it is better to use the Library GPL for that
> library."

Actually, we have read that.

For many users, the GPL/LGPL distinction won't actually matter - if you
aren't distributing the GPL's restrictions don't apply, so you can
deploy a proprietary application using Xapian on your webserver.

Ideally I'd prefer Xapian to be LGPL licenced (or perhaps something less
restrictive even).  But the current developers don't own all the
copyrights, so we can't just pick another licence.

Xapian is derived from software which was released under the GPL by
BrightStation plc.  BrightStation's plan was to sell licences to those
wanting to use the code but unwilling to GPL their own code.

I tried to negotiate a relicensing with those who now own the
BrightStation copyright (or at least claim to), but it seemed to just be
an infinite timesink.

I figured a better use of the time would be to simply rewrite any code
we couldn't convince the author to relicence.  It's certainly not my
major focus right now, but it's slowly happening naturally.

>> Gmane uses Xapian against 20+ million documents.

Including your message, which I found while testing!

Cheers,
    Olly (Xapian developer)

[htdig-dev] Re: HTML Parser and start of CLucene conversion

[Olly B. <ol...@su...>]

On 2005-02-02, Neal Richter <ne...@ri...> wrote:
>    Xapian is GPL, Lucene/CLucene is LGPL.  Evidently the Xapian people 
> didn't read the 4th paragraph of http://www.gnu.org/philosophy/why-not-lgpl.html
>
> "Using the ordinary GPL is not advantageous for every library. There are
> reasons that can make it better to use the Library GPL in certain cases. 
> The most common case is when a free library's features are readily 
> available for proprietary software through other alternative
> libraries. In that case, the library cannot give free software any
> particular advantage, so it is better to use the Library GPL for that
> library."

Actually, we have read that.

For many users, the GPL/LGPL distinction won't actually matter - if you
aren't distributing the GPL's restrictions don't apply, so you can
deploy a proprietary application using Xapian on your webserver.

Ideally I'd prefer Xapian to be LGPL licenced (or perhaps something less
restrictive even).  But the current developers don't own all the
copyrights, so we can't just pick another licence.

Xapian is derived from software which was released under the GPL by
BrightStation plc.  BrightStation's plan was to sell licences to those
wanting to use the code but unwilling to GPL their own code.

I tried to negotiate a relicensing with those who now own the
BrightStation copyright (or at least claim to), but it seemed to just be
an infinite timesink.

I figured a better use of the time would be to simply rewrite any code
we couldn't convince the author to relicence.  It's certainly not my
major focus right now, but it's slowly happening naturally.

>> Gmane uses Xapian against 20+ million documents.

Including your message, which I found while testing!

Cheers,
    Olly (Xapian developer)

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Geoff H. <ge...@ge...>]

> 	Geoff: could you create a release tarball (and maybe create a 
> document detailed how you generaly do this)

Such a document already exists. It's a little out-of-date (since it's 
back in the days before SourceForge), but it's still pretty much 
correct:

http://htdig.org/dev/checklist.html

I'd also add (before tagging the CVS release)
* Check copyright dates in maindocs/ README, and code to ensure they 
include the current year.

And after adding the tar and diff to the /files directory, you'll also 
need to:
* Add tar and diff to SF.net release manager
* Add NEWS item to SF.net project page

I think that's pretty much complete.

I'd be glad to help anyone going through the process to make sure 
there's accurate, up-to-date documentation of what to do. But I 
*really* think the more people who go through it, the better for the 
project. If I'm the only one who does it and I'm hit by a bus or fall 
off the map tomorrow, we're in trouble. :-)

-Geoff

[htdig-dev] 3.2.0 release plans?

[Dan L. <da...@la...>]

For those on the general list, sorry you're seeing this a second 
time.

What are the release plans for 3.2.0?  What can I do to help things along?

I ask because we're developing with 3.2.0b6.  Yet, we cannot expect that 
our customers will install "beta" software.  We also need the vendors 
to create the packages, because the enterprises won't install 
packages unless they come from the vendor.  Creating a production 
release of htdig 3.2.0 is becoming important to us.

cheers
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Jim <li...@yg...>]

On Fri, 25 Feb 2005, Neal Richter wrote:

> Hey all,
> 	This think we should just call it a day on version 3.2 and release 
> it.  Any objections?

I think we should at least take a look at the current bug list and see
if there is anything that deserves attention before going to 3.2. I know
that there is at least one major bug in SSL handling. I provided a
possible fix but never received any feedback. I also didn't receive any
response when I asked about getting sufficient access to apply the patch
and perhaps do some other project related housekeeping. Probably just
bad timing; I know everyone is very busy.

I am also aware of an argument parsing bug in the external parser code
that I tracked down when following up on a problem reported on the
htdig-general list. I don't think this one ever made it to the bug list.

In addition we should really follow up on the cross-site scripting
vulnerability that was recently reported for ht://Dig.

   http://securitytracker.com/alerts/2005/Feb/1013078.html

Gentoo, Red Hat, and Debian have already released fixes, and I don't
think it has even been discussed here aside from one message asking
about the vulnerability on htdig-general.

> 	Geoff: could you create a release tarball (and maybe create a 
> document detailed how you generaly do this)

If there is existing documentation describing the process, or someone
with a clue is willing to walk me through it, I would be willing to try
taking over this task for future releases.


Jim

[htdig-dev] Release this code! 3.2 is done!??!

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

Hey all,
 	This think we should just call it a day on version 3.2 and release 
it.  Any objections?

 	Geoff: could you create a release tarball (and maybe create a 
document detailed how you generaly do this)

Steps:
 	1) Create release tarball
 	2) Update WWW site
 	3) Call Bill Gates, Larry Page and Sergey Brin and let them know.

Thanks

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

[htdig-dev] Corrected Berkeley DB version number in LICENESE

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

Hey all,
 	Micael Olson @ Sleepycat contacted me recently about the special 
license they issued HtDig for BDB.  See db/LICENSE file.  We are using BDB 
3.0.55 code.. however the license had version 3.3.11 in it.

 	I just corrected this in CVS.

 	Thanks.

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

Re: [htdig-dev] Interested in Developing for this project.

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

On Sat, 19 Feb 2005, Abhijit Joshi wrote:

> Hello Experienced Developers,
> With all due respect to your experience in developing for this project
> and knowledge, I would like to ask one question.
> I am an interetsed candidate wanting to contribute to this project. I
> have never contributed to any open source project. But I have to start
> somewhere. I chose this project becasue of two reasons, 1) My interest
> education and theretical understaing of Information retrieval systems.
> 2) I want start developing rather than just having theoretical knowledge.
> I get ovewhelemed when I see such a huge project. What Is the approch
> that I should follow when trying to understand and then contribute to
> this project. If you can point me to certain steps, that will be
> appreciated. If you would like more information about this. Please let
> me know.

   The first step is to get it installed and compiled and learn about how 
HtDig is configured.  The step after that is to run it in a debugger and 
get a feel for the flow of the code.

   You are certainly welcome to participate and contribute code.

   HtDig's core design is fairly old, and there is lots of interesting new 
IR research out there.  This is good in that there is tons of low hanging
fruit to make good improvements.

   Code contributions of all kinds are welcome.

   Thanks

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

[htdig-dev] Interested in Developing for this project.

[Abhijit J. <jab...@gm...>]

Hello Experienced Developers,
With all due respect to your experience in developing for this project
and knowledge, I would like to ask one question.
I am an interetsed candidate wanting to contribute to this project. I
have never contributed to any open source project. But I have to start
somewhere. I chose this project becasue of two reasons, 1) My interest
education and theretical understaing of Information retrieval systems.
2) I want start developing rather than just having theoretical knowledge. 
I get ovewhelemed when I see such a huge project. What Is the approch
that I should follow when trying to understand and then contribute to
this project. If you can point me to certain steps, that will be
appreciated. If you would like more information about this. Please let
me know.

Thank you in advance,

Abhi

[htdig-dev] New Canada Mirrror

[Blair L. <ht...@ze...>]

Hi,

Looks like I accidentally cross-threaded my message last time - sorry
Gregory.

I just created a new Canadian (Canada) mirror:

http://www.htdig.ca

Please add it to the mirrors page.

Thanks,
Blair.

[htdig-dev] New Mirror

[Blair L. <ht...@ze...>]

Hi,

I just created a new Canadian (Canada) mirror:

http://www.htdig.ca

Please add it to the mirrors page.

Thanks,
Blair.

[htdig-dev] Re: unsigned long long int error (was: htdig and libstdc++ requirement)

[Gregory H. <gh...@ca...>]

> Date: Thu, 3 Feb 2005 22:49:49 -0700 (MST)
> From: Neal Richter <ne...@ri...>
> 
> On Thu, 3 Feb 2005, Gregory Hicks wrote:
> 
> >
[...snip...]
> >
> > However, Now I get back an error on "unsigned long long int":
> >
> > checking size of unsigned long long int... configure: error: cannot
> > compute sizeof (unsigned long long int), 77
> > See `config.log' for more details.
> > metis%
> >
> > [...config.log extract...]
> > configure:23057: checking for unsigned long long int
> > configure:23081: gcc -c -g -O2 -Wall  conftest.c >&5
> > configure:23087: $? = 0
> > configure:23090: test -z                         || test ! -s conftest.err
> > configure:23093: $? = 0
> > configure:23096: test -s conftest.o
> > configure:23099: $? = 0
> > configure:23110: result: yes
> > configure:23113: checking size of unsigned long long int
> > configure:23425: gcc -o conftest -g -O2 -Wall   conftest.c -lz -lnsl 
-lsocket  >&5
> > configure:23428: $? = 0
> > configure:23430: ./conftest
> > ld.so.1: ./conftest: fatal: relocation error: file ./conftest: symbol
> > __register_frame_info: referenced symbol not found
> > ./configure: line 1: 11852 Killed                  ./conftest$ac_exeext
> > configure:23433: $? = 137
> > configure: program exited with status 137
> > configure: failed program was:
> >
> > Any other thoughts?  Thanks for the assist and pointer though!
> 
>    I'll check ASAP, however I don't think we use any 'unsigned long long 
> int'.  You can probably hack the configure script and remove a 'long' 
> in the code that produces conftest.c and it will work fine.  Or comment 
> out that check.

Neal:

Well, I did that and then got a failure on "unsigned long int".  So I
went back to the original script.

Llooking back through the htdig archives, I saw a note from Kenneth
saying that the issue might be in libz.so...  Checking, I found that I
had two versions:  One in /usr/lib provided by Sun in packages SUNWzlib
and SUNWzlibx.  I also had one in /usr/local/lib...  I put
/usr/local/lib before /usr/lib in LD_LIBRARY_PATH and the configure
completed.  The one in /usr/local/lib is the one from GNU and was
either downloaded from http://sunfreeware.com or was compiled on my
machine.  (The Sun and GNU are both the same version - V1.1.3...)

I'm now doing a compile to see if it completes.  If so, then I'll did
further to see where binaries, scripts, et al need to be placed and
reconfigure.

Thanks for your assistance.  (I send this note so that others might see
and benefit.)

Regards,
Gregory Hicks

-------------------------------------------------------------------
Gregory Hicks                        | Principal Systems Engineer
Cadence Design Systems               | Direct:   408.576.3609
555 River Oaks Pkwy M/S 6B1          | Fax:      408.894.3400
San Jose, CA 95134 

I am perfectly capable of learning from my mistakes.  I will surely
learn a great deal today.

"A democracy is a sheep and two wolves deciding on what to have for
lunch.  Freedom is a well armed sheep contesting the results of the
decision." - Benjamin Franklin

"The best we can hope for concerning the people at large is that they
be properly armed." --Alexander Hamilton

Re: [htdig-dev] htdig and libstdc++ requirement was: htdig on win32?)

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

On Thu, 3 Feb 2005, Gregory Hicks wrote:

>
>> From: Jim <li...@yg...>
>> Date: Thu, 3 Feb 2005 14:24:30 -0700 (MST)
>>
>> On Wed, 2 Feb 2005, Gregory Hicks wrote:
>>
> [...snip...]
>>
>> Have you verified that a C++ compiler and library is really installed
>> and functional? Have you successfully compiled any other C++ code? If not,
>> you might want to try compiling a small test program. If you are not
>> familiar with C++, the following test might be helpful.
>
> Thanks Jim!  Problem solved.  It seems that there was a problem with a
> library in the gcc342 package I installed.  I downgraded to 3.3.2,
> recompiled the cpptest program and it works.  I'm running the configure
> script as I type now.
>
> Thanks for the pointer!
>
> However, Now I get back an error on "unsigned long long int":
>
> checking size of unsigned long long int... configure: error: cannot
> compute sizeof (unsigned long long int), 77
> See `config.log' for more details.
> metis%
>
> [...config.log extract...]
> configure:23057: checking for unsigned long long int
> configure:23081: gcc -c -g -O2 -Wall  conftest.c >&5
> configure:23087: $? = 0
> configure:23090: test -z                         || test ! -s conftest.err
> configure:23093: $? = 0
> configure:23096: test -s conftest.o
> configure:23099: $? = 0
> configure:23110: result: yes
> configure:23113: checking size of unsigned long long int
> configure:23425: gcc -o conftest -g -O2 -Wall   conftest.c -lz -lnsl -lsocket  >&5
> configure:23428: $? = 0
> configure:23430: ./conftest
> ld.so.1: ./conftest: fatal: relocation error: file ./conftest: symbol
> __register_frame_info: referenced symbol not found
> ./configure: line 1: 11852 Killed                  ./conftest$ac_exeext
> configure:23433: $? = 137
> configure: program exited with status 137
> configure: failed program was:
>
> Any other thoughts?  Thanks for the assist and pointer though!

   I'll check ASAP, however I don't think we use any 'unsigned long long 
int'.  You can probably hack the configure script and remove a 'long' 
in the code that produces conftest.c and it will work fine.  Or comment 
out that check.

Thanks.

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

Re: [htdig-dev] htdig and libstdc++ requirement was: htdig on win32?)

[Gregory H. <gh...@ca...>]

> From: Jim <li...@yg...>
> Date: Thu, 3 Feb 2005 14:24:30 -0700 (MST)
> 
> On Wed, 2 Feb 2005, Gregory Hicks wrote:
> 
[...snip...]
> 
> Have you verified that a C++ compiler and library is really installed
> and functional? Have you successfully compiled any other C++ code? If not,
> you might want to try compiling a small test program. If you are not
> familiar with C++, the following test might be helpful.

Thanks Jim!  Problem solved.  It seems that there was a problem with a
library in the gcc342 package I installed.  I downgraded to 3.3.2,
recompiled the cpptest program and it works.  I'm running the configure
script as I type now.

Thanks for the pointer!

However, Now I get back an error on "unsigned long long int":

checking size of unsigned long long int... configure: error: cannot
compute sizeof (unsigned long long int), 77
See `config.log' for more details.
metis% 

[...config.log extract...]
configure:23057: checking for unsigned long long int
configure:23081: gcc -c -g -O2 -Wall  conftest.c >&5
configure:23087: $? = 0
configure:23090: test -z                         || test ! -s conftest.err
configure:23093: $? = 0
configure:23096: test -s conftest.o
configure:23099: $? = 0
configure:23110: result: yes
configure:23113: checking size of unsigned long long int
configure:23425: gcc -o conftest -g -O2 -Wall   conftest.c -lz -lnsl -lsocket  >&5
configure:23428: $? = 0
configure:23430: ./conftest
ld.so.1: ./conftest: fatal: relocation error: file ./conftest: symbol 
__register_frame_info: referenced symbol not found
./configure: line 1: 11852 Killed                  ./conftest$ac_exeext
configure:23433: $? = 137
configure: program exited with status 137
configure: failed program was:

Any other thoughts?  Thanks for the assist and pointer though!

Regards,
Gregory Hicks

> 
> Create a file named cpptest.cpp with the following code.
> 
> #include <iostream>
> 
> int main(int, char* []) {
>       std::cout << "Success" << std::endl;
> 
>       return 0;
> }
> 
> Save the file and then execute the following command.
> 
> g++ -Wall cpptest.cpp -o cpptest
> 
> If you make it that far, execute the following.
> 
> ./cpptest
> 
> You should see the word 'Success' output by the program.
> 
> If you can't make it this far, then something is missing or fundamentally
> broken with respect to your environment or compiler install.
> 
> 
> Jim
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev

-------------------------------------------------------------------
Gregory Hicks                        | Principal Systems Engineer
Cadence Design Systems               | Direct:   408.576.3609
555 River Oaks Pkwy M/S 6B1          | Fax:      408.894.3400
San Jose, CA 95134                   | Internet: gh...@ca...

I am perfectly capable of learning from my mistakes.  I will surely
learn a great deal today.

"A democracy is a sheep and two wolves deciding on what to have for
lunch.  Freedom is a well armed sheep contesting the results of the
decision." - Benjamin Franklin

"The best we can hope for concerning the people at large is that they
be properly armed." --Alexander Hamilton

[htdig-dev] CORRECTION: Initial results of swap to CLucene

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

I'n my last email I incorrectly sent the stats for the uncompressed 
BDB index and called it the compressed index.

Here are the corrected numbers:

  ------------------- uncompressed BDB -----------

  real    5m31.248s
  user    1m14.760s
  sys     0m6.860s

  284k    webindex/db.docdb
  92k     webindex/db.docs.index
  5.3M    webindex/db.excerpts
  60M     webindex/db.words.db
  4.0k    webindex/luceneidx

  Total Size: ~ 66MG

  ------------------- compressed BDB -----------

real    7m30.228s
user    4m34.460s
sys     0m22.220s

284k    webindex/db.docdb
92k     webindex/db.docs.index
5.3M    webindex/db.excerpts
18M     webindex/db.words.db
16k     webindex/db.words.db_weakcmpr
4.0k    webindex/luceneidx

Total Size ~ 23MG

  ------------------- CLucene -----------

  real    2m31.635s
  user    1m57.850s
  sys     0m25.390s

  284k    webindex/db.docdb
  92k     webindex/db.docs.index
  16k     webindex/db.excerpts
  4.0k    webindex/db.words.db
  22M     webindex/luceneidx

  Total Size ~ 22 MG

Thanks

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