similar to: [LLVMdev] how to compile llvm-gcc whith lto support for ARM

Hello >  ../configure  --target=arm-unknown-linux-gnueabi --program-prefix=arm- > --prefix=/home/kursh/arm --enable-gold --enable-plugins > --with-sysroot=/home/kursh/arms/sys-root It seems you've configured binutils with gold... > /home/kursh/arm/arm-unknown-linux-gnueabi/bin/ranlib ./libgcc_eh.a > /home/kursh/arm/bin/arm-ld: error: libgcc/./_udivsi3_s.o: unsupported reloc

I get this when I type: brianherman at windows-8-[REDACTED] ~ $ nm libgcc_eh.a | grep register_frame nm: 'libgcc_eh.a': No such file brianherman at windows-8-[REDACTED] ~ $ nm libgcc_eh.a | grep register_fram nm: 'libgcc_eh.a': No such file brianherman at windows-8-[REDACTED] ~ $ On Tue, Jul 30, 2013 at 7:51 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi

brianherman at windows-8-doesn't rock /lib/gcc/i686-pc-cygwin/4.7.3 $ nm libgcc_eh.a | grep register_frame 000011b0 T ___deregister_frame 000011a0 T ___deregister_frame_info 000010d0 T ___deregister_frame_info_bases 00000fe0 T ___register_frame 00000fb0 T ___register_frame_info 00000f40 T ___register_frame_info_bases 00001070 T ___register_frame_info_table 00001010 T

> $ nm libgcc_eh.a | grep register_frame > nm: 'libgcc_eh.a': No such file I think he meant to find out where libgcc_eh.a lives under Cygwin and execute the command on that file. It should be somewhere amongst the stuff installed with gcc, but the exact location can vary quite a bit. Cheers. Tim.

2015-03-11 16:22 GMT-05:00 Richard Gorton < rcgorton at cognitive-electronics.com>: > I can confirm that musl builds and works correctly with clang/llvm. We > are using musl as a libc for our architecture. > It has a much smaller code footprint than newlib or glibc. > I successfully cross-compile the must-libc using clang, with the configuration: C=clang

Hello all, I wanna build a static linked executable using llvm. But I failed. My question is Can we use -static using llvm? Thanks for any response. Below is details ======== First I use $ clang++ test.cc `llvm-config --cxxflags --ldflags --libs` I works as usual. But if I use $ clang++ test.cc `llvm-config --cxxflags --ldflags --libs` -static It yells lots of undefined reference, like

Hi Brian, On 29/07/13 23:42, Brian Herman wrote: > I got the following error while compiling llvm and clang under cygwin. > > /cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b): > undefined reference to `__register_frame' I register_frame is used to enable the debugger (gdb) to

I am having a problem building OpenSSH on my AIX 4.3.3 box. It fails during the make with the following error: xlc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -L/usr/local/lib -L/usr/local/lib -L/usr/athena/lib -L/usr/afsws/lib -blibpath:/usr/lib:/lib:/usr/local/lib:/usr/athena/lib -lssh

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

On Wed, Oct 22, 2014 at 11:24 AM, Jonathan Roelofs < jonathan at codesourcery.com> wrote: > I remember there being a ARM EHABI reason why this won't work, but I don't > remember the specifics. IIRC, had something to do with how c++ rtti is > required > to be handled by the catch handlers, and would mean layering problems if we > moved it. Antoine, do you remember the

Hi, I am trying to compile R-2.2.1 on Solaris 2.9 with a 64-bit build. Following the instructions in "R Installation and Adminstration", I changed the following settings in "config.site": CC="gcc -m64" F77="g77 -64" CXX="g++ -m64" LDFLAGS="-L/usr/local/lib/sparcv9 -L/usr/local/lib" But I got the following error messages:

Hi Renato I had the impression that Michael actually wanted the latter, like GCC > has autoconf options to change the default behaviour of the compiler > at build time. > > I may be wrong, though. yes I thought that was what he wanted because he said Are they used to indicate that if the C/C++ compiler for building LLVM is > clang > That combined with the standard cmake

On 28 July 2015 at 12:10, Schlottke-Lakemper, Michael <m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used

On 30 January 2015 at 20:43, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > I think this dependence should be satisfied by the target system's unwinder, > whatever that is. If folks want to use this libunwind for their platform, > that's fine... but we should probably continue to use libgcc_s and libgcc_eh > on linux when that's the platform's unwinder.

On Fri, Jan 30, 2015 at 1:03 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 30 January 2015 at 20:43, Jonathan Roelofs <jonathan at codesourcery.com> > wrote: > > I think this dependence should be satisfied by the target system's > unwinder, > > whatever that is. If folks want to use this libunwind for their platform, > > that's fine...

Bill Wendling wrote: > On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote: > >> Hi Bill, thanks for fixing it. >> >> > No prob! :-) I can't build llvm-gcc4.2 on x86-32 Linux. What is kext64, and how do I disable it? (I suppose I don't need it on a 32-bit platform?) ..... ranlib kext/libgcc_eh.a

Although this has been discussed in the past, I think that given a few conversations, it seems that it unfortunately needs to be brought up again. There seems to be some disagreement over the ideal location of the unwinder (libunwind). Currently, libunwind resides in a subdirectory of libc++abi. There seems to be some desire from multiple parties that it be moved into compiler-rt or a separate

On 1/30/15 1:17 PM, Saleem Abdulrasool wrote: > Although this has been discussed in the past, I think that given a few > conversations, it seems that it unfortunately needs to be brought up again. > > There seems to be some disagreement over the ideal location of the > unwinder (libunwind). Currently, libunwind resides in a subdirectory of > libc++abi. There seems to be some

oops.. sorry, I posted the wrong HowTo-URL. The one I followed was: http://lists.xensource.com/archives/html/xen-devel/2004-12/msg00145.html _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi-- concept_df$NewCol <- ""; kw <- "acid|ph"; bb <- grepl(kw,concept_df$concept) concept_df[dd,2] <- "chemical" The is a bit late but it accomplish the same with base R. Good luck--EK PS.. my email doesn't accept reply [[alternative HTML version deleted]]