[FFmpeg-user] FFmpeg Hall of Shame

Thirumalaisamy K er.thirumalai at gmail.com
Wed Nov 29 15:47:57 EET 2017

I know the difference between GPL and LGPL. But, in both you have to
disclose the sources including controlling scripts.

I agree that I can just dump the config parameters from the binary itself
using -buildconf. But, it doesn't mean that I can just reproduce the same
binary with the script. There is no guarantee that the releaser hasn't
modified the sources.

I am not blaming a particular person. I have checked both websites that
provides the static binary for win and mac. Both are not providing the
build scripts.

I agree that They are doing the pretty good job on maintaining the binary
for everyone. But, it's not good for such a supporter to break LGPL.

Just clear question whether it's required to release the control scripts
when one release a binary made from LGPL code?
If it's required, does ffmpeg team officially support the violation of LGPL

*Thirumalaisamy K*

On 29 November 2017 at 17:58, Reindl Harald <h.reindl at thelounge.net> wrote:

> Am 29.11.2017 um 12:43 schrieb Thirumalaisamy K:
>> According to LGPL / GPL it's necessary to provide the complete source
>> codes
>> which includes the objects that linked against and scripts that controls
>> the compilation & installation. But, the websites linked in official
>> download pages are not providing the complete sources. Only just leaving
>> the link for the official ffmpeg sources. I have mailed to some of them. I
>> have got the reply from one of them (evermeet.cx) that It's not necessary
>> to provide the build scripts & claimed it's made from his own hard works
>> and asked ffmpeg devs to contact him. It's quite unfortunate to see this
>> response from the maintainer of a officially recommended download
>> location.‚Äč People are utilizing the hard work behind ffmpeg & refuses to
>> comply with LGPL. It's shame. And ffmpeg team recommends such download
>> locations
> WTF - ffmmpeg even displays the configure string and so you have all
> informations how it was built
> "which includes the objects that linked against" is nonsense, when YOU
> LINK against some GPL sourced libs you need to provide YOUR source - caus
> and affect inverted by you
> and with "According to LGPL / GPL" you clearly show you have no idea what
> you are talking about, otherwise you would know the differences of both and
> that you can link against LGPL libraries without release youzr sources
> under the same license
> *jesus christ* ffmmpeg is linked against tons of other libraries and you
> are inverting the intention of the GPL
> [harry at srv-rhsoft:~]$ ffmpeg
> ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
>   built with gcc 7 (GCC)
>   configuration: --prefix=/usr/local --bindir=/usr/local/bin
> --mandir=/usr/local/man --extra-cflags='-I/usr/local/x264 -m64 -O2 -g0
> -mfpmath=sse -mavx -msse2avx -march=sandybridge -mtune=sandybridge -fopenmp
> -pipe -fno-strict-aliasing -fomit-frame-pointer -fexceptions
> -fstack-protector-strong --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2
> -Wstack-protector -Wformat -Werror=format-security -Ofast -ffast-math
> -funsafe-math-optimizations -Wno-pointer-sign -minline-all-stringops
> -fno-strict-aliasing -fuse-ld=gold -fuse-linker-plugin -Wa,--noexecstack'
> --extra-ldflags='-I/usr/local/x264 -L/usr/local/x264 -ldl -Wl,--as-needed
> -Wl,-z,now -Wl,-z,relro -Wl,-z,noexecstack -m64 -O2 -g0 -mfpmath=sse -mavx
> -msse2avx -march=sandybridge -mtune=sandybridge -fopenmp -pipe
> -fno-strict-aliasing -fomit-frame-pointer -fexceptions
> -fstack-protector-strong --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2
> -Wstack-protector -Wformat -Werror=format-security -Ofast -ffast-math
> -funsafe-math-optimizations -Wno-pointer-sign -minline-all-stringops
> -fno-strict-aliasing -pie -fPIE -fuse-ld=gold -fuse-linker-plugin
> -Wa,--noexecstack' --ar=gcc-ar --ranlib=true --enable-nonfree --enable-gpl
> --enable-pic --enable-version3 --enable-libmp3lame --enable-libtheora
> --enable-libx264 --enable-libx265 --enable-libvpx --enable-openssl
> --enable-static --enable-runtime-cpudetect --disable-amd3dnow
> --disable-amd3dnowext --disable-avdevice --disable-debug --disable-devices
> --disable-ffplay --disable-ffprobe --disable-ffserver --disable-htmlpages
> --disable-hwaccels --disable-iconv --disable-libdc1394
> --disable-libfreetype --disable-libgsm --disable-libopencore-amrnb
> --disable-libopencore-amrwb --disable-libopencv --disable-libopenjpeg
> --disable-libopus --disable-librtmp --disable-libspeex --disable-libvorbis
> --disable-libxvid --disable-podpages --disable-postproc
> --disable-protocol=gopher --disable-shared --disable-txtpages
>   libavutil      55. 78.100 / 55. 78.100
>   libavcodec     57.107.100 / 57.107.100
>   libavformat    57. 83.100 / 57. 83.100
>   libavfilter     6.107.100 /  6.107.100
>   libswscale      4.  8.100 /  4.  8.100
>   libswresample   2.  9.100 /  2.  9.100
> Hyper fast Audio and Video encoder
> usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options]
> outfile}...
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".

More information about the ffmpeg-user mailing list