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 1/3] package/boost: disable boost-log with bfin uClibc 2014R1 toolchain
Date: Thu, 9 Apr 2015 23:31:50 +0200	[thread overview]
Message-ID: <20150409233150.03226fb5@free-electrons.com> (raw)
In-Reply-To: <1428611020-9329-1-git-send-email-romain.naour@openwide.fr>

Dear Romain Naour,

On Thu,  9 Apr 2015 22:23:38 +0200, Romain Naour wrote:
> pthread_spin_* functions are not implemented in the uClibc used by this toolchain.
> 
> In file included from libs/log/src/threadsafe_queue.cpp:33:
> ./boost/log/detail/spin_mutex.hpp: In constructor ?boost::log::v2_mt_posix::aux::spin_mutex::spin_mutex()?:
> ./boost/log/detail/spin_mutex.hpp:198: error: ?pthread_spin_init? was not declared in this scope
> ./boost/log/detail/spin_mutex.hpp: In destructor ?boost::log::v2_mt_posix::aux::spin_mutex::~spin_mutex()?:
> ./boost/log/detail/spin_mutex.hpp:205: error: ?pthread_spin_destroy? was not declared in this scope
> ./boost/log/detail/spin_mutex.hpp: In member function ?bool boost::log::v2_mt_posix::aux::spin_mutex::try_lock()?:
> ./boost/log/detail/spin_mutex.hpp:210: error: ?pthread_spin_trylock? was not declared in this scope
> ./boost/log/detail/spin_mutex.hpp: In member function ?void boost::log::v2_mt_posix::aux::spin_mutex::lock()?:
> ./boost/log/detail/spin_mutex.hpp:220: error: ?pthread_spin_lock? was not declared in this scope
> ./boost/log/detail/spin_mutex.hpp: In member function ?void boost::log::v2_mt_posix::aux::spin_mutex::unlock()?:
> ./boost/log/detail/spin_mutex.hpp:227: error: ?pthread_spin_unlock? was not declared in this scope

I believe a better option is probably to make this option depend on
BR2_TOOLCHAIN_HAS_THREADS_NPTL. pthread_spin_* are available in
linuxthreads, but not linuxthreads.old apparently, linuxthreads is very
rarely used. So I believe limiting to NPTL thread implementation is a
good enough approximation.

Also, it's probably a bit heavy to do one patch per toolchain version.

>  config BR2_PACKAGE_BOOST_LOG
> -        bool "boost-log"
> +	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2014R1 # missing pthread_spin_* in uClibc.
> +	bool "boost-log"

I've fixed up the indentation as a separate commit. The 'depends on'
line should be after the 'bool' line.

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

      parent reply	other threads:[~2015-04-09 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 20:23 [Buildroot] [PATCH 1/3] package/boost: disable boost-log with bfin uClibc 2014R1 toolchain Romain Naour
2015-04-09 20:23 ` [Buildroot] [PATCH 2/3] package/boost: disable boost-log with bfin uClibc 2013R1 toolchain Romain Naour
2015-04-09 20:23 ` [Buildroot] [PATCH 3/3] package/boost: disable boost-log with bfin uClibc 2012R2 toolchain Romain Naour
2015-04-09 21:31 ` 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=20150409233150.03226fb5@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