similar to: [LLVMdev] compiling llvm-gcc4 on ubuntu

Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] compiling llvm-gcc4 on ubuntu"

2007 Mar 01
0
[LLVMdev] compiling llvm-gcc4 on ubuntu
Hi Stefan, On Thu, 2007-03-01 at 23:26 +0100, Stefan Weigert wrote: > hello, > > i am new to llvm and can't manage to compile the gcc backend. Okay. Did you read: http://llvm.org/docs/GettingStartedGuide.html ? > > my steps: > i compile the llvm-source first as suggested in "README.LLVM" > that works fine and without any issues. Okay. > > then i
2006 Dec 03
3
[LLVMdev] problem building gcc4 front end on fedora core 5
I'm getting a build error when trying to build gcc4 from sources. This is for the recent 1.9 release. How I built llvm-1.9: ----------------------------- tar zxf llvm-1.9.tar.gz cd llvm-1.9/ ./configure --prefix=/custom/llvm-1.9 make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only make install How I built gcc4: ----------------------------- export
2006 Dec 03
0
[LLVMdev] problem building gcc4 front end on fedora core 5
There was a patch that went thru for this recently from Rafael Espindola. The fix is on the mirror. Index: gcc/dwarf2out.c =================================================================== --- gcc/dwarf2out.c (revision 120589) +++ gcc/dwarf2out.c (working copy) @@ -14361,9 +14361,8 @@ s->refcount++; /* Avoid unnecessarily putting strings that are used less than twice in the hash
2006 Nov 06
4
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which will find the libgcc.so that it just built, which is the one
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <b>Reid,<br> <br> I followed the steps but got stuck as described
2006 Nov 06
2
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
Hi Robert, On Mon, 2006-11-06 at 12:45 -0800, Robert Mykland wrote: > Reid, > > Here's the backtrace you asked for: > > (gdb) bt > #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction () Hmm, this is a little strange. Your LLVM build is non-debug (there's no line numbers or arguments in any of the llvm related calls). However, your llvm-gcc build seems to have
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Reid,<br> <br> Here's the backtrace you asked for:<br> <br>
2006 May 02
1
[LLVMdev] Bootstrapping llvm-gcc4 on Mingw
Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/
2007 Feb 28
1
[LLVMdev] Cygwin release build error
I did not realize that '--enable-llvm' was required and that invalidates my debug build results which were built just with LLVM on the path. I am now getting a segmentation fault when doing a 'make install' on LLVM-GCC4, possibly validating my original thoughts that GCC 4.1.1 was required to build LLVM-GCC 4.0.1. I will try using GCC 4.1.1. Heres the error anyway :- make[2]:
2006 Nov 06
1
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
Hi Robert, Please make sure that you: 1. Completely rebuild LLVM (make clean; make reconfigure; make tools-only) 2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) If you've done that, then please enter the debugger and get a stack trace for us. You will need to: 1. Capture the xgcc compile command that failed 2. Run that command
2006 Nov 06
3
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
I was having video problems, so upgraded my Linux box from SUSE 9.3, where LLVM frontend 4 source built fine, to SUSE 10.1, where I got the error message: ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:541: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://llvm.org/bugs> for instructions. This version of SUSE
2006 May 09
0
[LLVMdev] New llvmgcc4 snapshot
Hi, i tried compiling llvmgcc4 on x86_64-linux. The two changes i needed to apply to llvm and llvmgcc4 are attached. Those two patches tell llvmgcc4 to use the x86 code-generator for x86_64 and give x86_64-* targets a score of 10 for the x86 backend when trying to find appropriate backends. Now i'm getting stuck during the compile when an assertion is triggered: make[3]: Leaving
2007 Apr 01
3
[LLVMdev] trouble compiling llvm-gcc4 1.9
I'm having some trouble getting llvm-gcc4 to compile. It's unable to compile darwin-crt3.c. It's mentioning "Complex expression. Absolute segment assumed." but I'm not sure if that's a real error message. Has anyone run into this before? I'm running on a G4 apple 10.4.8, kernel version 8.6.0. I googled around and found a bug with the same error message:
2007 Jan 16
0
[LLVMdev] OK, how does this work?
Hi Michael, On Tue, 2007-01-16 at 10:24 +0800, Michael T. Richter wrote: > I'm trying to get LLVM1.9 working on my Ubuntu 6.10 system. The LLVM > version in the repositories is 1.7 and I've never managed to get it > successfully working because whoever packaged it thought it would be > fun to rename everything. This means I can't use it to build 1.9 and > I've
2007 Jan 16
2
[LLVMdev] OK, how does this work?
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
2007 Feb 28
7
[LLVMdev] Cygwin release build error
I am getting an "--emit-llvm is not supported in this configuration" error on a release build on Cygwin, the debug build is fine. make[3]: Entering directory `/usr/build/llvm/runtime/GCCLibraries/libc' llvm[3]: Compiling atox.c for Release build (bytecode) llvm-gcc: --emit-llvm is not supported in this configuration. make[3]: ***
2006 Mar 15
2
[LLVMdev] Re: Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
>> Sorry for the delay, please try this tarball: >> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz > > There's some confusion with --enable-llvm configure parameter. I've built > LLVM to a separate build dir. The source is ~ghost/Work/llvm-cvs and build > dir is /space/p2/ghost/build/llvm-cvs ... > So, it seems like, at the same time: > > 1. buildir
2007 Feb 28
0
[LLVMdev] Cygwin release build error
Aaron, On Wed, 2007-02-28 at 15:40 +0000, Aaron Gray wrote: > I am getting an "--emit-llvm is not supported in this configuration" > error on a release build on Cygwin, the debug build is fine. > > make[3]: Entering directory > `/usr/build/llvm/runtime/GCCLibraries/libc' > llvm[3]: Compiling atox.c for Release build (bytecode) > llvm-gcc:
2006 May 08
6
[LLVMdev] New llvmgcc4 snapshot
Hi All, There's a new snapshot of llvmgcc4 available here: http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz This release includes the various portability fixes contributed on llvmdev, includes fixes to build with mainline CVS (and, thus, *requires* mainline CVS), and includes various other bug fixes. If you're interested, please try it out. Thanks, -Chris --
2007 May 26
1
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren, you can try to configure with the following export CFLAGS="-m64" export LDFLAGS="-L/usr/lib64" LLVM: ../src/configure --prefix=`pwd`../install --enable-optimized --enable-jit --enable-targets=host-only make LLVM-GCC: ../llvm-gcc4-2.0.source/configure --prefix=`pwd`../install --program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/ --enable-languages=c,c++