From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] libeet and removed gnutls functions
Date: Mon, 7 Dec 2015 09:27:03 -0300 [thread overview]
Message-ID: <56657B17.4060008@zacarias.com.ar> (raw)
In-Reply-To: <566579EF.6050906@imgtec.com>
On 07/12/15 09:22, Vicente Olivert Riera wrote:
> According to gnutls upstream:
>
> ------------------
> "GnuTLS 3.4.x is source compatible with GnuTLS 3.3.x releases; however,
> several deprecated functions were removed, and are listed below."
>
> Old function Replacement
> [...]
> gnutls_x509_crt_verify_data gnutls_pubkey_verify_data2
> ------------------
>
> So, gnutls_x509_crt_verify_data no longer exists because has been
> replaced by gnutls_pubkey_verify_data2.
>
> libeet uses the former one:
>
> src/lib/eet_cipher.c: if (!gnutls_x509_crt_verify_data(cert, 0,
> &datum, &signature))
>
> And it fails with an error like this one:
>
> ../../src/lib/.libs/libeet.so: undefined reference to
> `gnutls_x509_crt_verify_data'
>
> You are more in touch with the enlightenment packages, so, how do you
> suggest to fix this? Do you think we could disable the gnutls support in
> libeet until upstream adds support for the 3.4.x branch?
Hi Vincent.
Likely http://patchwork.ozlabs.org/patch/538802/ (series) handles that.
Regards.
next prev parent reply other threads:[~2015-12-07 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-12-06 Thomas Petazzoni
2015-12-07 11:05 ` Yann E. MORIN
2015-12-07 11:08 ` Vicente Olivert Riera
2015-12-07 11:11 ` Yann E. MORIN
2015-12-07 12:22 ` [Buildroot] libeet and removed gnutls functions Vicente Olivert Riera
2015-12-07 12:27 ` Gustavo Zacarias [this message]
2015-12-07 12:32 ` Vicente Olivert Riera
2015-12-07 12:33 ` Romain Naour
2015-12-07 21:10 ` Romain Naour
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=56657B17.4060008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.