From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 27 Jul 2013 17:43:47 -0400
To: 9fans@9fans.net
Message-ID: <d34d6ce6c7d5b8da53d3bf53fd8f739e@brasstown.quanstro.net>
In-Reply-To: <20130727213936.GA22631@intma.in>
References: <c6ae82c24cabd68a535451350749816c@gmx.de>
	<e5998a9a676a19522953a416aee2dc43@ladd.quanstro.net>
	<20130727074822.50f9af70@Krypton>
	<906e7ed0e591c1125838c17258440bb6@kw.quanstro.net>
	<CAEAzY3-V=beXd7xS856acR68yFWyrtm=wTcjejZ+N-sQCfK6ZA@mail.gmail.com>
	<26c21ed605e201dcad928e22c7ec360c@brasstown.quanstro.net>
	<20130727213936.GA22631@intma.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] MirOS ksh (mksh) building out-of-the box on Plan9/APE
Topicbox-Message-UUID: 6e7b063e-ead8-11e9-9d60-3106f5b1d025

> it's an ape-specific question because the go maintainers chose to route
> around the problem.  his point was that mksh is not the only program
> that has run into SIGCHLD.  his point had nothing to do with whether go
> uses ape, which is a question nobody has ever asked.

SIGCHLD is not defined for plan 9, except in ape.  that's what i
would call ape-specific.

- erik