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: 103376,4fbd77cc2dc20a9c
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.180.96.3 with SMTP id do3mr272674wib.1.1359634097304;
        Thu, 31 Jan 2013 04:08:17 -0800 (PST)
Path: 
 bp2ni8109wib.1!nntp.google.com!proxad.net!feeder1-2.proxad.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Brian Drummond <brian@shapes.demon.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: Building PolyOrb - Windows XP; gnat 2012
Date: Thu, 31 Jan 2013 12:08:17 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <kedmrg$vri$1@dont-email.me>
References: <065d4266-dee0-46f4-b7e6-19e706f784cd@googlegroups.com>
	<lyzjzpsv2x.fsf@pushface.org>
Mime-Version: 1.0
Injection-Date: Thu, 31 Jan 2013 12:08:17 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="da745e888d4a5182b5fda6212bbb0a63";
	logging-data="32626"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19SFzYWYmRx7+CInMYetWUY7DM8l7G4ILU="
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
	git://git.gnome.org/pan2)
Cancel-Lock: sha1:NTAc0pxps5fdT/xpGyHwzdZCivo=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: 2013-01-31T12:08:17+00:00
List-Id: <comp.lang.ada>

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!

- Brian