This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: MicroBlaze glibc fixes
On Thu, 5 Jan 2017, Michael Eager wrote:
> Hi Joseph --
>
> I don't have a MicroBlaze Linux installation. I can't comment on
> the failures you encountered.
Is there anyone who does have such an installation and can run the full
glibc testsuite (both compilation and execution tests - either native or
cross testing is fine) during the freeze period each release cycle, report
the results on that release's wiki page and hopefully fix any obvious
breakage shown in the results? If not, we should consider obsoleting the
port.
There have been suggestions of expecting ports to have a buildbot testing
each commit, but in the absence of such a requirement, I think someone
reporting results during the freeze each release cycle (for a
representative configuration or configurations of the port, not
necessarily every variant) and making sure it's not too badly broken
should be the minimum expected for a port.
(m68k / sh / sparc / tilepro don't have results reported regularly for
each release cycle either, but are still in a better shape in that regard
than MicroBlaze.)
--
Joseph S. Myers
joseph@codesourcery.com