similar to: [LLVMdev] 2.4 Pre-release (v1) Available for Testing

On Fri, Oct 10, 2008 at 2:11 PM, Tanya M. Lattner <tonic at nondot.org> wrote: > > LLVMers, > > The 2.4 pre-release is available for testing: > http://llvm.org/prereleases/2.4/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or use

Hi Michael, On Tue, 2007-01-16 at 10:24 +0800, Michael T. Richter wrote: > I'm trying to get LLVM1.9 working on my Ubuntu 6.10 system. The LLVM > version in the repositories is 1.7 and I've never managed to get it > successfully working because whoever packaged it thought it would be > fun to rename everything. This means I can't use it to build 1.9 and > I've

On Tue, 2007-16-01 at 02:50 +0000, Reid Spencer wrote: > > The build instructions provided tell me to build llvm-gcc first from > > the source. > > The source for that tells me to build llvm first from the source. I'm > > not sure where to go from this point. > You should build llvm first, then llvm-gcc. When I build LLVM first, however, I get told that it

I'm trying to get LLVM1.9 working on my Ubuntu 6.10 system. The LLVM version in the repositories is 1.7 and I've never managed to get it successfully working because whoever packaged it thought it would be fun to rename everything. This means I can't use it to build 1.9 and I've therefore decided to try bootstrapping a 1.9 build. Yes, I've looked at the docs where it said

OvermindDL1 <overminddl1 at gmail.com> writes: [snip] > On this first compile everything compiled except for llc and lli, > which did not link due to: > unresolved external symbol "class llvm::FunctionPass * __cdecl > llvm::createPBQPRegisterAllocator(void)" That is because the lib/CodeGen project file is missing PBQP.cpp. [snip] > On Fri, Oct 10, 2008 at 2:11

Hello, Elvis > $ ../src/configure --program-prefix=llvm- --disable-bootstrap > --enable-checking --enable-languages=c,c++ You haven't configured llvm-gcc properly. Please do read readme.llvm file. However, afair, Trident was LLVM 1.5-based, and it will require massive rewrite to use LLVM 2.x (bytecode format was also changed) -- With best regards, Anton Korobeynikov Faculty of

On Thu, 28 Sep 2006, Nick Lewycky wrote: > Thanks for that workaround. What I've been doing is copying > /lib/libgcc_s.so.1 over LLVM's copy and rebuilding xgcc. > > A long-term fix for this would be nice. I'm not hitting this, so I'm relying on you guys to figure out what the right solution is. > Why does llvm-gcc build its own libgcc_s.so? Would we have the same

Nick, How exactly do you envision this being done? Looking at the contents of config/darwin.h, I see... /* Support -mmacosx-version-min by supplying different (stub) libgcc_s.dylib libraries to link against, and by not linking against libgcc_s on earlier-than-10.3.9. Note that by default, -lgcc_eh is not linked against! This is because in a future version of Darwin the EH frame

Hello all, little question. Has somebody already compiled samba on SunOS 5.8 because I cannot statically link libgcc libraries. I already tried "gcc -static-libgcc", added "-lgcc_s" to LIBS variable but always the same result. Below resulted compiled binary .. # ldd bin/ntlm_auth libthread.so.1 => /usr/lib/libthread.so.1 libsendfile.so.1 =>

On 22 October 2014 19:24, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > I do compiler_rt + libc++abi + libc++ + clang (with a custom ToolChain) testing > of libc++ on bare-metal ARM.... so it is possible. Perhaps you mean to say that > it's not possible to test libunwind on arm-linux when using compiler_rt? Yeah, it's hard and clumsy, not impossible. Basically,

On Fri, Sep 18, 2009 at 10:28:15AM -0700, Nick Kledzik wrote: > So, when these test cases are run, is the binary linked against /usr/ > lib/libgcc_s.10.5.dylib? or against some just built libgcc_s.10.5.dylib? > or against some just build libgcc_s.dylib? If either of the latter, then > if you changed the FSF build of libgcc_s for darwin to have the right > magic symbols, then

So, I remember we discussed this earlier this year, but I can't find the thread. The idea is to move libunwind into compiler-rt for the simple reasons below: 1. Unwinding is not exclusive to C++, nor exception handling. 2. Clang still includes libgcc_s and libgcc_eh when using compiler-rt (maybe eh isn't needed, but it was there for libgcc). 3. Testing the libunwind with libc++ on ARM is

Hi, I have seen the bug http://llvm.org/bugs/show_bug.cgi?id=896 Maybe it is a non-issue but I had some trouble with this. I am running Debian sid and were no longer able to compile llvm. /home/fred/llvm/build/gcc/xgcc: /home/fred/llvm/build/gcc/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) The installed version have this symbol. strings

Hi, I'm new to LLVM and I want to setup the Trident Compiler system on Mac OS X. I downloaded the llvm-gcc-4.2-2.4.source.tar.gz package, created a build directory and ran the following command to configure $ ../src/configure --program-prefix=llvm- --disable-bootstrap --enable- checking --enable-languages=c,c++ $ make -j 2 Configure works fine, but I get the following error

Hi all, There are symbols in libgcc (and compiler-rt) that JIT-compiled modules may need. These are currently linked correctly because lli and friends are linked against libgcc_s.so (i.e. shared library version of libgcc, so dlopen/dlsym works). However if a consumer links statically, dlsym won't find all compiler required functions (only the ones that were required by the JIT-compiler

I realize this is off-topic for the list, but I thought all the darwin developers here might want to be aware of this. The current regressions in gcc trunk regarding exception handling has been escalated to a P1 in order to attract darwin developers to the issue... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260#c31 If these regressions aren't fixed before gcc 4.5's release, it appears

This may be that the libgcc_s.dylib based unwinder is incompatible with the darwin unwinder. You cannot mix and match the two. One of the lines from the bugzilla comments shows: /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, being used. That will not work. All of the libgcc_s.dylib functionality has been subsumed into libSystem.dylib on SnowLeopard (darwin10). The

Hi, When i make LLVM with llvm-2.5.tar.gz an error occurs. The step is below tar -zxvf llvm-2.5.tar.gz cd llvm-2.5-tar.gz make ENABLE_OPTIMIZED=1 Then then the error is: /tools/IUS611/tools/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) What shall i do to avoid it? I am a newbie, maybe it's a foolish question Regards -------------- next

On Sep 18, 2009, at 10:43 AM, Jack Howarth wrote: > On Fri, Sep 18, 2009 at 10:28:15AM -0700, Nick Kledzik wrote: >> So, when these test cases are run, is the binary linked against /usr/ >> lib/libgcc_s.10.5.dylib? or against some just built libgcc_s. >> 10.5.dylib? >> or against some just build libgcc_s.dylib? If either of the >> latter, then >> if you

Fredrik Svensson wrote: > It is just the LD_LIBRARY_PATH that brings in the "llvm" libgcc_s.so.1 > that breaks the compilation. > > I added this to my build script and now llvm builds properly. > > cd build > ../llvm-gcc4/configure --prefix=$LLVM/install --enable-llvm=$LLVMOBJDIR > --enable-languages=c --disable-threads > sed -i