>>>>> "diger" == diger Kuhlmann <R> writes:
> Okay, look at it that way: Let's assume I have a tree of independent
> projects to (cross-)compile. Most use autoconf, some don't, notably
> perl5. So to configure in one sweep, I have to put some replacement
> of autoconf's configure into that directory that is called instead
> of perl5's Configure, which doesn't do anything else than feed the
> right values into Configure. Of course, I can't give my script the
> same name "configure" as the script already there, which is
> "Configure". Hence, I have to choose a different name -
> configure.gnu. Or do you prefer a different name?
Thanks, I now understand better what you are trying to address.
Still, why don't you want both Configure and configure in the same
dir? Are you using a case insensitive FS?
Also, why do you think it is Autoconf's configure which should be
renamed rather than Configure? configure.perl.
Well, if none of the solutions above is satisfying for you, and
provided Alexandre thinks we have to address this issue (Alexandre,
I'm a bit lost here, help!), I'd suggest something else than `gnu'.
`ac' seems OK. Alexandre?
Alternatively (sorry for insisting but your proposal seems a bit too
``specific'' to get into Autoconf per se), can't you just run
Configure with
AC_CONFIG_SUBDIRS(my/autoconfed/dir1 my/autoconfed/dir2)
AC_CONFIG_COMMANDS([perl], [sh perl5/Configure])
etc.?
