From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17300 invoked by alias); 9 Jul 2002 08:09:33 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 17293 invoked from network); 9 Jul 2002 08:09:31 -0000 Received: from unknown (HELO asa.co.uk) (193.119.169.33) by sources.redhat.com with SMTP; 9 Jul 2002 08:09:31 -0000 Received: from mailgate.asa.co.uk ([193.119.169.66] helo=bentley.asa.co.uk) by asa.co.uk with esmtp (Exim 2.05 #2) id 17Rpwn-0004dV-00; Tue, 9 Jul 2002 09:02:09 +0100 Received: from jamin.bentley.asa.co.uk ([192.168.10.112] helo=there ident=paulb) by bentley.asa.co.uk with smtp (Exim 2.05 #3) id 17Rpwk-0004dT-00; Tue, 9 Jul 2002 09:02:06 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Paul Butcher Organization: ASA Ltd. To: "Andrea 'Fyre Wyzard' Bocci" , gcc-help@gcc.gnu.org Subject: Re: Problem with C++ on gcc 3 Date: Tue, 09 Jul 2002 01:09:00 -0000 References: <5.1.0.14.2.20020704123900.00b29448@localhost> <5.1.0.14.2.20020708170113.00b4d068@localhost> In-Reply-To: <5.1.0.14.2.20020708170113.00b4d068@localhost> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: X-SW-Source: 2002-07/txt/msg00080.txt.bz2 For clarity I built gcc 3.1 from source for Win32/cygwin but have confirmed the behaviour against gcc 3.0.4 built for LInux for SuSE8.0. Paul Butcher Alton, Hants, UK On Monday 08 Jul 2002 16:03, Andrea 'Fyre Wyzard' Bocci wrote: > > At 09:50 08/07/2002 +0100, Paul Butcher wrote: > >Thanks for the obvious answer - my problem was two-fold: > >1. using gcc instead of g++ as you stated: -lstdc++ is not included in > > the linker stage. > >Why does gcc 3.1 not allow this? gcc 2.95.x included the correct > > libraries when calling gcc. > > Didn't know it did that :-) > > >2. I also had gcc 2.95.3 installed in a different path and libstdc++ was > >being found there before the new 3.1 library. > >Why does the library path used by gcc not start with its installation > >libraries rather than generic paths like /usr/lib? > > It depends on how you installed GCC: > if you installed a precompiled binary from a package, the fault is of the > packager; > if you bootstrapped from source, the fault is probably GCC's installation > procedure's. > > fwyzard