Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] protobuf: fix detection of __atomic_*() built-ins
Date: Wed, 10 Feb 2016 16:42:27 -0200 (BRST)	[thread overview]
Message-ID: <1240623306.1965860.1455129747228.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20160210165037.1b02b8ee@free-electrons.com>

[Thanks, Zimbra, for messing rearranging the messages in the inbox, so I answer them in the wrong order].

> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: buildroot at buildroot.org, "henrique marks" <henrique.marks@datacom.ind.br>
> Sent: Wednesday, February 10, 2016 1:50:37 PM
> Subject: Re: [PATCH 1/1] protobuf: fix detection of __atomic_*() built-ins

> Hello,
> 
> Thanks, this looks good, with one nit, see below.
> 
> On Wed, 10 Feb 2016 13:33:12 -0200, Carlos Santos wrote:
> 
>> diff --git
>> a/package/protobuf/0002-configure.ac-check-if-libatomic-is-needed.patch
>> b/package/protobuf/0002-configure.ac-check-if-libatomic-is-needed.patch
>> new file mode 100644
>> index 0000000..237bc71
>> --- /dev/null
>> +++ b/package/protobuf/0002-configure.ac-check-if-libatomic-is-needed.patch
>> @@ -0,0 +1,34 @@
>> +From 0883fa19d59ece19eec30937c65fd10162ef57b0 Mon Sep 17 00:00:00 2001
>> +From: Carlos Santos <casantos@datacom.ind.br>
>> +Date: Wed, 10 Feb 2016 12:54:43 -0200
>> +Subject: [PATCH] configure.ac: check if libatomic is needed
>> +
>> +In Buildroot, to simplify things, we've decided to simply require gcc 4.8
>> +as soon as the architectures has at least one __atomic_*() built-in
>> +variant that requires libatomic.
>> +
>> +Since protobuf most likely only uses the 1, 2 and 4-byte variants, it
>> +*could* technically build with gcc 4.7. This is probably not a big deal,
>> +and we can live with requiring gcc 4.8 on PowerPC to build protobuf.
>> +
>> +Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> 
> The patch description should not mention Buildroot and not mention
> Buildroot specific choices. It should be written as if you were going
> to submit it upstream, i.e with a proper justification as to why
> linking with libatomic may be needed.

This patch only exists to appease Buildroot but, anyway, I can rewrite the comment.

> And in fact, I'm even going to ask you to submit this patch upstream :-)

They don't need this. Their detection of the atomic built-ins already works without additional help.

Carlos Santos (Casantos)
DATACOM, P&D

  reply	other threads:[~2016-02-10 18:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 13:08 [Buildroot] [PATCH 1/1] protobuf: apply patch to compile for PowerPC Carlos Santos
2016-02-04 23:06 ` Thomas Petazzoni
2016-02-05 11:04   ` Henrique Marks
2016-02-05 13:09     ` Thomas Petazzoni
2016-02-05 13:22       ` Henrique Marks
2016-02-05 13:37         ` Thomas Petazzoni
2016-02-07 21:19         ` Thomas Petazzoni
2016-02-10 15:25   ` Carlos Santos
2016-02-10 15:57     ` Thomas Petazzoni
2016-02-10 16:32       ` Carlos Santos
2016-02-10 16:44         ` Thomas Petazzoni
2016-02-10 16:50           ` Carlos Santos
2016-02-10 18:30           ` Carlos Santos
2016-02-10 20:13             ` Thomas Petazzoni
2016-02-11 15:14               ` Carlos Santos
2016-02-10 15:33 ` [Buildroot] [PATCH 1/1] protobuf: fix detection of __atomic_*() built-ins Carlos Santos
2016-02-10 15:50   ` Thomas Petazzoni
2016-02-10 18:42     ` Carlos Santos [this message]
2016-02-10 20:06       ` Arnout Vandecappelle
2016-02-10 20:00   ` Arnout Vandecappelle
2016-02-11 14:56     ` Carlos Santos
2016-02-11 15:23   ` Carlos Santos
2016-02-17 17:43     ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 17:43       ` [Buildroot] [PATCH v2 1/1] " Carlos Santos
2016-02-27 21:55         ` Arnout Vandecappelle
2016-03-20 22:43         ` Thomas Petazzoni
2016-02-17 18:33       ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 20:51         ` 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=1240623306.1965860.1455129747228.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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