http://qs1969.pair.com?node_id=685245


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

Ah, lovely, thankyou---I didn't know what the 'DOS style line break' character was in perl. I've already got Perl 5.8.5. I tried to install 5.10.0 back when I started to learn Perl but gave up pretty quickly when I thought I'd need root permissions. I thought it'd be good to have a play around with it now that I'm a bit more experienced.

thanks!
........
Those are my principles. If you don't like them I have others.
-- Groucho Marx
.......
  • Comment on Re^4: Installing Perl 5.10.0: problems with ./Configure

Replies are listed 'Best First'.
Re^5: Installing Perl 5.10.0: problems with ./Configure
by ysth (Canon) on May 08, 2008 at 05:07 UTC
    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?

      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".

        Cheers,
        Rob
        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.