This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Slightly different interpretation of $PATH between Bash and Perl
- To: Peter Buckley <peter dot buckley at cportcorp dot com>, "Karr, David" <david dot karr at cacheflow dot com>, cygwin at cygwin dot com
- Subject: Re: Slightly different interpretation of $PATH between Bash and Perl
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- Date: Thu, 27 Sep 2001 09:30:50 -0400
- References: <2C08D4EECBDED41184BB00D0B74733420473F0CD@cf-bay-exch-03.cacheflow.com>
At 09:11 AM 9/27/2001, Peter Buckley wrote:
>I don't remember if it is recommended, but I have heard people say that
>you can make a copy of bash.exe and rename it to sh.exe and delete or
>rename the old sh.exe so perl and make will use bash instead of ash.
It's not recommended to replace sh.exe (ash) with bash.exe. The main
reason is that bash is slower than ash, which is important for configures.
Also, anyone who does replace sh.exe with bash.exe will see it changed back
to ash when upgrading via setup. A better solution might be to invoke
bash in the system() call for perl if bash is what's required for the
script. Another alternative is to modify the script to be ash (i.e.
Bourne shell) compatible.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/