[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-dev
Subject:    Re: [cfe-dev] msan fails to get configured
From:       Csaba Raduly via cfe-dev <cfe-dev () lists ! llvm ! org>
Date:       2018-04-26 7:39:47
Message-ID: CAEhDDbAx7_RTBRA2gwbt1kybqV3k3E1J+8z=oWa-8rKXrPQ-Zw () mail ! gmail ! com
[Download RAW message or body]

On 4/25/18, Bartling, Ryan via cfe-dev <cfe-dev@lists.llvm.org> wrote:
> In the past, when I've seen this error, it's because I didn't have g++ or
> clang++ installed
>
> Try "which c++" or "which g++"
>
> -RB
>
>

How would "which g++" deal with

"
    /home/csabaraduly/wk/LLVM/build_release_7/./bin/clang

  is not a full path to an existing compiler tool.
"

?

Note that I did not run CMake on msan. I ran CMake on the toplevel
"llvm" directory. Msan's CMake was invoked *during the build*.

Csaba
-- 
You can get very substantial performance improvements by not doing the
right thing.
   - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers
(C++TDaWYK)
_______________________________________________
cfe-dev mailing list
cfe-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

[prev in list] [next in list] [prev in thread] [next in thread]