Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] Cygwin release build error"
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:
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]:
2007 Feb 28
0
[LLVMdev] Cygwin release build error
Hello, Aaron.
> /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf':
> /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error:
> Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://llvm.org/bugs> for instructions.
You should:
1. Try to emit bytecode with --emit-llvm compiler switch.
1.1
2007 Feb 28
1
[LLVMdev] Cygwin release build error
Hello, Aaron.
> This is still at the stage of using xgcc.exe AFAICT before any LLVM bytecode
> generation.
Yep. But xgcc generates code via LLVM! So, you can just copy command
line from your terminal, add -emit-llvm, run it and you'll see, that
resulting .o will be LLVM bytecode (or won't if FE will crash).
> __eprintf is a very simple function so I do not know what could be
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
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
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 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 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 Jul 30
2
[LLVMdev] Building llvm under cygwin
Hi!
I'm trying to build LLVM under cygwin.
I have the latest version of cygwin and CVS versions of llvm, llvm-test and
llvm-gcc.
make of tools only succeeded.
make of frontend succeeded too
but full make of llvm failed on crtend in llvm/runtime/GCCLibraries with the
following message:
llvm[0]: Compiling crtend.c for Debug build (bytecode)
/bin/sh: -c: line 0: syntax error near unexpected
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/
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 Feb 28
0
[LLVMdev] Cygwin release build error
Anton,
> Hello, Aaron.
>
>> This is still at the stage of using xgcc.exe AFAICT before any LLVM
>> bytecode
>> generation.
> Yep. But xgcc generates code via LLVM! So, you can just copy command
> line from your terminal, add -emit-llvm, run it and you'll see, that
> resulting .o will be LLVM bytecode (or won't if FE will crash).
Okay that works, got a
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 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
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
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
Reid & Aaron
> > This is the same error that appears alot of times on the 'make check'
> > of the debug build.
> >
> > What is going on here please ?
>
> Sounds to me like the llvm-gcc being used wasn't configured using
> --with-llvm=. That message occurs when llvm-gcc is built
> "normally" (without using llvm).
Yes. llvm-gcc4