[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121123221533.eb6d941c.idunham@lavabit.com>
Date: Fri, 23 Nov 2012 22:15:33 -0800
From: Isaac Dunham <idunham@...abit.com>
To: musl@...ts.openwall.com
Cc: Florian Fainelli <florian@...nwrt.org>, openwrt-devel@...ts.openwrt.org
Subject: Re: Support for musl libc in OpenWrt
On Fri, 23 Nov 2012 21:10:33 +0100
Florian Fainelli <florian@...nwrt.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.
> - 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)?
At present, musl/mips relies on certain instructions that the kernel ordinarily emulates when they aren't supported.
--
Isaac Dunham <idunham@...abit.com>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
