similar to: [LLVMdev] [Cygwin] Build

Hi, I installed the cfrontend 1.5 and LLVM 1.5 from source in cygwin successfully using GCC3.4.3 and binutils2.15 (as in makefiles do not complain errors except some warnings). However when I do this, there are some errors like, *************************************************************** u0201201 at 9nnvf2ay /home/cfrontend/install/lib $ llvm-ranlib libiberty.a llvm-ranlib: Error opening

Okay, this I have no clue about. I've never done "make check" on llvm- gcc. I thought you meant "make check" on LLVM. You're into "new territory". Reid. On Thu, 2005-05-19 at 16:07 +0100, Aaron Gray wrote: > Does not look like the demangle test worked anyway :( > And 'make check' :- > > $ make check >

> I installed the cfrontend 1.5 and LLVM 1.5 from source in cygwin > successfully using GCC3.4.3 and binutils2.15 (as in makefiles do not > complain errors except some warnings). > > However when I do this, there are some errors like, > > *************************************************************** > u0201201 at 9nnvf2ay /home/cfrontend/install/lib > $ llvm-ranlib

>Okay, that file checks out just fine using llvm-ranlib and llvm-ar on >Linux, so the file is not the problem, llvm-ranlib on cygwin is. I don't >know what the issue could be. If you feel like gdbing llvm-ranlib while >it tries to process that file and get some info on why it can't read the >file, that would be useful. This isn't critical btw, not having ranlib'd

Hi, Got everything built but am now experiencing new errors on making the symbol tables and on 'make check'. Here's the errors I am experiencing :- Aaron Gray at AMD-LAPTOP-1 /usr/llvm-gcc/lib $ ls gcc libdummy.a libiberty.a libstdc++.a libsupc++.la libc.a libgcc.a libm.a libstdc++.la libtrace.a libcrtend.a libgcsemispace.a

Aaron, Could you send me the libiberty.a file? Please gzip it. I would like to make sure this isn't an llvm-ranlib bug. Thanks, Reid. On Thu, 2005-05-19 at 15:36 +0100, Aaron Gray wrote: > Hi, > > Got everything built but am now experiencing new errors on making the > symbol tables and on 'make check'. > > Here's the errors I am experiencing :- > >

Okay, this is looking much better. I'll commit the configure script. There's a couple of CFrontEnd failures. Possibly you're not working with the latest llvm-gcc? (built from CVS?) The others are known JIT failures on Cygwin .. it can't load symbols from the LLI executable. We don't have a fix for this (yet). So, I'd say we're good to go :) Reid. On Thu, 2005-06-02

Hi, I am wondering whether the bytecode generated by my llvm-gcc is correct? When I run $ llvm-gcc hello.c -o hello What I get is hello.exe.bc, and hello.exe (I can actually llvm-dis the bytecode file which is hello.exe.bc). However, I do not get a shell script(named hello) as stated in the documentation... Best Regards, Kiat On 5/25/05, Aaron Gray <angray at beeb.net> wrote: >

Does not look like the demangle test worked anyway :( And 'make check' :- $ make check make[1]: Entering directory `/usr/build/llvm-gcc/gcc' (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /usr/cfrontend/src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd

Reid, Heres the results, even better than before :- # of expected passes 1759 # of unexpected failures 12 # of expected failures 56 Previous working build :- # of expected passes 1736 # of unexpected failures 16 # of expected failures 56 Goodie, now for a release build. Aaron -------------- next part -------------- An HTML attachment was

Hi, Maybe I can provide you with the installation steps that I done in my machine. What I did is, 1. first install cygwin, I attached a list of the packages I installed. (there are quite a lot of packages) 2. build the binutils-2.15. 3. Then gcc-3.4.3. (I am using the new binutils which is the 2.15) 4. Next, I follow the instructions in the LLVM documentation to further build the

Actually, I just found out why. Remove the space from the end of the TOOLNAME line in llvm-ar and llvm-ranlib Makefiles. This is what's causing it, there's a space between "llvm-ar" and ".exe" I'll patch the makefiles when UIUC's CVS server isn't so sluggish. Reid On Thu, 2005-05-19 at 13:45 -0700, Reid Spencer wrote: > The rules for building llvm-ar

Also, this error: /usr/src/llvm/lib/Target/X86/X86ISelPattern.cpp:73: undefined reference to `X86CompilationCallback2' doesn't make sense. X86CompilationCallback2 is not visible outside of X86JITInfo.cpp, and line 73 of X86ISelPattern.cpp is in the middle of a comment block.

The rules for building llvm-ar and llvm-ranlib are identical to the rules for building all other tools so I don't know why the makefiles would single those two out. Reid On Thu, 2005-05-19 at 21:31 +0100, Aaron Gray wrote: > >No, I don't think so. The "bin" directory definitely gets created first > >as there is a rule for it in Makefile.rules and appropriate >

OK I've got GNU ld version 2.15.94 20041229 as and ar are the same version number etc. I think the latest release is 2.16. I guess you guys like to stay on the bleeding edge! I'll give it a try with the cfrontend included as suggested, but I'm actually writing a pattern matching compiler for a non-C scripting language and I'm looking for an optimizing back-end such as llvm. I

Here it is, a missing file "analyze.1" :- /usr/bin/groff -Tps -man /usr/build/llvm/docs/CommandGuide/analyze.1 > /usr/buil d/llvm/docs/CommandGuide/analyze.ps troff: fatal error: can't open `/usr/build/llvm/docs/CommandGuide/analyze.1': No such file or directory make[2]: *** [/usr/build/llvm/docs/CommandGuide/analyze.ps] Error 1 make[2]: Leaving directory

Aaron, That looks to me like the "install" program on your platform isn't quite up to snuff. It should be doing a command like: /usr/bin/install -c -m 0755 \ /proj/llvm/build/Debug/bin/llvm-ranlib /proj/install/bin/llvm-ranlib Its not supposed to create an llvm-ranlib directory, the second argument is the name of the file to create. This works fine on linux. Can you "make

On Thu, 2005-05-19 at 22:34 +0100, Aaron Gray wrote: > I do not really feel upto looking into makefiles yet as I don't really know > automake, configure scripts, etc, etc > Aaron, its trivial. Open up tools/llvm-ar/Makefile in an editor. Go to the TOOLNAME line, delete the space at the end of the line, save the file, rebuild. > >I'll patch the makefiles when UIUC's

Here's the instructions as I have them so far :- http://angray.members.beeb.net/llvm/MakingLLVM.html I was wondering whether you could look them over to see if I am doing something obviously wrong. Thanks, Aaron

Reid, Looks like the "make TOOL_VERBOSE=1 -C tools install" was fine. I have got :- install (GNU coreutils) 5.3.0 The copyright is 2005 so I would have thought it would be allright ??? Thanks, Aaron