Am 21.04.2018 um 15:33 schrieb Paul B Mahol: > On 4/21/18, Reindl Harald <[email protected]> wrote: >> Am 21.04.2018 um 15:08 schrieb Reindl Harald: >>> Am 21.04.2018 um 14:59 schrieb Paul B Mahol: >>>> On 4/21/18, Reindl Harald <[email protected]> wrote: >>>>> >>>>> Am 21.04.2018 um 14:46 schrieb Paul B Mahol: >>>>>> On 4/21/18, Reindl Harald <[email protected]> wrote: >>>>>>> could you guys make a decision if you spit out ffserver or not support >>>>>>> it any longer? that's at least the third time when building >>>>>>> snapshot-packages that i either get a ffserver binary or the option to >>>>>>> not build it is not supported and ends in a hard configure error >>>>>> >>>>>> PEBKAC >>>>> >>>>> bullshit - you likely did not understand what i wrote >>>>> >>>>> in current snaphots --disable-ffserver is a unknown option while in the >>>>> last few months it was later supported again and that leads when you >>>>> don't specify the option in get a ffserver binary >>>>> >>>>> so you have to adjust the ffmpeg-latest.spec back and forth >>>>> >>>> PEBKAC >>> >>> how is the problem between keyboard and chair when a configure option is >>> rmeoved and added back multiple times? are you drunken or what is so >>> difficult to understand in the question if someone consideres eiter >>> remove ffserver or not and stay at that decision? >> >> BTW: i do not take people serious which are not capable to operate their >> mail cient and strip list-footers from quotes - *that* is PEBKAC > > You are limited in sense to comprehend that ffserver option is removed > only once. > > You need to just check which version have it not removed and only then > enable that option
which is *not* true * it was removed in some snapshot * in a later release tarball *after* that snapshot it was there again * in the 4.0 release snapshot it is gone again * 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 * 4.0 again don't contain ffserver 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" _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
