On Sat, 2007-08-04 at 20:10 +0100, Richard Jones wrote: > You don't need to build anything. I'll make the package (spec file, > RPM), submit it through the Fedora build system which will build on > all architectures except (currently) ppc64, and you just need to have > Fedora development around so that you can download and test the final > package for me.
I have added a bash script: bin/flx-postinstall-check that will do that for you. Options: You can specify the test command prefix like: bin/flx-postinstall-check bin/flx --test This uses the developer flx script and developer felix. The command MUST be run in the developer directory because it looks for files like this: for i in test/*/*.flx tut/*/*.flx which won't work elsewhere. It just repeats all the build tests. It also takes a while to run :) Some tests fail, eg the Windows tests will fail. The real test harness knows which things to test. Output: ============= 3 FAILURES ============= \ntest/faio/win-1.01.01-0.flx\ntest/faio/win-1.01.02-0.flx \ntut/tutorial/tut-1.48-0.flx ============ TEST SUMMARY ============ GOOD 240 BAD 3 --------- TOTAL 243 --------- I have no idea why 'echo' doesn't respect \n but that's Unix for you :) One failure is a known problem with the new C parsing. The other two are Windows only tests so they rightly fail on Linux. Still one more mod needed: all these tests use dynamic linkage, should be repeated using static linkage. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language