All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libselinux: host gcc at least 4.7
Date: Mon, 13 Aug 2018 18:51:58 +0200	[thread overview]
Message-ID: <20180813185158.6658248e@windsurf> (raw)
In-Reply-To: <20180813150559.guf6i4qh6vogmwhl@sapphire.tkos.co.il>

Hello,

On Mon, 13 Aug 2018 18:05:59 +0300, Baruch Siach wrote:

> No. I mean all host and target packages that have host-libselinux in their 
> _DEPENDENCIES. Otherwise, enabling any of them would cause a build of 
> host-libselinux regardless of the Config.in dependency.
> 
> Isn't it easier to apply the alternative patch that uses the older __sync 
> routines for older gcc?

Is it would be much easier. The question is: is this patch correct ? I
am not super familiar with the semantic of those atomic operations, so
I'm not super confident in reviewing Hollis proposal. But if you think
Hollis patch is correct, a Acked-by or Reviewed-by on it would be good.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-08-13 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 14:33 [Buildroot] [PATCH] package/libselinux: host gcc at least 4.7 Matt Weber
2018-08-13 14:47 ` Baruch Siach
2018-08-13 14:50   ` Matthew Weber
2018-08-13 14:54     ` Baruch Siach
2018-08-13 14:56       ` Matthew Weber
2018-08-13 15:01         ` Matthew Weber
2018-08-13 15:05         ` Baruch Siach
2018-08-13 15:18           ` Matthew Weber
2018-08-13 16:51           ` Thomas Petazzoni [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=20180813185158.6658248e@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.