From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "André Zwing" <nerv@dawncrow.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libkrb5: doesn't build with libressl
Date: Sun, 22 May 2022 22:12:41 +0200 [thread overview]
Message-ID: <87zgj9xr5y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220418114103.276282-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Mon, 18 Apr 2022 13:41:03 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> libkrb5 does not build with libressl since commit
> b7a5b9d06d484700fc4fcbd354f2c15e0422688c and upstream is not interested
> in fixing this issue as a PR is opened for more than 4 years
> (https://github.com/krb5/krb5/pull/607):
> pkinit_crypto_openssl.c: In function 'cms_signeddata_verify':
> pkinit_crypto_openssl.c:1700:22: error: implicit declaration of
> function 'OBJ_get0_data'; did you mean 'BIO_get_data'?
> [-Werror=implicit-function-declaration]
> 1700 | print_buffer(OBJ_get0_data(etype), OBJ_length(etype));
> | ^~~~~~~~~~~~~
> | BIO_get_data
> Fixes:
> - http://autobuild.buildroot.org/results/e623f4e1d6b6004e98815b8b7da3938238890bd8
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-05-22 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 11:41 [Buildroot] [PATCH 1/1] package/libkrb5: doesn't build with libressl Fabrice Fontaine
2022-04-18 17:03 ` Petr Vorel
2022-04-19 20:37 ` Arnout Vandecappelle
2022-05-22 20:12 ` Peter Korsgaard [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=87zgj9xr5y.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=nerv@dawncrow.de \
/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.