Re: Running C++11 shared library with older gcc, libc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: NightStrike <nightstrike@xxxxxxxxx>
Subject: Re: Running C++11 shared library with older gcc, libc
From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Date: Thu, 23 Jun 2016 19:10:42 +0100
Cc: gcc-help <gcc-help@xxxxxxxxxxx>, Dinesh Pathak <dinesh.pathak@xxxxxxxxx>
In-reply-to: <CAF1jjLszJaBUJnzn30pDduhH8gH3cSewFaggmumQ0DLbJS-d5w@mail.gmail.com>
References: <CAHsD-6Da=98yN2efjqXNfJf0AaneB2JSGZXM0hYCDVqADhqyQA@mail.gmail.com> <CAH6eHdS77ZBddDb5pocbECtEVxZmCdpFEBFMA+RiLFHrg-YfPw@mail.gmail.com> <CAF1jjLszJaBUJnzn30pDduhH8gH3cSewFaggmumQ0DLbJS-d5w@mail.gmail.com>

On 23 June 2016 at 13:36, NightStrike wrote:
> Does it solve the problem by statically linking libstdc++ by default?

No, it links to a libstdc++_nonshared.a which only contains the
symbols not present in the system libstdc++.so

References:
- Running C++11 shared library with older gcc, libc
  - From: Dinesh Pathak
- Re: Running C++11 shared library with older gcc, libc
  - From: Jonathan Wakely

Prev by Date: Re: double and float in GCC
Next by Date: gcc 6.1 generates movaps for unaligned memory
Previous by thread: Re: Running C++11 shared library with older gcc, libc
Next by thread: gcc 6.1 generates movaps for unaligned memory
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux