search for: msg00305

...> ValueTypeEPKNS_4TypeE' of >> /home/sameerds/data/llvm-1.6/Debug/lib/LLVMSelectionDA >> G.o >> collect2: ld returned 1 exit status > > I believe this is a binutils issue (ld belongs to binutils). > See for example: > http://lists.debian.org/debian-gcc/2005/10/msg00305.html Thanks! Downgraded the binutils package from 2.16.1cvs20050902-1 (Debian unstable) to 2.16.1-2 (testing). The message still appears, but no error is reported and the build completes. Found similar messages in what appears to be an automated daily build for ia64 ... assuming those messages...

...._ZNK4llvm14TargetLowering12get > ValueTypeEPKNS_4TypeE' of > /home/sameerds/data/llvm-1.6/Debug/lib/LLVMSelectionDA > G.o > collect2: ld returned 1 exit status I believe this is a binutils issue (ld belongs to binutils). See for example: http://lists.debian.org/debian-gcc/2005/10/msg00305.html Marco

Hi, Tried to build the 1.6 release on Debian unstable, but ran into link problems for some utils ... Copying the messages when building llc, the same error occurs for lli, llvm-db and some of the examples. Is this a problem with the compiler version? LLVMSelectionDAG.o itself builds correctly. make[2]: Entering directory `/home/sameerds/data/llvm-1.6/tools/llc' llvm[2]: Linking Debug

Are there instructions anywhere for setting up dom0 under Debian Lenny on amd64? Are there suitable Debian packages? James. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...specifying br0 as the bridge name in xend-config.spx and it was still using the original default xenbr0. When the bridge name is specified in the network-bridge script, it is created correctly (ditto anti-spoofing). A recent patchset: http://lists.xensource.com/archives/html/xen-changelog/2005-10/msg00305.html removed the parameters vif-bridge and anti-spoofing from the xend/vifctl.py as the script was allowing them to be configured. The config file still has the examples, however, which results in the user setting those parameters in xend-config.spx futilely. The actual parameter that is used is...