similar to: [LLVMdev] GCC_4.2.0 problem

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

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

Chris Lattner wrote: >>Why does llvm-gcc build its own libgcc_s.so? Would we have the same >>problem if we tried to build FSF GCC 4.01, or is this problem LLVM-specific? > > libgcc is part of the GCC distro. My (possibly flawed) understanding of > the issue is that GCC generates code that contains calls into libgcc. > This means that any code compiled with llvm-gcc

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

Hi Heyu Zhu, > 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) you can get this if you compile C++ code using a different compiler to your system compiler. Based on the error message, your system compiler is gcc-4.2 and the other compiler is probably gcc-4.3 or later. What has happened

Hi. Consider the following situation: Solaris 8, /usr/local has gcc 2.95, my home has gcc 3.4.3, my gcc is first on PATH, LD_LIBRARY_PATH is unset (everything is perfect since I always use -R). In fact, programs compiled with my gcc do not work if LD_LIBRARY_PATH is set to something which has /usr/local/lib before home/lib, because it overrides stored path (-R) and I got libgcc_s.so.1

Hi. Consider the following situation: Solaris 8, /usr/local has gcc 2.95, my home has gcc 3.4.3, my gcc is first on PATH, LD_LIBRARY_PATH is unset (everything is perfect since I always use -R). In fact, programs compiled with my gcc do not work if LD_LIBRARY_PATH is set to something which has /usr/local/lib before home/lib, because it overrides stored path (-R) and I got libgcc_s.so.1

On 08/02/18 15:10, Felipe Westfields wrote: > I copied the error message exactly as it was on the screen > As John said, you are mistaken: $ rpm -qp --requires nvidia-x11-drv-304xx-304.135-1.el6.elrepo.x86_64.rpm /bin/sh /bin/sh /bin/sh /bin/sh /bin/sh /sbin/ldconfig /usr/bin/python config(nvidia-x11-drv-304xx) = 304.135-1.el6.elrepo grubby grubby libGL.so.1()(64bit)

Yep. This worked. Thanks! Why yum can't figure this out itself? On Mon, Sep 18, 2017 at 3:29 PM, Johnny Hughes <johnny at centos.org> wrote: > On 09/18/2017 08:18 AM, Armin Kunaschik wrote: >> Hello, >> >> I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7 >> p770) installation. >> yum update stops with >> Error: Multilib

Hello, I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7 p770) installation. yum update stops with Error: Multilib version problems found. [..] Protected multilib versions: systemd-libs-219-42.el7.ppc != systemd-libs-219-42.el7_4.1.ppc64 When I scroll back through the transaction check I see various package dependencies for *.ppc instead of *.ppc64. First appearance in

Hi, I'm still working on the Fedora Extras package for LLVM. Because of the Fedora requirement that all packages in Extras be built from source, I must build the dreaded C Front End. :) I think I've mostly got things set up correctly, but I've found what I suspect is a tricky problem: make[1]: Leaving directory `/home/adam/rpmbuild/BUILD/llvm-1.8/llvm-gcc4-obj/gcc' Checking

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 have R-261 running on a Linux 2.6 system, which has gcc-4.1.2 installed. It was working fine until the sysadmin installed an older version of gcc (3.4.6) which was required for an older app. The gcc-3.4.6 install is under /usr/local/bin. Now when a user invokes R, the error message "/opt/r-261/lib/R/bin/exec/R: /usr/local/lib/libgcc_s.so.1: version `GCC_4.0.0' not found (required

Reid Spencer wrote: > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > When you run it from the command line it will find yoursystem libgcc.so (which works) Not really. For systems that have gcc 4.2 natively installed, like the current Debian testing, the compiler gets GCC_4.2.0 version errors. It isn't easy to work around b/c xgcc wants to link

Building llvm-gcc4 on Linux requires a little modification to a Makefile. Attached is a patch to insert the following notice into the README.LLVM in llvm-gcc4. Here's the text of the patch, for those that are building llvm-gcc4: On more recent systems (e.g. Fedora Core 5), where the version of libgcc_s.so used by libstdc++.so is more recent than the version used by llvm-gcc, you will get an

Hi Scooter, On Mon, 2006-11-06 at 12:07 -0800, Scott Michel wrote: > Reid Spencer wrote: > > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > > When you run it from the command line it will find yoursystem > libgcc.so (which works) > > Not really. For systems that have gcc 4.2 natively installed, like the > current Debian

Oh, this might be the issue - yum says it can't open "nvidia-x11-drv-304xx-304.135-1.el6.elrepo.x86_64.rpm" - let me download it again and see what happens. Are there md5 hash sums on these files? On Thu, Feb 8, 2018 at 3:23 PM, Phil Perry <pperry at elrepo.org> wrote: > On 08/02/18 15:10, Felipe Westfields wrote: > >> I copied the error message exactly as it

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 llvm-gcc binary. 2) Run make check, send me the testrun.log 3) Run "make TEST=nightly report" and send me the

According to your description i should not use the system libstdc++ and i need to specify the OTHER compiler libstdc++. But i don't where the OTHER compiler libstdc++ is. Is the OTHER compiler libstdc++ contained in llvm-2.5.tar.gz? if not where can i get it? 2009/10/20, Duncan Sands <baldrick at free.fr>: > > Hi Heyu Zhu, > > Then then the error is: >>

On 09/18/2017 08:18 AM, Armin Kunaschik wrote: > Hello, > > I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7 > p770) installation. > yum update stops with > Error: Multilib version problems found. > [..] > Protected multilib versions: systemd-libs-219-42.el7.ppc != > systemd-libs-219-42.el7_4.1.ppc64 > > When I scroll back through the