similar to: [LLVMdev] Trying to build llvm-gcc no x86_64 linux

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Trying to build llvm-gcc no x86_64 linux"

2010 Aug 12
0
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
You'll need to install the dev packages for gcc 4.2. Rajika On Thu, Aug 12, 2010 at 1:27 PM, Romain Pechayre <rpechayr at gmail.com> wrote: > Hello all, > > I am trying to build the latest version of llvm-gcc on a x86_64 > architecture running a Linux distribution. Using the READM.LLVM I have > managed to run ./configure using appropriate options, but when I try to >
2010 Aug 12
2
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
I need to add, also you'll need bison+flex. Rajika On Thu, Aug 12, 2010 at 6:41 PM, Rajika Kumarasiri <rajika at wso2.com> wrote: > You'll need to install the dev packages for gcc 4.2. > > Rajika > > On Thu, Aug 12, 2010 at 1:27 PM, Romain Pechayre <rpechayr at gmail.com>wrote: > >> Hello all, >> >> I am trying to build the latest version
2010 Aug 12
2
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
On Thu, Aug 12, 2010 at 6:56 PM, Romain Pechayre <rpechayr at gmail.com> wrote: > Ok. Thank you for your input. New questions :) : > - Is the dev package basically the source code of gcc 4.2 ? Isn't it > already fully included in llvm-gcc code base ? > AFAIR, you need to have the set of headers, gcc-dev.( Some one else may provide you with this information) > - How
2010 Aug 12
1
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
I got this one fixed by rebuilding llvm Debug (oups). I had an old version. I now seem to have a classical message: version GLIBCXX_3.4.14 not found. I am indeed building llvm-gcc using gcc4.5. Is this the problem ? The fix to this problem indicated in README.LLVM does not help .. Thanks Romain On Thu, Aug 12, 2010 at 6:43 PM, Romain Pechayre <rpechayr at gmail.com> wrote: > Thanks.
2010 Aug 12
0
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
Thanks. It worked for a few more compilation lines. I now get the following linker error: undefined reference to llvm::MemoryBuffer::getNewMemBuffer(unsigned long, llvm::StringRef) I am surprised since the linker compile line already links with a whole bunch of llvm libraries ... Thanks for your help Romain On Thu, Aug 12, 2010 at 4:03 PM, Rajika Kumarasiri <rajika at wso2.com> wrote:
2010 Aug 12
0
[LLVMdev] Trying to build llvm-gcc no x86_64 linux
Ok. Thank you for your input. New questions :) : - Is the dev package basically the source code of gcc 4.2 ? Isn't it already fully included in llvm-gcc code base ? - How should I include bison+flex when I have installed Do I need to put additional flags to configure script ? Cheers, Romain On Thu, Aug 12, 2010 at 3:13 PM, Rajika Kumarasiri <rajika at wso2.com> wrote: > I need to
2009 Sep 25
6
[LLVMdev] JIT on ARM
Hello. My goal is to use LLVM with JIT compiler for ARM on Android device. Currently I have successfully built and executed LLVM bitcode with interpreter on Android. Speed is not so great, that is why I want to use JIT. I tried building bitcode on windows with llvm-gcc that is provided on llvm home page. Resulting bitcode runs great in interpreter, but it doesn't use JIT. From what I
2009 Oct 14
0
[LLVMdev] JIT on ARM
Forgot to mention. I don't know how well the canadian cross compile stuff works in 2.5. We made some improvements in that area for 2.6. If you have trouble with it, I'd suggest trying 2.6 (or even better, ToT svn) and seeing if things are improved there. -Jim On Sep 25, 2009, at 2:04 AM, Martins Mozeiko wrote: > Hello. > > My goal is to use LLVM with JIT compiler for ARM
2007 Sep 18
1
[LLVMdev] 2.1 Pre-Release Available (testers needed)
More bison woes. llvm-2.1 + the patch Chris mentioned builds without bison, but llvm-gcc4 doesn't: /home/emil/ll/llvm-gcc4.0-2.1.source/missing bison -d -o gengtype-yacc.c ../../llvm-gcc4.0-2.1.source/gcc/gengtype-yacc.y WARNING: `bison' missing on your system. You should only need it if you modified a `.y' file. You may need the `Bison' package in order for
2009 Oct 14
0
[LLVMdev] Fwd: JIT on ARM
Hi. Sorry for reposting my mail, but can somebody at lest give some general ideas for what to look to solve my problem? -- Martins Mozeiko Begin forwarded message: > From: Martins Mozeiko <49640f8a at gmail.com> > Date: September 25, 2009 12:04:04 GMT+03:00 > To: llvmdev at cs.uiuc.edu > Subject: JIT on ARM > > Hello. > > My goal is to use LLVM with JIT compiler
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
On Mon, Sep 17, 2007 at 12:25:40PM -0700, Chris Lattner wrote: > On Mon, 17 Sep 2007, Emil Mikulic wrote: > >> The 2.1 pre-release (version 1) is available for testing: > >> http://llvm.org/prereleases/2.1/version1/ > > > > I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be > > stale. I tried building LLVM without bison installed and got:
2007 Sep 17
3
[LLVMdev] 2.1 Pre-Release Available (testers needed)
On Mon, 17 Sep 2007, Emil Mikulic wrote: >> The 2.1 pre-release (version 1) is available for testing: >> http://llvm.org/prereleases/2.1/version1/ > > I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be > stale. I tried building LLVM without bison installed and got: Can you try it again without bison with these files:
2010 Jan 03
2
[LLVMdev] Help Required for LLVM
Sir/Ma'am, I am a MTech student at IIT Bombay, doing my thesis in compiler optimization. I am working on "Profile Based Pointer Analysis to Perform Optimization", and would like to implement the optimization in llvm for performing experiments. When I was trying to build and install the compiler after configuring llvm-gcc I got the following error: gcc: gengtype-lex.c: No such
2010 Jan 04
0
[LLVMdev] Help Required for LLVM
Hi Ambika, > I am a MTech student at IIT Bombay, doing my thesis in compiler > optimization. > I am working on "Profile Based Pointer Analysis to Perform > Optimization", and would like to implement the optimization in llvm for > performing experiments. > > When I was trying to build and install the compiler after configuring > llvm-gcc I got the following
2007 Apr 27
2
[LLVMdev] Boostrap Failure -- Expected Differences?
The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the
2006 Sep 25
5
HTTP Parser (Regal)
Hi I was interested to see how Mongrel uses Lex/Yacc to parse the HTTP requests using a Regal generated parser. I downloaded the source but do not see the lex and yacc files...
1997 Dec 05
2
lex, yacc
Hi there!! Can someone tell me where I can find 'supported' lex and yacc utilities that work on NT? Pardon me if this question is not relevant in this list.. Please send me the replies directly to my e-mail 'k.sundram@blr.sni.de' ; since I find that this list is getting bigger and better.. Thanx in advance K R Sundaram -- ************************************************ *****
2007 May 23
2
about lex/yacc
hello, what about these functions lex/yacc which can parse and recognize a syntax? thanks _____________________________________________________________________________ [[alternative HTML version deleted]]
2008 May 22
2
[LLVMdev] Latest SVN head (gcc front end) build failed
hi all, I was trying to build the latest LLVM gcc front end and it failed. rajika@:~/project/llvm/dst-directory$ svn info | grep URL URL: http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk configure option: ../dst-directory/configure --prefix=/usr/local/ --enable-llvm=/home/rajika/project/llvm/llvm-objects it gave me the following errors ../../dst-directory/gcc/llvm-convert.cpp:1163: error:
2010 Jan 16
1
[LLVMdev] Build failure in llvm trunk
hi, I am trying to build the llvm trunk with make. I am trying a debug build and I am ending with the following build error. /home/rajika/projects/llvm/llvm/lib/Target/TargetLoweringObjectFile.cpp: In member function ‘virtual bool llvm::TargetLoweringObjectFileMachO::shouldEmitUsedDirectiveFor(const llvm::GlobalValue*, llvm::Mangler*) const’: