On Tue, Jul 7, 2009 at 12:09 AM, Matthew Fluet <span dir="ltr"><<a href="mailto:fluet@tti-c.org">fluet@tti-c.org</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;">
This issue of paths with spaces would appear to affect all platforms, where one might install MLton at a location with spaces in the path. (MinGW is the only platform where by default the install location is a path with spaces).</blockquote>
<div><br>The problem is GNU make.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Does piping the output of mlton -stop f through sed to escape spaces suffice on MinGW? It seems to on other platforms. However, there are a number of different uses of 'mlton -stop f' in the mlton/Makefile, and it isn't quite as simple as using a Makefile function to abstract the piping through sed. An auxilary script in <src>/bin might suffice.<br>
</blockquote></div><br>Changing to:<br> $(shell if [ -r $(FILE) ]; then mlton -stop f $(FILE) | sed 's/ /\\ /'; fi)<br>did indeed work! I didn't think make supported backslash escapes. It doesn't supports "s.<br>
<div class="im">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Aren't the two platforms appearing as amd64-mingw and x86-mingw? You
should be able to add appropriate platform specific regression .ok
files for the different platforms.<br></blockquote></div>
<br>If I modify bin/platform to report amd64, the regressions run clean. The problem is that 'uname -m' reports i686 on both win32 and win64. I don't think there is a good way to tell the difference since msys/uname are 32-bit apps in both cases.<br>
<br>