<div dir="ltr"><br> </div><div dir="ltr">Hi Julien, <br> </div><div dir="ltr"><br> </div><div dir="ltr">Do you use the msys environment or the msys2 environment? I experienced some problems when running inside the bash shell and using the Mercury msys environment, it seemed fine when using native 64 Windows cmd.exe and the Windows environment configured, I'll try to reproduce this when I've access to my build machine again <br> </div><div dir="ltr"><br> </div><div dir="ltr">Cheers Sebastian. <br> </div><div dir="ltr"><br> </div><div dir="ltr"><br> </div><div dir="ltr"><br> </div><div class="wps_signature"></div><div class="wps_quotion">On May 23, 2016 1:41 PM, Julien Fischer <jfischer@opturion.com> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style></head> <body> <div class="PlainText"><br> Hi,<br> <br> On Mon, 23 May 2016, Paul Bone wrote:<br> <br> > On Fri, May 20, 2016 at 12:03:14PM +1000, Julien Fischer wrote:<br> >> Hi,<br> >><br> >> The recent changes to the creation of temporary files do not appear<br> >> to work on Windows (MinGW64). In particular, when the Mercury compiler<br> >> attempts to create a temporary file during linking we now get:<br> >><br> >> Could not create temporary file: error opening temporary file: Invalid<br> >> argument<br> >><br> >> This with rotd-2016-05-17.<br> >><br> ><br> > I've been working on this code some more, I'd like to wait until I post the<br> > changes I'm working on and then re-test.<br> <br> I've fixed one bug in your previous change and also added a workaround<br> for the fact that mkstemp doesn't work properly with (some versions<br> of?) MinGW64.<br> <br> I'm a bit concerned because I don't seem to be able to bootstrap recent<br> compilers on MinGW64 / MSYS2 at the moment -- the mmc up-to-date test in<br> configure keeps failing due to something going wrong when the Mercury<br> compiler attempts to link an executable. (Specifically, creating<br> an archive to hold the object files to pass to ar when compiling<br> with --restricted-commmand line isn't working for some reason.)<br> <br> I don't think this is related to your / Paul's change, since it occurs<br> with rotd-2016-03-04. It works with rotd-2015-10-20 on the same<br> machine.<br> <br> Has anyone else been encountering problems with MinGW64?<br> <br> Julien.<br> _______________________________________________<br> developers mailing list<br> developers@lists.mercurylang.org<br> <a href="https://lists.mercurylang.org/listinfo/developers">https://lists.mercurylang.org/listinfo/developers</a><br> </div> </body> </html> </blockquote></div>