cd ~\/sourceInstallations\r\nsvn co http:\/\/llvm.org\/svn\/llvm-project\/llvm\/tags\/RELEASE_360\/final llvm_RELEASE_360\r\ncd llvm_RELEASE_360\/tools\r\nsvn co http:\/\/llvm.org\/svn\/llvm-project\/cfe\/tags\/RELEASE_360\/final clang\r\ncd ..\/projects\r\nsvn co http:\/\/llvm.org\/svn\/llvm-project\/compiler-rt\/tags\/RELEASE_360\/final compiler-rt\r\nsvn co http:\/\/llvm.org\/svn\/llvm-project\/libcxx\/tags\/RELEASE_360\/final libcxx\r\nsvn co http:\/\/llvm.org\/svn\/llvm-project\/libcxxabi\/tags\/RELEASE_360\/final libcxxabi\r\ncd ..\r\nsvn update\r\n    At revision X.\r\n    --- Hopefully this outputs one line saying \"At revision X\", but numbers instead of \"X\".  If it downloads more source files, a new revision was released while you were downloading the source code.  This is highly unlikely unless you're using trunk (the most up to date, maybe unstable code.)  But, if this happens, perform a svn update in the tools\/clang, projects\/compiler-rt, projects\/libcxx, projects\/libcxxabi, and again ~\/sourceInstallations\/llvm_RELEASE_360, until you are fully up to date.\r\n<\/code><\/pre>\n<\/li>\n
Build LLVM & Clang. This will run for a while. If this completes correctly, the last line you will see will say “success”. It is normal to see some error-looking messages scrolling by quickly. It’s always a good idea to build things in a different directory than a source directory.\n
mkdir ..\/llvm_RELEASE_360_build\r\ncd ..\/llvm_RELEASE_360_build\r\ncmake -G \"Unix Makefiles\" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=\/usr\/local\/bin\/gcc -DCMAKE_CXX_COMPILER=\/usr\/local\/bin\/g++ ..\/llvm_RELEASE_360 && make && sudo make install && echo success\r\n    --- If your VPS has multiple cores, you can speed up the build by changing the middle part\r\n    ---   of this line from \"&& make &&\" to \"&& make -j <number of cores> &&\".\r\n    --- You can see the number of cores your VPS has by running \"nproc\"\r\n    --- If you omit -DCMAKE_BUILD_TYPE=Release, the build defaults to debug.  This is great if you need to debug LLVM & Clang itself, but slows down compilation of your end programs considerably.\r\n    --- If you omit the references to gcc and g++, it will default to using the older binary versions in \/usr\/bin\/, and will not compile.\r\n<\/code><\/pre>\n<\/li>\n
Check the installed versions, and see their locations.\n
clang --version\r\n    May say: clang version 3.6.0 (tags\/RELEASE_360\/final 237229)\r\nclang++ --version\r\n    May say: clang version 3.6.0 (tags\/RELEASE_360\/final 237229)\r\nwhich clang\r\n    \/usr\/local\/bin\/clang\r\nwhich clang++\r\n    \/usr\/local\/bin\/clang++\r\n<\/code><\/pre>\n<\/li>\n
Add the new libraries to ld (the GNU linker).\n
echo \"\/usr\/local\/lib\" > usrLocalLib.conf\r\nsudo mv usrLocalLib.conf \/etc\/ld.so.conf.d\/\r\nsudo ldconfig\r\n    --- This may say a file or two \"is not an ELF file - it has the wrong magic bytes at the start.\"\r\n    --- You may ignore this message.  It is silent about the work it successfully completed.\r\n<\/code><\/pre>\n<\/li>\n
Optionally make a “hello world” program.\n
mkdir ~\/code\r\ncd ~\/code\r\nCreate a file main.cpp that says:\r\n    #include <iostream>\r\n    using namespace std;\r\n    int main() {\r\n        cout << \"Hello world!\" << endl;\r\n        return 0;\r\n    }\r\n--- One way to create this file is to run \"vi main.cpp\", hitting \"i\" to enter insert mode,\r\n---   typing the above file, hitting ESC, and hitting \"ZZ\" to save.\r\nclang++ main.cpp -o main\r\n.\/main\r\n    Hello World!\r\nclang++ -stdlib=libc++ -lc++abi main.cpp -o main\r\n    --- This uses Clang's libc++ and libc++abi, instead of the GNU stdlibc++ and stdlibc++abi\r\n.\/main\r\n    Hello world!\r\n<\/code><\/pre>\n<\/li>\n
Use LLVM & Clang when you want to.\n
You could set LLVM & Clang to be your system's default C and C++ compiler by running:\r\n    echo \"export CC=\/usr\/local\/bin\/gcc\" >> ~\/.bashrc\r\n    echo \"export CXX=\/usr\/local\/bin\/g++\" >> ~\/.bashrc\r\n    source ~\/.bashrc\r\nOnce and a while there is a difference between Clang and GCC, but it's becoming more and more rare.  To be more conservative, you could specify in your code's buildsystem to use LLVM & Clang, but otherwise leave your system's default to the source build of GCC.\r\n<\/code><\/pre>\n<\/li>\n
Optionally reclaim hard drive space. Your\u00a0~\/sourceInstallations<\/code>\u00a0folder will be taking up around 11GB of disk space. It’s probably wise to keep the folders, as there are optional configuration options you may need to use at some point in the future, and it would be faster to have a lot already done. And, as mentioned above, there are additional “sub-projects” you can add to LLVM & Clang. Also, the build process makes logs that you can later check and work from if something goes wrong. But, after running “sudo make install” earlier, your installed LLVM & Clang isn’t depending on anything in this directory, and space can be at a premium, so you can do this step and reclaim the 11GB.\n
cd ~\/\r\nrm -rf sourceInstallations\r\n--- Again, if you can spare the space, you may someday be happy to have left it there.\r\n<\/code><\/pre>\n<\/li>\n<\/ol>\n
You now have your newer LLVM & Clang in\u00a0\/usr\/local\/bin<\/code>, your newer 64-bit LLVM & Clang libs in\u00a0\/usr\/local\/lib<\/code>, and your newer LLVM & Clang include files in\u00a0\/usr\/local\/include<\/code>.<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","manualknowledgebasecat":[231,242],"manual_kb_tag":[503],"_links":{"self":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3023"}],"collection":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/comments?post=3023"}],"version-history":[{"count":2,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3023\/revisions"}],"predecessor-version":[{"id":3025,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3023\/revisions\/3025"}],"wp:attachment":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/media?parent=3023"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manualknowledgebasecat?post=3023"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb_tag?post=3023"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}