This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/66530] libstdc++ testsuite links to incorrect shared libstdc++ library
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 16 Jun 2015 09:07:50 +0000
- Subject: [Bug libstdc++/66530] libstdc++ testsuite links to incorrect shared libstdc++ library
- Auto-submitted: auto-generated
- References: <bug-66530-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66530
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-06-16
Ever confirmed|0 |1
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jennifer Yao from comment #2)
> Are you sure that the libstdc++ in the build tree is the one that's loaded
> at runtime on your system? I only ask because I don't have a Linux system to
> test on, and it would be relatively easy to overlook since much of libstdc++
> is header-only anyway.
Absolutely 100% sure. I test it several times a day without installing anything
and if changes I made to non-header code were not testable without installing
the library I would have noticed years ago. For the most recent example, I
testing this patch without installing the library:
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00917.html
The problem seems to be that LD_LIBRARY_PATH is only used for dlopen() on
cygwin, not for finding dynamically-linked shared libraries.