in reply to Re^2: Disappointed with latest Strawberry Perl
in thread Disappointed with latest Strawberry Perl

Added a few remarks to the RT queue

(Strawberry Perl)++ ! Getting further and further. I also suggest to (sym)link/copy dmake to nmake and make and bundle Tk, as it cannot be installed with cpan, as make requires the extra argument "MSWin32" to succeed.


Enjoy, Have FUN! H.Merijn
  • Comment on Re^3: Disappointed with latest Strawberry Perl

Replies are listed 'Best First'.
Re^4: Disappointed with latest Strawberry Perl (dmake ne nmake)
by tye (Sage) on Dec 30, 2007 at 16:19 UTC

    Please don't link/copy dmake to nmake. Just because I install Strawberry Perl doesn't mean I don't have other Perls or other things that use nmake. It seems a very bad idea to potentially break things that actually want/need nmake in a way that will likely be quite confusing to diagnose.

    - tye        

      Linking would be no trouble for you either, as for the other perl's, you'd have the path to make and nmake in a part of your $PATH that corresponds to the perl you are working with. As said, I now have 5 different perls happily living side by side in thre different environments.


      Enjoy, Have FUN! H.Merijn

        I don't understand your explanation. But it could certainly cause a problem for me. I currently have Strawberry Perl first in $PATH and when I want to build a module for non-strawberry Perl, I run "bperl Makefile.PL; nmake ...". That would fail if Strawberry Perl had installed a non-nmake program as "nmake".

        And the proposed solution sounds like the wrong way to go anyway. If Tk is using the wrong "make", then Tk should be patched to ask Perl which make to use. Making "nmake" mean "either nmake or some other make, depending on which order things are in $PATH" just makes things more confusing.

        - tye        

