similar to: [LLVMdev] compiling with libstdc++.a that "could not read symbol"

Hi, I'm using Kmail and dovecot for my IMAP pleasure, and have had some problems, which are evident from the following exchange with some kmail developers. My patch to the imap protocol in KDE fixed my problem, but should dovecot be changed instead? Thank you for any insight! I've included the discussion on kmail-devel so far: [ I wrote: ] -- I've recently switched to IMAP for

Hi, here's a proposal of a new ssh/scp-feature: ------------------------------------------------------- please implement a timeout with non-zero error-returncode on "Are you sure you want to continue connecting (yes/no)?" ------------------------------------------------------- My situation: recently I have implemented a cronjob that is using scp. Due to organizational

Hi, I got a problem with iproute and shorewall but I don''t know where the real problem is yet, perhaps someone can shed any light on this one. What we currently do is route all traffic coming from a specific host through our second isp''s nat router. This is done via SNAT on our own router. /etc/shorewall/masq: eth2 $INTERNALHOSTA 192.168.0.142 We now

Hello all. I've been running Samba for quite some time but am now trying to move it up from (some rather limited) file sharing into being a full PDC for our network. I figured out all the "hard stuff" but am having a heck of a time with the printing. What I need to make sure of is that certain people can pause/delete, etc print jobs for other users, as well as start or stop the

Hi, I am just about to move out from my parents home and think about how I will phone from now on. In Germany there is a provider (QSC) who offers DSL (1024 down/256 up) with fastpath without volume or time limits. Does anybody know a comercial (or even semi-professional) provider who lets me dial out through H323 (or another protocol) and also offers an number where I can be called from

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.

Hal Davison <hal at faams.net> asked as above: And the answer is: compat-libstdc++-296-2.96-138 (on Centos 5.5, that is). Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144

Hello, I'm not sure if this is right list, but has anything recently changed which could explain why cmake c++ project (http://sourceforge.net/projects/gemrb/) started to fail upon linking stage (looking like libstdc++ is not included /usr/include/c++/4.2/)? It works normally if passed gcc48 as compiler which subsequently uses (ld) binutils from ports and relevant libstdc++. I have in

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?

On Sat, 16 Apr 2005, Markus F.X.J. Oberhumer wrote: > I have troubles with a freshly built CVS toolchain when linking a C++ program > with -Wl,-native: > > gccld: error: Cannot link in module > '/media/sda3/opt/cc-i386-linux/llvm/llvm-1.4.20050416-i386-linux/cfrontend/bin/../lib/gcc/i386-pc-linux-gnu/3.4-llvm/../../../libstdc++.a(allocator-inst.o)': > Linking globals

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:

Emil: I'm using LLVM 1.9 now. When I tried to do what you did I got the following though: $ llvm-g++ -emit-llvm -c x.cpp $ llvm-link -o=linked.o x.o std/*.o sup/*.o WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! ... $ lli linked.o lli((anonymous

On Tue, Nov 21, 2006 at 05:33:32PM +0800, Mohd-Hanafiah Abdullah wrote: > Emil: > > I'm using LLVM 1.9 now. When I tried to do what you did I got the > following though: > > $ llvm-g++ -emit-llvm -c x.cpp > $ llvm-link -o=linked.o x.o std/*.o sup/*.o > WARNING: Linking two modules of different target triples! > WARNING: Linking two modules of different target

On Tue, 21 Nov 2006, Emil Mikulic wrote: > LLVMers, given the same endianness and pointersize, can one mix and > match LLVM bytecode files produced on different platforms? No, not in general. For example, on the mac, printf it often #defined to printf$ldbl, which doesn't exist on linux. System headers generally foil the ability to move stuff around like that. -Chris --

Chris Lattner wrote: > On Tue, 21 Nov 2006, Emil Mikulic wrote: >> LLVMers, given the same endianness and pointersize, can one mix and >> match LLVM bytecode files produced on different platforms? > > No, not in general. For example, on the mac, printf it often #defined to > printf$ldbl, which doesn't exist on linux. System headers generally foil > the ability

Chris Lattner wrote: > Many aspects of the target compiler can leak through. So if one wants to use the LLVM system as a cross compiler, one has to configure llvm-gcc as a cross compiler? Fair enough, I guess. > One trivial example is: > > int X = sizeof(long); So I assume this also means that while getelementptr insulates llvm byte code from the details of target specific address

Pertti Kellomäki schrieb: > Chris Lattner wrote: >> Many aspects of the target compiler can leak through. > > So if one wants to use the LLVM system as a cross compiler, one > has to configure llvm-gcc as a cross compiler? Fair enough, I guess. I hope the C backend is still meant to generate portable code though. Philipp

On Thu, 2006-11-23 at 19:10 +0100, Philipp Klaus Krause wrote: > Pertti Kellomäki schrieb: > > Chris Lattner wrote: > >> Many aspects of the target compiler can leak through. > > > > So if one wants to use the LLVM system as a cross compiler, one > > has to configure llvm-gcc as a cross compiler? Fair enough, I guess. > > I hope the C backend is still

Hello Philipp, > Does that mean that I will have to configure llvm as a cross-compiler > even when using the C backend? Not llvm, but llvm-gcc only. I've successfully used llvm-gcc for crosscompiling with host=linux and target=mingw32 platform. So, you have just to supply host, build and target triples to llvm-gcc configure and be also sure, that configure will find target headers,

Reid Spencer schrieb: > hat you do need to do > is configure your front end to be a cross compiler. Then it will > generate the correct LLVM input for that platform (and consequently LLVM > will generate code for that platform) regardless of the platform on > which either LLVM or your front end are running. > Is that needed for thing like sizeof() and size of native datatypes