From: Dmitry Golubovsky <golubovsky@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Two suggestions for ape (was: egrep for Plan9)
Date: Mon, 26 Oct 2009 10:19:50 +0000 [thread overview]
Message-ID: <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.com> (raw)
In-Reply-To: <06a0be10-d05e-47f4-bebf-c9d9512de2b8@q14g2000vbi.googlegroups.com>
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.
next prev parent reply other threads:[~2009-10-26 10:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 10:43 Dimitry Golubovsky
2009-10-23 14:06 ` Jason Catena
2009-10-23 14:12 ` Charles Forsyth
2009-10-23 15:06 ` W B Hacker
2009-10-23 15:38 ` Federico G. Benavento
2009-10-23 15:54 ` Dmitry Golubovsky
2009-10-23 16:08 ` Jason Catena
2009-10-23 18:18 ` Tim Newsham
2009-10-23 18:58 ` Jason Catena
2009-10-23 21:19 ` Federico G. Benavento
2009-10-26 10:19 ` Dmitry Golubovsky [this message]
2009-10-26 13:15 ` hiro
2009-10-26 14:15 ` Dmitry Golubovsky
2009-10-26 15:06 ` [9fans] Two suggestions for ape W B Hacker
[not found] ` <636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.co>
2009-10-26 20:10 ` [9fans] Two suggestions for ape (was: egrep for Plan9) erik quanstrom
2009-10-27 16:10 ` Anthony Sorace
2009-10-27 16:16 ` erik quanstrom
2009-10-27 16:25 ` ron minnich
2009-10-27 16:37 ` erik quanstrom
2009-10-27 17:56 ` tlaronde
2009-10-27 21:43 ` Tim Newsham
2009-10-27 23:14 ` Francisco J Ballesteros
2009-10-28 0:23 ` Dave Eckhardt
2009-10-28 9:45 ` tlaronde
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=636733be-5009-4311-97ab-dc81634dbd06@p15g2000vbl.googlegroups.com \
--to=golubovsky@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).