search for: lxar

On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: > Jack, > > What version of CMake are you using? > > -Chris Chris, I am using cmake 3.5.2. My read of this problem is as follows. While libLLVM.dylib is being linked against -lxar when -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib is created with -Wl,-dead_strip such that any symbols from libxar not explicitly used with in the object files of libLLVM.dylib are stripped out. This means that those additional symbols used by llvm-objdump aren't access...

...16 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: >> Jack, >> >> What version of CMake are you using? >> >> -Chris > > Chris, > I am using cmake 3.5.2. My read of this problem is as follows. > While libLLVM.dylib is being linked against -lxar when > -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib > is created with -Wl,-dead_strip such that any symbols from libxar not > explicitly used with in the object files of libLLVM.dylib are stripped > out. This means that those additional symbols used by llvm-objdu...

...anz at apple.com> wrote: >>> Jack, >>> >>> What version of CMake are you using? >>> >>> -Chris >> >> Chris, >> I am using cmake 3.5.2. My read of this problem is as follows. >> While libLLVM.dylib is being linked against -lxar when >> -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib >> is created with -Wl,-dead_strip such that any symbols from libxar not >> explicitly used with in the object files of libLLVM.dylib are stripped >> out. This means that those additional symbols us...

...e build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I don't see anything in the cmakefiles for tools/llvm-objdump to provide the necessary linkage on the system libxar shared library. Appending the missing linkage for -lxar onto build/stage1tools/llvm-objdump/CMakeFiles/llvm-objdump.dir/link.txt... /sw/src/fink.build/llvm39-3.9.0-1/opt-bin/ccclang++ -fno-common -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered...

...DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on > the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I > don't see anything in the cmakefiles for tools/llvm-objdump to provide > the necessary linkage on the system libxar shared library. Appending > the missing linkage for -lxar onto > build/stage1tools/llvm-objdump/CMakeFiles/llvm-objdump.dir/link.txt... > > /sw/src/fink.build/llvm39-3.9.0-1/opt-bin/ccclang++ -fno-common > -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic...

Hi Jack, Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via: #ifdef HAVE_LIBXAR extern "C" { #include <xar/xar.h> } #endif I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this. Kev > On May 24, 2016, at

On Tue, May 24, 2016 at 1:24 PM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > On Tue, May 24, 2016 at 1:22 PM, Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote: >>> Kevin Enderby added those symbol uses in r270491. It has a cmake >>> feature test, and