similar to: [LLVMdev] Still Trying to Build on MINGW

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Still Trying to Build on MINGW"

2006 May 06
0
[LLVMdev] Still Trying to Build on MINGW
On Sat, 6 May 2006, Greg Pettyjohn wrote: > Now I'm having problems with this: > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid > I've tracked this down in the debugger. It is indeed a bug. The problem is that Path::isValid() will reject a string
2006 May 06
2
[LLVMdev] Still Trying to Build on MINGW
Greg, Looks like Jeff Cohen already fixed this in CVS. Please update and give it another shot. Thanks, Reid. On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: > > On Sat, 6 May 2006, Greg Pettyjohn wrote: > > > Now I'm having problems with this: > > > > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...> > >
2006 May 06
2
[LLVMdev] Still Trying to Build on MINGW
Chris Lattner wrote: > On Sat, 6 May 2006, Reid Spencer wrote: >> Looks like Jeff Cohen already fixed this in CVS. Please update and give >> it another shot. > > Is this fixing the issue, or just papering over it? Why are we trying > to load an archive member without a path set? We're not. It's just a sentry value. > > -Chris > >> On Sat,
2006 May 06
0
[LLVMdev] Still Trying to Build on MINGW
On Sat, 6 May 2006, Reid Spencer wrote: > Looks like Jeff Cohen already fixed this in CVS. Please update and give > it another shot. Is this fixing the issue, or just papering over it? Why are we trying to load an archive member without a path set? -Chris > On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote: >> >> On Sat, 6 May 2006, Greg Pettyjohn wrote: >>
2006 May 07
0
[LLVMdev] Still Trying to Build on MINGW
On Sat, 6 May 2006, Jeff Cohen wrote: >>> Looks like Jeff Cohen already fixed this in CVS. Please update and give >>> it another shot. >> >> Is this fixing the issue, or just papering over it? Why are we trying to >> load an archive member without a path set? > We're not. It's just a sentry value. Then why does it matter whether the path is
2006 May 07
1
[LLVMdev] Still Trying to Build on MINGW
The constructor for Path validates the path, period. It doesn't know or care whether the path is ever handed to the OS. An invariant for Path dictates that it always has a valid path. Chris Lattner wrote: > On Sat, 6 May 2006, Jeff Cohen wrote: >>>> Looks like Jeff Cohen already fixed this in CVS. Please update and >>>> give >>>> it another shot.
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 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 Apr 30
0
[LLVMdev] Building LLVM under Mingw. Part I: tools-only
BTW: I've also had to make this change when building tools. (I'm building right now and noticed that it doesn't come up anymore, maybe someone checked it in in the last week or so) On Sat, 29 Apr 2006, Anton Korobeynikov wrote: > Hello, Jeff. > > You wrote Saturday, April 29, 2006, 10:45:02 PM: > > JC> Yes, I know mingw doesn't support dbghelp. I can still rant
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
2006 Apr 29
2
[LLVMdev] Building LLVM under Mingw. Part I: tools-only
Hello, Jeff. You wrote Saturday, April 29, 2006, 10:45:02 PM: JC> Yes, I know mingw doesn't support dbghelp. I can still rant about it :) ;) Well. Maybe this library will be included in some next versions of mingw's win32api package. Anyway, we can make such library just "on-fly" from the corresponding .dll. JC> This is what's already there. What changed? Maybe
2008 Dec 29
3
[LLVMdev] Error when attempting to build llvm-gcc-1.5 on Mac OS X 10.5.6
Hi Anton, Where can I get gccas ? I am running Mac OS X 10.5.6 and I get the following error: xgcc: installation problem, cannot exec `gccas': No such file or directory make[2]: *** [libgcc/./_muldi3.o] Error 1 make[2]: *** Waiting for unfinished jobs.... xgcc: installation problem, cannot exec `gccas': No such file or directory make[2]: *** [libgcc/./_negdi2.o] Error 1 make[1]:
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 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
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 Apr 23
1
[LLVMdev] Re: Building CFE on MinGW
Thanks. I'll try some of this. Further comments in-line: On Sun, 23 Apr 2006, Oscar Fuentes wrote: > Greg Pettyjohn <gregp at ccs.neu.edu> writes: > > > I'm using a little shell script: > [snip] > > confopts="--prefix=$PREFIX" > > confopts="$confopts --disable-threads" > > confopts="$confopts --disable-nls" >
2006 Apr 23
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes: > I'm using a little shell script: [snip] > confopts="--prefix=$PREFIX" > confopts="$confopts --disable-threads" > confopts="$confopts --disable-nls" > confopts="$confopts --disable-shared" > confopts="$confopts --enable-languages=c,c++" >
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
2005 Jan 30
1
[LLVMdev] Patch for Path.inc on mingw
Hi, I would like this patch for Path.inc to be accepted. I cannot tell, why the win32 version of isValid() method fails when issuing a correct path on the mingw platform. This is especially annoying when configuring the cfrontend, because we get this misindicating error: 'checking for sin in -lm... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.' And it has
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/