[M3devel] 64-bit integer literals (v5.8.6, NT386)

[Jay K]

 >  although for some reason it tries to ship the new binaries to the same location as the old compiler, which of course fails
 
It is supposed to "wait" slightly, and then do exactly that.
I'll have to find time again...
 
 - Jay


 
Date: Fri, 16 Oct 2015 07:41:18 -0700
From: lists at darko.org
To: jcchu at acm.org
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] 64-bit integer literals (v5.8.6, NT386)

I haven't used those scripts so I have no idea why it does  that, but the work around would be to move or rename the old compiler and the use it manually to ship the new binaries.
I think there's also been some discussion regarding that issue in the mailing list in the last couple of months.
On Tue, Oct 13, 2015 at 11:43 PM, JC Chu <jcchu at acm.org> wrote:


I might have been doing it wrong.  I can actually use upgrade.py to produce a working compiler without having to “fudging” anything (except NT.common (the Quake script), since I have Visual Studio 2015, which now splits the C runtime into three parts (<https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx>)), although for some reason it tries to ship the new binaries to the same location as the old compiler, which of course fails.  Now I’m not really sure what to do from here.



— JC Chu    


_______________________________________________
M3devel mailing list
M3devel at elegosoft.com
https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20151124/6d44b85c/attachment-0001.html>