On Sat, Apr 21, 2018 at 15:39:09 +0200, Reindl Harald wrote: > * it was removed in some snapshot > * in a later release tarball *after* that snapshot it was there again
There's your misunderstanding: - recent 3.4.x releases were made from the n3.4 branch (and 3.3.x from n3.3 and so on; - snapshots are taken from the master branch; - recently, n4.0 and release 4.0 were made off master. If you are switching between snapshots and "latest releases", you were switching between master, where ffserver was removed at some point, and n3.4, where ffserver was still in. Then, in release 4.0, ffserver was also out. There was no "in and out" of ffserver. It was you who switched back and forth between master and 3.4: > * at begin of this year build against latest x264 failed > * then there was a snapshot which fixed that without ffserver > * later ffmpeg-3.4.2.tar.xz contaiend that fix but again ffserver That's a separate fix, which was apparently backported to 3.4. > the main problem is a idiotic behavior that --disable-ffserver is a > *hard* configure error just because ffserver was removed anyways while > that option refelects exactly the situation "no ffserver please" That might be for discussion. autoconf seems more tolerant: some-autoconf-project$ ./configure --disable-blafoo configure: WARNING: unrecognized options: --disable-blafoo [...] But that's not up to me, and I neither agree nor disagree that it's idiotic. Moritz _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
