Date: Wed, 8 Mar 2000 11:55:26 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Kalum Somaratna aka Grendel <kalum AT crosswinds DOT net>
cc: Rodeo Red <rodeored AT netstep DOT net>, djgpp AT delorie DOT com
Subject: Re: -wall messages
In-Reply-To: <Pine.LNX.4.10.10003071347130.929-100000@darkstar.grendel.net>
Message-ID: <Pine.SUN.3.91.1000308115507.6599G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 7 Mar 2000, Kalum Somaratna aka Grendel wrote:

> Actually -Wall turns on _all_ the warnings.

No, it doesn't.  It turns on many warnings, but not all of them.  -W
turns on several more, and then there are -Wfoo options which are not
part of either one of these two.

> the libc refrence "info libc"
> has a section dealing with the various warnings you can enable and disable
> etc..

You meant "info gcc", of course.  Compiler warnings have nothing to do
with the library.

> one difference is that when you compile c++ programs with the command gcc
> you must specify the -lstdcx option asking the linker to link in the c++
> libraries.
> 
> So a sample compile using gcc would go,
> gcc foo.cpp -o foo.exe -lstdcx

You meant -lstdcxx, of course.