<div dir="ltr">On Fri, Sep 5, 2008 at 4:16 PM, John Reppy <span dir="ltr"><<a href="mailto:t-johrep@microsoft.com">t-johrep@microsoft.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Unix doesn't have an EOF character (and I did an od to check that there<br>
wasn't anything funny at the end of the file; just a newline). Regular<br>
sml files created with a Unix editor (vi) go through MLton w/o problems.<br>
<br>
The problem appears to be related to my pathmap, which is pretty simple:<br>
<br>
$ cat /c/Users/t-johrep/Work/sml3d/src/sml3d-path-map<br>
SMLXD_LIB /c/Users/t-johrep/Work/sml3d/src<br>
<br>
If I remove references to $(SMLXD_LIB) from my mlb file, then I don't get<br>
the parse error anymore.<br>
</blockquote></div><br>You realize that the path "/c/foo/..." is a fiction? MLton is a native windows program and expects paths like c:\foo\bar. When you run something from the msys command line, it automatically translates /c/foo/bar into c:\foo\bar. c:/foo/bar will work too, though.<br>
<br>Looking over the relevant code, I see (yet another) bug to do with spaces in path names. So don't use c:/My Documents/foo in the mlb file either.<br><br></div>