similar to: yum install libstdc++-devel

On Thu, Aug 29, 2013 at 07:40:46PM +0200, Duncan Sands wrote: > Hi Jack, > > On 29/08/13 18:35, Jack Howarth wrote: >> Duncan, >> Is there a long term plan for handling the conflicting c++ libraries in building >> dragonegg? In particular, as vendors switch their clang++ system compilers to default >> to -stdlib=libc++, the resulting builds of llvm against

Duncan, Is there a long term plan for handling the conflicting c++ libraries in building dragonegg? In particular, as vendors switch their clang++ system compilers to default to -stdlib=libc++, the resulting builds of llvm against those compilers will be using the libc++ ABI but the dragonegg plugin will still need to be built against the libstdc++ ABI. For now, the only work-around appears to

Hi Jack, On 29/08/13 18:35, Jack Howarth wrote: > Duncan, > Is there a long term plan for handling the conflicting c++ libraries in building > dragonegg? In particular, as vendors switch their clang++ system compilers to default > to -stdlib=libc++, the resulting builds of llvm against those compilers will be using > the libc++ ABI but the dragonegg plugin will still need to be

Hi Jack, On 30/08/13 15:56, Jack Howarth wrote: > On Thu, Aug 29, 2013 at 07:40:46PM +0200, Duncan Sands wrote: >> Hi Jack, >> >> On 29/08/13 18:35, Jack Howarth wrote: >>> Duncan, >>> Is there a long term plan for handling the conflicting c++ libraries in building >>> dragonegg? In particular, as vendors switch their clang++ system compilers

Has anyone managed to get FF 18.0 to work on Centos 5.8? I've been hacking at it, placing a stack of .so files (from Centos 6) into a private directory, then using LD_LIBRARY_PATH to point the system to (in a shellscript that subsequently invokes ff 18) but so far I've not managed to find the right combination. I've moved over libstdc++, all or nearly all the .so files from glib2 and

On Sun, 22 Apr 2007, Christopher Lamb wrote: > When built using the guidelines in the README.LLVM to use the system's > libstdc++ I get the following types of errors whenever I try to use the > standard library (say by running the front end test suite in llvm/test): > > /usr/include/c++/4.0.0/cmath:49:28: error: bits/c++config.h: No such file or > directory >

Hi, I have been using CentOS 4 on a UML (User-Mode Linux) box for some time (>1 year) and have kept up to date with updates. I think I started on CentOS 4.1 and have progressively "yum update"'d since. User-Mode Linux, or at least the version of it that my hosts use, doesn't support NPTL. This hasn't been a problem to date; I've just moved /lib/tls out of the way, as

When built using the guidelines in the README.LLVM to use the system's libstdc++ I get the following types of errors whenever I try to use the standard library (say by running the front end test suite in llvm/test): /usr/include/c++/4.0.0/cmath:49:28: error: bits/c++config.h: No such file or directory /usr/include/c++/4.0.0/iosfwd:45:29: error: bits/c++locale.h: No such file or

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My

Hi all, I am really stumped on this problem. I googled and could not find any solution. Here is the problem. I compiled and installed glibc-2.5-20090518 in a local directory with gcc version 4.1.2. I compiled glibc-2.5 because I wanted to test glibc-2.5 on gcc first llvm-gcc. However, after I installed glibc, llvm-gcc does not work any more. It reported this error message:

I'm trying to install the Adaptec Storage Manager for the 21610SA SATA RAID controller on Centos 5.5. rpm reports that it failed on the dependency on libstdc++-libc6.1-1.so.2 yum provides */libstdc++-libc6.1-1.so.2 reports no matches found How can I install the required files to all the Adaptec Storage Manager to be installed?

Hi, the subject says it all... After some experimenting, I got a bit confused as far as what the proper thing to do might be.... I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese) where I also have successfully built a fsf-gcc 4.6.2 (and lately a 4.7 for that matter) from sources. Now, I think I understand that by playing

Hello, I am hearing of users having trouble linking with libxapian (on slackware and gentoo systems, and 0.9.2 I think), and I am not too sure where the problem comes from, or what the correct solution could be, so I am just asking here in case someone has a quick answer. What happens is that "xapian-config --libs" outputs libstdc++.la in the list of libraries. Something like:

I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a day or two. /home/ang/build/llvm-gcc/./gcc/xgcc -shared-libgcc

Hi all, If I try yum grouplist "FTP Server" I get the next large output: Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: OpenIPMI x86_64

Which rpm has libstdc++.so.5? xten-xlite for linux says it needs this. Of course, there will be something else it will need after I get this....

Hi there, I have a question on my linux box where I cant link properly. I've tried configure option --enable-shared or --disable-shared. The following are the message I got. Is there anything I can do to fix this linking/lib problem? thanks in advance, Tim ps. make[3]: Entering directory `/remote/dept5428a/clientstore/timoshiu/timoshiu_esp_main_llvm/obj/lib/Transforms/Hello' llvm[3]:

In CentOS 4.1/2, what package contains this library: libstdc++-libc6.2-2.so.3? I installed a couple of the compat- packages, but this library is still missing.

Hi, I'm trying to track down some nasty glibc failures on Linux. I think the problem is that my system compiler (3.4.6) doesn't match llvm-gcc (4.0.x) so when the llc compiled programs run they don't quite get the right libstdc++. If I run a test program with: LD_LIBRARY_PATH=/path/to/my/llvm-gcc4/libs Output/sieve.llc then I get this: Output/sieve.llc: symbol lookup error:

Greetings!!! Could you please suggest ways to build clang/llvm without libstdc++? In short, to avoid using GPLv3 libraries or tools while building clang/llvm. Thank you in advance. -Hiral -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150128/a6d24e76/attachment.html>