Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1"
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
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
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
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 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
2008 Mar 19
2
[LLVMdev] Merge Patch File
On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Bill, thanks for fixing it.
>
No prob! :-)
>
> > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c: In function 'ix86_expand_convert_uns_DI2DF_sse':
> > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c:10270: warning: large integer implicitly truncated to unsigned type
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 Jul 11
1
[LLVMdev] LLVM 2.0 / GCC 3.4
Hi there,
Is it possible to use GCC 3.4 with LLVM 2.0? I tried to compile GCC
3.4 with LLVM 2.0 and get following error message:
/scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/xgcc -B/
scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/ -B/scratch/
spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-solaris2.11/bin/ -
B/scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-
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
2007 Jan 16
3
[LLVMdev] OK, how does this work?
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
therefore decided to try bootstrapping a 1.9 build.
Yes, I've looked at the docs where it said
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
--
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
2006 Dec 23
1
[LLVMdev] in Cygwin problems
Problem 2:
Configure:
../src/configure --prefix=/tmp/llvm/install --disable-threads --disable-nls --disable-shared --enable-languages=c,c++ --disable-c-mbchar --program-prefix=llvm-
$ 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
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
2008 Feb 02
1
CC messed up in RELENG_7 build
The sources were csupped ~3 hours ago. My CC is defined as follows:
env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache cc
I have done many buildworld, buildkernel and port builds with this setting and
it never caused any problems. However today buildworld fails the following way:
env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache env CCACHE_PREFIX=/usr/local/bin/distcc
2006 Oct 26
0
[LLVMdev] Some basic questions about LLVM version 1.8 bytecode format
Hi Robert,
On Wed, 2006-10-25 at 16:00 -0600, Robert Mykland wrote:
> I generated LLVM bytecode for a "hello world!" program just to get the
> basic bytecode structure. I have a few questions about the global
> info module and the global constants module where there have
> apparently been changes since 1.4.
Okay.
> I would be happy to collect these differences and do
2006 Oct 25
2
[LLVMdev] Some basic questions about LLVM version 1.8 bytecode format
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I generated LLVM bytecode for a "hello world!" program just to get the
basic bytecode structure. I have
2007 Mar 01
3
[LLVMdev] compiling llvm-gcc4 on ubuntu
hello,
i am new to llvm and can't manage to compile the gcc backend.
my steps:
i compile the llvm-source first as suggested in "README.LLVM"
that works fine and without any issues.
then i make a new dir called build. from there i do the following:
stefan at ubuntu:~/programs/llvm/build$ ../llvm-gcc4-1.9.source/configure --enable-languages=c,c++ --prefix=/usr/local/