Date: Wed, 8 Mar 2000 18:46:35 +0600 (LKT) From: Kalum Somaratna aka Grendel X-Sender: root AT darkstar DOT grendel DOT net To: Eli Zaretskii cc: djgpp AT delorie DOT com Subject: Re: -wall messages In-Reply-To: Message-ID: 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 Wed, 8 Mar 2000, Eli Zaretskii wrote: > > 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. Yes you are indeed correct Eli, guess I woke up on the wrong side of the bed that day and I was typing out of habit, this was a genuine mistake since there are many problems dealing with the c library on this list I out of habit typed libc where I thought i had typed gcc...Well, I guess this happens to everyone once in a while... > > > 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. Of course. Obviously the day that I posted this message just wasn't my day ;-) I apologize to anyone who was affected by the unintentional mistakes in my original post. Grendel Hi, I'm a signature virus. plz set me as your signature and help me spread :)