[llvm-dev] llvm-trunk errors with gcc-5.3.0 on SuSE Linux

[Siegmar Gross via llvm-dev]

Hi Florian,

thank you very much for your help again. The build process finished
a few minutes ago and was successful with the enlarged number of
"svn update" commands.


Kind regards

Siegmar

Am 02.08.2017 um 17:03 schrieb Florian Hahn:
> 
> 
> On 02/08/2017 13:00, Siegmar Gross wrote:
>> Hi Florian,
>>
>> thank you very much for your help. I didn't use SVN before and I couldn't
>> find a good description how to download and build LLVM for parallel
>> programming. Now I do the following things.
>>
>> First check out:
>> ================
>>
>> svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
>> cd llvm/tools
>> svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
>> svn co http://llvm.org/svn/llvm-project/polly/trunk polly
>> cd clang/tools
>> svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk/ extra
>> cd ../../../projects
>> svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt
>> svn co http://llvm.org/svn/llvm-project/openmp/trunk openmp
>> svn co https://github.com/clang-ykt/openmp libomptarget
>>
>>
>> Hopefully I stored everything in correct places. Do I need anything else?
>>
>>
>> update
>> ======
>>
>> cd llvm
>> svn update
>> cd tools
>> svn update
>> cd clang
>> svn update
>> cd ../polly
>> svn update
>> cd ../clang/tools
>> svn update
>> cd extra
>> svn update
>> cd ../../../../projects
>> svn update
>> cd compiler-rt
>> svn update
>> cd ../openmp
>> svn update
>> cd ../libomptarget
>> svn update
>> cd ../../..
>>
>> Is it possible to update everything with fewer commands?
>>
>>
> 
> Maybe, though I am not aware of the better way, sorry.
> 
>> build:
>> ======
>>
>> rm -r build
>> mkdir build
>> cd build
>> cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/llvm-trunk \
>>    -DCMAKE_BUILD_TYPE:STRING="Release" \
>>    -DLLVM_PARALLEL_COMPILE_JOBS:STRING="4" \
>>    -DLLVM_PARALLEL_LINK_JOBS:STRING="4" \
>>    -DLLVM_TARGETS_TO_BUILD:STRING="NVPTX;X86" \
>>    -DLLVM_ENABLE_SPHINX=true \
>>    -DSPHINX_OUTPUT_MAN=true \
>>    -DCMAKE_C_COMPILER:STRING="/usr/local/gcc-5.3.0/bin/gcc" \
>>    -DCMAKE_C_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \
>>    -DCMAKE_CXX_COMPILER:STRING="/usr/local/gcc-5.3.0/bin/g++" \
>>    -DCMAKE_CXX_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \
>>    -DCMAKE_EXE_LINKER_FLAGS:STRING="-m64" \
>>    -DLLVM_LIBDIR_SUFFIX:STRING="64" \
>>    -DLLVM_POLLY_LINK_INTO_TOOLS:BOOL=ON \
>>
>> -DLIBOMPTARGET_DEP_LIBELF_INCLUDE_DIR:STRING="/usr/local/elfutils-0.169/include"
>> \
>>
>> -DLIBOMPTARGET_DEP_LIBELF_LIBRARIES:STRING="/usr/local/elfutils-0.169/lib64/libelf.so"
>> \
>>    -DLIBOMPTARGET_DEP_LIBFFI_INCLUDE_DIR:STRING="/usr/include" \
>>    -DLIBOMPTARGET_DEP_LIBFFI_LIBRARIES:STRING="/usr/lib64/libffi.so" \
>>    -DCUDA_INCLUDE_DIRS:STRING="/usr/local/cuda/include" \
>>    -DCUDA_LIBRARIES:STRING="/usr/local/cuda/lib64/libcudart.so" \
>>    -DBUILD_SHARED_LIBS:BOOL=ON \
>>    ../llvm \
>>    |& tee log.cmake
>> cmake --build . |& tee log.cmake-build
>>
>> Do you have further suggestions?
>>
>> Momentarily I try to build LLVM once more. I let you know, if I was able to
>> build it.
>>
> 
> I assume it worked now? If so, maybe respond to the thread created on
> the list, to let other people know, so they do not waste time looking
> into the issue too.
> 
> Cheers,
> Florian
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please 
> notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. 
> Thank you.