https://bugs.llvm.org/show_bug.cgi?id=34192
lab...@google.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #8 from lab...@google.com ---
(In reply to labath from comment #7)
> (In reply to Jonas Hahnfeld from comment #6)
> > (In reply to labath from comment #5)
> > > I believe <https://reviews.llvm.org/D39010> will fix your problem, but I
> > > can't tell for sure (as things were working for me in the first place). If
> > > you have some time, I'd appreciate it if you can test it.
> >
> > I think this works, but maybe for the wrong reasons: I build with the LLVM
> > tree with Clang 4.0.1 and therefore have LD_LIBRARY_PATH with libc++ set. So
> > it does not pick up the newly built library in <root>/lib/...
>
> The purpose of the test is not to test the newly-built libc++. We just need
> _any_ c++ library around to be able to run the inferior. So, we pick the c++
> library that you build the rest of your toolchain with, since that has to be
> around and working. In your case, we just happen to need LD_LIBRARY_PATH set
> in order to use c++ library that we build with.
>
> So, unless I misunderstood something, I think this solution is fine.
I have committed r316244, which should fix this.
If the test still fails for you, or you think the fix is incorrect, let me
know.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