Re^4: Disappointed with latest Strawberry Perl
by eserte (Deacon) on Dec 30, 2007 at 09:59 UTC
    What's wrong with Tk? I think it should build fine with Strawberry Perl, at least there's one PASS at cpan testers.

      Nothing is wrong with Tk :) It just needs an extra argument on the initial Makefile.PL command line.

      I just finished my complete list of modules, or more precicely the ones that PASS'd. The part I miss most is libexpat, so I cannot install any XML stuff. Maybe OpenSSL is second. Here's the list of PASS's and Failures, more specific output on request:

      Module Version ==================================== ========== V 0.13 Test::Pod 1.26 IO::Compress::Base 2.008 Compress::Raw::Bzip2 2.008 Compress::Raw::Zlib 2.008 IO::Compress::Bzip2 2.008 IO::Compress::Zlib * FAIL * Compress::LZF 3.1 IO::Compress::Lzf 2.008 Compress::Bzip2 2.09 IO::String 1.08 Archive::Zip 1.23 Heap 0.80 Graph 0.84 List::MoreUtils 0.21 Devel::Size 0.69 Devel::Trace 0.10 Debug::Trace 0.04 Sub::Uplevel 0.18 Test::Exception 0.26 Carp::Clan 5.9 Bit::Vector 6.4 Date::Calc 5.4 Date::Manip 5.48 Text::CSV_XS 0.32 DBI 1.601 SQL::Statement 1.15 DBD::SQLite 1.14 DBD::CSV 0.22 DBD::File 0.35 Digest::SHA1 2.11 Number::Compare 0.01 Text::Glob 0.08 File::Find::Rule 0.30 Data::Compare 0.17 CPAN::Checksums 1.064 Parse::RecDescent 1.94 Crypt::SSLeay * FAIL * Crypt::Rot13 * FAIL * Convert::ASN1 0.21 Convert::IBM390 0.23 Net::Rexec 0.12 Crypt::Rijndael 1.05 Crypt::CBC 2.24 Crypt::Blowfish 2.10 Crypt::DES 2.05 Digest::HMAC 1.01 Net::SNMP * FAIL * URI 1.35 HTML::Tagset 3.10 HTML::Parser 3.56 HTML-Tree * FAIL * XML::Parser * FAIL * XML::Writer 0.603 XML::XPath * FAIL * XML::SAX::Base 1.04 XML::Twig * FAIL * LWP 5.808 Net::SSLeay * FAIL * IO::Socket::SSL * FAIL * Authen::SASL 2.10 Net::NTP * FAIL * HTTP::Proxy * FAIL * News::NNTPClient 0.37 Text::Metaphone * FAIL * Text-Format+NWrap * FAIL * Text::OutputFilter 0.12 Tk 804.028 Tk::Clock 0.21 Tk::TreeGraph 1.030 Tk::TableMatrix * FAIL * Tk::FontDialog 0.14 Devel::ptkdb 1.1091 Term::Size * FAIL * Mail::Sendmail 0.79 Net::LDAP 0.34 Unix::Processors 2.034 BSD::Resource * FAIL * Devel::Symdump 2.08 YAML 0.66 Pod::Coverage 0.19 Test::Pod::Coverage 1.08 SOAP::Lite * FAIL * IO::Tee 0.64 OLE::Storage_Lite 0.15 Image::Base 1.07 Image::Xbm 1.08 Image::Xpm 1.09 Image::Size 3.1 Image::Info 1.27 Image::ExifTool 7.00 Spreadsheet::WriteExcel 2.20 Spreadsheet::ParseExcel 0.32 Spreadsheet::ReadSXC * FAIL * Spreadsheet::Read * FAIL * OpenOffice::OODoc * FAIL * OpenOffice::OOBuilder * FAIL * RTF::Tokenizer 1.10 RTF::Parser 1.09 RTF::Writer 1.11 Regexp::Common 2.120 Perl::Tidy 20071205 VCS::SCCS 0.10

      Enjoy, Have FUN! H.Merijn
        Nothing is wrong with Tk :) It just needs an extra argument on the initial Makefile.PL command line.

        Maybe that could be addressed with CPAN.pm's new support for "distroprefs". That should be able to automatically add the necessary keyword on Win32.

        The part I miss most is libexpat, so I cannot install any XML stuff. Maybe OpenSSL is second.

        I agree. Alias and I disagree about the extent of bundling things. I'd just as soon throw in a kitchen sink of libraries (e.g. most of the libraries in GnuWin32) but he prefers a more spare distribution. Once the new tools are documented, I may take a swing at a more full-featured distribution and we can let users decide.

        In the meantime, there are some ways to get expat, etc. support working:

        I have also downloaded and compiled OpenSSL in C:\OpenSSL. As I recall, Net::SSLeay found it there but failed some tests (apparently unrelated to the library itself). I forced the install and was able to go on to install and use IO::Socket::SSL, etc. So it takes a bit of work, but can be made to work with Strawberry if you're not afraid of the compiler.

        -xdg

        Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

        The part I miss most is libexpat, so I cannot install any XML stuff.

        These are the sorts of reasons that support the inclusion of PPM in Strawberry Perl. The expat library is certainly buildable on Windows (and xdg has provided some links on that), but not everyone wants to go to that much trouble - and PPM caters beautifully to those that *don't* enjoy going to that much trouble. PPM also makes available the openssl-based modules without having to build openssl. And, if Tk, is posing a problem - then just ppm install it. (I don't think I'd like to see Tk ship as standard with Strawberry Perl - that really would be bloat.)

        Cheers,
        Rob
Re^4: Disappointed with latest Strawberry Perl
by adamk (Chaplain) on Jan 03, 2008 at 00:17 UTC
    Lack of platform-detection sounds like a bug in the Tk Makefile.PL. It's not any concern of Strawberry's
      Tk builds fine on Strawberry. It must be another problem, maybe a broken PATH or so.
        No, I mean the decision to require an explicit MSWin32 flag be passed to Makefile.PL is not compatible with the CPAN.

        Thus, a bug in the packaging of Tk.