similar to: [LLVMdev] compiling java frontend

I am trying to compile the Java frontend in https:/ llvm.org/svn/llvm-project/java/trunk If there are another preferred Java frontend available, and it is suited for translating Java bytecode to LLVM bytecode, I'd be happy to use that frontend instead. thanks, Andreas On Thu, Sep 17, 2009 at 4:03 PM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 17, 2009, at 3:59

On Sep 17, 2009, at 3:59 PM, Andreas Saebjoernsen wrote: > I am looking for a way to translate Java bytecode to LLVM bytecode > and the LLVM Java frontend seem like a good match for initial > testing. But after checking out the svn version of the Java > frontend I get the following error when running configure > > configure: error: cannot find install-sh or install.sh

On Sep 17, 2009, at 4:17 PM, Andreas Saebjoernsen wrote: > I am trying to compile the Java frontend in > https:/llvm.org/svn/llvm-project/java/trunk > If there are another preferred Java frontend available, and it is > suited for translating Java bytecode to LLVM bytecode, I'd be happy > to use that frontend instead. That is really old and out of date, I'm sure it

Thanks, I am now working on compiling up VMKit. When compiling VMKit in my up-to-date svn checkout I get several error messages on missing members of the class 'llvm::Type': PNetLib.cpp: In function ‘void decapsulePrimitive(n3::VMObject*, const llvm::Type*, std::vector<llvm::GenericValue, std::allocator<llvm::GenericValue> >&)’: PNetLib.cpp:694: error: ‘Int1Ty’ is not a

Hi Andreas, Since you're only looking for a Java frontend, I suggest you only build the Java frontend of vmkit and don't pass any pnet or mono information to the configure script. I haven't updated the pnet part of the .Net frontend. On the other hand, the Java frontend is up-to-date. Nicolas Andreas Saebjoernsen wrote: > Thanks, I am now working on compiling up VMKit. When

Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. -- John T. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of Lane Schwartz [dowobeha at

Hi, I am attempting to set up a new frontend project based on the sample project (I'm following the instructions at http://llvm.org/docs/Projects.html). In doing so, I hit a problem with AutoRegen.sh which I worked around, and hit a problem with configure that I don't know how to work around. Below is what happens when I attempt to autoconf and configure the sample project that ships

On Fri, Apr 11, 2008 at 3:24 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Lane Schwartz wrote: > > > [snip] > > > > OK then. I didn't realize that having a newer version would be a problem. > > > > I compiled and installed autoconf 2.59. I still get the same problem: > > > > $ autoconf --version > > autoconf (GNU Autoconf)

On Sat, Apr 12, 2008 at 1:26 PM, Lane Schwartz <dowobeha at gmail.com> wrote: > John, > > Thanks for the advice. The script you sent gives me the same problem. > I am now able to work around the issue by making the following change > to the AutoRegen.sh script that comes with the sample project: > > 16,17c16,17 > < llvm_src_root=../../.. > <

On Sat, Apr 12, 2008 at 3:52 PM, Criswell, John T <criswell at ad.uiuc.edu> wrote: > Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. OK. Here are the complete steps required to successfully build the

On Fri, Apr 11, 2008 at 9:39 AM, Lane Schwartz <dowobeha at gmail.com> wrote: > Hi, > > I am attempting to set up a new frontend project based on the sample > project (I'm following the instructions at > http://llvm.org/docs/Projects.html). In doing so, I hit a problem with > AutoRegen.sh which I worked around, and hit a problem with configure > that I don't

On 2/23/07, Reid Spencer <rspencer at reidspencer.com> wrote: > > However, if I run the AutoRegen.sh script (after modifying it to > > accept autoconf 2.61, which I think is fine as gentoo slots it the > > same as the 2.5[0-9] versions), the configure no longer works: > > ~/programming/llvm-1.9/projects/zhe $ cd autoconf/ > >

Reid, Thanks for the help. I am trying out the fixes you checked into CVS. I seem to be getting some errors running AutoRegen.sh. I am a bit inexperienced with autoconf and m4. The errors I'm getting are below. Do you know what the problem is? I am using machines running FC3. The autoconf version is 2.59, the aclocal version is 1.9.2, and the m4 version is 1.4.1.

Hi Ryan, The output from autoconf doesn't look familiar (but then, does it ever?). Note that it thinks that AC_CONFIG_MAKEFILE isn't defined which is likely if you didn't get the LLVM_SRC_ROOT correct. Here's the only things I can think of: 1. You also need to cvs update llvm/autoconf/m4 to get the new definition of LLVM_CONFIG_PROJECT. 2. You typed in the LLVM source root

Reid, Thank you for all your help. I think that I have AutoRegen.sh working now. (I still get the warning about GOB2_HOOK, but I'm assuming that's not a problem.) I'll explain the scenario that led to the problem. I copied the sample project to ~/work/myproject/src/sample. Then I renamed it to ~/work/myproject/src/llvm, indicating that this was the llvm part of my project.

I'm trying to follow docs/Projects.html to use llvm in a project of my own. If I just copy the sample directory, running configure in the new one works fine: ~/programming/llvm-1.9/projects $ cp -a sample/ zhe ~/programming/llvm-1.9/projects $ cd zhe/ ~/programming/llvm-1.9/projects/zhe $ ./configure configure: creating ./config.status config.status: creating Makefile.common config.status:

Ryan, Rather than fix the documentation to match reality, I decided to fix reality to match the documentation. I have just committed (CVS head) changes to the sample project's AutoRegen.sh script that will prompt the user for the path to the LLVM source root and the LLVM object root, if it can't automatically determine the location (because your project is not located in the llvm/projects

Hello Scott, On Wed, 2007-02-21 at 18:57 -0500, me22 wrote: > I'm trying to follow docs/Projects.html to use llvm in a project of my own. > > If I just copy the sample directory, running configure in the new one > works fine: > ~/programming/llvm-1.9/projects $ cp -a sample/ zhe > ~/programming/llvm-1.9/projects $ cd zhe/ > ~/programming/llvm-1.9/projects/zhe $

Thank you for the response. I guess the only thing that is confusing is that the LLVM documentation, at http://llvm.org/docs/Projects.html under the "Create a Project from the Sample Project" heading, indicates that (1) you can place your project *anywhere* you want, and (2) that you are supposed to use the AutoRegen.sh script as is. However, that seems not to be the case. The

> Below is what happens when I attempt to autoconf and configure the > sample project that ships with LLVM. This is on Mac OS X 10.5 with > autoconf 2.6.0. For reference, /opt/src-llvm is where my llvm sources > are, and where I built those sources. My project is in > /opt/src-llvm/projects/sample. > > $ cd /opt/src-llvm/projects/sample > > $ cd autoconf/ > $