This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: I have no ideas about an error involving CXXABI
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Alec Teal <a dot teal at warwick dot ac dot uk>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Sat, 30 Nov 2013 10:23:53 +0000
- Subject: Re: I have no ideas about an error involving CXXABI
- Authentication-results: sourceware.org; auth=none
- References: <52993F21 dot 2060700 at warwick dot ac dot uk> <CAH6eHdR=dyv7kM_4XoFZWhMGjuRsp1q8E3qBQY_Otg=5ge2XXg at mail dot gmail dot com> <52994B57 dot 4030003 at warwick dot ac dot uk>
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.
>
>