Re: sparc32 and sparc64-only packages
On Wed, Jul 12, 2006 at 07:37:45PM -0700, Jurij Smakov wrote:
> >As xine comaintainer I'm interested if I should disable special vis
> >optimisations in the xine-lib source package sacrificing performance on
> >ultrasparc machines for the sake of older SPARCstations. This was not
> >meant as offence for SPARCstation users (and I don't have much clue
> >about sparc anyway), I rather want to find a good solutions for our
> >users.
> >
> >An other option would be to create a 'special' libxine1-vis package,
> >which has libxine recompiled with optimised libraries.
>
> That would be and ideal solution, however I'm not sure whether it is
> easily achievable. From a cursory look at the source of the component
> containing the sparc64-specific assembler I got an impression that it just
> does not ship any generic unoptimized code. I would be glad to be proven
> wrong on that, but to me it looked like making it work on sparc32 required
> a significant effort.
I meant to compile whole xine twice on sparc, like marillat does with
the mplayer packages. (yes, this is a ridiculous waste of cpu time on
the sparc buildds, and I'd rather avoid this).
> >If the decision is that it is okay to include vis depending code for
> >ffmpeg and related packages, then I think we should have this documented
> >in the Developers Reference, if not, in Debian Policy.
>
> I don't think it's such a big deal, but at the moment it's up to release
> team to decide whether such packages are considered RC-buggy.
Last time I asked on irc, I was said that the release team was waiting
for further comments from the sparc porters about this issue. Up to
know, I have seen no comments yet (besides from Goswin or you).
Gruesse,
Reinhard
Reply to: