From: Alec Teal <a.teal@warwick.ac.uk>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: I have no ideas about an error involving CXXABI
Date: Sun, 01 Dec 2013 01:04:00 -0000 [thread overview]
Message-ID: <529A8B18.1070008@warwick.ac.uk> (raw)
In-Reply-To: <CAH6eHdSweJibm6rgcxHZDVcHmgOTuy45th1Mm1Gdi42ab0vmfw@mail.gmail.com>
You're right Jonathan (I didn't doubt you really)
ls /usr/lib/x86_64-linux-gnu/ -l | grep libstdc
lrwxrwxrwx 1 root root 19 May 10 2013 libstdc++.so.6 ->
libstdc++.so.6.0.16
-rw-r--r-- 1 root root 962656 Apr 16 2012 libstdc++.so.6.0.16
I've looked at that page and I didn't think that this could happen. This
means I know less than the installation process than I thought I did.
Rather than blindly following that link can you please explain what
actually happens? (Though I am not a child if you want to withhold the
answer but give me the explanation I'd still appreciate that)
Alec
On 30/11/13 10:23, Jonathan Wakely wrote:
> On Saturday, 30 November 2013, Alec Teal wrote:
>> Thanks Jonathan.
>>
>> Already found that, I'm sending this because I am entirely out of ideas.
> But that's the solution.
>
> Where is your GCC 4.9.0 installed?
> (My guess is not /usr)
>
> What does the /usr/lib/x86_64-linux-gnu/libstdc++.so.6 symlink point to?
> (my guess is the libstdc++.so.6.0.17 from your GCC 4.7.3, which is too
> old to use for binaries built with GCC 4.9.0, which uses
> libstdc++.so.6.0.20)
>
>
>> Alec
>>
>> On 30/11/13 01:55, Jonathan Wakely wrote:
>>> On 30 November 2013 01:28, Alec Teal wrote:
>>>> The error is:
>>>>
>>>> ./A.out: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8'
>>>> not found (required by ./A.out)
>>> It means the version of libstdc++.so.6 being found by the dynamic
>>> linker at run-time is older than the version of libstdc++.so.6 that
>>> was used at link-time. That usually happens because you use a new
>>> version of GCC to compile and link, but do not tell the dynamic linker
>>> how to find the libraries from the new GCC.
>>>
>>> See http://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.how_to_set_paths
>>> and the section of the manual it links to.
>>
next prev parent reply other threads:[~2013-12-01 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 1:56 Alec Teal
2013-11-30 2:20 ` Jonathan Wakely
2013-11-30 4:19 ` Alec Teal
2013-11-30 17:51 ` Jonathan Wakely
2013-12-01 1:04 ` Alec Teal [this message]
2013-12-01 16:24 ` Jonathan Wakely
2013-12-03 16:45 ` Alec Teal
2013-12-04 13:21 ` Jonathan Wakely
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=529A8B18.1070008@warwick.ac.uk \
--to=a.teal@warwick.ac.uk \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).