Front page | perl.perl5.porters |
Postings from October 2016
On 16 October 2016 at 23:42, Craig A. Berry <craig.a.berry@gmail.com> wrote: > On Sun, Oct 16, 2016 at 4:37 PM, Jarkko Hietaniemi <jhi@iki.fi> wrote: >> On Sunday-201610-16 17:31, Craig A. Berry wrote: >>> >>> On Sun, Oct 16, 2016 at 3:43 PM, Jarkko Hietaniemi <jhi@iki.fi> wrote: >>>> >>>> On Sunday-201610-16 16:09, Jarkko Hietaniemi wrote: >>>>> >>>>> >>>>> The >>>>> >>>>> >>>>> http://perl5.git.perl.org/perl.git/commit/d1e7b5aaf871f3bb4562cefa3ee3153d9aa9506f >>>>> looks likely culprit. >>>> >>>> >>>> >>>> >>>> http://perl5.git.perl.org/perl.git/commit/69d1f2c2cdaa4ac2f37372e8c15c679848df2252 >>>> >>>> looks possible cure. >>> >>> >>> There may still be a problem when building on Sierra but targeting >>> older versions. See >> >> >> Urk. Didn't we have some macports contacts? > > I think that would be Mojca, whom I've cc'd. > >> >>> <http://www.nntp.perl.org/group/perl.perl5.porters/2016/09/msg239768.html> >>> >>> That scenario is probably not smoke tested so could easily slip >>> through and affect macports or anybody packaging on Sierra for >>> pre-Sierra deployments. What exactly should I test? Building Perl on Sierra with an older target and then try to run it on an older OS? Which version should I test exactly? MojcaThread Previous | Thread Next