If the latest version fails, report the problem to mailing list or IRC #ffmpeg on. If you think configure made a mistake, make sure you are using the latest Last 15 lines from /Users/brion/Library/Logs/Homebrew/ffmpeg/01.configure: configure -prefix=/usr/local/Cellar/ffmpeg/2.8 -enable-shared -enable-pthreads -enable-gpl -enable-version3 -enable-hardcoded-tables -enable-avresample -cc=clang -hos => Reinstalling ffmpeg with -with-theoraĪlready downloaded: /Library/Caches/Homebrew/ffmpeg-2.8.tar.bz2 $ brew reinstall ffmpeg -with-lame -with-theora Left-click FFmpegv2.2.2forAudacityonWindows64bit.exe to launch the installer (you can safely ignore any warnings that the 'publisher could not be verified'). Reply to this email directly or view it on GitHub. Left-click the link FFmpeg v2.2.2 INSTALLER (.EXE) for 64-bit FFmpeg and save the file anywhere on your computer. superenv tries to configure the build environment so that only libraries which have been declared as a dependency with depends_on are visible to the build. Homebrew intentionally does not pass build-related environment variables into the build environment. I'm not sure from your description whether this is expected behavior or not because I'm not sure exactly what changes you made. So I just built it myself and it worked first time, I was using brew to manage dependencies but this time for some reason no dice. So brew installs packages which are dependencies of other brew packages but brew later cannot allow those packages to be seen. This wasn't expected behaviour either as all the libraries are visible to pkgconfig and were in the pkg_config_path - indeed they were installed by brew. By customising the configure line manually I could see that it was libraries that couldn't be found. I hacked the ffmpeg formula to see why there was no change because the output of the failed build wasn't informative.
That's definitely not expected behaviour. (With all the libraries ready present on my system) it failed.
0 kommentar(er)
