Re: sparc64 most important tasks
> Feel free to take this part over:
>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902635
Umm, ok. That's pushing it a bit.
Where is that fix you mentioned in your last message, and what needs to be
done to get it working? Or, are you going to finish this before your vacation?
Also, AFAIK there is no common debports-sparc64 group on Salsa where I have
commit access and I'm not a DD, so if this is on a random repository the best
I can do is submitting MRs and contacting the maintainers.
> I am going to be on vacation from Monday, so any help is appreciated.
>
> Also, while the workaround fixes most issues, there are still a handful of
> tests failing. Maybe you could look into that?
I can look into it, but as said, the Ultra 10 is not a very powerful machine
and building large packages takes long time, so debugging is very inefficient.
>> In any case, I understand that they want to avoid bit rot, but removing
>> coff and a.out is pushing it a bit. Any chance that it gets restored?
>
> No idea.
>> loading ELF binaries, but I have no clue about sun4u. Maybe I could try
>> this on my Ultra 10, or have you verified that it really doesn't work?
>
> That might be the case. But we officially support all UltraSPARCs, so
> switching to ELF format is a no-go.
Understandable; but since the Debian port is only supporting sparc64 for now,
it might actually be possible that sparc64's already support ELF.
I'll try to ask around, maybe I'll actually find out if this issue has come up
before on other OS's.
>> Further down, someone suggested switching to elftoaout - does that tool
>> still exist? Do we need to package it?
>
> It's part of sparc-utils that is currently in the unreleased repositories.
>
> And now that you mention it, I remember that SILO actually uses it in its
> build process.
>
> GRUB upstream mentioned they could do the same. Maybe you can make a
> suggestion there.
Ok. I'll contact them and ask if this is a good way to move forward.
Why is it in unreleased? Because of bugs, or because it's only available on a
ports architecture?
Reply to: