search for: dcmake_shared_linker_flags

Hi, Trying to compile llvm with the following configuration on Linux x86-64: cmake -G Ninja -DBUILD_SHARED_LIBS=ON \ -DCMAKE_SHARED_LINKER_FLAGS="-fuse-ld=gold" \ -DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=gold"\ -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ -DCMAKE_C_FLAGS="-O2 -g" \ -DCMAKE_CXX_FLAGS="-O2 -g" \...

...Aug 1, 2017, at 7:07 AM, İsmail Dönmez via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> Trying to compile llvm with the following configuration on Linux x86-64: >> >> cmake -G Ninja -DBUILD_SHARED_LIBS=ON \ >> -DCMAKE_SHARED_LINKER_FLAGS="-fuse-ld=gold" >> \ >> -DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=gold"\ >> -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ >> -DCMAKE_C_FLAGS="-O2 -g" \ >> -DCMAKE_CXX_FLAGS=&...

...& cmake -G "Unix Makefiles" \ -DCMAKE_C_COMPILER="$TOOLCHAIN/usr/bin/clang" \ -DCMAKE_CXX_COMPILER="$TOOLCHAIN/usr/bin/clang++" \ -DCMAKE_CXX_FLAGS="-stdlib=libc++" \ -DCMAKE_EXE_LINKER_FLAGS="-stdlib=libc++" \ -DCMAKE_SHARED_LINKER_FLAGS="-stdlib=libc++" \ -DCMAKE_INSTALL_PREFIX="$WORKSPACE/llvm/install" \ .. && make -j && make install) # ...normal build output... make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by `lib/Target/AArch64/...

...bails out with: X:/tools/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: Error: export ordinal too large: 283482 The command I used is: cmake \ -DLLVM_TARGETS_TO_BUILD=X86 \ -DCMAKE_BUILD_TYPE=Debug \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DLLVM_BUILD_TOOLS=OFF \ -DCMAKE_SHARED_LINKER_FLAGS="-t" \ -DCMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS="-t" \ -G "MinGW Makefiles" Am I doing something wrong? Did anyone managed to get a LLVM.dll with this toolchain?

On Mon, Oct 3, 2016 at 10:54 PM, Teresa Johnson <tejohnson at google.com> wrote: > > Aha - finally reproduced! The difference is using ld.bfd not > ld.gold. With that I get the same failure (using 3.9 to build 3.9 > sources): Thanks a lot! [...] > I am not sure what the official support story is for LLVMgold.so and > ld.bfd. As mentioned earlier, the LLVM site indicates

.../c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/bin/clang++ -DCMAKE_CXX_FLAGS='-stdlib=libc++' -DCMAKE_BUILD_WITH_INSTALL_RPATH=1 '-DCMAKE_INSTALL_RPATH:STRING=/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib' -DCMAKE_EXE_LINKER_FLAGS='-lc++ -lc++abi' -DCMAKE_SHARED_LINKER_FLAGS='-lc++ -lc++abi' /w/src/llvm.org -Krzysztof On 3/2/2016 6:21 PM, Lang Hames wrote: > Hi Krzysztof, > > If I understand correctly you're building LLVM top-of-tree with 3.7.0? > Or is this a bug in 3.7.0? > > What operating system are you on? > > Cheers, &gt...

Hi, I have having hard time to let cmake configuration detect the zlib header in windows with "Visual Studio 12" generator. My cmake configuration goes like >> Set path, include and lib environment variables to point to zlib headers and libraries. Cmake version is 2.8.12.2 cmake -G "Visual Studio 12" -D LLVM_TARGETS_TO_BUILD:STRING=%TARG% -D

...attner at gmail.com> wrote: > On Tue, Oct 4, 2016 at 2:22 AM, Xinliang David Li <xinliangli at gmail.com> > wrote: > > For clang build, cmake flags: > > > > -DCMAKE_EXE_LINKER_FLAGS=-fuse-ld=gold \ > > -DCMAKE_MODULE_LINKER_FLAGS=-fuse-ld=gold \ > > -DCMAKE_SHARED_LINKER_FLAGS=-fuse-ld=gold \ > > Thanks, this didn't break the cmake run. > > I've been successfully using LDFLAGS, CXXFLAGS, CPPFLAGS, CFLAGS. > It works, but now I wonder if it's safer to pass those via a > -DCMAKE_CXXFLAGS. > Any idea? If so, what are the LLVM CMake variables...

