Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Configuring for the cfrontend build on Mingw"
2006 May 08
0
[LLVMdev] Configuring for the cfrontend build on Mingw
Hello, Greg.
You wrote Sunday, May 7, 2006, 10:46:34 PM:
GP> 3. One potential point of control is the INCLUDES variable found in
GP> cfrontent/gcc/Makefile.in:
GP> INCLUDES = -I. -I$(@D) -I$(srcdir) -I$(srcdir)/$(@D) \
GP> -I$(srcdir)/../include @INCINTL@
Just unpack mingw32's headers & libs (w32api && mingw-runtime) into
prefix directory. And configure script
2006 Apr 22
3
[LLVMdev] Building CFE on MinGW
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 report that the file
can't be found, and then proceed to give a path to where the
2009 Oct 27
2
[LLVMdev] msys/mingw32 llvm-gcc build errors
I successfully built llvm using msys/mingw, but I am getting the following
error when I try to build llvm-gcc using
$ ../llvm-gcc4.2-2.6.source/configure --prefix=/c/Temp/msys-llvm-gcc
--program-
prefix=llvm- --enable-llvm=/c/Temp/msys-llvm --enable-languages=c,c++
--disable
-shared
$make
--------------------------------------------------
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings
2008 Jul 30
0
[LLVMdev] More llvm-gcc build breakage
On Jul 30, 2008, at 11:17 AM, Julien Lerouge wrote:
> Not sure if that's related, but we had two failures last night as
> well:
>
> MacOS/Universal build failed on rev 54197, when building the x86->ppc
> cross:
>
> cc1: warnings being treated as errors
> /Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning:
> no
> previous prototype for
2008 Jul 30
2
[LLVMdev] More llvm-gcc build breakage
Not sure if that's related, but we had two failures last night as well:
MacOS/Universal build failed on rev 54197, when building the x86->ppc
cross:
cc1: warnings being treated as errors
/Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: no
previous prototype for 'outermost_tinst_level'
make[2]: *** [cp/pt.o] Error 1
MingW failed on rev 54208:
2006 May 07
0
[LLVMdev] The Next Win32 File System Problem
Yep, you found another bug. Unlike Unix, Windows does not allow a file
to be implicitly replaced via renaming. I'll fix it.
Greg Pettyjohn wrote:
> Fixing one bug uncovers the next one...
>
> To reproduce:
> llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...>
>
> The result:
> C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move
2006 May 07
2
[LLVMdev] The Next Win32 File System Problem
Fixing one bug uncovers the next one...
To reproduce:
llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...>
The result:
C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists.
So apparently, we're trying to move one file on top of another.
The
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 Apr 23
2
[LLVMdev] Building CFE in Mingw
Hello, all.
Just found this file in my e-mail atchive, hope it will be useful for somebody.
===cut=here===
Some small rules:
1) No blankspace in the paths to the top-level directories.
2) Add paths to binaries to your system PATH variable.
3) Use short paths to top-level directories.
1. Some checks & preparations.
1) Be sure, that you're using right make version:
$ make
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/
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 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
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]:
2005 May 14
2
[LLVMdev] Building Cygwin binaries
Hi,
I have got GCC 3.4.3 and binutils 2.15 installed on Cygwin.
Had to copy as.exe to gccas.exe to get llvm-gcc to get this far.
I am getting the following error message(s) :-
/usr/build/llvm-gcc/gcc/xgcc -B/usr/build/llvm-gcc/gcc/ -B/usr/llvm-gcc/i686-pc-
cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem
/usr/llvm-gcc/i686-pc-c
ygwin/include -isystem
2009 Aug 28
2
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
/home/ang/build/llvm-gcc-coff/./gcc/xgcc
-B/home/ang/build/llvm-gcc-coff/./gcc/
-B/home/ang/llvm-gcc/i686-pc-cygwin/bin/
-B/home/ang/llvm-gcc/i686-pc-cygwin/lib
/ -isystem /home/ang/llvm-gcc/i686-pc-cygwin/include -isystem
/home/ang/llvm-gcc
/i686-pc-cygwin/sys-include -O2
-I/home/ang/svn/llvm-gcc-coff/gcc/../winsup/w32
api/include -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
2010 Jan 08
3
[LLVMdev] Cygwin llvm-gcc regression
I am getting an assertion firing while building TOT llvm-gcc on Cygwin in
libgcc2.c :-
/home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/
-B/home/an
g/llvm-gcc/i686-pc-cygwin/bin/ -B/home/ang/llvm-gcc/i686-pc-cygwin/lib/
-isystem
/home/ang/llvm-gcc/i686-pc-cygwin/include -isystem
/home/ang/llvm-gcc/i686-pc-c
ygwin/sys-include -O2
2009 Jul 26
2
[LLVMdev] [Cygwin] error building llvm-gcc
I am getting an error building svn llvm-gcc on Cygwin :-
/home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/
-B/usr/llv
m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem
/usr/llvm
-gcc/i686-pc-cygwin/include -isystem
/usr/llvm-gcc/i686-pc-cygwin/sys-include -
O2 -I/home/ang/svn/llvm-gcc/gcc/../winsup/w32api/include -O2 -g -O2
-DIN_GCC
-W -Wall
2009 Jul 26
0
[LLVMdev] [Cygwin] error building llvm-gcc
Hi Aaron,
Which revision are you building?
Assuming TOT, it's possible this is a bug that I introduced/triggered
with the name changes. I know nothing of the status of cygwin however,
can you confirm that this used to work?
If you use r77097, does it work?
- Daniel
On Sun, Jul 26, 2009 at 4:23 AM, Aaron
Gray<aaronngray.lists at googlemail.com> wrote:
> I am getting an error