From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10996] New: bogus musl ARM toolchain
Date: Tue, 08 May 2018 12:41:04 +0000 [thread overview]
Message-ID: <bug-10996-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10996
Bug ID: 10996
Summary: bogus musl ARM toolchain
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: thomas.petazzoni at free-electrons.com
CC: buildroot at uclibc.org
Target Milestone: ---
The following defconfig doesn't build:
BR2_arm=y
BR2_cortex_a8=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_BUILDROOT_MUSL=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
BR2_PACKAGE_ZIP=y
# BR2_TARGET_ROOTFS_TAR is not set
It doesn't build because the toolchain is broken, and doesn't manage to link a
simple program like this:
$ cat foo.c
int main(void) { mktime(); return 0; }
./output/host/bin/arm-linux-gcc -o foo foo.c
foo.c: In function ?main?:
foo.c:1:18: warning: implicit declaration of function ?mktime?
[-Wimplicit-function-declaration]
int main(void) { mktime(); return 0; }
^~~~~~
/home/thomas/projets/buildroot/output/host/lib/gcc/arm-buildroot-linux-musleabihf/6.4.0/libgcc.a(_dvmd_lnx.o):
In function `__aeabi_idiv0':
/home/thomas/projets/buildroot/output/build/host-gcc-final-6.4.0/build/arm-buildroot-linux-musleabihf/libgcc/../../../libgcc/config/arm/lib1funcs.S:1354:
undefined reference to `raise'
collect2: error: ld returned 1 exit status
This is causing the following build issues in our autobuilders:
http://autobuild.buildroot.net/?reason=zip%&libc=musl.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-05-08 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:41 bugzilla at busybox.net [this message]
2018-05-11 15:53 ` [Buildroot] [Bug 10996] bogus musl ARM toolchain bugzilla at busybox.net
2018-05-13 20:05 ` bugzilla at busybox.net
2018-05-13 20:16 ` bugzilla at busybox.net
2018-08-14 20:25 ` bugzilla at busybox.net
2018-08-14 22:31 ` bugzilla at busybox.net
2018-08-15 11:38 ` 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-10996-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