[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: wrong `configure' results (ITS#327)

Devel issue should be resolved by latest commit by testing
for availability of a prototype and, if not recongizable,
ignoring ctime_r().  This is the best course of action as
it would be incorrect to define _POSIX_THREAD_SAFE_FUNCTIONS
(this should never be set by applications) and inappropriate
to define _REENTRANT (this should only be set when the
application is linked with threaded libraries).

At 09:34 AM 10/16/99 GMT, wowa@jetinf.com wrote:
>Full_Name: Vladimir V. Tsichevski
>Version: CVS snapshot 15.10.99
>OS: Linux 2.2.3 libc.5
>Submission from: (NULL) (
>CTIME_R_NARGS incorrect setup by configure (3 args detected instead of 2
>in my headers). Here is an excerpt from /usr/include/time.h
>extern char	* asctime_r	__P((__const struct tm *, char *));
>extern char	* ctime_r	__P((__const time_t *, char *));
>extern struct tm* gmtime_r	__P((__const time_t *, struct tm *));
>extern struct tm* localtime_r	__P((__const time_t *, struct tm *));

Kurt D. Zeilenga		<kurt@boolean.net>
Net Boolean Incorporated	<http://www.boolean.net/>