From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-26
Date: Tue, 28 Feb 2017 15:34:56 +0000 [thread overview]
Message-ID: <1488296096.2557.13.camel@synopsys.com> (raw)
In-Reply-To: <20170227142854.34d3fb86@free-electrons.com>
Hi Thomas,
On Mon, 2017-02-27 at 14:28 +0100, Thomas Petazzoni wrote:
> >????????? arc |???????????????????? mpd-0.20.4 | NOK ?
>
> Lacks a -lpthread apparently:
>
> /home/peko/autobuild/instance-1/output/host/opt/ext-toolchain/bin/../lib/gcc/arc-snps-linux-
> uclibc/6.2.1/../../../../arc-snps-linux-uclibc/bin/ld: libthread.a(Thread.o): undefined reference to symbol
> 'pthread_create'
> /home/peko/autobuild/instance-1/output/host/usr/arc-buildroot-linux-uclibc/sysroot/lib/libpthread.so.0: error adding
> symbols: DSO missing from command line
>
> but the configure script fails to detect thread support:
>
> checking for the pthreads library -lpthread... no
>
> Aah, they test if the compiler defines _REENTRANT:
>
> conftest.c:15:26: error: #error "_REENTRANT must be defined"
> ?#??????????????????????? error "_REENTRANT must be defined"
>
> and I know some architectures forget to do so.
>
> I already reported this bug to gcc upstream:
>
> ?https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71749?
>
> Vlad, could you have a look into this? We have
> package/gcc/6.3.0/895-bfin-define-REENTRANT.patch for Blackfin in the
> tree, but we don't have the corresponding patch for ARC.
The patch you have provided in gcc bugzilla solves the issue, thanks.
I am going to send it to Buildroot soon.
If you want to upstream your patch to gcc please send it to GCC mailing list. And please don't forget to include Claudiu
Zissulescu <claziss@synopsys.com>?in CC as he is co-maintainer of GCC port for ARC.
Thanks!
--
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>
next prev parent reply other threads:[~2017-02-28 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-26 Thomas Petazzoni
2017-02-27 13:28 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-27 15:54 ` Yann E. MORIN
2017-02-27 15:57 ` Thomas Petazzoni
2017-02-27 16:54 ` Frank Hunleth
2017-02-27 20:20 ` Thomas Petazzoni
2017-02-27 22:38 ` [Buildroot] Analysis of build results for 2017-02-26: libsidplay issue on PowerPC64 Thomas Petazzoni
2017-02-28 0:41 ` Sam Bobroff
2017-02-27 22:38 ` [Buildroot] Analysis of build results for 2017-02-26: classpath issue Thomas Petazzoni
2017-02-27 23:01 ` [Buildroot] Analysis of build results for 2017-02-26: librsvg failure Thomas Petazzoni
2017-02-28 9:00 ` Peter Korsgaard
2017-02-28 9:05 ` Thomas Petazzoni
2017-02-28 14:16 ` Thomas Petazzoni
2017-02-28 14:48 ` Peter Korsgaard
2017-02-28 15:37 ` Thomas Petazzoni
2017-02-28 16:10 ` Peter Korsgaard
2017-02-28 15:34 ` Vlad Zakharov [this message]
2017-02-28 16:02 ` [Buildroot] Analysis of build results for 2017-02-26 Thomas Petazzoni
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=1488296096.2557.13.camel@synopsys.com \
--to=vladislav.zakharov@synopsys.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