similar to: [LLVMdev] LLVM Makefile MODULE_NAME error

For anyone who encounters this issue in the future, my issue was the configuration of llvm-gcc. Configure with --with-llvmgccdir=YOUR/PATH doesn't work, instead you are supposed to use --with-llvmgcc=PATH/TO/llvm-gcc and --with-llvmgxx=/PATH/TO/llvm-g++ That will at least get you past my error. Best, Kyle Quoting nicolas geoffray <nicolas.geoffray at gmail.com>: > I am

Hello, I've been able to get J3 working with the single and multimap garbage collectors but have hit several snags with Boehm and MMTk. For MMTk I get here: Buildfile: /cs/student/kyleklein/vmkit/mmtk/java/build.xml main: [mkdir] Created dir: /cs/student/kyleklein/vmkit/mmtk/java/classes [javac] Compiling 373 source files to /cs/student/kyleklein/vmkit/mmtk/java/classes

Hi all, I haven't found this trick anywhere (including llvm/docs/MakefileGuide.html) so it maybe useful. This occurs only in 64 bit version of linux, linker of 32 bit system understands everything correctly. Situation: While building, at link stage, a 64bit version of some executable, with several archive libraries, say, A.a, B.a, C.a build fails with some "undefined reference to

Hi All, Thanks Nicolas for pointing out that I needed --enable-targets=x86,cpp for my llvm config to get vmkit to build. The process gets a lot farther but fails in different places depending upon the vmkit config (Can you please see the three case below?). My machine is a intel core i7 running ubuntu karmic and gcc 4.4.1. What arch/OS/distro/gcc do you all have VMKit working on? thanks for

Thanks Alysson. Unfortunately, those instructions don't work for me (I followed them exactly using a clean system) -- probably because of the recent changes to the svn heads. After fixing EscapeAnalysis in vmkit to use the updated CallInst.getArgOperand interface I hit the error below. I was interested in using mmtk with the system (as recommended), but that requires a llvm-gcc build (and

Dear Michael, The symbols that are said undefined by the compiler live in libAllocator.a. That file should be in Release/lib/, do you have it? It is possible that the compiler has linking order problems. What is the version of your gcc? You can try changing the link order of the make command by editing tools/vmkit/Makefile. Also, you should know that the GC of vmkit does not work on a

Hi, I can't seem to get VMKit to compile correctly. I'm on a 64 bit Jaunty system. I compiled llvm and llvm-gcc from the subversion source no problem, but when I try to compile VMKit I get some issue with GCAllocator: /home/mmwu/Download/llvm$ ./configure /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 /home/mmwu/Download/llvm$ make ENABLE_OPTIMIZED=1 install ...

Hi Bakiras, On Wed, Oct 19, 2011 at 11:02 AM, bakiras <h.bakiras at gmail.com> wrote: > Hi everyone, > > I am Harris Bakiras the new VMKit engineer. > Welcome :) > > I followed the VMKit "Getting Started" instructions to install VMKit on > my Linux Ubuntu 11.10 64-bit but I get the following error : > > make[1]: Entering directory

Hi Dean, Applies thanks! Out of curiosity, which part of mvm are you using? I guess the GC? Nicolas Dean Calver wrote: > Hello, > > Here's a tiny patch to the VMKIT tools makefile, that allows you to > build VMKIT without both Java and CLI. I'm working on a new bytecode > front end so wanted a 'clean' mvm without building to two existing > front ends.

Hello, Here's a tiny patch to the VMKIT tools makefile, that allows you to build VMKIT without both Java and CLI. I'm working on a new bytecode front end so wanted a 'clean' mvm without building to two existing front ends. Currently it still tries to build VMJC even when its told not to build the JNJVM. This patch fixes that. Index: tools/Makefile

Hi everyone, I am Harris Bakiras the new VMKit engineer. I followed the VMKit "Getting Started" instructions to install VMKit on my Linux Ubuntu 11.10 64-bit but I get the following error : make[1]: Entering directory `VMKIT_ROOTDIR/lib/Mvm/StaticGCPass' make[1]: *** No rule to make target `VMKIT_ROOTDIR/lib/Mvm/StaticGCPass/Release+Asserts/StaticGCPass.ll', needed by

