[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: perl v5.38.0 is coming
From:       Tony Cook <tony () develop-help ! com>
Date:       2023-04-10 2:56:40
Message-ID: ZDN66IrrODREmH7N () venus ! tony ! develop-help ! com
[Download RAW message or body]

On Mon, Apr 10, 2023 at 12:28:57PM +1000, sisyphus wrote:
> On Mon, Apr 10, 2023 at 12:00 PM Craig A. Berry <craig.a.berry@gmail.com>
> wrote:
> 
> >
> > The following two PRs prevent two sources of blead build failure on
> > VMS and the second one is probably also needed for nmake builds on
> > Windows, though I haven't had a chance to verify that:
> >
> > https://github.com/Perl/perl5/pull/21007
> >
> > https://github.com/Perl/perl5/pull/21008
> >
> >
> I don't think nmake is affected by the second.
> For the last 10 months, I've regularly been building perl devel  releases
> as they've become available (up to and including 5.37.10) using MSVC-143
> (VS 2022) and nmake, without issue.
> I do both 32-bit and 64-bit builds.
> 
> So, unless I've somehow evaded the troublesome perl source, I would say
> that nmake handles things just fine as it stands.

nmake appears to just treat the .PHONY directive as a target, ie. you
can do C<nmake .PHONY> to build everything listed after the ".PHONY:".

Tony
[prev in list] [next in list] [prev in thread] [next in thread]