From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Jardin <vjardin@free.fr>
Cc: Vadim Kochan <vadim4j@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/1] package/frr: update to 9.1.1
Date: Tue, 27 Aug 2024 18:33:00 +0200 [thread overview]
Message-ID: <20240827183300.593192bb@windsurf> (raw)
In-Reply-To: <20240826131924.7702-2-vjardin@free.fr>
Hello,
On Mon, 26 Aug 2024 15:19:24 +0200
Vincent Jardin <vjardin@free.fr> wrote:
> Update to the latest 9.x version. Protobuf is now mandatory.
>
> Thanks to the suggestions from Thomas Petazzoni: Since there is
> a dependency on BR2_PACKAGE_PROTOBUF_C, the dependencies of protobuf_c
> should be imported into FRR's Config.in and the comment should be
> aligned accordingly.
> Note that in order to enable FRR, the following must be enabled
> to support C++:
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_FRR=y
This paragraph wasn't really needed, as it's just stating the
"obvious". In addition, it is not true that
BR2_TOOLCHAIN_BUILDROOT_CXX=y is needed. Indeed, this option only
exists if you use an internal/Buildroot toolchain. If you use an
external toolchain, the option name is different. So I simply dropped
this paragraph.
> COPYING hash updated:
> The COPYING file has evolved to expose more details: the respective
> licenses are now listed, except for the GPLv3 license. The GPLv3
> license is only required when FRR is compiled with the GCC plugin
> that extends printf type checks. This plugin should not be enabled
> for production code.
> For more information, see FRR's workflow.rst document.
>
> Signed-off-by: Vincent Jardin <vjardin@free.fr>
> Suggested-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
>
> frr/Config.in: enable CXX
>
> Signed-off-by: Vincent Jardin <vjardin@free.fr>
Here you had some left-over from squashing patches I suppose?
I fixed up those minor details, and applied the patch to our next
branch. Thanks a lot for having persisted through 4 iterations!
Best regards,
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
next prev parent reply other threads:[~2024-08-27 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240823185817.4658f57a () windsurf>
2024-08-25 16:40 ` [Buildroot] [PATCH v3 0/1] package/frr: update to 9.1.1 Vincent Jardin
2024-08-25 16:40 ` [Buildroot] [PATCH v3 1/1] " Vincent Jardin
2024-08-25 16:50 ` [Buildroot] [PATCH v3 0/1] " Vincent Jardin
2024-08-26 13:19 ` [Buildroot] [PATCH v4 " Vincent Jardin
2024-08-26 13:19 ` [Buildroot] [PATCH v4 1/1] " Vincent Jardin
2024-08-27 16:33 ` Thomas Petazzoni via buildroot [this message]
2024-08-27 18:03 ` Vincent Jardin
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=20240827183300.593192bb@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vadim4j@gmail.com \
--cc=vjardin@free.fr \
/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