From: <mingli.yu@windriver.com>
To: <raj.khem@gmail.com>, <openembedded-devel@lists.openembedded.org>
Subject: [meta-oe][PATCH] log4cplus: remove gold linker setting
Date: Wed, 31 Jul 2019 00:01:03 -0700 [thread overview]
Message-ID: <20190731070103.34814-1-mingli.yu@windriver.com> (raw)
From: Mingli Yu <mingli.yu@windriver.com>
After commit[3a7abb175 log4cplus: Fix build with gold linker]
applied, with below logic in conf/local.conf
MACHINE ??= "qemumips64"
MULTILIB_GLOBAL_VARIANTS_append = " libn32"
MULTILIBS ?= "multilib:lib32 multilib:libn32"
DEFAULTTUNE_virtclass-multilib-lib32 ?= "mips"
DEFAULTTUNE_virtclass-multilib-libn32 ?= "mips64-n32"
require conf/multilib.conf
There comes below build error:
$ libn32-log4cplus
| checking for the pthreads library -lpthread... no
| configure: error: Requested threads support but no threads were found.
Actually the logic[CXXFLAGS += "-fuse-ld=gold"] is not
needed in commit[3a7abb175 log4cplus: Fix build with gold linker],
so remove it to fix the above build error.
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb b/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
index b396cabf3..566de2853 100644
--- a/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
+++ b/meta-oe/recipes-devtools/log4cplus/log4cplus_2.0.4.bb
@@ -18,5 +18,3 @@ UPSTREAM_CHECK_REGEX = "log4cplus-stable/(?P<pver>\d+(\.\d+)+)/"
inherit autotools pkgconfig
BBCLASSEXTEND = "native"
-
-CXXFLAGS += "-fuse-ld=gold"
--
2.21.0
next reply other threads:[~2019-07-31 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 7:01 mingli.yu [this message]
2019-07-31 7:05 ` [meta-oe][PATCH v2] log4cplus: remove gold linker setting mingli.yu
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=20190731070103.34814-1-mingli.yu@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.