search for: have_libxar

On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: > 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. While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on the cmake options produ...

...May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: >> 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. > > While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=O...

...itly used with in the object files of libLLVM.dylib are stripped out. This means that those additional symbols used by llvm-objdump aren't accessible from libLLVM.dylib's linkage on libxar and an additional explicit linkage on libxar is required in the tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and LLVM_LINK_LLVM_DYLIB are set. Jack > >> On May 24, 2016, at 11:00 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: >> >> On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote: >>> Hi Jack, >>> >>&...

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 10:28 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > > On Tue...

...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 all the uses of those symbols appear bracketed in >>> HAVE_LIBXAR, so I don't know what went wrong for you. >> >> The trigger for this build failure is the usage of >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >> option, the linkage failure for llvm-objdump disappears. > > Wrong cmake option. I meant to say...

...e object files of libLLVM.dylib are stripped > out. This means that those additional symbols used by llvm-objdump > aren't accessible from libLLVM.dylib's linkage on libxar and an > additional explicit linkage on libxar is required in the > tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and > LLVM_LINK_LLVM_DYLIB are set. > Jack Also note that this issue doesn't arise for the cmake build with -DBUILD_SHARED_LIBS:BOOL=ON because the resulting lib/Object/CMakeFiles/LLVMObject.dir/link.txt contains... /sw/src/fink.build/llvm39-3.9.0-1/opt-bin/ccclang++ -fno-commo...

...f libLLVM.dylib are stripped >> out. This means that those additional symbols used by llvm-objdump >> aren't accessible from libLLVM.dylib's linkage on libxar and an >> additional explicit linkage on libxar is required in the >> tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and >> LLVM_LINK_LLVM_DYLIB are set. >> Jack > > Also note that this issue doesn't arise for the cmake build with > -DBUILD_SHARED_LIBS:BOOL=ON because the resulting > lib/Object/CMakeFiles/LLVMObject.dir/link.txt contains... > > /sw/src/fink.build/llvm39-3...

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 all the uses of those symbols appear bracketed in > HAVE_LIBXAR, so I don't know what went wrong for you. The trigger for this build failure is the usage of -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake option, the linkage failure for llvm-objdump disappears. > > On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev > <l...

Kevin Enderby added those symbol uses in r270491. It has a cmake feature test, and all the uses of those symbols appear bracketed in HAVE_LIBXAR, so I don't know what went wrong for you. On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in > current trunk? > > [ 95%] Linking CXX executable ../../bin/llvm-o...

...rth <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 all the uses of those symbols appear bracketed in >> HAVE_LIBXAR, so I don't know what went wrong for you. > > The trigger for this build failure is the usage of > -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake > option, the linkage failure for llvm-objdump disappears. Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYL...

Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in current trunk? [ 95%] Linking CXX executable ../../bin/llvm-objdump Undefined symbols for architecture x86_64: "_xar_serialize", referenced from: DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, unsigned int, bool, bool, bool, std::__1::basic_string<char, std::__1::char_traits<char>,

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...NTERNAL=1 //Have include inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have symbol isatty HAVE_ISATTY:INTERNAL=1 //Have library dl HAVE_LIBDL:INTERNAL=1 //Have library edit HAVE_LIBEDIT:INTERNAL=1 //Have library pthread HAVE_LIBPTHREAD:INTERNAL=1 //Have library rt HAVE_LIBRT:INTERNAL=1 //Have library xar HAVE_LIBXAR:INTERNAL= //Have library z HAVE_LIBZ:INTERNAL=1 //Have include link.h HAVE_LINK_H:INTERNAL=1 //Have symbol lseek64 HAVE_LSEEK64:INTERNAL=1 //Have include mach/mach.h HAVE_MACH_MACH_H:INTERNAL= //Have symbol mallctl HAVE_MALLCTL:INTERNAL= //Have symbol mallinfo HAVE_MALLINFO:INTERNAL=1 //Have includ...