similar to: OSX 10.5 PowerPC and hang after "Looking for __cxa_throw in stdc++"

I'm trying to build LLVM, CFE and RT from sources on an old PowerMac with OS X 10.5. After download and unpack into LLVM_SOURCE_DIR (with --strip-components=1), I configure with: cmake -DCMAKE_INSTALL_PREFIX="/opt/llvm" \ -DLLVM_TARGETS_TO_BUILD="PowerPC" \ -DLLVM_INCLUDE_TOOLS="ON" \ -DLLVM_BUILD_TESTS="ON"

Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git

Hi, I switched from "configure and make" to "cmake" build-system and wanted to speedup my build. In my build-script I use... CMAKE_JOBS="1" ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS -DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS" [1] says in "LLVM-specific variables" section... ***

I had only a quick view on the blog-texts. It might be that a CLANG generated with LTO/PGO speeds up the build. Can you confirm this? Can you confirm binutils-gold speed up the build? Has LLVM an own linker? Can be used? Speedup the build? Yesterday night I loooked through available CMAKE/LLVM variables... ### GOLD # CMAKE_LINKER:FILEPATH=/usr/bin/ld #

Before: /Users/echeng/LLVM/llvm/Release/bin/llvm-ld -L/Developer/usr/llvm- gcc-4.2/lib/gcc/i686-apple-darwin9.2.0/4.2.1 -L/Developer/usr/llvm- gcc-4.2/lib Output/444.namd.linked.bc -lc -lstdc++ -lm -o Output/ 444.namd.llvm llvm-ld: warning: Cannot find library 'stdc++' Now: /Users/echeng/LLVM/llvm/Release/bin/llvm-ld -L/Developer/usr/llvm-

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

On Fri, Nov 16, 2018 at 12:46 AM Tom Stellard <tstellar at redhat.com> wrote: > > On 11/15/2018 09:39 PM, Jeffrey Walton via llvm-dev wrote: > > I'm trying to build LLVM, CFE and RT from sources on an old PowerMac > > with OS X 10.5. > > Which version of clang/llvm are you using? LLVM 7.0. The script is available at

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>

What u wrote here: >>once again this folder stdc++.txt does exist.... ...reminds me on having charset problems with samba, doing the same stuff here until I set up the right charsets. Also, u see in logfile: >>call_trans2qfilepathinfo: vfs_stat of New Folder2231113/.directory failed >>(No such file or directory) And u say: >>but this directory NewFolder2231113 does

Thus wrote David Demelier via llvm-dev: > Also you will need to add more options to the components. See for example: > > LIBCXX_CXX_ABI=libcxxabi > LIBCXX_USE_COMPILER_RT=On > LIBCXXABI_USE_LLVM_UNWINDER=On > LIBCXXABI_USE_COMPILER_RT=On > LIBCXX_HAS_GCC_S_LIB=Off > LIBUNWIND_USE_COMPILER_RT=On > > And as mentioned above > > CLANG_DEFAULT_CXX_STDLIB=libc++

Hi, I'm try to build llvm on my PC but it failed. I'm using following command, $ cmake -G "Ninja" ../llvm -DCMAKE_INSTALL_PREFIX=prefix=$INSTALL_PATH -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On $ ninja-build -j 2 I have skipped libcxx and libcxxabi package. It shows below error, 00:04:23 [3261/3430] Building CXX object

>because with that generator the CMAKE_BUILD_TYPE variable is ignored >because it is a "multi-configuration target". thanks for the link, is that a bug in the CMake configuration (or better not getting any warning) or is there just documentation missing? so i can use --config Debug or --config Release and get the correct results - i hope that works the build takes hours

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) directory structure test   llvm <-- git clone https://github.com/llvm-mirror/llvm     tools       clang <-- git clone https://github.com/llvm-mirror/clang   llvm_build Debug build: clean build, llvm_build is deleted before llvm_build> cmake

>are you setting the optimized tablegen option? LLVM_OPTIMIZED_TABLEGEN is not active - i will try that >In addition, make sure you have plenty of memory i've got only Intel Core 2 Quad CPU Q8300/2.50Ghz and 8GB RAM for testing not much cpu power AND memory Am 19.09.2018 um 11:31 schrieb James Henderson: > Regarding the Debug build taking hours, are you setting the optimized

Hello, I'm working on a project involving LLVM and keep shifting between the Debug and Release build by assigning different values to CMAKE_BUILD_TYPE in <llvm_build>/CMakeCache.txt and then building it. I wanted to know if this was a safe alternative to re-configuring the build after removing <llvm_build>/CMakeFiles/ and <llvm_build>/CMakeCache.txt. Thanks, Sanjay

Hello All Where is the documentation for ADT/StringMap.h (given into account that I am not quite familiar with stdc++ library)? In particular, I am surprised that key strings are specified by their start and end, I was expecting C-like strings, ie null terminated array of chars. Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email:

Hi Vivek, you can also include these lines below to your ~/.bash_profile: LLVM_BUILD="/Developer/llvm/build" # Path to your build directory alias new-clang="$LLVM_BUILD/bin/clang -Wno-expansion-to-defined -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include" alias new-clang++="$LLVM_BUILD/bin/clang++

At 2013-07-14 13:20:42,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/13/2013 09:18 PM, Star Tan wrote: >> >> >> At 2013-07-14 02:30:07,"Tobias Grosser" <tobias at grosser.es> wrote: >>> On 07/13/2013 10:13 AM, Star Tan wrote: >>>> Hi Tobias, >>> >>> Hi Star, >[...] >>> Before we write a

Dear community, this is just a suggestion, but might be useful for the following R releases. I was programming some C code for R and my compiler constantly showed me some crazy messages that a stdc++ macro length() was supplied with 4 arguments whereas only one was required. The problem could be partially resolved by changing the order of includes. However as soon as the file was used from