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 v2] package: protobuf, python-protobuf: bump to v3.3.0
Date: Fri, 5 May 2017 20:20:49 +0200	[thread overview]
Message-ID: <20170505202049.643d7041@free-electrons.com> (raw)
In-Reply-To: <CAKKQwLQWLytghCPeEWWjMsLw2vrcL-DumzWcevz2Dz+uwE0HGQ@mail.gmail.com>

Hello,

On Fri, 5 May 2017 14:24:00 -0300, Mario Rugiero wrote:

> I fixed that particular issue in my local copy, but fails because
> Atomic32 is not supported in that toolchain.
> Do you know if there is any similar toolchain with such support?
> Otherwise, how should I fix that?

What error do you have exactly?

Something like an undefined reference to some __atomic_*() function? If
so, then make sure you link with -latomic.

Best regards,

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

  reply	other threads:[~2017-05-05 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 20:59 [Buildroot] [PATCH v2] package: protobuf, python-protobuf: bump to v3.3.0 Mario J. Rugiero
2017-05-04 12:56 ` Thomas Petazzoni
2017-05-04 13:34   ` Mario Rugiero
2017-05-05 17:24     ` Mario Rugiero
2017-05-05 18:20       ` Thomas Petazzoni [this message]
2017-05-05 18:27         ` Mario Rugiero
2017-05-11 21:00 ` Thomas Petazzoni
2017-05-12  7:35   ` Mario J. Rugiero
2017-05-12  8:07     ` Thomas Petazzoni
2017-05-12  8:13       ` Mario Rugiero
2017-05-12 20:01         ` Mario Rugiero
2017-07-02  8:31     ` Thomas Petazzoni

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=20170505202049.643d7041@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