for what it's worth, I have been met with similar issue on this list.
Very unfortunate, and the principals are not doing anything about it.
On 06/15/2016 06:21 PM, James Almer wrote:
On 6/15/2016 8:16 PM, Ivan Kalvachev wrote:
Loads of crap
No one, and i mean no one reply to this email.
You
Please ignore.
Problem was in system.
On 04/29/2016 05:56 PM, jd1008 wrote:
On 04/29/2016 05:25 PM, Michael Niedermayer wrote:
On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I
On 04/29/2016 05:25 PM, Michael Niedermayer wrote:
On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
libavcod
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
libavcodec/x86/ -o libavcodec/x86/vp3dsp.o libavcodec/x86/vp3dsp.asm
libavcodec/x86/h264_qpel_mmx.c: Assembler messages:
libavcode