From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: buildroot@buildroot.org, Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/3] package/collectd: enforce c++17
Date: Mon, 2 Feb 2026 23:15:22 +0100 [thread overview]
Message-ID: <aYEh2bxpSzVWD8cG@windsurf> (raw)
In-Reply-To: <20260107140858.129302-1-buildroot@heine.tech>
On Wed, Jan 07, 2026 at 03:08:45PM +0100, Michael Nosthoff via buildroot wrote:
> abseil since 20250512.0 and hence protobuf/grpc now need C++17.
> collectd in the currently used version sets C++ to 11.
> So bump the C++ Version used when building collectd like it was done
> before to bump it to C++14 in commit 5fcc4e19602ad37d018ccf3543fe82a291837f43
> with patch 0002.
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
I've significantly reworded the commit message, which I believe was
still quite confusing, and then I applied to master. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-02-02 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:08 [Buildroot] [PATCH v2 1/3] package/collectd: enforce c++17 Michael Nosthoff via buildroot
2026-01-07 14:08 ` [Buildroot] [PATCH v2 2/3] package/libabseil-cpp: bump to version 20250814.1 Michael Nosthoff via buildroot
2026-02-02 22:15 ` Thomas Petazzoni via buildroot
2026-01-07 14:08 ` [Buildroot] [PATCH v2 3/3] package/grpc: bump to version 1.76.0 Michael Nosthoff via buildroot
2026-02-02 22:16 ` Thomas Petazzoni via buildroot
2026-02-02 22:15 ` Thomas Petazzoni via buildroot [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=aYEh2bxpSzVWD8cG@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=buildroot@heine.tech \
--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 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.