similar to: [LLVMdev] Multiple definitions of _floor_log2

> LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. I am trying with llvm-gcc-4.2 from svn. Aaron

Hello, Seth > Any help would be appreciated. Well, at least you should check, where and how floor_log2 is defined in your system libstdc++ -- WBR, Anton Korobeynikov

In trying to package up LLVM for Debian, it appears that x86_64 is no longer a supported architecture -- so, my first question is, is that correct? Best I can tell, the only thing that's supposed to work for x86_64 is the C backend. For Debian, I need to build everything from scratch. When trying to build llvm-gcc4 from source, though, I get part way through the build and am told that

This is a forward of a question from the SourceForge LLVM forum. If anyone has experience with Cygwin and building the C front-end there, please reply and CC Alex. --- Post by Alex Vinokur below --- =============== Windows 2000 GNU gcc 3.3.3 (cygwin special) =============== ./configure ./make I have got compilation error ------------------------------- make[1]: Entering directory

I posted this message first. But it was missing so I post again. I think there is a some bug in build configration files. Can you check up the following errors and fix it? The error has no concern with UTF-8 patch. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- [root at saturn xapian-core-0.9.4_svn6707]# make ... ... mkdir .libs/libxapian.lax/libqueryparser.a

On Sat, 23 Dec 2006, Roman wrote: > How to solve this problem? Java isn't supported. Use --enable-languages=c,c++ -Chris > $ make > make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' > make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory

How to solve this problem? $ make make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[1]: Leaving directory `/tmp/llvm3/llvm/build/libiberty' make[1]: Entering directory

Hi, in trying to build an llvm-gfortran on linux from today's gcc4 SVN, I get the following link errors that didn't show up on OS X. This is also using LLVM CVS from this morning. They appear to mostly be related to CodeWarrior compatibility code, but a couple are less obvious. What's the best way to fix this? I'm stuck without my powerbook for at least three weeks and I'd

On Mon, 14 May 2007, Nicolas Geoffray wrote: > Hi everyone, I am using linux/ppc and after porting llvm's jit for this > architecture, I am currently trying to compile llvm-gcc on it. > > I have gcc 4.1.1 and use llvm-gcc from cvs. This looks like you're compiling llvm-gcc3, which is quite dead by now. Please follow these instructions: http://llvm.org/docs/CFEBuildInstrs.html

Hi everyone, I am using linux/ppc and after porting llvm's jit for this architecture, I am currently trying to compile llvm-gcc on it. I have gcc 4.1.1 and use llvm-gcc from cvs. Compilation fails and the message is: gcc -O2 -DIN_GCC -DDEFAULT_TARGET_MACHINE=\"powerpc-unknown-linux-gnu\" -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long

It has been observed that binaries contents are depending on the order of linked objects. This order is caused by GNU make's wildcard function and the position of sources on filesystem. This change tries to prevent this kind of randomness. Also consider building using -j1 flag to make it even more reproductible. Change-Id: Ie8eee7f336e6f1fa2863c4150d967afd15519f1d Bug:

Sometimes I find it useful to put C or Fortran sources under subdirs of "mypackage/src", especially to distinguish between my own files and e.g. lapack or blas sources. To get this working I would need a Makefile in my package which contains the appropriate dependencies to these sources in subdirs. But I don't want to add a complete Makefile, I want only a Makevars file containing

/usr/src/sys/modules/hifn/Makefile appears to need an update to make it same as HEAD. Same with ..modules/ubsec/Makefile. Patches: Index: Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/ubsec/Makefile,v retrieving revision 1.2.2.1 diff -u -r1.2.2.1 Makefile --- Makefile 21 Nov 2002 23:38:47 -0000 1.2.2.1 +++ Makefile 5 Jun 2003

hi, i also have problems compiling llvm-gcc (current svn version). llvm is current llvm svn. i tried to use every gcc version from 4.0 to 4.3 to compile llvm-gcc. i configured llvm-gcc like this (and tried every other combination of disable-shared, disable-multilib and bootstrap) : ../llvm-gcc/configure --prefix=/usr --enable-llvm=/usr --enable-languages=c,c++ --disable-shared

any ideas what library has these symbols lang_eh_catch_all get_pointer_alignment validate_arglist i get these linker errors when trying to link llvm-gcc: make[1]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[2]: Entering directory

I have download source ?1.10? from the internet and build it into lib Then I create a project as the helpdoc said I using vc2005(vc8) The source in my test project is as follow??copy from the helpdoc? #include <xapian.h> #include <iostream> using namespace std; int main(int argc, char **argv) { // Simplest possible options parsing: we just require three or more

llvm-gcc is producing segmentation fault when running with -emit-llvm. Running cc1 in valgind produces the warning: ==12768== at 0x8D042C: llvm::llvm_ostream& llvm::llvm_ostream::operator<< <llvm::Module>(llvm::Module const&) (Streams.h:41) ==12768== by 0x8D0464: llvm::PrintModulePass::runOnModule(llvm::Module&) (PrintModulePass.h:41) ==12768== by 0xED6EB9:

Hi, After a svn/cvs update I get the following errors when building the frontend. Anyone that sees the same ? http://gcc.gnu.org/svn/gcc/branches/apple/trunk/gcc/expr.h /* APPLE LOCAL begin radar 4441049 */ extern tree objc_v2_component_ref_field_offset (tree exp); extern tree objc_v2_bitfield_ivar_bitpos (tree exp); /* APPLE LOCAL end radar 4441049 */ mentions APPLE, is it only working on

samuel, I have a try with HVM stubdomain on r17062, but failed to make on 32b platform. Attached patch can fix it, but don''t know if okay. After installation, I failed to start stubdom. So I created it manually and got following debug mesg(both HVMdomain and stubdom are created) Can you give some lights on following questions: 1. I use default vnclisten. Does it matter? 2. Seems qemu

On Wednesday 30 July 2008 18:13:27 Duncan Sands wrote: > On x86-64 linux, in stage 2, I get: > > c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ > fortran/arith.o