ffmpg -version gives strange version output
This happens after I compile the git ffmpeg source (baaa6d6): ./ffmpeg -version ffmpeg version 2.1.git-tessus built on Feb 14 2014 22:15:20 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-libmodplug --enable-fontconfig --enable-libfreetype --enable-libass --enable-libbluray --enable-filters --enable-runtime-cpudetect libavutil 52. 63.101 / 52. 63.101 libavcodec 55. 52.101 / 55. 52.101 libavformat 55. 32.101 / 55. 32.101 libavdevice 55. 9.101 / 55. 9.101 libavfilter 4. 1.102 / 4. 1.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 In previous versions it was shown as (just an exampe from a previous build): ffmpeg version N-60633-g674195c-tessus I asked this question on the #ffmpeg-devel channel as well and Michael suggested to clone the repository into a new directory and try again. I did that and it did not help. Maybe it has to do with the --extra-version config option or somebody changed the build scripts, because the version.sh script does give me an output in the format N-MMMMM-gXXXXXXX, but I couldn't find that string anywhere in the code. Isn't the build process supposed to write that info into a version file? Cheers, Helmut -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
Helmut Tessarek wrote:
This happens after I compile the git ffmpeg source (baaa6d6):
./ffmpeg -version ffmpeg version 2.1.git-tessus built on Feb 14 2014 22:15:20 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-libmodplug --enable-fontconfig --enable-libfreetype --enable-libass --enable-libbluray --enable-filters --enable-runtime-cpudetect libavutil 52. 63.101 / 52. 63.101 libavcodec 55. 52.101 / 55. 52.101 libavformat 55. 32.101 / 55. 32.101 libavdevice 55. 9.101 / 55. 9.101 libavfilter 4. 1.102 / 4. 1.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100
In previous versions it was shown as (just an exampe from a previous build): ffmpeg version N-60633-g674195c-tessus
I asked this question on the #ffmpeg-devel channel as well and Michael suggested to clone the repository into a new directory and try again.
I did that and it did not help. Maybe it has to do with the --extra-version config option or somebody changed the build scripts, because the version.sh script does give me an output in the format N-MMMMM-gXXXXXXX, but I couldn't find that string anywhere in the code.
Isn't the build process supposed to write that info into a version file?
Cheers, Helmut
One trick you can do to set a specific version is this... 1) config + build ffmpeg 2) edit libavutil/ffversion.h adding a custom version 3) make (at top of tree again, which just rebuilds a few files) Here's an example with latest version + date + changeset: ffmpeg version 2.2-2014-04-02-62040-gcecb6d6
On 02.04.14 9:46 , David Favor wrote:
One trick you can do to set a specific version is this...
Thanks, after a few git upgrades on my system, everything seems to be in order again. Apparently my git code was unstable or in a wacky state. Cheers, Helmut
Helmut Tessarek wrote:
On 02.04.14 9:46 , David Favor wrote:
One trick you can do to set a specific version is this...
Thanks, after a few git upgrades on my system, everything seems to be in order again. Apparently my git code was unstable or in a wacky state.
Cheers, Helmut
Sounds good!
participants (2)
-
David Favor -
Helmut Tessarek