From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] assimp: fix pthread linking
Date: Tue, 4 Oct 2016 21:46:05 +0200 [thread overview]
Message-ID: <20161004214605.65fc336e@gmx.net> (raw)
In-Reply-To: <1474839222-26976-1-git-send-email-ps.report@gmx.net>
On Sun, 25 Sep 2016 23:33:42 +0200, Peter Seiderer <ps.report@gmx.net> wrote:
> Fixes [1]:
>
> [100%] Linking CXX executable ../../bin/assimp
> /home/test/autobuild/run/instance-2/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-uclinux-uclibcgnueabi/5.4.0/../../../../arm-buildroot-uclinux-uclibcgnueabi/lib/libstdc++.a(guard.o): In function `(anonymous namespace)::get_static_cond()':
> guard.cc:(.text._ZN12_GLOBAL__N_115get_static_condEv+0x6): undefined reference to `pthread_once'
> ...
>
> [1] http://autobuild.buildroot.net/results/c10/c10886686a0d29877004a0afe2106a77aa2f2ba0
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/assimp/assimp.mk | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/package/assimp/assimp.mk b/package/assimp/assimp.mk
> index cda02dd..fecf6d7 100644
> --- a/package/assimp/assimp.mk
> +++ b/package/assimp/assimp.mk
> @@ -18,4 +18,8 @@ endif
>
> ASSIMP_CONF_OPTS += -DASSIMP_BUILD_TESTS=OFF -DCMAKE_CXX_FLAGS="$(TARGET_CXXFLAGS) $(ASSIMP_CXXFLAGS)"
>
> +ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
> +ASSIMP_CONF_OPTS += -DCMAKE_EXE_LINKER_FLAGS="-pthread"
> +endif
> +
> $(eval $(cmake-package))
Waldemar is sure this is a uClibc-ng failure and will be fixed with update to
uClibc-ng 1.0.18 (as stated for similar failure of powertop, see [2]), will
defer this patch in patchwork...
Regards,
Peter
next prev parent reply other threads:[~2016-10-04 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 21:33 [Buildroot] [PATCH v1] assimp: fix pthread linking Peter Seiderer
2016-10-04 19:46 ` Peter Seiderer [this message]
2016-10-04 19:49 ` Peter Seiderer
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=20161004214605.65fc336e@gmx.net \
--to=ps.report@gmx.net \
--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.