similar to: [LLVMdev] Easier project support

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

> 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/ > $

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

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

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) 2.59 > > $ cd /opt/src-llvm/projects/sample/autoconf > $ ./AutoRegen.sh > $ cd .. > > $ ./configure

On Fri, Apr 11, 2008 at 12:35 PM, Tanya M. Lattner <tonic at nondot.org> wrote: > > > 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 >

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)

I currently have a slightly modified llvm-2.0 source tree (from the release tarball). I checked out poolalloc into the projects directory and attempt to configure it, but I keep getting errors. I would understand if there were problems building it (since it may require a different version of llvm), but it should at least configure. Specifically, I've tried the following commands: >

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.

Chris, Thanks for your answer Here is the verbose output: =========================== gmake tools-only VERBOSE=1 TOOL_VERBOSE=1 for dir in lib/System lib/Support utils lib tools ; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir//$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all )

On Sunday 30 September 2007, Ben Chambers wrote: > Specifically, I've tried the following commands: > > ./configure --with-llvmsrc=~/Documents/research/llvm/llvm-2.0/ > > --with-llvmobj=~/Documents/research/llvm/llvm-2.0/Release/bin/ > > > > ./configure --with-llvmsrc=~/Documents/research/llvm/llvm-2.0/ > >

Hi These are: ======================== llvm[2]: Linking Release Object Library LLVMbzip2.o gmake[2]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support/bzip2' gmake[1]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support' gmake[1]: Entering directory `/homes/myuser/LLVM/llvmobj/utils' gmake[2]: Entering directory `/homes/myuser/LLVM/llvmobj/utils/Burg' llvm[2]:

I'm forwarding this bug resolution because it has a pretty wide impact on LLVM developers. This bug (451) has been resolved (well, works for me anyway). If you have reconfigured your build tree since October 4th, you need to reconfigure again. The bug produced shared objects that don't have a .so extension. Reconfiguring will fix this problem. The notes below show what was needed to

It seems that this happened before but I do not know the details: http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > llvm[2]: Compiling zalloc.c for Release build > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for

I commented this line and it is compiling now: extern void *malloc ARGS((unsigned)); I hope that will not cause a different kind of problem. What it is zalloc used for? Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > It seems that this happened before but I do not know the details: > >

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

On Mon, Feb 23, 2009 at 6:32 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Aaron Gray wrote: > > I am trying to build llvm-test in a separate directory to the main llvm > tree. > > > > I have put llvm and llvm-gcc's bin directories on the path but think I am > missing a switch on the configure command. > > > You need to use --with-llvmsrc and

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

Yes, sorry for not mentioning it. I added that header also Although I suppose that if I am not using Sparc there will be no problem (it's an Itanium 2 machine) Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > I commented this line and it is compiling now: > > > > extern void *malloc ARGS((unsigned)); > >