All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-03-04
Date: Sun, 5 Mar 2017 09:53:51 +0100	[thread overview]
Message-ID: <20170305085351.GC1819@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170305094814.7fd9ae85@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> /home/test/autobuild/run/instance-2/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/lib/libintl.a(loadmsgcat.o): In function `_nl_load_domain':
> loadmsgcat.c:(.text+0x36): undefined reference to `pthread_mutex_lock'
> loadmsgcat.c:(.text+0xfc): undefined reference to `pthread_mutex_unlock'
> 
> That's the usual deal of libintl using pthread functions, which causes
> issues in static linking scenarios. There was this story that glibc
> provides dummy pthread functions in libc, and the real ones in
> libpthread, so that if you don't link with pthread, you don't use the
> slow thread-aware versions.
> 
> But since static linking is only with musl/uclibc anyway, and they now
> all use a single-library approach that doesn't matter. I guess this
> error still occurs because the ARC pre-built toolchain uses a uClibc
> version that predates the merge-them-all-into-libc change.
> 
> Waldemar, do you confirm ?

Yes, I hope they finally update to latest, soon :/
Don't know if they have a reason to build with the last
non-merge-them-all-into-libc change.
 
best regards
 Waldemar

  reply	other threads:[~2017-03-05  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05  7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-04 Thomas Petazzoni
2017-03-05  8:48 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-03-05  8:53   ` Waldemar Brodkorb [this message]
2017-03-05  9:09   ` Yann E. MORIN
2017-03-05 14:10     ` Yann E. MORIN

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=20170305085351.GC1819@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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.