similar to: [LLVMdev] Help with Mac OS X 10.6.2 build

Hi, Try these scripts to build llvm and llvm-gcc. It's the ones I use and I managed to get them to work when I saw another build script using those CFLAGS. They compile llvm and stuff using only x86_64, but you can then generate code for i386 (just use a different backend). The configuration options are at the top of the scripts and they install llvm and llvm-gcc to ~/llvm. Regards,

I am new to llvm so I might be missing a critical step. My system is Fedora 12 but this also happens in Mac OS X 10.6.2. Here are the steps I used to compile llvm: export TARGETS=x86,x86_64,cpp export INSTALLDIR=/home/rovitotv/llvm ../llvm-2.6/configure --prefix=$INSTALLDIR --enable-bindings=none --enable-targets=$TARGETS --enable-optimized --with-llvmgccdir=$INSTALLDIR

First, you have to call llvm-g++ to use the llvm-gcc front end, but it doesn't matter here. I'd like to suggest that you use pastebin to put your code and the send us the link, so that we can download it. The problem is that TheExecutionEngine is set to NULL (maybe because of a previous error), but it will be really better if you use pastebin. On Wed, Feb 17, 2010 at 6:01 AM, Todd Rovito

Hi all, I've started work on a new programming language for which I am considering using LLVM as the backend, and trying to experiment with it using the Kaleidoscope demo compiler. Taking the full source listing from http://llvm.org/docs/tutorial/LangImpl3.html#code and trying to compile it with the provided instructions gives me the following errors: a at a-desktop:~$ g++ -g -O3 toy.cpp

Probably you missed to install llvm-dev package with headers for llvm. 2010/1/4 Russell Wallace <russell.wallace at gmail.com> > Hi all, > > I've started work on a new programming language for which I am > considering using LLVM as the backend, and trying to experiment with > it using the Kaleidoscope demo compiler. > > Taking the full source listing from >

On Wed, Feb 17, 2010 at 6:29 AM, Conrado Miranda <miranda.conrado at gmail.com> wrote: > First, you have to call llvm-g++ to use the llvm-gcc front end, but it > doesn't matter here. I got the compile command from the Kaleidoscope documentation. > I'd like to suggest that you use pastebin to put your code and the send us > the link, so that we can download it. The

I tried apt-get install llvm-dev just now, and it says it was already installed, and when I again try compiling toy.cpp, it gives the same set of error messages. On Mon, Jan 4, 2010 at 10:27 AM, Oleg Knut <oleg77 at gmail.com> wrote: > Probably you missed to install llvm-dev package with headers for llvm. > > 2010/1/4 Russell Wallace <russell.wallace at gmail.com> >>

Hello , I have build llvm from release_38 branch ( only llvm and clang ) and install it. My DYLD_LIBRARY_PATH points to installation-directory/lib. I am compiling example files for Kaleidoscope with following command : clang++ -g toy.cpp -std=c++11 `llvm-config --cxxflags --ldflags --system-libs --libs core mcjit native` -O3 -o toy but it fails with following error: Undefined symbols for

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

There were some typos in the tutorial. This patch should fix them: index b7f968b..50619e0 100644 --- a/docs/tutorial/LangImpl2.html +++ b/docs/tutorial/LangImpl2.html @@ -933,7 +933,7 @@ public: /// of arguments the function takes). class PrototypeAST { std::string Name; - std::vector&lt; Args; + std::vector&lt;std::string&gt; Args; public: PrototypeAST(const std::string

I resend email with updated (after mass header move) log examples. > LLVM build without big problems in obj dir == src dir case (for example, > last night tester build) > But I have problem with building CVS version LLVM in obj dir != src dir > case. > gmake[1]: Entering directory `/usr/home/wanderer/pkg/build/llvm/obj/projects' gmake[2]: Entering directory

I need to generate variables like status1, status2, status3, ...... request1, request2, request3, ...... this is my code, other unrelated detail are eliminated. static int varNum; static const char *getVarNum() { ++varNum; std::stringstream ss; ss << varNum; std::string *varname = new std::string(ss.str()); return varname->c_str(); } const char *VarNum = getVarNum(); Twine *x1 = new

> On Mon, 5 Nov 2007, Aaron Gray wrote: >> Nice job. The only bit that is not immediately clear is the 'Proto' >> variable, but is clear when looking through the code at the end of the >> page. > > Where in the tutorial? What would you suggest that I say? First reference in 'Function *FunctionAST::Codegen()'. What Proto is is not totally clear till

I'm working through the Kaleidoscope tutorial through section 2.4, and I've encountered some problems: several minor bugs, and finally a bus error that has me stumped: ------- In the code listed in LLVM Tutorial section 2.2 Implementing a Parser and AST. Line 19 has a comma at the end of line that shouldn't be there Line 120 is missing a closing angle bracket. Line 120 should be

Nice work, Chris! This is a much needed tutorial. Some comments: -- It would be helpful to add some navigation links at the top and bottom of the pages. -- Not clear why PrototypeAST::Codegen returns a Function* instead of a Value* like the other CodeGen methods? -- It can be convenient to use Visitor methods on the AST classes for code generation, instead of hard-coding the CodeGen

²Š'

On Mon, 5 Nov 2007, Aaron Gray wrote: >> Anyone have thoughts or feedback? :) > > Nice job. The only bit that is not immediately clear is the 'Proto' > variable, but is clear when looking through the code at the end of the page. Where in the tutorial? What would you suggest that I say? > Could do with a link to the LLVMBuilder class reference material. I added a link

Hi All, LLVM has long needed a tutorial for people who are interested in using it to implement their favorite language and to demonstrate how to use the JIT. To help solve this, I've put together a little tutorial that runs through the implementation and extension of a toy language here: http://llvm.org/docs/tutorial/ At this point, the tutorial is feature complete, but might

I've hit this weird compiler error when building llvm/clang $ clang --version clang version 2.9 (trunk 125254) Target: x86_64-apple-darwin10 Thread model: posix Source rev is 125326 $ make llvm[1]: Compiling APFloat.cpp for Release build llvm[1]: Compiling APInt.cpp for Release build llvm[1]: Compiling APSInt.cpp for Release build llvm[1]: Compiling Allocator.cpp for Release build llvm[1]: