ANN: microblaze-rtems4.11 toolchain

[Gedare Bloom]

I disagree with pushing out toolchains for unsupported/uncommitted
architectures. It sends the message that we will provide/have support
for targets that we do not. I should think that anyone working on a
port they ought to be able to manage their own toolchains until they
release it publicly.

-Gedare

On Thu, Apr 19, 2012 at 9:29 AM, Ralf Corsepius
<ralf.corsepius at rtems.org> wrote:
> Hi,
>
> By public demand, I have added a microblaze-rtems4.11 to the toolchains I am
> building for RTEMS.
>
> The corresponding patches are integrated into the latest rtems-4.11
> toolchain patches, which can either be found in
> rtems-4.11-branch in git://git.rtems.org/data/git/cross-rpms.git
> or in
> ftp://ftp.rtems.org/pub/rtems/SOURCES/4.11
>
> For now, this toolchain is just a "first, experimental stab", which "just
> builds", but has not seen any actual testing yet and is meant to be
> convenience to prospective users.
>
> Any feedback welcome.
>
> Ralf
>
> P.S.: I don't mean to threaten anybody, but as I don't have any use for this
> target myself, I would not have many problems in removing this toolchain
> again, shouldn't we see an RTEMS microblaze port inside of the sourcetree in
> "not too distant future" ;)
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users