According to J. op den Brouw:
> On Tue, 25 Sep 2001, Gilles Detillieux wrote:
> > your system. Knowing whether HAVE_STRPTIME and HAVE_TIMEGM are defined
> > in your include/htconfig.h will tell us if the problem function is ours
> > or in your C library.
>
> ...
> /* Define if you have the strerror function. */
> #define HAVE_STRERROR 1
>
> /* Define if you have the strptime function. */
> #define HAVE_STRPTIME 1
>
> /* Define if you have the strstr function. */
> #define HAVE_STRSTR 1
>
> /* Define if you have the timegm function. */
> /* #undef HAVE_TIMEGM */
>
> /* Define if you have the vsnprintf function. */
> #define HAVE_VSNPRINTF 1
> ...
OK, I'm pretty sure the bundled timegm() function is solid, so let's go
with the hunch than strptime() is failing. I'd still like to know how
it's failing. Using the LOOSE_* formats as in the original source, could
you uncomment the ViewStructTM() call on line 100 in HtDateTime::SetFTime()
in htlib/HtDateTime.cc, and add a "#define TEST_HTDATETIME" somewhere
above this to enable the test code in this module? This should show the
intermediate values in the tm structure after strptime(), and maybe we'll
see where/why it's failing.
--
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
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
