RE: configure doesn't find cl

[Syd Polk <jazzman@bayarea.net>]

Believe me, you want config.cache to work. configure would take four to 
five times as long without config.cache.


Stojanovic, Marta wrote:

>Hello Syd & Mark !
>
>Thank you very much for your help, that worked fine. In fact, when you sent
>me that tip, I recalled having that problem before, but I then managed to
>find the solution by myself (although, I didn't manage to remember it, as
>you see ... I'm getting very old). The problem is in this : instead of
>typing "export CC=cl" I typed by mistake just "CC=cl" on the command line
>the first time I used configure. When I ran configure, of course it didn't
>find CC, so it took gcc instead ... and put it in config.cache. Afterwards I
>realized that I should have used "export ...", but it wouldn't work. Now,
>there is probably a way to tell configure not to use cached info, but I'm
>not aware of it. It's rather frustrating to make all those changes to the
>environment to accomodate configure, while it never uses them if it once
>stored all the environment in config.cache ... Anyway, thanks a lot ! Hope
>my grey cells will remember it next time ...
>
>Kind regards,
>Marta.
>
>
>
>
>Marta,
>
>Syd Polk wrote:
>
>> Stojanovic, Marta wrote:
>> 
>> 
>>>Hi all !
>>>
>>>I don't know what I'm doing wrong : I used to build SN without any
>problems
>>>on Win2000 using cygwin and MSVC6, but now when I'm trying configure again
>>>it gives the following message : 
>>>
>>>.....
>>>checking for gcc... (cached) gcc
>>>
>> 
>> Try removing the file "config.cache". Actually, blow away your build 
>> directory and reconfigure.
>I strongly suggest the latter course - trying to work out how to get
>
>configure / autoconf / automake / libtool to take notice of configuration
>changes is a
>
>_very_ black art.
>
>
>
>--MarkT


Syd Polk
jazzman@bayarea.net                 http://www.bayarea.net/~jazzman
"Let the music be your light." -- Dave Edwards, KUHF-FM, 1982