...ONS:BOOL=OFF -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_C_FLAGS=-fno-common -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON -DCMAKE_CXX_FLAGS=-fno-common -DCMAKE_SHARED_LINKER_FLAGS= -L/sw/lib -DCMAKE_MODULE_LINKER_FLAGS= -L/sw/lib -DCMAKE_EXE_LINKER_FLAGS= -L/sw/lib > On Sat, Oct 14, 2017 at 8:32 AM, Jack Howarth < > howarth.mailing.lists at gmail.com> wrote: > >> >> >> On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com&g...

> On Dec 20, 2016, at 5:49 AM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > ​Hi again, Teresa. > > Looks like I had forgotten to report back with success > when finally building 3.9.0 in ThinLTO linker mode > back in October. Sorry about that and thanks for > helping me out. I know how important it is to get > success reports as well, as a

...G=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= >> -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 >> -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_C_FLAGS=-fno-common >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON -DCMAKE_CXX_FLAGS=-fno-common >> -DCMAKE_SHARED_LINKER_FLAGS= -L/sw/lib -DCMAKE_MODULE_LINKER_FLAGS= >> -L/sw/lib -DCMAKE_EXE_LINKER_FLAGS= -L/sw/lib >> >> >>> On Sat, Oct 14, 2017 at 8:32 AM, Jack Howarth < >>> howarth.mailing.lists at gmail.com> wrote: >>> >>>> >>>> >>>>...

...I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_EXE_LINKER_FLAGS="-lc++abi -lc++" -DCMAKE_EXE_LINKER_FLAGS="-lc++abi -lc++" -DCMAKE_SHARED_LINKER_FLAGS="-lc++abi -lc++" -DCMAKE_MODULE_LINKER_FLAGS="-lc++abi -lc++" -DLLVM_ENABLE_LIBCXX=ON -DLLVM_LIBDIR_SUFFIX=64 -DCMAKE_INSTALL_PREFIX=/usr -DLLDB_DISABLE_PYTHON=1 -DTARGET_TRIPLE="x86_64-pc-linux-gnu" -DLIBCXX_INSTALL_EXPERIMENTAL_LIBRARY=ON -DLLVM_ENABLE_LLD=ON...

After re-cmaking and rebuilding everything from scratch, I'm seeing failures in MCJIT. It this something known or expected? I build LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++". Example failure: /w/bld/org/./bin/lli -remote-mcjit -mcjit-remote-process=/w/bld/org/./bin/lli-child-target /w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll -- Exit Code:

...; -DLLVM_TARGETS_TO_BUILD="X86" >> -DCMAKE_BUILD_TYPE=Release >> -DCMAKE_C_COMPILER=/usr/bin/clang >> -DCMAKE_CXX_COMPILER=/usr/bin/clang++ >> -DCMAKE_EXE_LINKER_FLAGS="-lc++abi -lc++" >> -DCMAKE_EXE_LINKER_FLAGS="-lc++abi -lc++" >> -DCMAKE_SHARED_LINKER_FLAGS="-lc++abi -lc++" >> -DCMAKE_MODULE_LINKER_FLAGS="-lc++abi -lc++" >> -DLLVM_ENABLE_LIBCXX=ON >> -DLLVM_LIBDIR_SUFFIX=64 >> -DCMAKE_INSTALL_PREFIX=/usr >> -DLLDB_DISABLE_PYTHON=1 >> -DTARGET_TRIPLE="x86_64-pc-linux-gnu" >> -DLIBC...

On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com> wrote: > Hi Jack: > > Yes, I was just looking at that. Seems like TableGen wasn't done along > with the rest of llvm. I'll work up a complete patch shortly. > > Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by > any chance? You might check the value for

On 2020-03-29, Nemanja Ivanovic via llvm-dev wrote: >Glad you got it working. >My suggestion about LLVM_ENABLE_THREADS didn't work because you didn't >apply it when building the build linker. > >When you don't have the ability to rebuild the build compiler, this doesn't >apply. In those cases, I end up doing a dirty hack where I use a wrapper >script with