> "Hari" == Raja R Harinath <[EMAIL PROTECTED]> writes:
Hari> No. It is currently safe only if one of the AC_PROG_CC or
Hari> AC_PROG_CXX commands is present in configure.in, thanks to the
Hari> shenanigans in init.m4. That's why I went through the extra
Hari> step.
Thanks for clearing tha
Hi,
Tom Tromey <[EMAIL PROTECTED]> writes:
>> "Hari" == Raja R Harinath <[EMAIL PROTECTED]> writes:
>
> Hari> Akim once suggested adding a facility to hook commands to files
> Hari> listed in AC_CONFIG_FILES.
>
> The problem with this idea is that the information about which files
> is known
> "Hari" == Raja R Harinath <[EMAIL PROTECTED]> writes:
Hari> Akim once suggested adding a facility to hook commands to files
Hari> listed in AC_CONFIG_FILES.
The problem with this idea is that the information about which files
is known when automake is run, not when autoconf is run.
Hari>
>>> "Ted" == Ted Irons <[EMAIL PROTECTED]> writes:
[...]
Ted> if test "${lt_cv_prog_compiler_c_o_CXX+set}" = set; then
Ted> echo $ECHO_N "(cached) $ECHO_C" >&6
Ted> else
Ted> lt_cv_prog_compiler_c_o_CXX=no
[...]
Ted> save_CFLAGS="$CFLAGS"
Ted> CFLAGS="$CFLAGS -o out/conftest2.$ac_objext"
[.
