From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build error for nptl with no-mmu (arm7tdmi)
Date: Sun, 28 Jul 2013 14:32:56 +0800 [thread overview]
Message-ID: <1374993176.3762.1.camel@phoenix> (raw)
hi list,
In my config, I have
# ARCH_HAS_MMU is not set.
I got below build error (I got the same error on both buildroot-2013.05 and current git tree):
AS libpthread/nptl/sysdeps/unix/sysv/linux/arm/clone.os
AS libpthread/nptl/sysdeps/unix/sysv/linux/arm/vfork.os
CC libpthread/nptl/sysdeps/unix/sysv/linux/arm/fork.os
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
make[1]: Leaving directory `/opt/test/buildroot/buildroot-2013.05/output/toolchain/uClibc-0.9.33.2'
make: *** [/opt/test/buildroot/buildroot-2013.05/output/toolchain/uClibc-0.9.33.2/lib/libc.a] Error 2
Any idea how to fix this?
Regards,
Axel
next reply other threads:[~2013-07-28 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 6:32 Axel Lin [this message]
2013-07-28 8:14 ` [Buildroot] Build error for nptl with no-mmu (arm7tdmi) Axel Lin
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=1374993176.3762.1.camel@phoenix \
--to=axel.lin@ingics.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 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.