On Wed, Oct 17, 2018 at 05:16:15PM -0400, Andrew Dunstan wrote:
> On 10/17/2018 04:38 AM, Victor Wagner wrote:
> >BTW, have anyone experienced some success using Strawberry perl instead
> >of Active perl both for building postgres and as PL/Perl engine?
> >
> >Active State seems to abandon support
On 10/17/2018 05:16 PM, Andrew Dunstan wrote:
On 10/17/2018 04:38 AM, Victor Wagner wrote:
Colleagues,
Since Active State stopped to distribute perl 5.22, we decided to
upgrade installer builds to most use recent version available
(5.26.1.2601 now).
But upstream perl changes policy around
On 10/17/2018 04:38 AM, Victor Wagner wrote:
Colleagues,
Since Active State stopped to distribute perl 5.22, we decided to
upgrade installer builds to most use recent version available
(5.26.1.2601 now).
But upstream perl changes policy around this version and no longer
adds current director
On Wed, 17 Oct 2018 18:45:42 +0530
Sandeep Thakkar wrote:
> > Simple adding
> >
> > use lib ".";
> >
> > to the beginning of these script solves problem.
> >
> >
> > We observed the same issue with Strawberry Perl 5.26. We use 5.24
> > to
> execute the build.pl.
Of course. This is (mis)featu
Hi
On Wed, Oct 17, 2018 at 2:08 PM Victor Wagner wrote:
> Colleagues,
>
> Since Active State stopped to distribute perl 5.22, we decided to
> upgrade installer builds to most use recent version available
> (5.26.1.2601 now).
>
> But upstream perl changes policy around this version and no longer
>
Colleagues,
Since Active State stopped to distribute perl 5.22, we decided to
upgrade installer builds to most use recent version available
(5.26.1.2601 now).
But upstream perl changes policy around this version and no longer
adds current directory to the module search path.
This doesn't break w
