[M3devel] problems rebuilding on Win XP

[Jay K]

  > is there some minimalist binary distribution I can download, install, and use  
 

I used one of these:
http://www.opencm3.net/uploaded-archives/cm3-all-x86-pre5.8.5-VC80.msi    
http://www.opencm3.net/uploaded-archives/cm3-all-x86-pre5.8.5-VC90.msi    

but any of these ought to work:
 http://www.opencm3.net/uploaded-archives/cm3-min-x86-pre5.8.5-*.zip     
   * any of VC20 VC40 VC41 VC42 VC50 VC60 VC70 VC80 VC90  

   VC80 vs. VC90 shouldn't need to match what you are using,  
   it is just what they were built with.  
    Some of them depend on the "VC redist", which you likely already have.  


   and upgrade.py   


   You'll need the fix in FSWin32.m3.   


 I'll try to test some of these this week, 
   and 1) upload updated archives  
   and 2) try the C backend to target AMD64_NT! That was one of the goals of the C backend -- new targets, w/o gcc backend.


  "NT386" is probably still supported, but I'd really like to someday get rid of:  
  NT386, SOLsun, SOLgnu, LINUXLIBC6, FreeBSD4.  


  For years we have had: I386_NT, SPARC_SOLARIS, I386_LINUX, I386_FREEBSD.   


With the C backend, even these names will have less significance, as the backend output
is nearly the same across many targets, and hopefully will become more common in time.


 - Jay




From: rcolebur at SCIRES.COM
To: m3devel at elegosoft.com
Date: Sun, 25 Aug 2013 22:59:19 +0000
Subject: [M3devel] problems rebuilding on Win XP









I’m having all sorts of problems rebuilding cm3 on WinXP.
 
I have an old WinXP laptop on which I had a working cm3 system circa 2008.
I decided to update to the last sources, so I used CVS to update my sandbox from the HEAD branch.
Then, I began the rebuild process.
Stage 1 of the rebuild went ok, then when I got to stage 2, I ran into a problem with a compile error in “cm3/m3-libs/libm3/src/os/WIN32/SocketWin32.m3” that I repaired with Jay’s help.
Now going back thru the rebuild again, the compilation failed in stage 1 (even though it had worked previously).
 
Figuring that I’d somehow messed up everything, I saved off my bin, pkg, lib folders and replaced them with an old backup of a working system.
Now, I run into all kinds of problems with the system trying to find stuff in “I386_NT” folders instead of “NT386”.
I tried renaming all the NT386 folders to I386_NT, but that didn’t help (seems that internally something still wants the NT386).
So, I modify cm3.cfg to force use of NT386, so I can make progress again, but now I’m getting all kinds of compilation errors.
 
Given my predicament, is there some minimalist binary distribution I can download, install, and use to rebuild everything in my sandbox afresh on 32-bit Windows XP ?  (BTW, this system uses Visual Studio 2008 for the linker and other Microsoft
 tools.)
 
Has there been a definite plan to change the naming of “NT386” to “I386_NT” ?
 
Once I get the 32-bit XP working, I’m going to want to build everything on Windows 7 (64-bit), so any thoughts in advance on how to best succeed in that endeavor are also appreciated.
 
Thanks,
Randy Coleburn
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130827/f2b71c07/attachment-0002.html>