From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: What is happening ?????
Date: Sun, 02 Feb 1997 03:55:51 -0800
Organization: Two pounds of chaos and a pinch of salt
Lines: 30
Message-ID: <32F480C6.2610@cs.com>
References: <32f253f2 DOT 517889 AT news DOT flashnet DOT it> <01bc10c4$155d4600$30520cce AT Pbrainstorm DOT lightspeed DOT bc DOT ca>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp107.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Anne Compton, David/Andrew Gasson wrote:
> 
>         I'm learning, too, and I had the same exact problem.  This is how I got
> around it (but it probably isn't the only way or the best way :-) ) First,
> create an object file by doing something like
>                 gcc -c a1.cc
> then change the object file into an exe by typing
>                 gxx -o a1.exe a1.o
> Probably, there is a way to do this in one step--perhaps somebody else
> knows?  Hope this works,

Yeah, you can just run 'gxx' on the original a1.cc file like so:

	gxx -o a1.exe a1.cc

You may also consider turning on extra warnings, optimizations, and
debugging info like so:

	gxx -Wall -O -g -o a1.exe a1.cc

These switches can provide invaluable information for debugging
programs, for beginning and advanced users alike.

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I      |   mailto:fighteer AT cs DOT com   |
| God's final message to His Creation: | http://www.cs.com/fighteer |
| "We apologize for the inconvenience."| Fight against proprietary  |
|                      - Douglas Adams | software - support the FSF!|
---------------------------------------------------------------------