Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] Building CFE on MinGW"
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/
2008 Aug 18
1
nanobsd build problem
I'm trying to build nanobsd. I get the error below. Any ideas?
-------------------------------------------------------------
>>> stage 4.2: building libraries
--------------------------------------------------------------
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/nanobsd.soekris/ MACHINE_ARCH=i386
MACHINE=i386 CPUTYPE=
2006 Apr 22
2
[LLVMdev] Re: Building CFE on MinGW
Is the MinGW user's list on the web? Can you give me a link to the thread?
(What's IIRC?)
Thanks.
On Sat, 22 Apr 2006, Oscar Fuentes wrote:
> Greg Pettyjohn <gregp at ccs.neu.edu> writes:
>
> > I've blown a couple of weekends trying to build under MinGW.
> >
> > I can build the llvm tools with only a couple of minor hassles, but can't
> > seem
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
> Cyrille Mescam wrote:
> >Hi,
> >
> >
> >When compiling the cfrontend for Linux/PPC architecture on a powermac
> >G5, i got
> >the following error :
>
> I hate to ask a silly question, but are you using "make bootstrap" to
> build the cfrontend? Your output looks like gccas
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
> Okay, I took a closer look at your output.
>
> I was correct in that gccas is attempting to assemble a native PPC
> assembly language file. However, this appears to be happening because
> the assembly file is generated by the GCC Makefiles for libgcc2 (in
> llvm-gcc/gcc/config/rs6000/t-ppccomm, I think).
>
> The first thing I would try is Marco's suggestion: add
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>
2005 Jun 13
0
[LLVMdev] problem compiling the cfrontend on Linux/PPC
Cyrille Mescam wrote:
> On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
>
>>Cyrille Mescam wrote:
>>
[snip]
>
> In fact, i am using the CFE build procedures. I am on instructions 5.
>
> cyrille
>
Okay, I took a closer look at your output.
I was correct in that gccas is attempting to assemble a native PPC
assembly language file. However,
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
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 Apr 23
3
[LLVMdev] Re: Building CFE on MinGW
I'm using a little shell script:
BUILD_ROOT=/home/llvm-1.7/cfrontend
PREFIX="$BUILD_ROOT/install"
LOCAL_BUILD_DIR="$BUILD_ROOT/build"
SOURCE_DIR="$BUILD_ROOT/src"
echo $__me: Building $TARGET
echo $__me: BUILD_ROOT == $BUILD_ROOT
echo $__me: SOURCE_DIR == $SOURCE_DIR
echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR
echo $__me: PREFIX == $PREFIX
2006 May 07
0
[LLVMdev] Configuring for the cfrontend build on Mingw
So the fundamental problem I'm trying to solve is how get my cfrontend
build configured properly.
The usual symptom of an incorrect configuration is the inability to find
various header files.
Here's some example spew:
$ /home/llvm_home/llvm-gcc-build/gcc/xgcc -v
-B/home/llvm_home/llvm-gcc-build/gcc/ -Bc:/msys/1.0/mingw32/bin/
-Bc:/msys/1.0/mingw32/lib/ -isystem
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 Apr 22
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes:
> Is the MinGW user's list on the web?
Look on www.mingw.org -> mailing list
> Can you give me a link to the thread?
Sorry, no time for that. Once on the mailing list archives, do a
search for 'configure'.
> (What's IIRC?)
If I Remember Correctly.
By the way, what's your configure command?
--
Oscar
2008 Oct 31
2
[LLVMdev] building for sparc-sun-solaris2.10
I am trying to do some research that involves instrumenting LLVM IR,
that I need to test for performance and scalability on a bunch of systems.
I've started trying by trying to get sparc-sun-solaris2.10 (niagara)
working. It appears that neither llvm nor llvm-gcc will build natively
on the system, so I think that I need to build an llvm-gcc cross compiler.
The documentation for building
2008 Oct 31
2
[LLVMdev] building for sparc-sun-solaris2.10
Mike Stump wrote:
> On Oct 31, 2008, at 1:10 PM, Luke Dalessandro wrote:
>> I've started trying by trying to get sparc-sun-solaris2.10 (niagara)
>> working. It appears that neither llvm nor llvm-gcc will build natively
>> on the system, so I think that I need to build an llvm-gcc cross
>> compiler.
>
> Get a gcc binary from someplace, use that to then build
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
2005 Jun 13
3
[LLVMdev] problem compiling the cfrontend on Linux/PPC
Hi,
When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got
the following error :
-------------------------------Compilation error listing
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
make
GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc
-B/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/
2006 Apr 22
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes:
> I've blown a couple of weekends trying to build under MinGW.
>
> I can build the llvm tools with only a couple of minor hassles, but can't
> seem to make any headway with the C Front End
>
> Most errors I run into involve not being able to find header files.
> The most frustrating part is that the error messages
2005 Mar 11
3
[LLVMdev] Anyone seen this before?
So, I'm trying to build everything from source for the Debian
package for LLVM, including the C/C++ front end. I'm running
this build on LLVM 1.4 source (the released tarball), using
Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64
box, dual CPU). Before I get _too_ deep into it, I thought I
would ask if the following compilation failure on the CFE
looks the least bit familiar