Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.php Subject: Re: how to set default timezone as a .config argument? Date: Thu, 14 Jan 2016 08:49:21 +0100 Lines: 57 Message-ID: <56975301.8000108@arnowelzel.de> References: <5696DB4E.1020802@arnowelzel.de> <56975237.1070907@arnowelzel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Trace: individual.net lnHtRNPCH5ORYtMxHaw66wGRVFfk8MRoNKGw/1JB5OzqYE+Xn1 Cancel-Lock: sha1:H1RSnEI4Ndd8Of77+f5Ll/AaeAo= In-Reply-To: <56975237.1070907@arnowelzel.de> Xref: csiph.com comp.lang.php:16267 Arno Welzel schrieb am 2016-01-14 um 08:45: > crankypuss schrieb am 2016-01-14 um 08:13: > >> Arno Welzel wrote: >> >>> crankypuss schrieb am 2016-01-13 um 23:54: >>> >>>> When building PHP from source, I want to set the default timezone to >>>> UTC via some .config option, is there such an option? >>> >>> No, there isn't. >>> >>> See . >> >> Why should I read again the same text that is provided by ".configure -- >> help"? > > I just mentioned it because I was not sure if you did read it at all or > you may believe ".configure --help" will not show all possible options. > >>>> What I've found is, >>>> >>>> "To assign environment variables (e.g., CC, CFLAGS...), specify them >>>> as VAR=VALUE." >>> >>> Yes - but this has nothing to do with the default timezone PHP uses at >>> runtime. See >>> >> . >>> >>> Even if TZ is set this makes no difference for compilation. >> >> One of the reasons I want to build PHP from source is so I'm not >> constantly hounded by whatever is deprecated this week. If there's no >> option I can use when building it that will shut off the damned idiotic >> warning, I'll just hunt it down and remove it. > > Things do not become deprecated from one week to the next. They become > deprecated between PHP major version updates - e.g. from PHP 5.6 to 7. > And these changes don't happen every week and are well documented - and > not many things become deprecated at all each release: > > > Oh - and BTW: deprecation also means that a feature may get *removed* completely in the future. So it is really not helpful to just remove deprecation warnings as you need to change your code to work with future PHP versions as well. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de