Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Jianhui Zhao <zhaojh329@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libuwsc: fix wolfssl build
Date: Fri, 16 Dec 2022 16:05:09 +0100	[thread overview]
Message-ID: <87bko3qti2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221208202610.5018-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 8 Dec 2022 21:26:10 +0100")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > libuwsc needs BR2_PACKAGE_WOLFSSL_ALL (which enables openssl compat
 > layer) to avoid the following wolfssl build failure raised since the
 > addition of the package in commit
 > 120c04775d7ebe5a2cfc14848f5d11f3a333970b:

 > /home/br-user/work/instance-1/output-1/build/libuwsc-3.3.5/src/ssl.c:62:5: error: unknown type name 'SSL_CTX'
 >    62 |     SSL_CTX *ctx;
 >       |     ^~~~~~~

 > Fixes:
 >  - http://autobuild.buildroot.org/results/6c2a6ed6fca1f92aab299f6ed9cd900b20e8d512

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2022.11.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-12-16 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 20:26 [Buildroot] [PATCH 1/1] package/libuwsc: fix wolfssl build Fabrice Fontaine
2022-12-10  8:45 ` Yann E. MORIN
2022-12-16 15:05 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-14 15:56 Fabrice Fontaine
2024-01-15  7:47 ` Peter Korsgaard
2024-02-03 10:39 ` Peter Korsgaard

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=87bko3qti2.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=zhaojh329@gmail.com \
    /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