[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mplayer2 FTBFS on sparc

On Sun, Oct 09, 2011 at 10:50:39PM +0200, Kurt Roeckx wrote:
> On Sun, Oct 09, 2011 at 09:46:02PM +0200, Reinhard Tartler wrote:
> > On So, Okt 09, 2011 at 21:05:56 (CEST), Jurij Smakov wrote:
> > 
> > > I thought about it, and I don't really see why we would keep the 
> > > linux32 wrapper on the buildds. It made sense in the past, when we 
> > > supported sparc32 and really wanted to guarantee that if a package 
> > > has CPU type autodetection, we would get the code which works on both 
> > > sparc32 and sparc64 machines. These days it probably just leads to a 
> > > ton of unnecessarily-unoptimized binaries in the archive.
> > 
> > Indeed, please notify me (e.g., with a wishlist bugreport) when the
> > buildds get changed, because I have to revert this change then:
> I basicly have 2 questions:
> - Do all sparc porters agree that I should drop the linux32 from
>   the buildds?  And will people fix things if it breaks?

I just checked what "old" binary objects I have in my /usr/bin and 
/usr/lib, and found that in /usr/bin there are no such binaries, and 
only a handful of libs in /usr/lib:

jurij@debian:/usr/lib$ for i in *; do file $i | grep 'ELF' | grep -v 'V8\+'; done | awk -F: '{print $1}'

Based on that, I don't think that there will be any significant impact 
(famous last words :-).  

> - Do you still plan to have a (full) release of sparc for wheezy, or will
>   you try to move to sparc64?

Personally, I'm not involved in any way with the sparc64 port, so I 
don't know what the current status or plans with respect to wheezy 
are (I also don't have any special reasons to be opposed to it 
either). I guess that Aurelien is pretty much the only person who can 
answer that.

Best regards,
Jurij Smakov                                           jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC

Reply to: