From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] MirOS ksh (mksh) building out-of-the box on Plan9/APE
Date: Fri, 16 Aug 2013 09:26:08 +0200 [thread overview]
Message-ID: <20130816092608.0185245c@Krypton> (raw)
In-Reply-To: <20130726085930.6909f7e9@Krypton>
On Fri, 26 Jul 2013 08:59:30 +0200
Jens Staal <staal1978@gmail.com> wrote:
> Dear all,
>
> From yesterday upstream mksh (cvs and future R48 and onwards) builds
> out of the box on Plan9 simply by:
>
> ape/psh
> ./Build.sh
>
> One issue remains and that is that the shell will get "stuck" after
> executing an external command. To build a working shell, there is a
> temporary work-around by issuing:
>
> CFLAGS="-DMKSH_NOPROSPECTOFWORK" ./Build.sh
>
> This disables a number of features in the shell.
>
> I have uploaded an R47 build with the modified Build.sh (with
> -DMKSH_NOPROSPECTOFWORK)
> at /n/sources/contrib/staal1978/pkg/mksh-R47.tbz.
>
> In order to get a fully-functional mksh, something needs to be fixed
> host-side. A good guess is that it is the way APE handles SIGCHLD,
> since the same "freezing" has occurred on a number of other ports of
> mksh:
>
> http://www.mail-archive.com/miros-mksh@mirbsd.org/msg00215.html
>
> Is there interest in fixing SIGCHLD on APE and if so, what would be
> the best approach?
>
> If there is interest, it would thus be entirely possible to have an
> upstream, modern and mantained ksh shell which builds unmodified for
> APE (possibly as replacement of the old pdksh port now acting as
> "sh"). The mksh shell is used in many different contexts, most
> notably as shell in the more modern versions of Android.
The R48 of mksh is now released, so from now on one should basically be
able to download the latest tarball at any given time from
https://www.mirbsd.org/MirOS/dist/mir/mksh/
and build it on Plan9 by
ape/psh
./Build.sh
and until the SIGCHLD thing gets resolved, just build with
CFLAGS="-DMKSH_NOPROSPECTOFWORK" ./Build.sh
prev parent reply other threads:[~2013-08-16 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 6:59 Jens Staal
2013-07-26 16:26 ` cinap_lenrek
2013-07-26 17:01 ` erik quanstrom
2013-07-27 5:48 ` Jens Staal
2013-07-27 14:01 ` erik quanstrom
2013-07-27 15:11 ` Aram Hăvărneanu
2013-07-27 15:23 ` erik quanstrom
2013-07-27 21:39 ` Kurt H Maier
2013-07-27 21:43 ` erik quanstrom
2013-07-27 22:39 ` Aram Hăvărneanu
2013-07-28 0:55 ` erik quanstrom
2013-07-28 5:38 ` lucio
2013-08-16 7:26 ` Jens Staal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130816092608.0185245c@Krypton \
--to=staal1978@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).