libavformat/tls_openssl.c: implicit declaration of function 'BIO_meth_*'

[LigH]

Compilation fails, trying to build ffmpeg (static 32-bit) in ​media-autobuild_suite; see attached build log. It's related to their ​issue #622.

[LigH]

explicit build log

[Hendrik]

We cannot debug build issues with third party build systems.

To give this any chance, we need the full configure line as well as ffmpegs config.log.

[Hendrik]

(also,Trac is dumb and for some reason reverts any edits that were in progress when you write a comment, wtf)

[LigH]

ffmpeg configure log

[LigH]

logs archive

[LigH]

Attached the configure log and the full archive of MABS logs. I hope it may contain everything that might be helpful to you.

[Hendrik]

Which version of OpenSSl is this trying to use?

[LigH]

Unfortunately I have only little experience using a Linux like shell...

MABS updates itself and the underlying MSYS2 environment before building software. According to the directories in the pacman package registry (msys64/var/lib/pacman/local), I assume it's libopenssl-1.0.2.l-2; to be certain, I would need to know which command to type into an MSYS2/MinGW shell...

[Hendrik]

Check H:/development/media-autobuild_suite-master/local32/include/openssl/opensslv.h
It should list the version somewhere.

Browsing around in the script, it appears to use LibreSSL, and not OpenSSL. LibreSSL is not currently supported by FFmpeg. We only support OpenSSL or any of its forks that are actually version and binary compatible. LibreSSL typically claims to be OpenSSL in a very recent version, but not actually offer its full API.

[LigH]

You are right: "LibreSSL 2.6.2"

I will mention this detail to the MABS developers; does it mean that ffmpeg or libavformat suddenly use OpenSSL features they did not use before, and which LibreSSL may not yet implement?

[Hendrik]

These functions are in use since 10/2016 when support for OpenSSL 1.1 was added. LibreSSL breaks the version checks of OpenSSL by pretending to be OpenSSL in a very new version, but only offering the OpenSSL 1.0 API.

I don't know why the LibreSSL people didn't bother to do this properly, but alas.

[LigH]

Surprising for me: The ffmpeg options set refers to gnutls instead of libressl. See next attachment.

[LigH]

ffmpeg options set

[Hendrik]

I don't know how it does things, but I see --enable-openssl in there.

[James]

gnutls and openssl can't go together, so just remove the --enable-openssl line, since it's obviously not working with your libressl install.

[LigH]

I guess from here on, we will better wait for the MABS developers to check what happened. I believe they have some own experience with SSL/TLS libraries and their interdependencies... I won't be able to support much more.

[LigH]

Reading the development in MABS, I believe this ticket can be closed; they seem to agree that including both GnuTLS and OpenSSL is a mistake in the generation of the build options file.

[Carl Eugen Hoyos]

I have sent a patch that fixes the issue described in the ticket title (unrelated to MABS).

[LigH]

I wonder if your commit got lost; I don't see any updates related to "tls" or "ssl" in the github repo since this one (which I suspect to have caused it, but I have no clue, just spotted changes around a "BIO_*" function name mask):

​avformat/tls_openssl: move some functions up in the file

Can you link your submitted patch, please? (mere curiosity)

[Hendrik]

The patch is still on the mailing list, being discussed.

[Carl Eugen Hoyos]

Duplicate of ticket #6580