[M3devel] status report on Windows XP

[Randy Coleburn]

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

CONFIDENTIALITY NOTICE:  This email and any attachments are intended solely for the use of the named recipient(s). This e-mail may contain confidential and/or proprietary information of Scientific Research Corporation.  If you are not a named recipient, you are prohibited from making any use of the information in the email and attachments.  If you believe you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts of the email or attachments.

EXPORT COMPLIANCE NOTICE:  This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR).  Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require export authorization by the appropriate U.S. Government agency prior to export or transfer.  In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization.  By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090722/5c212bf9/attachment-0002.html>