From: Florian Fainelli <florian@openwrt.org>
To: musl@lists.openwall.com
Cc: Isaac Dunham <idunham@lavabit.com>, openwrt-devel@lists.openwrt.org
Subject: Re: [musl] Support for musl libc in OpenWrt
Date: Sun, 25 Nov 2012 12:46:26 +0100 [thread overview]
Message-ID: <201211251246.27100.florian@openwrt.org> (raw)
In-Reply-To: <20121123221533.eb6d941c.idunham@lavabit.com>
Le samedi 24 novembre 2012 07:15:33, Isaac Dunham a écrit :
> On Fri, 23 Nov 2012 21:10:33 +0100
>
> Florian Fainelli <florian@openwrt.org> wrote:
> > Hi All,
> >
> > Support for musl libc in OpenWrt has been added in revision r34314,
>
> Glad to hear it!
>
> > Note that the following issues are known:
> >
> > - unable to complete libstdc++ build due to some missing declarations
> > (WIP)
>
> Are you using the default "linux-gnu" libstdc++, or the "generic" target?
> Only the latter is known to work at this point.
It is the linux-gnu libstdc++, we do not support building the "generic" one
yet, might be worth supporting it now.
>
> > - MIPS and MIPSel ports are not functionnal (details below)
> >
> > --
> > MIPS and MIPSel specific issues:
> >
> > using qemu's binary emulation (qemu-mips[el]) against a statically
> > linked binary works, a dynamic binary makes my host qemu segv. Using
> > qemu-system-mips[el], the binary segfaults while being executed by the
> > kernel. So far I have not had the time to debug this further.
>
> There are likely other issues, but are you using a hardfloat-compatible
> kernel (FPU emulation enabled)?
No, we have patched the kernel do disable the hardware FPU emulation, which
was actually the issue, because musl setjmp MIPS-specific code tried to access
Cop1 registers. After patching setjmp not to access these it works flawlessly
on MIPS (big-endian) but MIPS (little-endian) still segfaults while being
executed either from the kernel or qemu-mipsel.
> At present, musl/mips relies on certain
> instructions that the kernel ordinarily emulates when they aren't
> supported.
You mean ll/sc right? I build for MIPS32r2 so this should not be an issue.
--
Florian
next prev parent reply other threads:[~2012-11-25 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 20:10 Florian Fainelli
2012-11-23 22:19 ` Szabolcs Nagy
2012-11-23 22:52 ` Florian Fainelli
2012-11-24 6:15 ` Isaac Dunham
2012-11-24 10:01 ` Szabolcs Nagy
2012-11-25 11:46 ` Florian Fainelli [this message]
2012-11-25 13:37 ` [musl] " Szabolcs Nagy
2012-11-25 18:41 ` Re: [OpenWrt-Devel] " John Spencer
2012-11-25 19:29 ` Florian Fainelli
2012-12-01 4:15 ` Rich Felker
2012-12-01 9:16 ` Florian Fainelli
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=201211251246.27100.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
--cc=openwrt-devel@lists.openwrt.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).