From: Andrew Dunstan <andrew@dunslane.net>
To: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Peter Eisentraut <peter@eisentraut.org>
Subject: Re: meson vs make: missing/inconsistent ENV
Date: Mon, 27 Feb 2023 08:36:12 -0500
Message-ID: <d104f128-4437-69a3-5d2a-a6bdf788d027@dunslane.net> (raw)
In-Reply-To: <f5a573f0-f453-261a-99df-16b7b395a107@dunslane.net>
References: <20230226225239.GL1653@telsasoft.com>
<20230226232104.5djexwyitlfemrhg@awork3.anarazel.de>
<20230227020029.GN1653@telsasoft.com>
<87edqbjr1i.fsf@wibble.ilmari.org>
<f5a573f0-f453-261a-99df-16b7b395a107@dunslane.net>
On 2023-02-27 Mo 07:33, Andrew Dunstan wrote:
>
>
> On 2023-02-27 Mo 06:17, Dagfinn Ilmari Mannsåker wrote:
>> Justin Pryzby<pryzby@telsasoft.com> writes:
>>
>>> On Sun, Feb 26, 2023 at 03:21:04PM -0800, Andres Freund wrote:
>>>>> Is there any consideration of promoting these or other warnings to
>>>>> fatal?
>>>> You mean the perl warnings?
>>> Yes - it'd be nice if the warnings caused an obvious failure to allow
>>> addressing the issue. I noticed the icu warning while looking at a bug
>>> in 0da243fed, and updating to add ZSTD.
>> Perl warnings can be made fatal with `use warnings FATAL =>
>> <categories>;`, but one should be careful about which categories to
>> fatalise, per<https://metacpan.org/pod/warnings#Fatal-Warnings;.
>>
>> Some categories are inherently unsafe to fatalise, as documented in
>> <https://metacpan.org/pod/strictures#CATEGORY-SELECTIONS;.
>>
>
> Yeah.
>
>
> It would be nice if there were some fuller explanation of the various
> categories, but I don't know of one.
>
>
>
Looks like the explanations are in the perldiag manual page.
<https://perldoc.perl.org/perldiag;
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, ilmari@ilmari.org, pryzby@telsasoft.com, andres@anarazel.de, peter@eisentraut.org
Subject: Re: meson vs make: missing/inconsistent ENV
In-Reply-To: <d104f128-4437-69a3-5d2a-a6bdf788d027@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox