From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7562] New: musl buildroot-toolchain and BR2_MIPS_SOFT_FLOAT break
Date: Sun, 26 Oct 2014 18:19:11 +0000 (UTC) [thread overview]
Message-ID: <bug-7562-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7562
Summary: musl buildroot-toolchain and BR2_MIPS_SOFT_FLOAT break
Product: buildroot
Version: 2014.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: alex+buildroot at digriz.org.uk
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I use the following settings:
BR2_mipsel=y
BR2_TOOLCHAIN_BUILDROOT_MUSL=y
BR2_MIPS_SOFT_FLOAT=y
Even trying to run busybox fails as ld-musl-mipsel.so.1 does not exist. Some
digging around I found that ld-musl-mipsel-sf.so.1 does, I am guessing 'sf'
stands for "soft float".
To workaround the problem, I slipped into my post-build.sh script the
following:
----
ln -f -s /lib/libc.so "$1/lib/ld-musl-mipsel.so.1"
----
That gets things working again. Not should how this should actually be fixed,
otherwise I would submit a patch.
Let me know if you need anything from me to help get this fixed.
--
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:[~2014-10-26 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 18:19 bugzilla at busybox.net [this message]
2014-11-07 7:37 ` [Buildroot] [Bug 7562] musl buildroot-toolchain and BR2_MIPS_SOFT_FLOAT break bugzilla at busybox.net
2014-11-09 10:33 ` bugzilla at busybox.net
2014-11-09 13:23 ` bugzilla at busybox.net
2016-03-10 22:20 ` 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-7562-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 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.