This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: missing symbols in libstdc++.so.6 built from the 4.9 branch
- From: Aurelien Jarno <aurel32 at debian dot org>
- To: Matthias Klose <doko at ubuntu dot com>
- Cc: "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, gcc Development <gcc at gcc dot gnu dot org>, Ramana Radhakrishnan <ramana dot radhakrishnan at arm dot com>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>, Dave Anglin <dave dot anglin at bell dot net>
- Date: Wed, 2 Jul 2014 11:43:06 +0200
- Subject: Re: missing symbols in libstdc++.so.6 built from the 4.9 branch
- Authentication-results: sourceware.org; auth=none
- References: <53B273E6 dot 8040402 at ubuntu dot com>
On Tue, Jul 01, 2014 at 10:40:06AM +0200, Matthias Klose wrote:
> on some linux architectures there are some symbols missing in libstdc++.so.6
> built from the 4.9 branch. I didn't notice before due to a packaging bug.
> affected are ARM32, HPPA, SPARC.
>
> - ARM32 (build log [1], both soft and hard float) are missing
> __aeabi_atexit@CXXABI_ARM_1.3.3
> __aeabi_vec_*
>
> Can these be ignored?
>
> - HPPA (build log [2]), is missing all the future_base symbols and
> exception_ptr13exception symbols, current_exception and
> rethrow_exception.
>
> - SPARC (build log [3]) configured for sparc64-linux-gnu is missing
> symbols in the 32bit multilib build, although these are present
> in a sparc-linux-gnu build. Missing are same ones as in the HPPA
> build, long double 128 related symbols, numeric_limits, and some
> math symbols.
>
> Looks like more than one issue is involved, I remember that the
> math symbols were already dropped in earlier versions for other
> architectures. The build is configured -with-long-double-128.
>
I think that for sparc long double issue, the problem is that
-with-long-double-128 doesn't work as -mlong-double-64 is forced when
-m32 is used. I sent a patch a few months ago [1], but it has some side
effect and I never came to a better version. Any help on how to do that
properly is welcome, and I can build test some patches if needed.
[1] https://gcc.gnu.org/ml/gcc-patches/2013-12/msg00318.html
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net