-----Original Message-----
From: ActiveState Support [mailto:support@activestate.com]
Sent: 09 November 2012 20:53
To: Duncan Garland
Subject: Re: [OTS#020329423] Form submission from: Contact Us
Duncan,
Not SSH, but we do ship OpenSSL libraries, so many more of the SSL based
modules are now available from us for current Perls than used to be
possible.
I note there are some inventive ways to use SSL, such as:
http://code.activestate.com/ppm/Net-FTPSSL/
MinGW64 is one of the things we want to make work, but it is not the top
priority item.
And yes, Strawberry is closely coupled with Padre (Padre is Stawberry's
default IDE and Strawberry is bundled in the Padre binary installers), so
they *must* work together. Padre uses WxPerl/WxWidgets, which is also a
third-party library that can't be distributed with ActivePerl. WxPerl is
available from wxperl.co.uk in PPM form.
http://www.wxperl.co.uk/
Best regards,
Graham Stuart
Technical Support Engineer
ActiveState - Code to Cloud: Smarter, Safer, Faster.
http://www.ActiveState.com
Get insights on Open Source and Dynamic Languages at
www.activestate.com/blog
11/08/2012 13:30 - Duncan Garland wrote:
> Hi Graham,
>
> I'm not surprised that upgrading Perl broke a few modules. I am
> surpised that you have discontinued support, directly or indirectly, for
SSH.
>
> You say that you ship linked version of the SSH libraries. Why? Which
> modules are these designed to run with? I may be able to use one of those.
>
> You say that MinGW64 does not work with ActiveState Perl. Is this a
> temporary thing?
>
> I was advised to uninstall ActiveState and install Strawberry Perl.
> Apparently that does come with the correct libraries. That seems a shame.
> I've used ActiveState for over ten years now.
>
> As an aside. I was unable to install Padre either. That runs on
> Strawberry Perl, I believe.
>
> Bad couple of days really.
>
> Regards
>
> Duncan
>
>
> -----Original Message-----
> From: ActiveState Support [mailto:support@activestate.com]
> Sent: 05 November 2012 20:31
> To: duncan.garland@ntlworld.com
> Subject: Re: [OTS#020329423] Form submission from: Contact Us
>
> Duncan,
>
> You should not be surprised that moving to a new Perl breaks modules
> from an older version of Perl. This is by design. All Perl binaries
> become incompatible across any major version change, and newer Perls
> are enforcing API discipline more
> effectively:
>
http://perldoc.perl.org/5.14.0/perldelta.html#C-API-Changes
>
> Our build engineers tell me that we first built Net:SSH2 in 2010 for a
> heavily customized ActivePerl Enterprise distribution, and that it has
> never been shipped with any other products.
>
> It is most likely that you got the a pre-built version of the module
> from a non-ActiveState PPM repository. The University of Winnipeg used
> to distribute Net::SSH2, and many other related modules. They were the
> main source of all things crypt for many years during a period where
> we intentionally did not ship anything using crypt libraries in order
> to comply with Federal export regulations around encryption software.
>
> Unfortunately, the University has not been able to maintain their
> repositories after the death of Randy Kobes, and they are not up to date.
> Sergei Trouchelle has not built Net:SSH2, and neither has Bribes de Perl.
>
> As far as I am aware, the only option is using the "cpan" script to
> compile to module locally. But I have to say, this does not look
promising.
>
> Right away, I can see one very big problem in the BUILDING.Win32
> instructions- if you are wanting a 64bit version they use MinGW64, but
> MinGW64 is not working with
> ActivePerl64 yet.
>
> Even with a 32-bit version, the process is likely to be quite a bit
> worse than expected, since ActivePerl ships static linked versions of
> OpenSSL and zlib. These are probably not the same versions as
> specified in the directions, and multiple versions of zlib and OpenSSL
> can cause compatibility conflicts. Historically, dll conflicts with
> different versions of dynamically linked OpenSSL has long been a bane
> for Windows users, and would have been one of the main difficulties in
> building and keeping this module running.
>
> Best regards,
>
> Graham Stuart
> Technical Support Engineer
> ActiveState - Code to Cloud: Smarter, Safer, Faster.
>
http://www.ActiveState.com
> Get insights on Open Source and Dynamic Languages at
> www.activestate.com/blog
>
> 11/04/2012 08:10 - duncan.garland@ntlworld.com wrote:
>
> > Contact Technical Support form submission
> > -------------------------------------------------------
> > Name: Duncan Garland
> > Position: Technical Lead/Developer/Engineer
> > Company: N/A
> > Email Address: duncan.garland@ntlworld.com
> > Phone Number:
> > Product Interest: ActivePerl
> > -------------------------------------------------------
> > I upgraded to ActiveState Perl 5.16.1 yesterday.
> >
> > My copy of Net::SSH2 has stopped working.
> >
> > You no longer include this in your repositories and your records
> > show a build
> failure.
> >
> > I've spoken to the Perl maintainer who has told me that the
> > libraries are quite
> difficult to build on Windows. He provides clear instructions, but it
> apparently takes about an hour. You used to get around this by
> pre-building the module, but you have stopped.
> >
> > It seems quite bad that upgrading has caused my module to fail like
> > this. It is
> going to take quite a bit of effort to get it running again.
> >
> > Apparently Strawberry Perl still pre-builds the libraries and ships
> > with a
> working module.
> >
> >
>
>
