This is the mail archive of the
mailing list for the Cygwin project.
RE: activestate perl on cygwin
> What does that matter? It's still short sited.
Yes, I don't disagree. Personally I do not care. I will deal with
having to port something when it happens.
> And what does #! look like?
> 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
But I think, there is some confusion here. My script will correctly execute
program using Activestate perl. 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. 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?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html