> You are right. In the future, we might think of eliminating the
> architectures that are clearly wrong from the selection.
>
> For the toolchain you're using, qemu-arm-0.8.1-sb2 might be the one
> you're looking for.
Thanks.
But what's the basis for that choice. Where can I learn what these
Your toolchain's architecture is arm, so you'll have to choose arm
instead of armeb. As a rule of thumb, it's wise to choose the latest
qemu version.
The "sb2" stands for the patchset applied to that version of qemu. The
"m2" is slightly different patchset, but it is very unlikely in your
cas
On Thu, Feb 08, 2007 at 01:12:30PM +0100, Murray Cumming wrote:
> > You are right. In the future, we might think of eliminating the
> > architectures that are clearly wrong from the selection.
> >
> > For the toolchain you're using, qemu-arm-0.8.1-sb2 might be the one
> > you're looking for.
>
Alas, you can't just copy your favorite flavor of qemu (or some other
binary which offers you a cpu transparency method) inside
/scratchbox/devkits/cputransp/bin and use it.
You'll need either to do some hacking or compile a static version which
is (in my opinion) no less trouble than adding i
I'm trying to set up a debian Etch system inside scratchbox, running on
my x86 host PC. This seems vaguely possible by starting with the arm
toolchain, changing the sources.list and updating. This isn't for Maemo
or Nokia.
But Debian Etch uses different versions of gcc and glibc than the
scratchb
Riku Voipio wrote:
On Thu, Feb 08, 2007 at 01:12:30PM +0100, Murray Cumming wrote:
You are right. In the future, we might think of eliminating the
architectures that are clearly wrong from the selection.
For the toolchain you're using, qemu-arm-0.8.1-sb2 might be the one
you're looking for.
