similar to: [LLVMdev] rpath'd binaries

Hello LLVM devs, I am trying to package llvm for NetBSD. The package checker scripts are complaining about bad rpaths in the binaries. I see that they are relative to the build directory. I have no idea why that would be. Can you explain? If I build as myself, for testing (e.g.): $ readelf -d ~/downloads/llvm-2.6/Release/bin/llvm-ar Dynamic section at offset 0x15af28 contains 25 entries:

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

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

> Are you using cmake for building LLVM? > > If the answer is yes, please ask on the cmake mailing list. > > Usually cmake sets the RPATH when building LLVM as shared objects. But > on my Linux box it does not set RPATH when building LLVM as static > libraries. I do not have cmake installed - and when packaging for NetBSD (IIRC) you need to explicitly tell it that cmake is

"Larson, Timothy E." <TELarson at west.com> writes: > Hello LLVM devs, > > I am trying to package llvm for NetBSD. The package checker scripts > are complaining about bad rpaths in the binaries. I see that they are > relative to the build directory. I have no idea why that would be. > Can you explain? Are you using cmake for building LLVM? If the answer is

Anton, Thanks for your comment. 2nd patch attached. - s/SharedDir/SharedLibDir/g - move prefix=cyg sunk into if(cygwin or mingw) arigato gozaimasu...Takumi * Additional issues - You may build LLVMHello.dll but I don't modify lib/Transforms/Makefile. Because making LLVMHello.dll requires the library LLVM.dll, but it oughta be on the way to making libs at building

Hi All, I'm looking to package up celt for inclusion in Fedora as the next stable release of ekiga/opal will have support for it. I've run into two issues in compiling it into a rpm. The first is a show stopper, then second one not so much of an issue but thought I'd report it for reference. The first issue is due to the celtdec and celtenc explicitly define rpath. I get the

Hi all, I'm trying to understand why LLVM uses @rpath as the install name in its dynamic libraries on macOS. This complicates the process of linking against libLLVM from third-party tools and isn't nearly as common a practice on macOS as it is on Linux. I tried tracing through history on the LLVM repo and the main thing I could find was a commit from ages ago saying that the libraries are

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

On 07/30/2014 10:06 AM, Larry Evans wrote: > On 07/30/2014 12:35 AM, Ben Pope wrote: >> On Wednesday, July 30, 2014 01:31 PM, Ben Pope wrote: >> >>> ldd your_built_clang | grep libstdc++ >>> chrpath -l your_built_clang >> >> Hmm, where "your_built_clang" should be the actual failing executable: >>

Hey Michael, I completely agree that setting the rpath properly the first time around is much preferred. But, changes to the binary, particularly during development is much quicker. Prebuilt libraries which are being repackaged is one use case that is missed. In the past, I’ve even used it to repair am incorrectly built library which was missing the library name. There are a few different

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

I'm following this thread here http://www.centos.org/modules/newbb/viewtopic.php?topic_id=23749&forum=38 to build an rpm for thunderbird 3.1.6/3.1.7 from source. While it works well on i386, compilation fails for x86_64. Any advice how to fix the spec file? ... rm -f libthebes.so c++ -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth

Hi LLVMDev, The following issues have been fixed since the last update I sent out. Completed: * Bug 19462 - Use the INSTALL(EXPORT ...) to export CMake definitions * Bug 21561 - Update release scripts to use CMake These issues are still outstanding. Classification of blocking vs non-blocking are my own opinions, please let me know if you disagree. All non-blocking issues are still serious bugs

Hello, thank you for the thoughts. > Have you seen the docs for CMake3.0 [1] (see cmake-buildsystem > especially)? They certainly aren't perfect but they are considerably > better than what was there before. Okay, the documentation has come a long way since 3.0 although it still needs a bit of polish. > I wouldn't say that much "important functionality is plain

Hi all, Time for another update on the status of the CMake build system. Completed: * Bug 18496 - [cmake] .S assembly files not compiled by cmake in libclang_rt.ARCH * Bug 22725 - lldb build with cmake fails with "Program error: Invalid parameters entered, -h for help. " * Update GettingStarted to prefer CMake Still Outstanding: * Bug 14109 - CMake build for compiler-rt should use

Hey everyone! Recently there has been some progress on LLVM-based tools for manipulating MachO binaries: llvm-objcopy has been gaining a lot of important bits to support MachO (it's relatively close to the point where one can implement the strip-like functionality), llvm-lipo is functional and supports most of cctools' lipo options (https://llvm.org/docs/CommandGuide/llvm-lipo.html). There

Probably not a blocker for replacing autoconf, while at it: Bug 23468 - LLVM_OPTIMIZED_TABLEGEN does not work with Visual Studio. It makes the tablegenning really slow. 2015-05-28 18:22 GMT+03:00 Chris Bieneman <beanz at apple.com>: > Hi all, > > Time for another update on the status of the CMake build system. > > Completed: > * Bug 18496 - [cmake] .S assembly files not

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the