All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Nosthoff via buildroot <buildroot@buildroot.org>
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>,
	Kamel Bouhara <kamel.bouhara@gmail.com>,
	buildroot@buildroot.org,
	Marcin Niestroj <m.niestroj@grinn-global.com>,
	Asaf Kahlon <asafka7@gmail.com>, Julien Olivain <ju.o@free.fr>,
	Woodrow Douglass <wdouglass@carnegierobotics.com>,
	Christian Stewart <christian@aperture.us>,
	Robert Rose <robertroyrose@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot]  [PATCH v3 1/4] package/{python-}protobuf: bump to version 28.1
Date: Mon, 28 Oct 2024 21:35:08 +0100	[thread overview]
Message-ID: <5109d-671ff580-3-4946930@44461145> (raw)
In-Reply-To: <20241028025410.62158-1-james.hilliard1@gmail.com>

Hi James,

On Monday, October 28, 2024 03:54 CET, James Hilliard <james.hilliard1@gmail.com> wrote:

> Migrate protobuf build from autotools to cmake.
> 
> Migrate protobuf-python to use pypi sources which are now required
> for setup.py builds:
> https://github.com/protocolbuffers/protobuf/tree/v28.1/python#building-from-setuppy
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---

with this series I can now build protobuf-c successfully.

The packages I now see issues with are mosh and collectd.

For mosh the error message is:

 119 | static_assert(PROTOBUF_CPLUSPLUS_MIN(201402L), "Protobuf only supports C++14 and newer.");

this is already addressed upstream: https://github.com/mobile-shell/mosh/commit/eee1a8cf413051c2a9104e8158e699028ff56b26
So we could cherry pick this patch (which raises the required C++ Version to 17) or could alter the package to build in C++14 mode...

For collectd it does find grpc but for some reason fails to find the correct protoc version:

checking for protobuf... yes
checking for main in -lprotobuf... yes
checking for google/protobuf/util/time_util.h... yes
checking for protoc... /build/buildroot/output/host/bin/protoc
checking for protoc 3.0.0+... no (libprotoc 28.1)
checking for libprotobuf-c... yes
checking for protobuf_c_message_pack in -lprotobuf-c... yes
checking for protobuf-c/protobuf-c.h... yes
checking for protoc-c... /build/buildroot/output/host/bin/protoc-c
....
grpc  . . . . . . . . no (protoc3 not found) (dependency error)

not sure what is going wrong there.

this is what I found in a short compile test...

used defconfig:

BR2_arm=y
BR2_cortex_a15=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_PACKAGE_OLA=y
BR2_PACKAGE_USBGUARD=y
BR2_PACKAGE_COLLECTD=y
BR2_PACKAGE_COLLECTD_GRPC=y
BR2_PACKAGE_KISMET=y
BR2_PACKAGE_MOSH=y
BR2_PACKAGE_CRIU=y

Regards,
Michael

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-10-28 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28  2:54 [Buildroot] [PATCH v3 1/4] package/{python-}protobuf: bump to version 28.1 James Hilliard
2024-10-28  2:54 ` [Buildroot] [PATCH v3 2/4] package/grpc: bump to version 1.66.1 James Hilliard
2024-10-28  2:54 ` [Buildroot] [PATCH v3 3/4] package/pkgconf: bump to version 2.3.0 James Hilliard
2024-10-28  2:54 ` [Buildroot] [PATCH v3 4/4] package/protobuf-c: fix protobuf >= 26.0 compatibility James Hilliard
2024-10-28 20:35 ` Michael Nosthoff 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=5109d-671ff580-3-4946930@44461145 \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=buildroot@heine.tech \
    --cc=christian@aperture.us \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=kamel.bouhara@gmail.com \
    --cc=m.niestroj@grinn-global.com \
    --cc=marcus.folkesson@gmail.com \
    --cc=robertroyrose@gmail.com \
    --cc=wdouglass@carnegierobotics.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.