Msys works great, but I have this nagging problem with bison that
I just cannot figure out. I see other complaints about this, and
usually it resolves to directories with blanks (Program Files).
My directories do not have blanks, and I'm unable to isolate this issue
with gdb or Windows procmon.
On 9 May 2010, at 22:59, Dick Dunbar wrote:
$ bison -d -y jamgram.y
C:\Msys\local\bin\bison.exe: cannot open file
`/usr/local/share/bison/m4sugar/m4sugar.m4': No such file or directory
$ ls -l /usr/local/share/bison/m4sugar/m4sugar.m4
-rw-r--r-- 1 dick Administrators 98348 May 8 16:19
/usr/loca
On Sun, May 9, 2010 at 3:23 PM, Hans Aberg wrote:
> On 9 May 2010, at 22:59, Dick Dunbar wrote:
>
> $ bison -d -y jamgram.y
>> C:\Msys\local\bin\bison.exe: cannot open file
>> `/usr/local/share/bison/m4sugar/m4sugar.m4': No such file or directory
>> $ ls -l /usr/local/share/bison/m4sugar/m4sugar
It's now pretty clear that bison is not going to work correctly on Msys.
Works perfectly on cygwin, so I used strace to see the flow.
Bison depends on file handler support, which appears to be built into
the "mount" support in cygwin, to translate from Windows to cygwin
style directories.
I thoug
