The other option would be to undefine HAVE_TIMEGM
in include/htconfig.h. I'd be curious to know what the
compile time errors actually were, and why, if OpenBSD
has the timegm() function, can't htdig use it. It may be
that we need a more sophisticated test for timegm() than
simply testing if it's there in the library. BSD systems do
seem to have a knack for thwarting many of ht://Dig's
configure tests.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=149687
The other option would be to undefine HAVE_TIMEGM
in include/htconfig.h. I'd be curious to know what the
compile time errors actually were, and why, if OpenBSD
has the timegm() function, can't htdig use it. It may be
that we need a more sophisticated test for timegm() than
simply testing if it's there in the library. BSD systems do
seem to have a knack for thwarting many of ht://Dig's
configure tests.
Logged In: YES
user_id=149687
Version 3.1.6 now does away with timegm/mytimegm. We still
need to do likewise with 3.2.0b4.