Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] liburcu: Explicitly add pthread options to cflags
Date: Fri,  9 Mar 2018 03:00:48 -0800	[thread overview]
Message-ID: <20180309110049.10725-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20180309110049.10725-1-raj.khem@gmail.com>

Some architectures e.g. riscv gcc does not add -D_REENTRANT
when enabling pthreads. Help it here by adding these options
while gcc gets fixed

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 meta/recipes-support/liburcu/liburcu_0.10.1.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-support/liburcu/liburcu_0.10.1.bb b/meta/recipes-support/liburcu/liburcu_0.10.1.bb
index 0c8cd3571a..a73890af90 100644
--- a/meta/recipes-support/liburcu/liburcu_0.10.1.bb
+++ b/meta/recipes-support/liburcu/liburcu_0.10.1.bb
@@ -15,3 +15,5 @@ SRC_URI[sha256sum] = "9c09220be4435dc27fcd22d291707b94b97f159e0c442fbcd60c168f8f
 
 S = "${WORKDIR}/userspace-rcu-${PV}"
 inherit autotools
+
+CPPFLAGS  += "-pthread -D_REENTRANT"
-- 
2.16.2



  reply	other threads:[~2018-03-09 11:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 11:00 [PATCH 1/3] packagegroup-core-sdk: Disable SANITIZERS for riscv64 Khem Raj
2018-03-09 11:00 ` Khem Raj [this message]
2018-03-09 15:56   ` [PATCH 2/3] liburcu: Explicitly add pthread options to cflags Richard Purdie
2018-03-09 16:24     ` Khem Raj
2018-03-09 11:00 ` [PATCH 3/3] recipes: Disable lttng for riscv Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2018-03-09 20:28 [PATCH 0/3] Build fixed for riscv64 Khem Raj
2018-03-09 20:29 ` [PATCH 2/3] liburcu: Explicitly add pthread options to cflags Khem Raj

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=20180309110049.10725-2-raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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