All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org,
	Marcus Folkesson <marcus.folkesson@gmail.com>,
	Kamel Bouhara <kamel.bouhara@gmail.com>,
	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 v2 1/3] package/{python-}protobuf: bump to version 28.1
Date: Mon, 28 Oct 2024 21:11:03 +0100	[thread overview]
Message-ID: <20241028211103.67456028@windsurf> (raw)
In-Reply-To: <CADvTj4poUTwYNeVK63EkZHKyYZ9BWAnVMNv9jOxcd-0guH+wAQ@mail.gmail.com>

Hello James,

On Sun, 27 Oct 2024 20:57:32 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> > make[1]: *** [Makefile:1567: protoc-c/protoc_gen_c-c_bytes_field.o] Error 1
> > make[1]: Leaving directory '/home/thomas/projets/buildroot/output/build/host-protobuf-c-1.5.0'
> > make: *** [package/pkg-generic.mk:289: /home/thomas/projets/buildroot/output/build/host-protobuf-c-1.5.0/.stamp_built] Error 2
> >
> > This is on a Fedora 39 system, gcc 13.x.
> >
> > Could you have a look? Also Michael Nosthoff reported a separate
> > (weird) pkg-config issue.  
> 
> Yeah, there's a pending PR that appear to fix this:
> https://github.com/protobuf-c/protobuf-c/pull/711

Which of the two issues is this fixing? I was reporting a build
failure, and Michael Nosthoff was reporting a build hang in pkg-config.

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

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  2:39 [Buildroot] [PATCH v2 1/3] package/{python-}protobuf: bump to version 28.1 James Hilliard
2024-09-24  2:39 ` [Buildroot] [PATCH v2 2/3] package/libabseil-cpp: bump to version 20240722.0 James Hilliard
2024-10-26 14:28   ` Thomas Petazzoni via buildroot
2024-09-24  2:39 ` [Buildroot] [PATCH v2 3/3] package/grpc: bump to version 1.66.1 James Hilliard
2024-10-23  7:49 ` [Buildroot] [PATCH v2 1/3] package/{python-}protobuf: bump to version 28.1 Michael Nosthoff via buildroot
2024-10-28  2:40   ` James Hilliard
2024-10-26 14:27 ` Thomas Petazzoni via buildroot
2024-10-28  2:57   ` James Hilliard
2024-10-28 20:11     ` Thomas Petazzoni via buildroot [this message]
2024-10-28 20:21       ` James Hilliard
2024-10-28 20:53         ` Thomas Petazzoni via buildroot
2024-10-28 20:54           ` James Hilliard
2024-10-28 20:25       ` Michael Nosthoff via buildroot

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=20241028211103.67456028@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --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=thomas.petazzoni@bootlin.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.