All, I have branched main 4.1 fixes to 4.1.2 and the doc 4.1 fixes to 4.1.2.
https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/branches/4.1.2/trunk and https://oorexx.svn.sourceforge.net/svnroot/oorexx/docs/branches/4.1.2/trunk I have added the beta folders to SourceForge: https://sourceforge.net/projects/oorexx/files/oorexx/4.1.2%20%28beta%29/ and https://sourceforge.net/projects/oorexx/files/oorexx-docs/4.1.2%20%28beta%29/ The docs are built and uploaded to SourceForge. The Windows installers, a 32-bit ubuntu deb installer, a 64-bit fedora rpm, and the source packages are uploaded. Note: To run the test suite for ooRexx 4.1.2 you should check out this branch of the suite: https://oorexx.svn.sourceforge.net/svnroot/oorexx/test/branches/4.1.2 I've run the test suite with no errors on all the systems I built on. I added some logs to the historic logs section in trunk of the test suite. You can check them out to take a look at them from this URL: https://oorexx.svn.sourceforge.net/svnroot/oorexx/test/trunk/historic.logs or use svn browse in the code section on SourceForge. I plan on sending out the beta announcement a little later this evening. Note: I had trouble building the external API test binaries on Ubuntu with a recent version of gcc. I committed some changes to Makefile.linux to the 4.1.2 test suite. If you are trying to build the test binaries and have problems, you could post here. -- Mark Miesfeld ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
