Re: progress
- To: Thorsten Glaser <tg@mirbsd.de>
- Cc: debian-68k@lists.debian.org
- Subject: Re: progress
- From: Laurent Vivier <Laurent@vivier.eu>
- Date: Sun, 30 Jan 2011 10:58:15 +0100
- Message-id: <[🔎] 1296381495.2843.17.camel@Quad>
- In-reply-to: <Pine.BSM.4.64L.1012292033570.21154@herc.mirbsd.org>
- References: <20101228161618.GC1446@kasbah> <Pine.BSM.4.64L.1012291559190.21154@herc.mirbsd.org> <Pine.BSM.4.64L.1012291954390.21154@herc.mirbsd.org> <AANLkTikv+o_Gv43Ws15OEM2n=fowC2Lwwf2FaFV7M36V@mail.gmail.com> <Pine.BSM.4.64L.1012292033570.21154@herc.mirbsd.org>
Le mercredi 29 décembre 2010 à 20:35 +0000, Thorsten Glaser a écrit :
> Geert Uytterhoeven dixit:
>
> >> root@zigo:~ # qemu-m68k ./hello
> >> Segmentation fault
>
> >> (Looks as if qemu isn’t up to it…)
A little bit late, but I've a fork of qemu managing (real) m68k:
git clone http://git.gitorious.org/qemu-m68k/qemu-m68k.git
It is based on previous work from Andreas Schwab.
I allows to "chroot" to a filesystem populated with aranym.
Some binaries like vi, nano or gcc segfault, but I'm searching why.
> >
> >It's limited to Coldfire, and doesn't handle an MMU?
>
> It's supposedly the user-space emulation. But that was just the
> check from https://wiki.debian.org/BuildingCrossCompilers so no
> worries. It worked on the real thing after all.
>
> bye,
> //mirabilos
> --
> <ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^
> <mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
> <ch> should have cloned into a clean repo │ fault (core dumped)
> <ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh
>
>
--
--------------------- laurent@vivier.eu ----------------------
"Tout ce qui est impossible reste à accomplir" Jules Verne
"Things are only impossible until they're not" Jean-Luc Picard
Reply to: