From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-05
Date: Sat, 10 Sep 2016 15:27:35 +0200 [thread overview]
Message-ID: <f085357f-93a2-1496-725f-e7b0404f43b7@gmail.com> (raw)
In-Reply-To: <20160906063034.C474D1028BB@stock.ovh.net>
Hi Thomas, Waldemar,
Le 06/09/2016 ? 08:30, Thomas Petazzoni a ?crit :
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2016-09-05, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Build failures related to your packages:
>
> bfin | xenomai-2.6.4 | http://autobuild.buildroot.net/results/fcae0611ac87204ab68d6828276b635d1a31a178
>
I think it's an issue between uClibc-ng and Xenomai on Blackfin due to
pthread_atfork(), shm_open() and shm_unlink() local definition in Xenomai.
Error:
bind.c:(.text+0x20): multiple definition of `pthread_atfork'
.libs/libxenomai_la-assert_context.o:assert_context.c:(.text+0x54): first
defined here
sem_heap.c:(.text+0xc): multiple definition of `shm_open'
.libs/libxenomai_la-bind.o:bind.c:(.text+0x2c): first defined here
sem_heap.c:(.text+0x24): multiple definition of `shm_unlink'
.libs/libxenomai_la-bind.o:bind.c:(.text+0x44): first defined here
It's because the Xenomai definition use declare these function as "inline" and
not uClibc-ng
Xenomai [1]:
/* uClibc does not provide pthread_atfork() for this arch; provide it
here. Note: let the compiler decides whether it wants to actually
inline this routine, i.e. do not force always_inline. */
inline __attribute__((weak)) int pthread_atfork(void (*prepare)(void),
void (*parent)(void),
void (*child)(void))
uClibc-ng:
extern int pthread_atfork (void (*__prepare) (void),
void (*__parent) (void),
void (*__child) (void)) __THROW;
I guess those "inline" should be removed?
Weldemar what do you think?
Best regards,
Romain
[1] xenomai/include/asm-blackfin/syscall.h
next parent reply other threads:[~2016-09-10 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160906063034.C474D1028BB@stock.ovh.net>
2016-09-10 13:27 ` Romain Naour [this message]
[not found] ` <20160910135635.GH6777@waldemar-brodkorb.de>
2016-09-10 15:45 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-05 Romain Naour
[not found] ` <9a18dc1c-25bd-0925-1a78-dc7a5612d465@gmail.com>
[not found] ` <20160911133437.GI6777@waldemar-brodkorb.de>
2016-09-13 6:56 ` Romain Naour
2016-11-05 17:12 ` Romain Naour
2016-11-05 17:17 ` Waldemar Brodkorb
2016-11-05 18:57 ` Romain Naour
[not found] <20160906063035.18941102741@stock.ovh.net>
2016-09-07 9:13 ` Chris Packham
2016-09-07 9:21 ` Yann E. MORIN
2016-09-07 9:44 ` Thomas Petazzoni
2016-09-07 9:28 ` Thomas Petazzoni
2016-09-08 8:07 ` Chris Packham
2016-09-08 9:43 ` Peter Korsgaard
2016-09-08 10:07 ` Chris Packham
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=f085357f-93a2-1496-725f-e7b0404f43b7@gmail.com \
--to=romain.naour@gmail.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