From: gmarzot@BayNetworks.com (Joe Marzot)
>
> I got the following message while testing out a compile of the new
> 5.002beta1 fresh out of the box.
>
> I ran Configure on a sun4 4.1.3 with gcc 2.6.3
>
> prompt>./Configure -Dcc=gcc
> ...<snip>...
> *** WHOA THERE!!! ***
> The recommended value for $d_tzname on this machine was "undef"!
> Keep the recommended value? [y]
>
>
> I think I have seen this before and it has not hurt me but was always a
> little unsettling.
I posted to p5p about this a couple of weeks ago.
Here is a copy of the message
> From owner-perl5-porters@nicoh.com Tue Nov 14 11:16:25 1995
> Return-Path: <owner-perl5-porters@nicoh.com>
> Date: Tue, 14 Nov 95 11:09:16 GMT
> From: pmarquess@bfsec.bt.co.uk (Paul Marquess)
> Message-Id: <9511141109.AA15268@claudius.bfsec.bt.co.uk>
> To: doughera@lafcol.lafayette.edu, ram@hptnos02.grenoble.hp.com
> Subject: SunOS and d_tzname
> Cc: perl5-porters@africa.nicoh.com
> Sender: owner-perl5-porters@nicoh.com
> List-Name: perl5-porters
> Content-Length: 692
> X-Lines: 21
>
> I've been meaning to get to the bottom of this for a while...
>
> Every time I build Perl on my SunOS box, I get this message:
>
> tzname[] found.
>
> *** WHOA THERE!!! ***
> The recommended value for $d_tzname on this machine was "undef"!
> Keep the recommended value? [y]
>
> I've had a go at trying to find where Configure is getting the duff
> definition of tzname. Once I added a bit of tracing logic to Configure
> I found that it checked for the existance of tzname by grepping the
> file libc.tmp for the string tzname. This matched the line below
>
> 00009198 t _getzname
>
> If it had grepping libc.list instead it would have correctly not found
> tzname. Is the fix as simple as that?
>
> Paul
>