enh dixit:
>probably related to
>https://code.google.com/p/android/issues/detail?id=66815. i think the
Right, similar issue.
>hard part is what to set $TMPDIR to.
Agreed.
If I get a C API I can just call, I would put it into main.c in mksh
(set TMPDIR to that value, unless we import it from the environment
already).
Otherwise, something should ensure that $TMPDIR is set whenever mksh
is called. Since the shell can be called various ways (during boot,
adb, from a local application), this is pretty complicated; I’d suggest
adding code to bionic which I can call might be easier.
>the AOSP x86 emulator is pretty fast, as long as you have hardware
>that lets you use kvm. just don't forget to supply the flag so the
>emulator takes advantage of it!
Hrm. I’ll have to see if linux-kvm works inside a linux-kvm VM.
IIRC, this works with AMD CPUs. What is the “magic invocation”
to build for that, instead of for emulator (which I used to be
as close to upstream as possible)?
bye,
//mirabilos
--
Yes, I hate users and I want them to suffer.
-- Marco d'Itri on gmane.linux.debian.devel.general
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366451
Title:
"mksh -v" should display mksh's version number, plus the attached
chunk of text, onscreen
To manage notifications about this bug go to:
https://bugs.launchpad.net/mksh/+bug/1366451/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
