[M3devel] status report on Windows XP

[jay.krell at cornell.edu]

I tried python 3.x once it didn't work. I stay with 2.x for now. - 
clean often does not work, I use realclean.
I will check the test directory. You should be able to filter out  
m3cc. I might.

  - Jay (phone)

On Jul 22, 2009, at 9:06 AM, "Randy Coleburn" <rcoleburn at scires.com>  
wrote:

> Jay:
>
> I tried the python script, but it did not work for me.  I installed  
> python 2.6.2.  Should I have used 3.1?  There was a note about 3.1  
> not being compatible with some stuff.
>
> I discovered a problem in the PkgInfo.txt where the 3 juno packages  
> didn't have the path "juno-2/" prepended, so I've fixed that and  
> I've updated my local CVS copy to be current with the repository,  
> and rebuilt everything using my script, e.g. "do-cm3 all clean  
> buildship".
>
> The only packages from PkgInfo.txt that fail to build (i.e., cm3  
> exits with errorlevel  >0) on Windows now are:
> m3-sys/m3cc
> caltech-parser/parserlib/parserlib/test
>
> Interestingly, although "m3-obliq/obliqrt" builds, "cm3 -clean" on  
> that package fails.
>
> Regards,
> Randy Coleburn
>
> >>> Jay K <jay.krell at cornell.edu> 7/21/2009 6:39 PM >>>
>
> I use the Python all the time on various platforms. It works.
> The .cmds I wrote I rarely use, and then, only on Windows.
> I thought your list of failures would be down to just m3cc. What are  
> they?
>
> - Jay