bash scripts fail with bash3.1-8
mwoehlke
mwoehlke@tibco.com
Wed Oct 4 15:21:00 GMT 2006
Thomas Porschberg wrote:
> Am Tue, 3 Oct 2006 17:02:29 +0100
> schrieb "Dave Korn" :
>> On 03 October 2006 16:43, Turly O'Connor wrote:
>>> By way of an example as to what broke, note that in the following
>>> that "cleartool" is not a cygwin tool (it's a Windows executable),
>>> writing its CRLF-terminated output to Windows' stdout.
>>>
>>> CHECKOUTS=`cleartool lsc -all -cvi -s` # list all my checkouts
>>>
>>> I used to be able to do
>>>
>>> for one in $CHECKOUTS ; do echo $one Hello ; done
>>>
>>> C:/Path/To/file1 Hello
>>> C:/Path/To/file2 Hello
>>>
>>> Now it seems that "$one" above contains the binary CR, so I get:
>>>
>>> Hello h/To/file1
>>> Hello h/To/file2
>>>
>>> What do I need to do to get this working again?
>> How about
>>
>> CHECKOUTS=`cleartool lsc -all -cvi -s | d2u` # list all my checkouts
>>
>> or
>>
>> for one in $((echo $CHECKOUTS | d2u)) ; do echo $one Hello ; done
>>
>> depending on how happy cleartool is on piping output to a cygwin
>> program.
>
> This is exactly the problem I have with my sqlplus call.
> Is there a way to solve it without introducing the d2u filter ?
You could try the new shopt... but have you considered arranging for
'sqlplus' to point to a shell script that would exec 'sqlplus.exe' and
pipe it through d2u?
--
Matthew
This message will self destruct in five millennia.
--
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/
More information about the Cygwin
mailing list