Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <200403021528.i22FSGwo004451@smtp1.adl2.internode.on.net> From: "Gareth Pearce" To: Subject: RE: gcc problem Date: Wed, 3 Mar 2004 02:28:15 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <1591625311494.20040302142332@familiehaase.de> X-IsSubscribed: yes > > g++ is in a separate package named gcc-g++, be sure you have installed > this too. Then you need to link against libstdc++ when using gcc as > driver: > gcc -o gtest gtest.cc -lstdc++ > or you use g++ as driver which includes libstdc++ automatically: > g++ -o gtest gtest.cc Just want to drop my usual line here - Do use g++ rather then gcc -lstdc++ Since gcc -lstdc++ isn't always enough, and what is enough may not always be enough in the future. Gareth PS - in response to the other email - .cc Is pre-processor input - since that's the Normal state for c++ code - pre-processor input of which the output is then fed to a c++ compiler. (Virtually at least, in practice it can end up being integrated somewhat. The C standard allows 'as if' interpretation in the implementation of the pre-processing component.) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/