[PATCH] [RSB] use updated newlib revision for or1k

[Joel Sherrill]

On Apr 10, 2016 7:11 PM, "Hesham Almatary" <heshamelmatary at gmail.com> wrote:
>
> This is the patch. It would conflict with Joel's [PATCH 3/5]
4.12/rtems-or1k.bset: Update newlib to 2.4.0, so we can choose either
according to the current RSB convention (releases or git revisions).

The ports need to get to newlib 2.4.0. If I don't merge my patch, can you
bump the newlib version in yours?

I am holding a few pthread patches that need the updated newlib.

> On Wed, Mar 30, 2016 at 4:48 PM Stefan Wallentowitz <
stefan at wallentowitz.de> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 30.03.2016 07:29, Sebastian Huber wrote:
>> >
>> >
>> > On 30/03/16 07:26, Stefan Wallentowitz wrote:
>> >> there is also a GCC-6 snapshot available:
>> >> https://github.com/openrisc/newlib/releases/tag/gcc6-preview
>> >>
>> >> This was the GCC version used in the other architectures last
>> >> week, so maybe it makes sense to bump to this GCC version, too.
>> >
>> > Are there any plans to integrate the or1k stuff into the FSF GCC?
>> >
>>
>> Hi Sebastian,
>>
>> this is unfortunately not possible due to one missing FSF copyright
>> assignment of the original author. We have repeatedly tried to
>> convince him or find a proper workaround, but do not have a solution.
>> But we are keeping up with upstream GCC pretty fast currently.
>>
>> If you accidentally know somehow who would be interested to rewrite
>> the GCC port from scratch..
>>
>> Cheers,
>> Stefan
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>>
>> iEYEARECAAYFAlb7aKkACgkQuMYtsrn2U9wbjgCffW0gkH6MDa2T/SnwGGFkXLWe
>> s9oAnAyqPfD8jNiXSdDsfOZW3QIn2anE
>> =BBl7
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160410/370c1cc0/attachment-0002.html>