From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] libeet and removed gnutls functions
Date: Mon, 7 Dec 2015 22:10:47 +0100 [thread overview]
Message-ID: <5665F5D7.4010101@openwide.fr> (raw)
In-Reply-To: <235549288.4898236.1449491634762.JavaMail.zimbra@openwide.fr>
Hi Vicente, Gustavo, All
Le 07/12/2015 13:33, Romain Naour a ?crit :
> Hi Vicente,
>
> ----- Mail original -----
>> De: "Vicente Olivert Riera" <Vincent.Riera@imgtec.com>
>> ?: "Romain Naour" <romain.naour@openwide.fr>
>> Cc: "buildroot" <buildroot@buildroot.org>
>> Envoy?: Lundi 7 D?cembre 2015 13:22:07
>> Objet: libeet and removed gnutls functions
>
>> Dear Romain, all,
>>
>> On 07/12/15 07:30, Thomas Petazzoni wrote:
>>
>>> sparc64 | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/826a8f36631daa35ebd49850e12304e784ff9be8/
>>> arm | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/7d5f483cdce508d27678acf5ac387b57fffae9bd/
>>> i686 | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/e47b75bf07892126eb1fa21268edd24077f140c7/
>>> i686 | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/1025f598e3995ce2157fd028345796e00ac36da6/
>>> mips | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/a5f9100346aca894188126b499ba2ac84579c8d3/
>>> arm | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/1a90ae4963a73ce1f12b743272e61697dee25454/
>>> xtensa | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/bb4a2715923f9d098607b2de76f208ea6c9f2c42/
>>> aarch64 | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/5836d5758ff8c8421973b325fdd80ab70f04699e/
>>> mips | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/5d7202143f0ca453a251ac147421b9d284ed942e/
>>> arm | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/746be354f6372df33dae9e2cc969e2a497fe9a3b/
>>> arc | libeet-1.7.10 | NOK |
>>> http://autobuild.buildroot.net/results/46896031bcf3195716ee2224679400eff37c4151/
>>
>> 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?
>
> No since the libeet package will be removed with the efl bump series.
> But...
>
>> Do you think we could disable the gnutls support in
>> libeet until upstream adds support for the 3.4.x branch?
This commit answer your question (from efl 1.8 release) :)
https://git.enlightenment.org/core/efl.git/commit/?id=511d8e86728be555a4a57e470c4f6c90b5bb8bca
efl packages has been unmaintained for a too long time :-/
Best regards,
Romain
>
> I'll take a look to the gnutls support with efl 1.15.2 which provide
> an updated version of libeet.
>
> Best regards,
> Romain
>
>>
>> Regards,
>>
>> Vincent.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
prev parent reply other threads:[~2015-12-07 21:10 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
2015-12-07 12:32 ` Vicente Olivert Riera
2015-12-07 12:33 ` Romain Naour
2015-12-07 21:10 ` Romain Naour [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=5665F5D7.4010101@openwide.fr \
--to=romain.naour@openwide.fr \
--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