Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
Date: Sat, 18 Aug 2018 22:20:10 +0200	[thread overview]
Message-ID: <20180818222010.17f19f75@windsurf> (raw)
In-Reply-To: <CAPi7W808osYXWuNs8URXOdOix6eP4P46+ESrH+DuaR6syRLz5A@mail.gmail.com>

Hello,

On Sat, 18 Aug 2018 22:09:13 +0200, Fabrice Fontaine wrote:

> OK, this last one is easy, azmq selects BOOST_LOG but BOOST_LOG depends on
> !(BR2_powerpc && BR2_TOOLCHAIN_USES_UCLIBC):
> 
> warning: (BR2_PACKAGE_AZMQ) selects BR2_PACKAGE_BOOST_LOG which has unmet
> direct dependencies (BR2_PACKAGE_BOOST && BR2_TOOLCHAIN_HAS_THREADS_NPTL &&
> (!BR2_powerpc || !BR2_TOOLCHAIN_USES_UCLIBC))
> 
> I will fix this by removing the dependency on !(BR2_powerpc &&
> BR2_TOOLCHAIN_USES_UCLIBC) from BOOST_LOG as it seems that boost-log builds
> fine on powerpc with uclibc nowadays.

OK. This was added by me in commit
7aaa9bee2e6009c6c00fa2a356b8f014999e9a54. There was no clear
explanation of the problem, it was just "it doesn't build, and nobody
cares". And it was 3 years ago, so there are high chances that the
problem has been fixed either in uClibc or in Boost. So let's try to
remove this dependency indeed. Waiting for your patch!

(BTW, you still haven't joined IRC! :-))

Thanks!

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

      reply	other threads:[~2018-08-18 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 22:10 [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS Fabrice Fontaine
2018-08-17 22:10 ` [Buildroot] [PATCH v2, 2/2] boost: thread needs atomic if GCC hasn't lock-free Fabrice Fontaine
2018-08-18 15:49 ` [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS Thomas Petazzoni
2018-08-18 19:29   ` Thomas Petazzoni
2018-08-18 20:09     ` Fabrice Fontaine
2018-08-18 20:20       ` 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=20180818222010.17f19f75@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox