search for: dmksh_no_limit

...d Plan 9? >but it seems this is a bug in the operating environment, >not the shell. With Debian unstable as of today, the same still happens. Steps to produce an mksh executable: % env CVS_RSH=ssh cvs -d _anoncvs at anoncvs.mirbsd.org:/cvs \ co -PA mksh % cd mksh % env CC=klcc CPPFLAGS=-DMKSH_NO_LIMITS sh Build.sh -r Then, ?./test.sh -v? fails, as does this: tg at frozenfish:~/mksh $ ./mksh -c 'echo foo; ls; echo bar' foo Build.sh check.t eval.c expr.o jobs.c lex.o mksh sh_flags.h syn.c var.c CVS dot.mkshrc eval.o funcs.c jobs.o main.c mksh...

...minimalistic pseudo-arc4random(3) behind it. I?ve revisited the code. An mkstemp testsuite from the ?net shows it works, except for not caring how many ?X?en are in the template. Addressing #516294, it allows compiling and linking an mksh from today?s CVS against it: tg at tg-sidvm:~/b $ CPPFLAGS=-DMKSH_NO_LIMITS CC=klcc dash ../mksh/Build.sh -r However, the signal problem persists: tg at tg-sidvm:~/b $ ./mksh -c 'print hi' hi tg at tg-sidvm:~/b $ ./mksh -c 'ls' Rebuild.sh eval.o expr.o histrap.o lalloc.o main.o mksh signames.inc test.sh var.o edit.o exec.o funcs.o jobs....