mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Arvid E. Picciani" <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: testing mips port ?
Date: Thu, 12 Jul 2012 16:11:15 +0200	[thread overview]
Message-ID: <1278340fc0863a0fbbef5b33b82c7723@exys.org> (raw)
In-Reply-To: <20120712050950.GB544@brightrain.aerifal.cx>

I'd use an arbitrary router supported by openwrt. I made good 
experience with the wrt500gp
Should be like ~25Eur on ebay.
Openwrt because it's hack-friendly, allowing you to rebuild the whole 
firmware in any obscure way you like.

If it's just about running some arbitrary binary to confirm a crash, i 
can do that.


On Thu, 12 Jul 2012 01:09:50 -0400, Rich Felker wrote:
> hi all,
>
> does anybody have real mips hardware that could be used to test the
> new mips port? i've been trying to run libc-testsuite in qemu
> (aboriginal linux), but the pthread cancellation tests are failing.
> adding some debug code, it looks like qemu is not giving the signal
> handler a valid/correct ucontext_t structure, but unfortunately i
> don't have any real hardware to test it on to confirm that this is
> just a qemu bug and not a musl bug.
>
> by the way, there's no shared library support for mips yet, mainly 
> due
> to the abi being atrociously bad and incompatible with musl's clean
> and simple way of doing dynamic linking, which is having a dynamic
> linker that naturally just works without any relocations. so if you
> want to test it, please just disable shared libraries for now.
>
> rich

-- 
Arvid E. Picciani


  reply	other threads:[~2012-07-12 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  5:09 Rich Felker
2012-07-12 14:11 ` Arvid E. Picciani [this message]
2012-07-12 14:11   ` Rich Felker
2012-07-12 15:25     ` Arvid E. Picciani

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=1278340fc0863a0fbbef5b33b82c7723@exys.org \
    --to=aep@exys.org \
    --cc=musl@lists.openwall.com \
    /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).