From: Jason <bigjmack AT NOSPAM DOT rt66 DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Follow Up: Why doesn't C++ work!?!?!
Date: Sat, 05 Sep 1998 20:37:54 -0600
Organization: Rt66.COM, New Mexico's #1 ISP
Lines: 28
Distribution: world
Message-ID: <35F1F582.BA2AD667@NOSPAM.rt66.com>
References: <35EF0D07 DOT DC9983E1 AT sandia DOT gov> <35F07A4B DOT F830F880 AT sandia DOT gov> <35F0B505 DOT 13EF5FB3 AT cartsys DOT com>
NNTP-Posting-Host: pmd17.rt66.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
Precedence: bulk

> Did you read README.1ST?  It very definitely explains this issue.

Exerpt from "readme.1st":

-------------------
To compile a C or C++ source file into an object file, use this
command line:

 gcc -c -Wall myfile.c  (for C source)
  or
 gcc -c -Wall myfile.cc (for C++ source)

This produces the object file myfile.o.  The `-Wall' switch turns on
many useful warning messages which are especially beneficial for new
users of GCC.
...
To link a C++ program, use gxx instead of gcc, like this:

 gxx -o myprog.exe mymain.o mysub1.o mysub2.o
-------------------

I'm a little bit confused here - after the help from the news groups, my
understanding was that I needed to append -lstdc to gcc in order to compile a
C++ program - here this is not stated.  It later states that you only need to
use gxx in order to "link a C++ program".  Huh?

--JA$ON--