[FFmpeg-user] http hangs, https not, following ubuntu build from scratch.

[James Northrup]

returning to this topic...

downgrading my host environment to ubuntu 18.04 yeilds failures of at least
librsvg and librtmp, the latter of which is documented as an option to
 replace the simpler builtin rtmp.

"pkg-config does not find XXXX" is cropping up on many ubuntu -dev packages

the results appear the same or nearly same in ubuntu 18 and 19 LTS

this started out as an embillished version of # build ffmpeg with
libfdk_aac#
*@ *
https://stackoverflow.com/questions/18746359/compile-ffmpeg-with-libfdk-aac

this gave me good results with a 12Mb  ffmpeg executable for aac he-v2 by
eliminating video codecs

now i'd like to support dash, and live streaming.  maybe host icons from
podcasts as video down the road.  presently, I *think* i need to validate
"ffmpeg  -i rtmp:foo" to mux into dash or HLS

pkgconfig failures from stock ubuntu as follows:
----

sudo apt-get update -qq &&
PKGS=(
    autoconf
    automake
    build-essential
    cmake
    curl
    git
    gpac
    libass-dev
    libbz2-dev
    libfdk-aac-dev
    libfreetype6-dev
    libmp3lame-dev
    libopus-dev
    libsmbclient-dev
    libsnappy-dev
    lib{ss{l,h},r{tmp,svg2}}-dev
    libtool
    libva-dev
    libvorbis-dev
    libvpx-dev
    libxcb1-dev
    libtheora-dev libtwolame-dev libx264-dev libx265-dev
    nasm
    pkg-config
    texinfo
    wget
    yasm
    zlib1g-dev
) && sudo apt-get -y install ${PKGS[@]}
  sudo mkdir -p /usr/local/src;sudo chmod 777 /usr/local/src;pushd
/usr/local/src;

curl https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2|tar xjvf - && cd
ffmpeg
let NCPU="1 + $(egrep -e 'processor\s+\:' /proc/cpuinfo|tail -n1|cut -f 2
-d ' ') "


CONFIGS=(
    --disable-ffplay
    --enable-bzlib
    --enable-ffmpeg
    --enable-gpl
    --enable-iconv
    --enable-libfdk-aac
    --enable-libmp3lame
    --enable-libopus
    --enable-libsnappy
    --enable-libssh
    --enable-nonfree
    --enable-openssl
    --enable-version3
    --enable-zlib
)


CONFIGS+=(  #stuff that may not apply to all my servers goes here.

    --enable-libfreetype
    --enable-libtwolame
    --enable-libvpx
#    --enable-cuda-nvcc
    --enable-avresample
    --enable-librsvg
    --enable-librtmp
    --enable-libx264
#    --enable-libx{avs{,2},264}
#    --enable-libx{avs{,2},26{4..5}} avs and x265 -- pkconfig disagrees
    --enable-libvorbis
#    --enable-libdrm
#    --enable-librtmp
    --enable-libtheora
#    --enable-libopenh264
    --enable-gpl
)

TRIMMED=( #likewise, final link decisions may differ
   ${CONFIGS[@]}
    --disable-shared
       --enable-{lto,static}
)
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig"
./configure \
    --prefix="$HOME/ffmpeg_build" \
    --pkg-config-flags="--static" \
    --extra-cflags="-I$HOME/ffmpeg_build/include" \
    --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
    --extra-libs="-lpthread -lm" \
    --bindir="$HOME/bin" \
    $(eval  echo "${TRIMMED[@]}" ) && \
    make  clean && \
  PATH="$HOME/bin:$PATH" make -j $NCPU && \
  make install && \
  hash -r




On Tue, Mar 19, 2019 at 9:01 PM Moritz Barsnick <barsnick at gmx.net> wrote:

> On Tue, Mar 19, 2019 at 16:28:48 +0700, James Northrup wrote:
> > I have been having to wrap http in -i <( curl URL) using head ffmpeg on
> > ubuntu 19
>
> Interesting.
>
> > i want to know if there is a configure switch i might've used that
> creates
> > a situation where http is buggered.  i have two such ubuntu 19 machines
> > with similar results.
>
> This is your own built binary? You could try a binary from
> https://johnvansickle.com/ffmpeg/ for comparison.
>
> It can't be an ffmpeg issue, https uses mostly the same code as http,
> except for establishing the connection.
>
> > Immediate exit requested
>
> I don't know which code causes this, perhaps there's more insight from
> "-loglevel debug".
>
> Since you write that curl works, I would guess that a semi-transparent
> proxy is choking on ffmpeg's implementation of the protocol, but not
> curl's? Or the server's HTTP port doesn't like your source address. Or
> something similarly stupid. A tcpdump/Wireshark trace might be
> interesting. But try a different binary first please.
>
> Cheers,
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".