This is an auto-filled bug because media-video/ffmpeg fails to compile on arm. Feel free to adjust the summary to clarify the exact issue. Attached build log and emerge --info
Created attachment 623880 [details] ffmpeg-4.1.3:20200319-080900.log build log
Created attachment 623882 [details] emerge --info emerge --info
If 4.1.3 fails to build, how was it marked stable on arm then?
Does media-video/ffmpeg-4.2.2 build?
(In reply to Andreas Sturmlechner from comment #3) > If 4.1.3 fails to build, how was it marked stable on arm then? I didn't mark it stable. I suppose that: 1) it builds for who marked it stable 2) it was marked stable by mistake (In reply to Andreas Sturmlechner from comment #4) > Does media-video/ffmpeg-4.2.2 build? I'll test it
(In reply to Andreas Sturmlechner from comment #4) > Does media-video/ffmpeg-4.2.2 build? It doesn't, but I suppose there is something wrong when you run an arm chroot on an arm64 host, infact I see something like: src/libavutil/aarch64/bswap.h:38:5: error: invalid 'asm': invalid operand for code 'w' aarch64 should not be involved.
(In reply to Agostino Sarubbo from comment #6) > (In reply to Andreas Sturmlechner from comment #4) > > Does media-video/ffmpeg-4.2.2 build? > > It doesn't, but I suppose there is something wrong when you run an arm > chroot on an arm64 host, infact I see something like: > src/libavutil/aarch64/bswap.h:38:5: error: invalid 'asm': invalid operand > for code 'w' > > aarch64 should not be involved. Looks like --arch=arm may be a workaround for now but this may happen on other arches if you're in a chroot too. Will test when my box updates.
it was my fault. I didn't call linux32 when chrooting from aarch64 hw.