This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, I am hoping that someone can explain this change of behavior I have noticed that occurred between Cygwin version 1.3.18-1 and 1.3.19-1. In order to remain compatible with MKS, and also to keep version control as simple as possible we need to continue using ksh to execute our scripts. On Cygwin we have been using the pdksh ( http://www.cs.mun.ca/~michael/pdksh/ ). Here is a sample script: --- #!/bin/ksh set +u --- Using Cygwin 1.3.18-1, the script can be executed, apparently successfully, like so: $ d:/cygcheck/testscript Using Cygwin 1.3.19-1 and executing the script in the same manner yields the following error message: $ d:/cygcheck/testscript :unknown optionscript[2]: set: - I have attached 'cygcheck -s -v -r' output for both version 1.3.18 and .19 as setup on my computer. Thanks, Paul Coltrin pablo (at) projtech (dot) com
Attachment:
cygcheck19out.txt
Description: Text document
Attachment:
cygcheck18out.txt
Description: Text document
-- 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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |