Re: changing the default compilers for autoconf

[Sanjay Gianchandani]

Hi Ralf,
sorry for mailing you directly, but I wasnt getting much response on the
mailing list, and I am still wondering as to which direction to proceed...
these changes that u suggested, if i inject them in acspecific.m4, wont that
serve my purpose?
I am not exactly sure though, as I am not completely aware of the flow of
autoconf...
any help would be greatly appreciated...
moreover, I read somewhere that autoconf also uses some flags at compile
time, which means that I would need to ensure that these flags work in the
same way for the "changed" compiler too, right? any ideas abt which flags
autoconf uses?

any help would b greatly appreciated!
thanks,
sanjay

On 9/7/07, Ralf Wildenhues <address@hidden> wrote:
>
> Hello Sanjay,
>
> * Sanjay Gianchandani wrote on Fri, Sep 07, 2007 at 02:55:16PM CEST:
> > I have been working on Solaris, and have been trying to increase the
> > efficiency of autoconf built softwares on the system.
> > The main issue here is that autoconf by default, and as a rule, uses the
> GNU
> > based compilers to make the software, while
> > on Solaris, Sun Studio compilers prove to be much more efficient.
>
> For yourself, just get in the habit of using
>   .../configure -C CC=cc CXX=CC F77=f77 FC=f95
>
> or write a config.site file that sets these as defaults once and for
> all, for your system; see
> <http://www.gnu.org/software/autoconf/manual/html_node/Site-Defaults.html>
> for more information.
>
> If you want to change the defaults for your specific package, but every
> user of it, then you can put something like
>   : ${CC=cc}
>   : ${CXX=CC}
>   # ...
>
> in your configure.ac, right before AC_PROG_CC; but be warned that users
> may not like your decision all that much and at least require that you
> do this only on Solaris.  For that, invoke AC_CANONICAL_HOST and then
> match $host against *-*-solaris*:
>   AC_CANONICAL_HOST
>   case $host in
>   *-*-solaris*)  : ${CC=cc}  ... ;;
>   esac
>   AC_PROG_CC
>
> As to changing Autoconf's defaults globally, i.e., for everyone and
> every package without package-specific modifications: preference of GCC,
> the GNU Compiler Collection, is a policy decision.  From an effort point
> of view, you'd have more luck in improving GCC so that it ends up being
> the better compiler, than getting GNU to promote a proprietary compiler
> over its own free one.  ;-)
>
> Cheers,
> Ralf
>



-- 
****************************************************************************
§âñjây
************************Words from my heart****************************
We dont need no education!
give us free pizza instead ;)
*****************************************************************************