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,6e10dbd84b94a267
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: GNAT Compilation Problems
Date: 1996/10/09
Message-ID: <dewar.844905925@merv>#1/1
X-Deja-AN: 188363575
references: <51u63c$80c@netty.york.ac.uk>
 <R.01bba753$d2824ee0$1c8371a5@dhoossr.iquest.com>
 <52skmb$j8@cronkite.seas.gwu.edu> <dewar.844782448@schonberg>
 <325AE88C.BC7@empire.net>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-10-09T00:00:00+00:00
List-Id: <comp.lang.ada>


Gandalf said

"While Robert is correct that gnatinfo.txt has some great information,
the command lines for compilation using gnat for DO$ is

gcc -c 'your_file_name_goes_here'
"

This is very bad advice, as you will find out from reading gnatinfo.txt,
the proper way to compile programs using GNAT from the DOS prompt or 
anywhere else is to use gnatmake. There is very seldom a reason for typing
in a gcc command.