public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Carlos Rubio <crubion@cirsa.com>
To: gcc@gcc.gnu.org
Subject: Can I run gcc 3.2 with libstdc++ v3.1?
Date: Thu, 19 Dec 2002 03:43:00 -0000	[thread overview]
Message-ID: <200212191040.35282.crubion@cirsa.com> (raw)

Hi,

I'm working with xercesc v2 and gcc 3.2 and my program gives me this link
warning:

usr/bin/ld: warning: libstdc++.so.4, needed by
/work/development/bola/xerces-c2_1_0-linux7.2gcc31/lib/libxerces-c.so, not
found (try using -rpath or -rpath-link)

That library comes with gcc 3.1. Why libstdc++.so.5 is not good for xercesc?
Do I have to use gcc 3.1 and not the last one? Could I just uninstall
libstdc++ v3.2 and install libstdc++ v3.1? in other words, can GCC 3.2 run
with libstdc++4.0-devel-3.1-3cl.i386.rpm?

Any help would be really appreciated!

Thanks,
Carlos

-------------------------------------------------------

             reply	other threads:[~2002-12-19  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  3:43 Carlos Rubio [this message]
2002-12-19 11:15 Benjamin Kosnik

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=200212191040.35282.crubion@cirsa.com \
    --to=crubion@cirsa.com \
    --cc=gcc@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).