MicroBlaze glibc fixes

[Szabolcs Nagy]

On 05/01/17 17:11, Joseph Myers wrote:
> 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.
> 

openadk.org has microblaze setup, but i don't know
if it wants to take on the burden of glibc testing
and port maintenance.

and i know that gcc needs a patch to compile musl
correctly on microblaze, the patch is pending on
the gcc bugzilla for almost two years now
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65649

> 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.)
>