http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1162
------- Comment #5 from wmeier@xxxxxxxxxxx 2006-10-16 03:51 GMT -------
As mentioned above, Cygwin Bash versions 3.1-8 and 3.1-9 have changed their
handling of \r\n in Bash sripts on Cygwin file structures mounted as 'bin' (the
recommended configuration).
The result of the change is that Wireshark Bash scripts under Cygwin may or
will fail (since normally the scripts downloaded to Windows will have \r\n as
line terminators).
(See the cygwin mailing list (http://www.cygwin.com/ml/cygwin) for lots of
detailed discussion).
V 3.1-9 implements a shell option 'igncr' which, when enabled, causes \r
characters in Bash scripts to be ignored.
It appears to me that currently a good way to allow Wireshark to build using
Cygwin Bash v3.1-9 on Windows is to define the BASH_ENV environment variable
(in Windows) specifying a file which contains the following (exactly as shown):
shopt -s igncr;#
This file will be read and executed whenever Cygwin Bash is invoked
non-interactively. (Note that this will not work on Bash v3.1-8).
Having said all of the above, it appears that a v 3.1-10 release is being
considered which may improve matters further possibly meaning that Wireshark
will again build successfully on Windows with an 'out-of-the-box' Cygwin
installation.
So: another option is just to stay with Bash v3.1-6 until the situation further
resolves itself.
Bill Meier
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.