Point release to fix OpenRISC

Olof Kindgren olof.kindgren@gmail.com
Sun Jan 18 06:42:00 GMT 2015

On Sat, Jan 17, 2015 at 5:57 PM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
> On January 17, 2015 8:37:29 AM CST, Olof Kindgren <olof.kindgren@gmail.com> wrote:
>>Hi people,
>>I'm part of the OpenRISC community and was very happy to see the
>>OpenRISC support being added for newlib 2.2.0. Unfortunately a few
>>patches came in after the release, with the result that the OpenRISC
>>target in newlib 2.2.0 doesn't work at all.
>>Would there be any interest in releasing a 2.2.1 now that all
>>OpenRISC-related patches are applied? I haven't found any release
>>policies, but noticed that new minor versions are released
>>approximately once a year.
> Since the version was accidentally not updated, this would be a good idea.

Cool. Let's kill two birds with one stone then :)

> What version of GCC works with this? I tried the or1k-gcc repo this week and it wouldn't build. I would like to find the most recent GCC that works for RTEMS.

That's strange. I have successuflly built it on both a 32- and a
64-bit machine this week. I've been using rev
1ee8ef4190f85934479fa00abbc29e164af80f00 (which has been head of the
or1k branch since late november), and the build instructions outlined
here (http://wallento.github.io/newlib/). If you have some logs, I
would be happy to take a look

> Any luck on wrapping up the submission process on that?

No news regarding that unfortunately, but in the meantime one of the
other OpenRISCers is busy hunting down the last of the GCC regression
suite errors.

>>Best Regards,
> --joel


More information about the Newlib mailing list