[cfe-users] installing a complete clang++ environment

Klaus Rudolph lts-rudolph at gmx.de
Mon Sep 29 08:07:25 PDT 2014

> On 09/29/2014 06:09 PM, Klaus Rudolph wrote:
> > Ups forgett to tell you that the install script also fails:
> >
> > -- Installing: /usr/local/include/lldb/Symbol/TypeVendor.h
> > -- Installing: /usr/local/include/lldb/Symbol/ObjectContainer.h
> > -- Installing: /usr/local/include/lldb/Symbol/VerifyDecl.h
> > -- Installing: /usr/local/include/lldb/Symbol/TypeList.h
> > CMake Error at tools/lldb/scripts/cmake_install.cmake:36 (FILE):
> >   file INSTALL cannot find
> >   "/home/krud/work/clang_complett_aus_source/build/lib/python2.7".
> > Call Stack (most recent call first):
> >   tools/lldb/cmake_install.cmake:42 (INCLUDE)
> >   tools/cmake_install.cmake:70 (INCLUDE)
> >   cmake_install.cmake:61 (INCLUDE)
> >
> It's lldb fail. It puts its files to lib64/ directory, although the
> installation script look them in lib/ directory. You can just copy all
> files from ~/build/lib64/ to ~/build/lib/ before make install.
> Try to compile clang without lldb and clang-extra-tools.
> What distro do you use? It's a challenge to break Linux :)

It kills my last clang compiler, because it was installed there :-) So I can't compile anymore with any sort of clang... The rest of the distro is partly affected because the used dynamic libs are also lost. 

I am wondering why the install script ignores the target directory.

For the missing python??? things I simply removed the part of the install script. But I wonder if it did not work because python is installed on my system and it works.

And have you any idea why the build process must be handcrafted? I must fix so many files for additional include dirs. Could you compile and install without that? It feels quite hard to do a compile from sources and I am wondering that others can do it without such problems. And yes, why is there no actual documentation or maybe a simple bash script or Makefile for that?


More information about the cfe-users mailing list