Build scripts for compiling ffmpeg under OSX / Linux
I'm getting an error in the last step ------------------------------------------------------------------------------- compile ffmpeg ------------------------------------------------------------------------------- ``` HEAD is now at 947122f libavfilter: Fix fate-source after 072788c46e36a21ca9e8f1e3cc19a1944db5b89c From https://github.com/FFmpeg/FFmpeg * branch master -> FETCH_HEAD Already up to date. install prefix /root/playout/ffplayout_engine/compile-ffmpeg-osx-linux/local ``` ....... ....... ...... ``` libavdevice/avdevice.c: In function ‘avdevice_configuration’: ./config.h:4:30: error: missing terminating " character #define FFMPEG_CONFIGURATION "--disable-debug --disable-shared --disable-doc --enable-gpl --enable-version3 --enable-runtime-cpudetect --enable-avfilter --enable-zlib --enable-pic ^ ./config.h:4:30: note: in definition of macro ‘FFMPEG_CONFIGURATION’ #define FFMPEG_CONFIGURATION "--disable-debug --disable-shared --disable-doc --enable-gpl --enable-version3 --enable-runtime-cpudetect --enable-avfilter --enable-zlib --enable-pic ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libavdevice/avdevice.c:44:5: warning: ‘return’ with no value, in function returning non-void return FFMPEG_CONFIGURATION; ^~~~~~ libavdevice/avdevice.c:42:14: note: declared here const char * avdevice_configuration(void) ^~~~~~~~~~~~~~~~~~~~~~ ffbuild/common.mak:70: recipe for target 'libavdevice/avdevice.o' failed make: *** [libavdevice/avdevice.o] Error 1 ------------------------------------------------- build ffmpeg-git failed... delete the source folder under '/root/playout/ffplayout_engine/compile-ffmpeg-osx-linux/build' and start again, or if you know there is no dependences hit enter for continue it first close the batch window, then the shell window ```
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by burakguder and has received 1 comments.