According to Bill & Kim:
> I did the first two -- the last one wasn't necessary as there were no
> references to htlib/regex.ht in htfuzzy/Makefile.

Yes, that's right.  The reference to htlib/regex.h only gets inserted if
you do a "make depend".

>  I actually made the first
> change in the Makefile.in before the first make, otherwise it did not work
> for some reason.
> 
> If worked just fine after these changes.  Needless to say, I was very happy.
> 
> Yes, I am running BSD 4.0 and I am sure others will run into the same
> problem.
> 
> Thanks,
> Bill
> 
> 
>    To go around this problem do the following:
> 
>     . Remove references to regex.o from htlib/Makefile.
>     . Remove, htlib/regex.h.
>     . Remove references to htlib/regex.h in htfuzzy/Makefile.
> 
> Please give this a try, and let us know if this fixes the problem for you.
> If it does, we should try to figure out a way to do this automatically via
> configure, in future releases.

Thanks for the update, Bill.  I'm cc'ing the htdig3-dev list, so I hope
someone can work out a way of automating this via configure.  As this seems
to confirm, the change should be made for all *BSD* systems.  However, I
should reiterate my previous observation on Red Hat Linux 4.2:  it's not
enough to simply test for the presence of /usr/include/regex.h - this file
exists on my system, but if you make the change above and try to use the
regex code in libc5, htfuzzy endings crashes with a segmentation fault.
So, in this case at least, you must use the bundled code rather than the
system code.  It's a strange discrepancy.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.

Reply via email to