Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/protobuf: depend on gcc >= 4.5
Date: Sat, 29 Apr 2017 14:31:36 +0200	[thread overview]
Message-ID: <20170429143136.3da63d52@free-electrons.com> (raw)
In-Reply-To: <20170426162850.5214-1-mrugiero@gmail.com>

Hello,

On Wed, 26 Apr 2017 13:28:50 -0300, mrugiero at gmail.com wrote:
> From: "Mario J. Rugiero" <mrugiero@gmail.com>
> 
> Protobuf hits a bug in gcc < 4.5 which breaks the build.
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=189

This bug is marked as FIXED, and it has been fixed since many years.

What is the actual problem you are seeing? Is there a reference to an
autobuilder issue?

I've tried to build with gcc 4.3, and indeed I'm getting:

./google/protobuf/metadata.h: In constructor 'google::protobuf::internal::InternalMetadataWithArena::InternalMetadataWithArena(google::protobuf::Arena*)':
./google/protobuf/metadata.h:175: error: class 'google::protobuf::internal::InternalMetadataWithArena' does not have any field named 'InternalMetadataWithArenaBase'
./google/protobuf/metadata.h: In constructor 'google::protobuf::internal::InternalMetadataWithArenaLite::InternalMetadataWithArenaLite(google::protobuf::Arena*)':
./google/protobuf/metadata.h:204: error: class 'google::protobuf::internal::InternalMetadataWithArenaLite' does not have any field named 'InternalMetadataWithArenaBase'

Is this the issue we're talking about ?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-29 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 16:28 [Buildroot] [PATCH] package/protobuf: depend on gcc >= 4.5 mrugiero at gmail.com
2017-04-29 12:31 ` Thomas Petazzoni [this message]
2017-04-29 14:54   ` Mario Rugiero
2017-04-29 20:02     ` Mario Rugiero
2017-04-30  7:29       ` Thomas Petazzoni
2017-05-01  4:57         ` Mario Rugiero
2017-05-02  1:43           ` Matthew Weber
2017-05-02 12:03             ` Thomas Petazzoni
2017-05-02 15:04               ` Mario Rugiero

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=20170429143136.3da63d52@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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