Akim Demaille wrote:
>
> >>>>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>
> Ralf> Hi,
>
> Hi!
>
> Ralf> With autoconf-cvs AC_EXEEXT doesn't do anything anymore. I.e.
> Ralf> configure-scripts which are using AC_EXEEXT, but do not
> Ralf> explicitly call AC_PROG_CC, silently break with autoconf-cvs
> Ralf> (@EXEEXT@ will not be substituted).
>
> Ralf> Can't autoconf at least warn about using AC_EXEEXT w/o
> Ralf> AC_PROG_CC?
>
> Hm, does EXEEXT make sense when there are no binaries? I mean,
> shouldn't it be defined to nothing. And in fact, how come it is used
> if there are no binaries?
I encountered this issue with a package which sets up rpm.specs for
Cygwin-rpms (rpm.specs for Cygwin require the executables to be
packaged into them with .exe).
Until now this package's configure.in has been using AC_EXEEXT alone
(w/o AC_PROG_CC), now I seem to need adding AC_PROG_CC, but ..
.. autoupdate doesn't diagnose this issue.
.. autoconf doesn't complain
.. Why should one need AC_PROG_CC to a configure.in, if a package
does not require any compiler?
.. Adding AC_CANONICAL_HOST would give sense, but this also
apparently isn't sufficient.
Ralf
--
Ralf Corsepius
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
(FAW)
Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690
mailto:[EMAIL PROTECTED] FAX: +49/731/501-999
http://www.faw.uni-ulm.de
