From: Sangjung <sangjung.woo@samsung.com>
To: buildroot@busybox.net
Subject: [Buildroot] NPTL compile error without MMU (ARM)
Date: Thu, 27 Mar 2014 15:33:41 +0900 [thread overview]
Message-ID: <5333C645.8000203@samsung.com> (raw)
Dear developers.
Hi. I found out that nptl make a compile error when MMU (i.e. 'Toolchain
- Enable MMU support') is disabled.
Detailed error message is as below.
--------------------------------------------------------------------------------
In file included from
libpthread/nptl/sysdeps/unix/sysv/linux/arm/fork.c:31:0:
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:61:17: error:
'fork' undeclared here (not in a function)
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:63:1: error:
'__libc_fork' redeclared as different kind of symbol
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:61:23: note:
previous declaration of '__libc_fork' was here
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:228:1: error:
'fork' redeclared as different kind of symbol
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:227:1: note:
previous declaration of 'fork' was here
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:229:1: error:
'__EI_fork' aliased to undefined symbol '__GI_fork'
make[1]: *** [libpthread/nptl/sysdeps/unix/sysv/linux/arm/fork.os] Error 1
--------------------------------------------------------------------------------
This problem is already reported by Axel Lin.
(Link: http://lists.uclibc.org/pipermail/uclibc-cvs/2013-May/031094.html)
However, it looks like that this issue is not solved for a long time.
If someone let me know the alternative solution, I'd be really happy.
Thank you in advances.
BRs,
Sangjung
next reply other threads:[~2014-03-27 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 6:33 Sangjung [this message]
2014-03-27 6:40 ` [Buildroot] NPTL compile error without MMU (ARM) Thomas Petazzoni
2014-03-27 7:11 ` Sangjung
2014-03-27 7:21 ` Thomas Petazzoni
2014-03-27 14:48 ` Sangjung Woo
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=5333C645.8000203@samsung.com \
--to=sangjung.woo@samsung.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