X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: activestate perl on cygwin Date: Fri, 12 Jan 2007 19:30:45 -0600 Lines: 35 Message-ID: References: <000301c733a2$28c29db0$7a47d910$@rr.com> <006901c73528$574b11d0$05e13570$@rr.com> <009701c7357f$4b05f9b0$e111ed10$@rr.com> <00af01c735f2$43713980$ca53ac80$@rr.com> <00d701c73646$7d628e10$7827aa30$@rr.com> <00e301c736a6$a66de740$f349b5c0$@rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: <00e301c736a6$a66de740$f349b5c0$@rr.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Kevin T Cella wrote: >> And what does #! look like? > #! /usr/bin/perl Is there something that the space after the "!" and before the "/" buys you? So your specifically saying by your shebang line - execute Cygwin's perl. >> what does ls portion after #! in your script return? > Before the conversion using cygpath, it returns the same as in the > error: /home/kcella/bin/myscript.pl So then you are saying that you have no /usr/bin/perl? Is so then why do you put "#! /usr/bin/perl" in your script at all? > But I think, there is some confusion here. My script will correctly > execute the program using Activestate perl. So now you are saying that you have no problem?!? > The example I gave is for when I have no wrapper script and just > create a symlink in /usr/bin/perl that points to /c/Perl/bin/perl.exe. Huh? There is no /c/... although I've heard of a way to do that I've also heard that it's not supported. Futher, why would you want to symlink /usr/bin/perl -> /c/Perl/bin/perl.exe?!? Or, since you insist on using ActiveState, then why not specifically specify something like #!C:/Perl/bin/perl.exe or something like that? > The root cause of the example is the reason for the initial post. The > wrapper script was the solution I happened to choose to get around the > path problem, but quickly found out that it does not work properly > with: perl -e 'print join "\n", @INC, "\n";' >> Oh and what is PATH set to? > /home/kcella/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Perl/bin/:/c > /WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem You could probably also simply use #!perl since C:/Perl/bin is in your path... -- Andrew DeFaria Anything worth fighting for is worth fighting dirty for. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/