This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libitm/63781] potential linkage issue with libitm.1.dylib
- From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 08 Nov 2014 19:04:38 +0000
- Subject: [Bug libitm/63781] potential linkage issue with libitm.1.dylib
- Auto-submitted: auto-generated
- References: <bug-63781-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63781
--- Comment #7 from howarth at bromo dot med.uc.edu ---
(In reply to howarth from comment #6)
> Okay, I see the missing linkage on libstdc++ is intentional...
>
> # Force link with C, not C++. For now, while we're using C++ we don't
> # want or need libstdc++.
> libitm_la_DEPENDENCIES = $(libitm_version_dep)
> libitm_la_LINK = $(LINK) $(libitm_la_LDFLAGS)
> libitm_la_LDFLAGS = $(libitm_version_info) $(libitm_version_script)
>
On reflection, if this were true shouldn't there be no undefined symbols from
libstdc++ present in the libitm shared library?