-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 > You'd need to post your whole config.log (pastebin) likely. > > However, this list is for development of FFmpeg itself, and this > question should be on the user mailing list, or #ffmpeg on > FreeNode, where you'll likely get better answers.
I'd usually agree, but I'm building the binaries for macOS and I'm running into the same issue. Either the latest x265 broke something or a change in ffmpeg's configure messed things up. What I don't understand is that you didn't run into the same problem with fate. The last successful build I had was Dec 24th: ffmpeg 92795-gcdbf8847ea x265 20181217-1f44f1f1623d 2.9+16-1f44f1f1623d So something between then and now screwed things up. Cheers, K. C. - -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlwmtxUACgkQvgmFNJ1E 3QDHLQ/7BK1EDTPotGqn+7LQODL2TSmDGq8mQf7emx5ckG42R5Kpb0G84eZ5Ns6a Mii8oQ/tovX/kRtFjd4+H17xIUA2u7e+kXc/yNSHC51jFhE5F8QxfuU/3T2wfSIt nLbPx68t5LARPqUdaldWUJ3r7kL/wyctNaeqYfZrMuhhzRm5BCRnKJC1mLgNCB+e 8628iMdCCeucZwj1Eb3bK+Y4YgoxalEHHjnqSnrAxlxuWO2WdlIbD1z5gfTMJ8s7 bDsKVmKKdgy27lI4JU0vRZ5Q1d2GaPqicVRij7L3XjYr0OC6Yn2Oe9h9mYZCBLfp Z3f/wxUMOSQI4CwA2yd97ZV1fcs82B28StAvdaixTDWxecWyjF89dMC2mYqmpIFu SFqrtzEZdrWnFgNljSkvkd4t2evLCIS+A5l9b01sXVxN7RyqFv0kThs+bHll/cH9 jYXm/bVYn1hUuAp73xsKlHlNWjRcCgTQQSqVAKxAU6NP2PeIRogf/NpU8M7hACuo mds/OIFPNUMTnul58pvT59xTnrQV96aULDvbm+lTvskP93T/x4VDjs2yrYJ3q4tH 45J0a2x6eCmU2yVKLK/6wf2NwciBCDxItBIwqRPZ5m/8creDlfF46dHspE/q2wqd mR0YmeWr5ouOigFSnXi0EZk/eZwbqMPrUc+87LGm9Gt3gdHCHAs= =G6TL -----END PGP SIGNATURE----- _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
