From: Ian Lance Taylor <iant@google.com>
To: mahmoodn <nt_mahmood@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc++.so conflict
Date: Sat, 01 Dec 2007 17:16:00 -0000 [thread overview]
Message-ID: <m3zlwugwue.fsf@localhost.localdomain> (raw)
In-Reply-To: <14102515.post@talk.nabble.com>
mahmoodn <nt_mahmood@yahoo.com> writes:
> >You have a shared library which requires libstdc++.so.6.
> >Either your compiler, or another shared library, requires
> >libstdc++.so.5. You neglected to mention which version of the
> >compiler you are using, so I don't know which.
> >libstdc++.so.5 and libstdc++.so.6 should not be used in the same
> >executable.
>
> Thanks,
> I use gcc 3.3. So how can I fix it?
Use a newer version of gcc which uses libstdc++.so.6, or use an older
version of the shared library which uses libstdc++.so.5.
Ian
next prev parent reply other threads:[~2007-12-01 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 9:13 mahmoodn
2007-11-30 18:44 ` mahmoodn
2007-11-30 19:47 ` Ian Lance Taylor
2007-12-01 5:53 ` mahmoodn
2007-12-01 17:16 ` Ian Lance Taylor [this message]
2007-12-02 5:17 ` mahmoodn
2007-12-02 5:19 ` Ian Lance Taylor
2007-12-02 18:05 ` mahmoodn
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=m3zlwugwue.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nt_mahmood@yahoo.com \
/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).