Re: [Mingw-msys] Re: using mingw with msys

[Soren A. <sor...@sp...>]

On Wed, 27 Mar 2002 20:43:59 +0200, "Jean le Roux" <je...@in...> said:
> On Wed, Mar 27, 2002 at 08:29:48PM +0200, Jean le Roux wrote:
> > Now the question, why does it not stick to the compiler it found in
> > the first place ?
> 
> Hmm, i did an autoscan for the project, and merged the results with
> my configure.in. Then it picked up the header files, becasue it was
> using the correct compiler.
> 
> the difference in the two is basically
> 
> AC_PROG_CXX -->i had this
> these were added
> AC_PROG_AWK
> AC_PROG_CC
> AC_PROG_INSTALL
> AC_PROG_LN_S
> 
> Seems I'm sorted, for now :)

Good! Yes, it matters in some very important cases, the precedence of calling autoconf macros, and this is one of the big gotchas. One needs to call AC_PROG_CC very early on before almost any other checks. Other checks will depend on the result of that one and it is a B I G weakness of autoconf that it won't correctly inform the user about the early failure in normal screen output.

I invite readers to go look at the article I posted to newsgroup awhile ago regarding the overall autotools build system. It is my passionate conviction that people need to be very careful of how much they put blind faith in autotools. But if your blood pressure is a problem right now perhaps skip it, because it's a rowdy posting not calculated to make friends for me everywhere (you've been warned!):
--------- watch for long url wrapping -----
http://groups.google.com/groups?q=%2BSoren+%2Bautomake&hl=en&selm=Xns91D2A2408EF9Dsorenngrp89%4064.8.1.226&rnum=3
---------------------------------------------

      Best,
      Soren Andersen