From @jhi

Currently the C compiler warning flags are not propagated to the ext/* builds. They should be.

The flags can be grabbed from the "cflags" script generated from the "cflags.SH". (If there's no such script at the top level, the UNIXy build process was probably not involved, and never mind.)

(Though, in Win32, there are probably some VC warning flags we could deploy. The more compilers the merrier.)

I tried looking at make_ext.pl and EU​::MM but for some reason got this hammering migraine.

(Possibly also include dist/*, since the core "half-controls" those)

(If we get crazy enough, also cpan/*, to raise the robustness level of at least those CPAN modules that have been deemed important enough to be in the core)

From @Leont

On Wed, Sep 3, 2014 at 4​:46 PM, Jarkko Hietaniemi <perlbug-followup@​perl.org

wrote​:

Currently the C compiler warning flags are not propagated to the ext/*
builds. They should be.

The flags can be grabbed from the "cflags" script generated from the
"cflags.SH". (If there's no such script at the top level, the UNIXy build
process was probably not involved, and never mind.)

(Though, in Win32, there are probably some VC warning flags we could
deploy. The more compilers the merrier.)

I tried looking at make_ext.pl and EU​::MM but for some reason got this
hammering migraine.

(Possibly also include dist/*, since the core "half-controls" those)

(If we get crazy enough, also cpan/*, to raise the robustness level of at
least those CPAN modules that have been deemed important enough to be in
the core)

I would guess the obvious way to do this is to add a %Config option with
those arguments, and a MakeMaker option to add them to the compile commands.

Leon

The RT System itself - Status changed from 'new' to 'open'

From @jhi

On Wednesday-201409-03, 19​:15, Leon Timmermans wrote​:

I would guess the obvious way to do this is to add a %Config option with
those arguments, and a MakeMaker option to add them to the compile commands.

Not so obvious because currently those warning options are selected
completely outside (or after) Configure.

From @greerga

On Wed, 3 Sep 2014, Jarkko Hietaniemi wrote​:

# New Ticket Created by Jarkko Hietaniemi
# Please include the string​: [perl #122694]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=122694 >

Currently the C compiler warning flags are not propagated to the ext/* builds. They should be.

The flags can be grabbed from the "cflags" script generated from the "cflags.SH". (If there's no such script at the top level, the UNIXy build process was probably not involved, and never mind.)

(Though, in Win32, there are probably some VC warning flags we could deploy. The more compilers the merrier.)

I tried looking at make_ext.pl and EU​::MM but for some reason got this hammering migraine.

(Possibly also include dist/*, since the core "half-controls" those)

(If we get crazy enough, also cpan/*, to raise the robustness level of at least those CPAN modules that have been deemed important enough to be in the core)

Doing "cpan/*" with at least enforcing C89 variable declarations might
have prevented the Scalar-List-Utils update from failing on Win32, so that
would be a good first step.

--
George Greer

From @jhi

(If we get crazy enough, also cpan/*, to raise the robustness level of at

least those CPAN modules that have been deemed important enough to be in
the core)

I would guess the obvious way to do this is to add a %Config option with
those arguments, and a MakeMaker option to add them to the compile commands.

http​://perl5.git.perl.org/perl.git/commit/2313e9ca3be65223d835c40b25c76765e8c35547

now grabs the extra flags during configpm and propagates them as
$Config{ccwarnflags} and $Config{ccstdflags}.

Now how do we get them used by MM, say, if PERL_CORE=1?