From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Ryan Barnett <ryan.barnett@collins.com>
Subject: Re: [Buildroot] [PATCH] package/websocketpp: fix build with C++20
Date: Wed, 08 Nov 2023 21:34:04 +0100 [thread overview]
Message-ID: <874jhwq91f.fsf@48ers.dk> (raw)
In-Reply-To: <20231104144320.471020b7@windsurf> (Thomas Petazzoni via buildroot's message of "Sat, 4 Nov 2023 14:43:20 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> Hello Michael,
> On Fri, 3 Nov 2023 12:16:12 +0100
> Michael Nosthoff via buildroot <buildroot@buildroot.org> wrote:
>> websocketpp had some ill-formed usage of template parameters which was
>> finally removed in C++20. Hence build fails when building with C++20 support
>> enabled.
>>
>> The patch is already in the develop branch but no new release was done.
>>
>> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
>> ---
>> .../websocketpp/0001-fix_cpp20_build.patch | 108 ++++++++++++++++++
>> 1 file changed, 108 insertions(+)
>> create mode 100644 package/websocketpp/0001-fix_cpp20_build.patch
> Thanks a lot, I have extended the commit log with the very useful
> details you provided as a reply to my question, and applied to master.
> Thanks!
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-08 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 11:16 [Buildroot] [PATCH] package/websocketpp: fix build with C++20 Michael Nosthoff via buildroot
2023-11-03 19:31 ` Thomas Petazzoni via buildroot
2023-11-03 20:54 ` Michael Nosthoff via buildroot
2023-11-04 13:43 ` Thomas Petazzoni via buildroot
2023-11-08 20:34 ` 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=874jhwq91f.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ryan.barnett@collins.com \
--cc=thomas.petazzoni@bootlin.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