From: Paul Butcher <paul.butcher@asa.co.uk>
To: "Andrea 'Fyre Wyzard' Bocci" <fwyzard@inwind.it>, gcc-help@gcc.gnu.org
Subject: Re: Problem with C++ on gcc 3
Date: Tue, 09 Jul 2002 01:09:00 -0000 [thread overview]
Message-ID: <E17Rpwk-0004dT-00@bentley.asa.co.uk> (raw)
In-Reply-To: <5.1.0.14.2.20020708170113.00b4d068@localhost>
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
prev parent reply other threads:[~2002-07-09 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 2:18 Paul Butcher
2002-07-04 3:39 ` Andrea 'Fyre Wyzard' Bocci
2002-07-08 1:54 ` Paul Butcher
2002-07-08 8:03 ` Andrea 'Fyre Wyzard' Bocci
2002-07-09 1:09 ` Paul Butcher [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17Rpwk-0004dT-00@bentley.asa.co.uk \
--to=paul.butcher@asa.co.uk \
--cc=fwyzard@inwind.it \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).