Hi all, I am trying to build VMKit on Linux/x86 and I got error messages like below, llvm[1]: Linking Debug+Asserts executable vmjc /root/llvm/vmkit/tools/vmjc/Debug+Asserts/vmjc.o: In function `mvm::SpinLock::acquire()': /root/llvm/vmkit/include/mvm/Threads/Locks.h:164: undefined reference to `__sync_val_compare_and_swap_4' /root/llvm/vmkit/include/mvm/Threads/Locks.h:168: undefined

Resending, now that I've signed up to the dev list correctly... Sorry about duplicates. ---------- Forwarded message ---------- From: Zoe Wolk <zoewolk at gmail.com> Date: Mon, Jun 28, 2010 at 3:54 PM Subject: vmkit and llvm 2.8 To: llvmdev at cs.uiuc.edu Hi All, Has vmkit been updated and tested with LLVM 2.8? I am unable to build it (llvm builds fine). There were some errors with

Hi All, Has vmkit been updated and tested with LLVM 2.8? I am unable to build it (llvm builds fine). There were some errors with Makefile.rules: $(Verb) $(LLVMAS) -f $(<F) -o - | $(LLC) -march=cpp -cppgen=contents -o $@ (march and cppgen options not recognized). What I cannot get past is this one (the warnings concern me as well): ... make[3]: Leaving directory

Hi Frederic, On Wed, Aug 24, 2011 at 11:01 AM, Frederic Perez Ordeig <fredericp at gmail.com > wrote: > Ah yes, thanks, this was one problem, now I hit another: > > llvm[2]: Building Release+Asserts mmtk-vmkit.jar all > Thread 0x110000000 received a SIGSEGV: either the VM code or an external > native method is bogus. Aborting... > ; 0x5cfeed (0x1100fe410) in

I tried to build VMKit on an ARM device today (a Sheevaplug - armv5te) (native, not cross compiled), and got this error: llvm[3]: Building LLVM assembly with /home/debio/build/vmkit-build/vmkit/lib/Mvm/Runtime/LLVMAssembly.ll /home/debio/build/vmkit-build/vmkit/lib/Mvm/Runtime/LLVMAssembly64.ll ExpandIntegerResult #0: 0x16fbf88: i64,ch = AtomicCmpSwap 0x16e8d84, 0x16fbf00, 0x16fc3c8,

Hi Nicolas, I'm trying now to build vmkit with mmtk: ./configure --with-llvmsrc=/home/zoewolk/RESEARCH/llvm --with-llvmobj=/home/zoewolk/RESEARCH/llvm --with-gnu-classpath-glibj=/home/zoewolk/RESEARCH/classpath-0.97.2/lib --with-gnu-classpath-libs=/home/zoewolk/RESEARCH/classpath-0.97.2/lib --with-gc=mmtk I've built llvm-gcc from source and configured llvm so that it can find it.

Ah yes, thanks, this was one problem, now I hit another: llvm[2]: Building Release+Asserts mmtk-vmkit.jar all Thread 0x110000000 received a SIGSEGV: either the VM code or an external native method is bogus. Aborting... ; 0x5cfeed (0x1100fe410) in _Z14sigsegvHandleriP7siginfoPv ; 0x2b889c232c60 in Unknown method ; 0x561499 (0x1100fe900) in _ZN2j310JavaObject7acquireEPS0_ ; 0x55b464 (0x1100fe920)

Are you running on 64bit (your backtrace addresses suggest you are)? I'm encountering the same error when trying to use VMKit on 64bit, which I believe is an unsupported target. ~Will On Tue, Aug 23, 2011 at 5:17 PM, Frederic Perez Ordeig <fredericp at gmail.com> wrote: > I'm trying to build the SVN version of VMKit and I'm getting this error > while building. > I

Hi Konrad, I have added some diagnostic message when failing that early in the bootstrap in the VM. Please svn up and let me know what it prints. About the SIGSEGV you get with clojure.jar, I ran the code and got the same error. After investigation, it turns out that the methods you have in that .jar are quite big (50,000 bytecodes) and the static initializer of the core__init class just crashes