On Thu, Dec 15, 2016 at 09:28:58 +0100, Carl Eugen Hoyos wrote: > > Include the log file "config.log" produced by configure as this will help > > solve the problem. > > Did you read this?
He did, and he did include config.log. > > I assure that the latest x264 lib is installed. > > > > -rw-r--r-- 1 denis staff 1,5M 14 Dic 21:57 libvpx.a > > *-rwxr-xr-x 1 root wheel 715K 14 Dic 22:14 libx264.148.dylib* > > *-rw-r--r-- 1 root wheel 820K 14 Dic 22:14 libx264.a* > > *lrwxr-xr-x 1 root wheel 17B 14 Dic 22:14 libx264.dylib -> > > libx264.148.dylib* > > You didn't tell where you installed it. > If it is in the default location "/usr/local", it should be picked up > automatically. The problem is clearly outlined at the very bottom of config.log: > /var/folders/z_/pqkmr0g95ll4dszy7z6ns3v40000gn/T//ffconf.WnmjwMvN.c:1:10: > fatal error: 'x264.h' file not found > #include <x264.h> > ^ > 1 error generated. > ERROR: libx264 not found You (Denis) do indeed have the libs installed, but you also need the headers in order to compile against an external library such as libx264. As Carl Eugen mentioned, both the libraries and the headers (or a pkgconfig file) must be under standard locations in order to be found automatcally. Environment variables and ./configure options can help point the configure process to locations which differ. Moritz _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
