[Qemu-devel] mksh on Slackware (was Re: CVS: herc.mirbsd.org: src)
Hi all! Thanks for this: Commit ID: 100548597A713CD6746 CVSROOT: /cvs Module name: src Changes by:t...@herc.mirbsd.org2014/12/08 12:20:42 UTC Modified files: bin/mksh : Build.sh Log message: port this to GNU bash 1.12.1 from http://www.qemu-advent-calendar.org/#day-1 The image has JOE 0.1.5, some sort of jupp¹-ish editor, which made me happy. But I’ve got another problem: I can’t run mksh’s testsuite, whose driver is written in Perl, which I don’t speak. root@slack:/root/mksh # perl -v This is perl, version 4.0 $RCSfile: perl.c,v $$Revision: 4.0.1.7 $$Date: 92/06/08 14:50:39 $ Patch level: 35 Copyright (c) 1989, 1990, 1991, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 4.0 source kit. Any help in porting mksh/check.pl² to t̲h̲a̲t̲? ☺ Thanks in advance, //mirabilos ① https://www.mirbsd.org/jupp.htm ② https://www.mirbsd.org/cvs.cgi/src/bin/mksh/check.pl?rev=HEAD -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
Re: [Qemu-devel] mksh on Slackware (was Re: CVS: herc.mirbsd.org: src)
enh dixit: [ mksh testsuite ] have you considered using sh instead? :-) Not pure sh, that’s nowhere near enough. Maybe mksh. But if the one just built has issues, that may mask it. If another, you’ve got hen/egg problems. Maybe C. But then, (cross-)building a C program to test another one just built *may* (or may not) be more susceptible to errors than using a completely separate tool. No, I’m not happy with the current testsuite driver, but it’s there, it’s reasonably portable, and does its job, after some prodding (and I still don’t speak Perl). (there's no perl on Android, which makes running the mksh tests impractical. one can *build* perl for Android, i'm led to believe, but I’ve successfully (modulo the things that just didn’t exist, or didn’t work with toolbox) run the testsuite on Android (on the emulator) once, with a native Bionic perl. Nowadays, I’d probably just get a Linux/ARM box (Debian poterbox would be superb, except I retired from Debian recently), build a native Perl against dietlibc or musl, statically, then copy that over to Android, as it only relies on the kernel, and this is enough for the testsuite. Another idea we will have to try out: check if the testsuite can be run on the build system (instead of the target), using ssh (or adb shell) to invoke the to-be-tested utility on the target. Con: we’d probably need to NFS-mount or rsync the directory tree. But maybe something the *WRT people are also interested in. (Or we could move file generation to the target as well. Needs more hacking work in the testsuite driver.) Anyway, this is still enough short-term. bye, //mirabilos -- “The final straw, to be honest, was probably my amazement at the volume of petty, peevish whingeing certain of your peers are prone to dish out on -devel, telling each other how to talk more like a pretty princess, as though they were performing some kind of public service.” (someone to me, privately)
Re: [Qemu-devel] mksh on Slackware (was Re: CVS: herc.mirbsd.org: src)
On Mon, Dec 8, 2014 at 12:49 PM, Thorsten Glaser t...@mirbsd.de wrote: I’ve successfully (modulo the things that just didn’t exist, or didn’t work with toolbox) run the testsuite on Android (on the emulator) once, with a native Bionic perl. (AOSP master now has toybox, which should help with this side of things.) Another idea we will have to try out: check if the testsuite can be run on the build system (instead of the target), using ssh (or adb shell) to invoke the to-be-tested utility on the target. Con: we’d probably need to NFS-mount or rsync the directory tree. But maybe something the *WRT people are also interested in. (Or we could move file generation to the target as well. Needs more hacking work in the testsuite driver.) this is the way we usually go. the libc++ tests are currently run like that, for example, and that's what i'm hoping to find time to do with toybox's tests (though they'll be able to rely on mksh, so i might have more choices there). --elliott
Re: [Qemu-devel] mksh on Slackware (was Re: CVS: herc.mirbsd.org: src)
On Mon, Dec 8, 2014 at 4:34 AM, Thorsten Glaser t...@mirbsd.de wrote: The image has JOE 0.1.5, some sort of jupp¹-ish editor, which made me happy. But I’ve got another problem: I can’t run mksh’s testsuite, whose driver is written in Perl, which I don’t speak. have you considered using sh instead? :-) (there's no perl on Android, which makes running the mksh tests impractical. one can *build* perl for Android, i'm led to believe, but it's not likely to ever be in the AOSP tree.)
