in reply to Re^4: Installing Perl 5.10.0: problems with ./Configure
in thread Installing Perl 5.10.0: problems with ./Configure

If the problem was DOS line endings, either you got the source from a bad place or you did something bad in extracting it. Where did you get it and what did you do to extract it?
  • Comment on Re^5: Installing Perl 5.10.0: problems with ./Configure

Replies are listed 'Best First'.
Re^6: Installing Perl 5.10.0: problems with ./Configure
by why_bird (Pilgrim) on May 08, 2008 at 07:37 UTC

    I tried two---I got one from CPAN, and I'm not sure where the other one was from. I extracted it using Winzip (I've had problems trying to extract Perl modules using tar before, so this is the method I've been using for a while). It's odd because I use the exact same method when installing Perl modules and have never had this problem or anything similar.
    I'll give tar another go and see if that solves it.

    Update: Awesome---using tar to unzip and extract seems to have fixed it :) Thanks. V strange though.
    Those are my principles. If you don't like them I have others.
    -- Groucho Marx
      I extracted it using Winzip

      With my (old) version of WinZip, you would open the WinZip GUI, then select Options->Configuration->Miscellaneous and disable the "TAR file smart CR/LF conversion".

      Not so strange. WinZip likes making text files look like they would in windows, so it adds the carriage-return. Then when you do ./Configure, the linux kernel sees "#! /bin/sh", carriage-return, line-feed, and knows the script is supposed to be processed by a program named "/bin/sh" + carriage-return (which is a legal filename character under linux), and there is no such program to be found.