Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Russ Allbery writes:

>> [AC_TRY_LINK(
>> [#include <time.h>
>> #ifndef tzname /* For SGI.  */
>> extern char *tzname[]; /* RS6000 and others reject char **tzname.  */
>> #endif
>> ],
>> [atoi(*tzname);], ac_cv_var_tzname=yes, ac_cv_var_tzname=no)])

>> The atoi() makes no sense.

> I suspect that just writing `tzname;' would cause some dumb compilers to
> complain.

My macro instead does *tzname = "UTC".  I'm not aware of any platform that
uses these variables but doesn't allow the user to modify them, so that
seems to work.

> Actually, there is no namespace for functions. There is just
> HAVE_<thing>, for any <thing>. Consider checking for the C++ header
> <string> vs the class `string'.

Point.

> Better timezone'ish macros would be appreciated.

Well, I need ones like the ones I included, one way or another, but I've
been putting off making everything nice and pretty and properly quoted
until I have a reference base to work from, can include .m4 files so that
it doesn't all have to go in two files, and most relevantly can check the
work into INN without requiring a CVS snapshot autoconf.

So expect to see lots of macros from me after autoconf 2.50 is released.

Currently in INN and not in autoconf:

 - Finding BerkeleyDB and OpenSSL and setting up an appropriate
   compilation environment (libraries, headers, etc.) as necessary.

 - The installed version of Perl.

 - The flags necessary for building with an embedded Perl or Python
   interpreter.

 - IOV_MAX (the maximum allowable structs for a readv or writev).

 - Whether there's a tm_gmtoff in struct tm, and if not whether there are
   external timezone and daytime variables.

 - int32_t and uint32_t, if not provided by the implementation.

 - Working inet_ntoa.

 - If changes made by write show up in an mmap'd region of the file in the
   same program.

 - If changes made to an mmap'd region show up when reading from the file.

 - A more aggressive mmap check.

 - How many arguments msync takes.

-- 
Russ Allbery ([EMAIL PROTECTED])             <http://www.eyrie.org/~eagle/>

Reply via email to