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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,69179bcaa90d714b
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Gnatmake query
Date: 1996/11/02
Message-ID: <dewar.846953451@merv>#1/1
X-Deja-AN: 194081952
references: <55a2qj$bv0@saturn.brighton.ac.uk>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-11-02T00:00:00+00:00
List-Id: <comp.lang.ada>


iJohn English asks

"Can anyone tell me why, when building a program which has already
been built and is fully up-to-date, gnatmake still does gnatbind -x
followed by gnatlink?  Is there a way of convincing it otherwise?"

Yes, it is easy to tell you why -- you are not using the latest version
of GNAT, in which this behavior is modified to only bind and link if
necessary. For example, in OS/2:

[OS2-F:\emx\gnu\gcc-2.7\ada]gnatmake a
gcc -c a.adb
gnatbind -x a.ali
gnatlink a.ali

[OS2-F:\emx\gnu\gcc-2.7\ada]gnatmake a
gnatmake: "a.exe" up to date.