similar to: [LLVMdev] Stacker config problems

If I remember correctly, you get the following warning when you configure LLVM: configure:2087: WARNING: Unknown project (Stacker) won't be configured automatically That leads would lead me to believe that you need to run configure inside llvm/projects/Stacker (and inside llvm/projects/Hello) before you run gmake inside of them. I don't know for sure, but perhaps that might fix

Hi all! I have sucessfully installed LLVM 1.9 under FreeBSD on a x86 PC. I have successfully executed "An Example Using the LLVM Tool Chain" that is written in the document http://llvm.org/docs/GettingStarted.html When I tried out the demo projects "Hello" and "Stacker" I get compile errors. When I run "gmake" in the directory

Next problem detected by nighttest: LLVM build fail with errors: gmake[4]: Entering directory `/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime' llvm[4]: Compiling stacker_rt.c for Debug build (bytecode) default/bin/llvm-gcc: not found gmake[4]: *** [/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime/Debug/stacker_rt.bc] Error 1

>I successfully build CFE frontend at FreeBSD 5.3. > > Next nighttest run show more detail information :) After last 2 nighttest runs i see stable failure result: llvm[2]: Compiling dummylib.c for Debug build (bytecode) llvm-g++: installation problem, cannot exec `gccas': No such file or directory gmake[3]: ***

Hello, I was wondering what happened to the "Stacker" example. The old link to it "http://llvm.org/docs/Stacker.html" is dead. Thanks, Wayne ________________ Wayne Anderson

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. ======= Finished building ModuleMaker debug executable (without symbols) ======= gmake[2]: Leaving directory `/usr/home/wanderer/pkg/build/llvm/obj/examples/ModuleMaker' gmake[1]: Leaving directory

Sloppy me. I fixed the path for llvm-gcc but not for llvm-g++. My last patch to Makefile.rules fixes that so it should start working again. Reid. On Fri, 2004-12-24 at 05:21, Vladimir Merzliakov wrote: > >I successfully build CFE frontend at FreeBSD 5.3. > > > > Next nighttest run show more detail information :) > > After last 2 nighttest runs i see stable failure

On 2008-04-08, at 20:21, Lane Schwartz wrote: > I checked out the Stacker directory from svn, and put it in my llvm- > src/projects directory. Unfortunately, when I run make, I get the > errors below. I wondered whether the stacker code might simply be > out of date It is. The fixes are likely mechanical, but just require someone stepping up and submitting a patch. — Gordon

Hi! In current LLVM CVS: llvm/projects/Stacker/Makefile.common.in llvm/projects/sample/Makefile.common.in llvm-java/llvm-java/Makefile.common.in have line: include $(LLVM_OBJ_ROOT)/Makefile.common that have line: include $(LLVM_OBJ_ROOT)/Makefile.config (also $(LLVM_OBJ_ROOT)/Makefile.config used in llvm-test/Makefile.config.in) and llvm/Makefile.config.in have lines: INSTALL_SH :=

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

On Tue, Apr 8, 2008 at 8:00 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On 2008-04-08, at 20:21, Lane Schwartz wrote: > > > I checked out the Stacker directory from svn, and put it in my llvm- > > src/projects directory. Unfortunately, when I run make, I get the > > errors below. I wondered whether the stacker code might simply be > > out of

As a learning aid for myself and for other would be source language writers for LLVM, I have decided to write a very simple language I'm calling "Stacker". Its kinda like Forth but way, way, way simpler. Its nowhere near ANS Forth and it won't be useful for much other than demonstrating how to create a source language using LLVM. I thought I'd mention this just so everyone

On Mon, 30 Aug 2004 21:27:26 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > On Mon, 30 Aug 2004 20:48:45 -0700 > Jeff Cohen <jeffc at jolt-lang.org> wrote: > > > When I ran configure after updating, I get various errors. First: > > > > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc > > checking for a

Personally, I don't think LLVM projects should need much in the way of autoconf stuff. They certainly don't need to replicate things like install-sh and mkinstalldirs. I'd vote for taking these out of the projects rather than making the makefiles deal with them. I think in most cases these are just historical artifacts that have been with the projects since long before the new

Hi, I'm new to LLVM, and I'm trying to get things set up. So far I've successfully gotten the C and C++ frontends to run, using the pre-compiled Mac OS X PPC binaries. I've also successfully compiled the main LLVM package (minus the gcc frontend). I'm now trying to get the Stacker sample project to compile. I checked out the Stacker directory from svn, and put it in my

On Mon, 2005-02-14 at 20:53, Chris Lattner wrote: > On Mon, 14 Feb 2005, Reid Spencer wrote: > > > Personally, I don't think LLVM projects should need much in the way of > > autoconf stuff. They certainly don't need to replicate things like > > install-sh and mkinstalldirs. I'd vote for taking these out of the > > projects rather than making the makefiles

Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's

On Mon, 14 Feb 2005, Reid Spencer wrote: > Personally, I don't think LLVM projects should need much in the way of > autoconf stuff. They certainly don't need to replicate things like > install-sh and mkinstalldirs. I'd vote for taking these out of the > projects rather than making the makefiles deal with them. I think in > most cases these are just historical artifacts

On Mon, 30 Aug 2004 20:48:45 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > When I ran configure after updating, I get various errors. First: > > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc > checking for a BSD-compatible install... /usr/bin/install -c > checking build system type... i386-unknown-freebsd5.2.1 > checking host system

I updated my source tree and after putting malloc.h back things look a lot better. Still getting a large number of JIT-only failures. There is now only one assertion failure: /home/cfe/x86/llvm-gcc/bin/g++ -I/usr/home/llvm/obj/projects/llvm-test/MultiSource/Benchmarks/Prolangs-C++/city -I/usr/home/llvm/obj/projects/llvm-test/../../../projects/llvm-test/MultiSource/Benchmarks/Prolangs-C++/city