From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/ffmpeg: Disable rtmpdump support when PolarSSL is enabled
Date: Thu, 15 Oct 2015 19:28:49 -0300 [thread overview]
Message-ID: <562028A1.8070908@zacarias.com.ar> (raw)
In-Reply-To: <20151016000223.65fd40c3@free-electrons.com>
On 15/10/15 19:02, Thomas Petazzoni wrote:
> Dear Bernd Kuhls,
>
> On Thu, 15 Oct 2015 21:55:21 +0200, Bernd Kuhls wrote:
>> Using rtmpdump with PolarSSL breaks ffmpeg configure:
>> /home/test/autobuild/instance-1/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/lib/librtmp.so: undefined reference to `havege_random'
>> /home/test/autobuild/instance-1/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/lib/librtmp.so: undefined reference to `havege_init'
>
> This indicates that polarssl doesn't provide all the symbols needed by
> librtmp.
>
> So the problem should not be fixed at the ffmpeg level, but at the
> librtmp level: any other package that will try to link with librtmp
> will have the same issue.
Hi Thomas, definitely...
> The fix should be done in rtmpdump.mk, by disabling the possibility of
> using polarssl as the crypto library. I guess it has to do with the API
> change of PolarSSL (Gustavo ?).
Those are part of the 1.2 API so no issues there.
However rtmpdump has severe issues with it's Makefile and the resulting
librtmp.pc.
librtmp.pc.in says:
Requires: @CRYPTO_REQ@
The Makefile says (condensed):
CRYPTO=OPENSSL
#CRYPTO=GNUTLS
...
REQ_GNUTLS=gnutls,hogweed,nettle
REQ_OPENSSL=libssl,libcrypto
...
CRYPTO_REQ=$(REQ_$(CRYPTO))
Hence polarssl is never thrown into the pkgconfig fail, hence it will
always fail.
So, as it is, rtmpdump is useless with polarssl even if it builds with
it, so your fix is the right one unless rtmpdump is fixed.
Regards.
prev parent reply other threads:[~2015-10-15 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 19:55 [Buildroot] [PATCH v2 1/1] package/ffmpeg: Disable rtmpdump support when PolarSSL is enabled Bernd Kuhls
2015-10-15 22:02 ` Thomas Petazzoni
2015-10-15 22:28 ` Gustavo Zacarias [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562028A1.8070908@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox