On 2009/12/20 23:59, Edd Barrett wrote:
> On Sun, Dec 20, 2009 at 7:03 PM, Brad wrote:
> > Even if --disable-asm is an option with x264 it cannot be updated at the
> > moment.
>
> Sorry, I thought you meant binutils can not be updated. What stops
> x264 being updated?
It's part of a huge interde
On Sun, Dec 20, 2009 at 7:03 PM, Brad wrote:
> Even if --disable-asm is an option with x264 it cannot be updated at the
> moment.
Sorry, I thought you meant binutils can not be updated. What stops
x264 being updated?
> As I had said to him on icb he will have to use a snapshot of MPlayer
> befor
On Sunday 20 December 2009 13:50:02 Jacob Meuser wrote:
> On Sun, Dec 20, 2009 at 05:21:29PM +, Edd Barrett wrote:
> > Hi,
> >
> > This is just a heads up email. I discussed this with brad and I know
> > this is not trivial.
> >
> > The newest mplayer snapshot will refuse to accept our "old" x2
On Sun, Dec 20, 2009 at 05:21:29PM +, Edd Barrett wrote:
> Hi,
>
> This is just a heads up email. I discussed this with brad and I know
> this is not trivial.
>
> The newest mplayer snapshot will refuse to accept our "old" x264
> library. Upon attempting to update x264, I am told that our bin
Hi,
This is just a heads up email. I discussed this with brad and I know
this is not trivial.
The newest mplayer snapshot will refuse to accept our "old" x264
library. Upon attempting to update x264, I am told that our binutils
version is too old:
Found GNU assembler 2.15
Minimum version is binu
