I have no ideas about an error involving CXXABI

[Alec Teal]

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.
>>