Hi Christian, Am 30.12.2014 um 12:43 schrieb Christian Svensson: > As for the assignment: > A few months later I verified the assignment status with the FSFs GNU > administration. > All the authors have successfully assigned copyright, except one whom I > have successfully reached out to but since then lost contact with. If > someone knows a Mr. M****z B**s***r and can ask him to assign copyright, > I'd be most delighted. > In any case, if anyone feels like they want to try to reach out to our > last contributor please contact we and I will supply the contact details > that I know of.
How much code are we talking about here that's missing copyright assignment? > As for the code status: > Last time I tried to run the GCC testsuites I got quite the number of > failed test cases. This may or may not be issues in everything from GCC, > glibc and even Linux. Or it might be that the testcase is stupid for > OpenRISC and should be disabled. This said, I'm not convinced that we > will get a go ahead given that we haven't got a 100% pass yet. Having > some continuous testing here would be sweet if anyone would like to set > that up - or at least some way of tracking the regressions (we used to > have this on the old wiki but I don't think it has been updated). Stefan Wallentowitz has set up Jenkins CI (http://lis.ei.tum.de/jenkins/), which is already used for the newlib port as well as some other build tests. It's probably not too hard to add the GCC test suites to it. Could you quickly describe what's needed to run the test suite? Then I'll get it set up and we have at least some progress information on how things are moving, and I'll see if I can get the test suite results into a usable form for tracking progress. > Let me know if you wonder something or want to help push this beast > forward. Thanks Christian for your work, it's very much appreciated. Philipp _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
