From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4249] New: uClibc and libpthread
Date: Fri, 23 Sep 2011 14:52:19 +0000 (UTC) [thread overview]
Message-ID: <bug-4249-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4249
Summary: uClibc and libpthread
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: bachmann at tofwerk.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I compiled a new rootfs for my SAM9-L9260-Board from Olimex.
I used the buildroot-2011.08, with uClibc-0.9.32.
The compiling worked just fine, but when i try to compile my own program on the
Target it failes.
Here the situation which lead to the bug:
My compile command:
g++ -g /TPSController.cpp -llua -ldl -lpthread -o /TPSController
My compile output:
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libc.a(sigprocmask.os):
In function `sigprocmask':
sigprocmask.c:(.text+0x0): multiple definition of `sigprocmask'
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libpthread.a(pt-sigprocmask.os):pt-sigprocmask.c:(.text+0x0):
first defined here
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libc.a(sigaction.os):
In function `__libc_sigaction':
sigaction.c:(.text+0x0): multiple definition of `__libc_sigaction'
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libpthread.a(pt-sigaction.os):pt-sigaction.c:(.text+0x0):
first defined here
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libc.a(sigaction.os):
In function `sigaction':
sigaction.c:(.text+0x84): multiple definition of `__sigaction'
/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.6/../../../libpthread.a(pt-sigaction.os):pt-sigaction.c:(.text+0x84):
first defined here
collect2: ld returned 1 exit status
I've got the same fault even if i try the different thread implementation that
uClibc has. I thought that the NPTL should be fixed in the uClibc-0.9.32
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-09-23 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 14:52 bugzilla at busybox.net [this message]
2011-09-23 15:36 ` [Buildroot] [Bug 4249] uClibc and libpthread bugzilla at busybox.net
2011-09-24 15:50 ` bugzilla at busybox.net
2011-10-06 21:36 ` bugzilla at busybox.net
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=bug-4249-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox