similar to: [LLVMdev] llvm-config Perl not found ProjLibsPaths 'bug'

Hello Aaron, Aaron Gray wrote on 14/10/2005 at 10:22 a.m.: > I am not sure but it looks like a problem with your Cygwin > instillation ? Try a 'make configure' or 'make reconfigure'. Hmmm, I was able to build llvm/tools-only.... As for "make configure" - that didn't help. > Here's a link to the instructions I developed for building LLVM on > Cygwin

Oleg, > - llvm/make tools-only worked ok Good. > - llvm-gcc/make all failed with the following message (2nd try): > make[2]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > make[1]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > Checking multilib configuration... > multilib.out is unchanged > Configuring in i686-pc-cygwin/libstdc++-v3 >

Aaron Gray wrote: > Turns out I did not have Perl installed and hence no pod2man command, so > it was not groff after all. > > But 'true', what ever it does, does not seem to be working on Cygwin. > > true pod2man --release=1.5 --center="LLVM Command Guide" > /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod >

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: >

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

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

Sure, but not right now. I need to go out for a bit. I'll look at them tonight. Reid. On Mon, 2005-05-30 at 20:41 +0100, Aaron Gray wrote: > 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. > >

On Fri, 14 Oct 2005, Oleg Smolsky wrote: > Hello Aaron, > Aaron Gray wrote on 14/10/2005 at 10:22 a.m.: >> I am not sure but it looks like a problem with your Cygwin >> instillation ? Try a 'make configure' or 'make reconfigure'. > Hmmm, I was able to build llvm/tools-only.... As for "make configure" - > that didn't help. > >>

>From: "Aaron Gray" <angray at beeb.net> >Date: Fri, 4 Nov 2005 16:44:23 -0000 > >>You're welcome to join me. Say when you're ready to dig... > >I'll join in at some point, if that is okay. > >I'd like to get LLVM working on MinGW running as well as Cygwin. > Sure, I would love to have you on the team, too, so we can get llvm via this

Anton, Thanks for your comment. 2nd patch attached. - s/SharedDir/SharedLibDir/g - move prefix=cyg sunk into if(cygwin or mingw) arigato gozaimasu...Takumi * Additional issues - You may build LLVMHello.dll but I don't modify lib/Transforms/Makefile. Because making LLVMHello.dll requires the library LLVM.dll, but it oughta be on the way to making libs at building

Turns out I did not have Perl installed and hence no pod2man command, so it was not groff after all. But 'true', what ever it does, does not seem to be working on Cygwin. true pod2man --release=1.5 --center="LLVM Command Guide" /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod /usr/build/llvm/docs/CommandGuide/analyze.1 'true' seems to behaving like a

>You're welcome to join me. Say when you're ready to dig... I'll join in at some point, if that is okay. I'd like to get LLVM working on MinGW running as well as Cygwin. Aaron

I am wanting to upgrade my Fedora Core 6's GCC as it is version 4.1.1 and that does not build LLVM-GCC4. What version of GCC is recomended ? Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070303/c5da364e/attachment.html>

> You can get one for free on code.google.com. It comes as part of code > hosting. Authentication/authorization for both wiki and svn is > governed by the same credentials as given by the project owner(s) (the > wiki is driven by the same svn repo as the code). So even hosting svn > there might be a good thing . That would not host the commits mailing list. Aaron

Hello Aaron, Aaron Gray wrote on 14/10/2005 at 5:50 a.m.: >> Also, it would be really nice if an official cygwin build (the >> binary) was published too. I spent quite a bit of time screwing >> with it a few months ago, and it was quite a bastard to get >> going... > I had quite a time with it too, could only get the debug version to > build as there seemed to be an

Hi all, I'm building the LLVM 2.0 pre-release on a brand new FreeBSD 6.2 install. Without the bison package installed, the build breaks: $ tar zxf llvm-2.0.tar.gz $ mkdir objdir $ cd objdir $ ../llvm-2.0/configure $ gmake [...] gmake[2]: Entering directory `/usr/home/emil/objdir/utils/TableGen' llvm[2]: Compiling AsmWriterEmitter.cpp for Release build llvm[2]: Compiling

Hi Aaron, Sorry for the delay. Please be aware, that these instructions has not been used lately. However, I'll try to follow up on your questions. Here are my instructions to compile the cfe: 5. Configure, build, and install the C front-end: a. Before configure: export CPPFLAGS="-D__MINGW32__ " ?export LDFLAGS=-Wl,-no-keep-memory"

> llvm[2]: Flexing FileLexer.l > llvm[2]: Bison of FileParser.y SKIPPED -- bison not found > llvm[2]: Compiling FileLexer.cpp for Release build > /usr/home/emil/llvm-2.0/utils/TableGen/FileLexer.l:34:24: FileParser.h: No such file or directory > > Is this a packaging issue where FileParser.h was omitted > from the tarball, or does LLVM *need* bison in order to build? No,

Hi Aaron, Please be aware that my instructions are directed to get the cfe to compile on mingw. I wasn't in the first place aware that you were building on the Cygwin platform. However, me and others will try to help you to compile the cfe. Please submit your compiling errors on this mailing list. Henrik. >From: "Aaron Gray" <angray at beeb.net> >Reply-To: LLVM

Hi LLVM'ers, has anyone read the license details for MASM32 and understood how these fit in with Open Source projects, especially GPL? - As far as I can see - no one is allowed to license projects under GPL or at worst other OS licenses nor the deritives of the project, if you're using MASM32. Are the MASM backend compatible with the MS version of MASM or other not so license