From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Date: Mon, 26 Oct 2009 10:19:50 +0000 From: Dmitry Golubovsky Message-ID: <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <06a0be10-d05e-47f4-bebf-c9d9512de2b8@q14g2000vbi.googlegroups.com> Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9) Topicbox-Message-UUID: 901442a4-ead5-11e9-9d60-3106f5b1d025 Tim, On Oct 23, 2:23 pm, news...@lava.net (Tim Newsham) wrote: > What if you just made a command "gnuconfig" which rewrote the > configure script, fixing the minor defects, and ran the result? > Or bound in a dummy "ls" and "egrep" before executing the real > configure script? > Lets keep the infection contained. If I need to fix this for my project only, I have already done that. The problem is, everyone who generates configure by this version (or some range of versions) of autoconf would run into this because this is inserted in the configure's initialization code without any feature tests requested by configure.ac Since the purpose of ape is to emulate the environment configure is expected to run in, and such mismatch has been found, it migh be easier to fix ape than to convince maintaners of autoconf to fix on their side... Dmitry.