Some configuration parameters fail when I run the configure command - bad or ok anyway?

Crazy Fin

I have recently realised that when I run the ./configure command I see some fails (I have removed the rows with checks that were ok):

=============================
Checking support/features
checking for cc libiconv ... fail
checking for cc libhdhomerun/hdhomerun.h ... fail
checking for pkg liburiparser ... fail (detected <none>)
checking for ffmpeg libraries ... fail

checking for pkg libavcodec >=55.34.1 ... fail (detected 54.35.0)

WARNING: none or old libav or libffmpeg libraries were detected
use --disable-libav or --enable-libffmpeg_static * supported ffmpeg libs n1.2+

supported libav libs v10+

Options:
v4l no
hdhomerun_client no
hdhomerun_static no
libav no
libffmpeg_static no
uriparser no
ccache no
bundle no
dvbcsa no
kqueue no
android no
mpegps no

=============================

I am wondering if any of these fails and not enabled options are bad and need to be fixed (or enabled for the options)?

ProfYaffle

It depends on what you want to use tvheadend for to a great extent...

If you don't need to translate to/from Unicode, you don't need libiconv. I've never missed it, but I use unaccented characters on English-language channels 99.9% of the time.

If you don't have an HDHR device, then you don't need libdhhomerun.

liburiparser makes life easier, I think - tvh has some internal code to perform basic URI parsing, but the library is probably more reliable. Used to find icons and make sense of other URLs.

ffmpeg/libavcodec are really there for transcoding. You can use static libraries instead, though, which are currently more reliable (--enable-libffmpeg_static).