Created attachment 874476 [details] build.log Hi, I don't know if this goes here or maybe it's an upstream issue or a combination of the compilation flags that I am using, but the latest version of media-video/mplayer doesn't build for me on an armv7 device. I get this assembler compilation error: {standard input}: Assembler messages: {standard input}:363: Error: selected FPU does not support instruction -- `vcvt.s32.f32 q0,q0,#31' {standard input}:364: Error: selected processor does not support `vqrshrn.s32 d0,q0,#15' in Thumb mode {standard input}:365: Error: selected FPU does not support instruction -- `vcvt.s32.f32 q1,q1,#31' {standard input}:366: Error: selected processor does not support `vqrshrn.s32 d1,q1,#15' in Thumb mode {standard input}:381: Error: selected FPU does not support instruction -- `vcvt.s32.f32 d0,d0,#31' {standard input}:382: Error: selected processor does not support `vqrshrn.s32 d0,q0,#15' in Thumb mode {standard input}:1344: Error: selected FPU does not support instruction -- `vcvt.s32.f32 q0,q0,#31' {standard input}:1345: Error: selected processor does not support `vqrshrn.s32 d0,q0,#15' in Thumb mode {standard input}:1346: Error: selected FPU does not support instruction -- `vcvt.s32.f32 q1,q1,#31' {standard input}:1347: Error: selected processor does not support `vqrshrn.s32 d1,q1,#15' in Thumb mode {standard input}:1362: Error: selected FPU does not support instruction -- `vcvt.s32.f32 d0,d0,#31' {standard input}:1363: Error: selected processor does not support `vqrshrn.s32 d0,q0,#15' in Thumb mode Checking the file where this code is (libaf/af_format.c), I can see it's conditional to having Neon: #if HAVE_NEON && !ARCH_AARCH64 The thing is that I do have neon: # fgrep neon /proc/cpuinfo Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 But, anyway, removing 'neon' from CPU_FLAGS_ARM fixed the issue for me. Interestingly, a blank CFLAGS while still keeping 'neon' in CPU_FLAGS_ARM also seemed to fix the issue. Setting any other value to CFLAGS, even if it's just '-O2', made the issue appear again. Full build.log and emerge info attached.
Created attachment 874477 [details] emerge-info.txt
