From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,4fbd77cc2dc20a9c
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.180.93.134 with SMTP id cu6mr2513299wib.5.1359636448431;
        Thu, 31 Jan 2013 04:47:28 -0800 (PST)
Path: 
 i11ni31114wiw.0!nntp.google.com!goblin2!goblin.stu.neva.ru!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Building PolyOrb - Windows XP; gnat 2012
Date: Thu, 31 Jan 2013 12:47:25 +0000
Organization: A noiseless patient Spider
Message-ID: <lyr4l1sen6.fsf@pushface.org>
References: <065d4266-dee0-46f4-b7e6-19e706f784cd@googlegroups.com>
	<lyzjzpsv2x.fsf@pushface.org> <kedmrg$vri$1@dont-email.me>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="c8da4aa61d590a5e477a2e03e552a940";
	logging-data="21166"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+aBdtur0DG2Mv0l1kd2buXhr+ZXUESwaQ="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (darwin)
Cancel-Lock: sha1:X4IgeExqHDiuuZUmEv5pIepOsII=
	sha1:QtxsQIDF6CN9b0qPMV7rDSEGMrg=
Content-Type: text/plain
Date: 2013-01-31T12:47:25+00:00
List-Id: <comp.lang.ada>

Brian Drummond <brian@shapes.demon.co.uk> writes:

> On Thu, 31 Jan 2013 06:52:22 +0000, Simon Wright wrote:
>
>> "RasikaSrinivasan@gmail.com" <RasikaSrinivasan@gmail.com> writes:
>> 
>>> When I issue ./configure (under mingw) - it terminates with "Ada
>>> compiler is not working"
>>>
>>> it was able to check for gnat chop, gnatls etc.
>>>
>>> I am wondering what command it is using to check? (I am not too
>>> familiar with configure scripts).
>> 
>> Try searching config.log for the error message.
>
> Heh. That advice didn't help me much, at first...
>
> After the console error message, there is usually a "leaving directory
> xxx/yyy" message...
>
> Once I realised I had to check the config.log *in that directory*
> things made a lot more sense!

Oh yes ... it's been a while.