This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc-3 0-branch configure.in modified, configure not rebuilt
- To: pedwards at disaster dot jaj dot com
- Subject: Re: gcc-3 0-branch configure.in modified, configure not rebuilt
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Wed, 11 Apr 2001 02:37:16 +0200
- Cc: gcc at gcc dot gnu dot org
- Organization: Ecole Normale Superieure (quatramaran)
- References: <20010331231432.A17349@home-desktop> <20010331212017.A15901@lucon.org> <20010331233328.A17421@home-desktop>
In article <20010401010253.A18370@disaster.jaj.com> you write:
>On Sat, Mar 31, 2001 at 11:33:28PM -0600, Gordon Sadler wrote:
>> guess I'm just too used to autoconf by now. However, the point still
>> stands, doesn't it? configure, by hook or crook -), needs to be
>> regenerated and committed?
>
>No, the topmost configure and configure.in files have nothing to do with
>autoconf. They are /both/ handwritten and hand-maintained. They're related
>to something called Cygnus Configure.
>
>Stop right there -- don't ask. The few people who have learned details
>about Cygnus Configure are no longer allowed to handle sharp objects or
>go outside unsupervised. :-)
One does wonder why, after all this time that Cygnus configure has been
around, the autoconf script does not detect it and not do anything with
it.
I mean, there's already everything and the kitchen sink in autoconf.
Why not add such a friendly luser feature as well ? :)