From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Jérôme Pouiller" <jezz@sysmic.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/strongswan: fix wolfssl build
Date: Sat, 17 Sep 2022 08:50:14 +0200 [thread overview]
Message-ID: <87o7ve4hqx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220818213936.442912-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 18 Aug 2022 23:39:36 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix the following build failure with BR2_PACKAGE_WOLFSSL_ALL raised
> since bump to version 5.9.0 in commit
> da912a3d2abe2eb2b338c03ec56c7e39a4d640f9:
> In file included from ../../../../src/libstrongswan/utils/utils.h:59,
> from ../../../../src/libstrongswan/library.h:101,
> from wolfssl_common.h:29,
> from wolfssl_aead.c:23:
> wolfssl_aead.c:90:16: error: conflicting types for 'encrypt'; have '_Bool(union <anonymous>, chunk_t, chunk_t, chunk_t, chunk_t *)'
> 90 | METHOD(aead_t, encrypt, bool,
> | ^~~~~~~
> ../../../../src/libstrongswan/utils/utils/object.h:99:20: note: in
> definition of macro 'METHOD'
> 99 | static ret name(union {iface *_public; this;} \
> | ^~~~
> In file included from /home/autobuild/autobuild/instance-5/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/include/wolfssl/wolfcrypt/wc_port.h:573,
> from /home/autobuild/autobuild/instance-5/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/include/wolfssl/wolfcrypt/types.h:35,
> from /home/autobuild/autobuild/instance-5/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/include/wolfssl/wolfcrypt/logging.h:33,
> from /home/autobuild/autobuild/instance-5/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/include/wolfssl/ssl.h:35,
> from wolfssl_common.h:64,
> from wolfssl_aead.c:23:
> /home/autobuild/autobuild/instance-5/output-1/host/powerpc64le-buildroot-linux-musl/sysroot/usr/include/unistd.h:149:6: note: previous declaration of 'encrypt' with type 'void(char *, int)'
> 149 | void encrypt(char *, int);
> | ^~~~~~~
> Fixes:
> - http://autobuild.buildroot.org/results/02f080c2f6d8272cb8cc1de66e058d66fb7499bc
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 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-09-17 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:39 [Buildroot] [PATCH 1/1] package/strongswan: fix wolfssl build Fabrice Fontaine
2022-08-20 8:23 ` Yann E. MORIN
2022-09-17 6:50 ` 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=87o7ve4hqx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=jezz@sysmic.org \
/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