X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Changing HOME for PERL Date: Thu, 27 Aug 2009 10:37:53 -0400 Message-ID: In-Reply-To: <4A9697B2.6050101@bopp.net> References: <4A959537 DOT 7020900 AT bopp DOT net> <4A95AA6A DOT 9010909 AT bopp DOT net> <4A9697B2 DOT 6050101 AT bopp DOT net> From: To: , X-EMM-EM: Active X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com OK as you and Larry kindly suggest I will go back to basics and re-look at the problem report. Please know that I did read the Cygwin site carefully before submitting so as to not upset and to also respect the folks out here. Before I go and end this thread can you tell me if the Perl.exe I have in Cygwin looks correct? I can cd /usr/bin=20 and the Perl there is: dextem AT USENDEXTEML1C /usr/bin $ ls -la Perl.exe -rwxrwxrw-+ 1 dextem mkgroup-l-d 34304 Jul 19 2007 Perl.exe I am not seeing the 'x' for execute however and maybe this is the issue? Thank you, Mike -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Jeremy Bopp Sent: Thursday, August 27, 2009 10:27 AM To: cygwin AT cygwin DOT com Subject: Re: Changing HOME for PERL Dexter_Michael AT emc DOT com wrote: > Also the command od -c test1-mike.pl, shows \n ONLY throughout the file > excepts a couple sots near the end of the file. Do I need to worry > about those couple spots \n\n doubles appears. No, you don't need to worry about \n\n sequences. They just indicate that you have empty lines in the file. Try removing one of the empty lines and see out the od -c output changes. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > dextem AT USENDEXTEML1C ~/PERL > $ od -c test1-mike.pl > 0000000 # ! / u s r / b i n / p e r l \n > 0000020 \n $ x =3D 3 ; \n $ c =3D " h > 0000040 e " ; \n $ s =3D $ c x $ > 0000060 x ; \n $ b =3D " b y e " ; \n p > 0000100 r i n t " $ s \ n " ; > 0000120 # h e h e h e \n p > 0000140 r i n t $ s . " \ n " ; > 0000160 # h e h e h e \n \n > 0000200 $ a =3D $ s . $ b ; \n p r > 0000220 i n t $ a ; > 0000240 # h e h e h e b y > 0000260 e \n \n > 0000263 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D >=20 > Now when I run the file I am getting same error without the ^M >=20 > dextem AT USENDEXTEML1C ~/PERL > $ ./test1-mike.pl > bash: ./test1-mike.pl: /usr/bin/perl: bad interpreter: Permission denied I went ahead and recreated your script based on your od -c output, but as expected, I can't recreate your problem without purposely breaking my Cygwin installation. Only by removing all execute permissions from my Perl program at /usr/bin/perl am I able to get the error you receive. Now I just took a closer look at what you did earlier to work around this problem when you changed the SheBang line to: #!/cygdrive/c/PERL/BIN/perl What you have done by making this change is direct Cygwin to run what is most likely a Windows-native Perl installation installed into C:\PERL in order to interpret your script. Since this change works for you, this Perl installation is obviously good; however, this is *not* the Perl installation under Cygwin. Since your Cygwin-based Perl installation seems to be lacking some necessary permissions, it appears that there is something wrong with your Cygwin installation. Following the problem reporting guidelines (http://cygwin.com/problems.html) will provide more information which will hopefully help the Cygwin maintainers identify the cause of the issue. Good luck. -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple