similar to: [LLVMdev] Compiling poolalloc

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

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 >

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

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

A following question about how to install "poolalloc". I checked out poolalloc from svn. But I had a problem of installing it. When I tried to run "configure" with options "--with-llvmsrc" and "--with--llvmobj" pointing to where the source of my llvm and objs dir are (/home/usr/Tools/llvm, e.g.), "configure" complained error message

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

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

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

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

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)

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]:

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

Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > Did you link the shared libraries? (step 2). > > Also, can you send me your configure option? > > NicolasOn Wed, Jul 20, 2011 at 3:45 PM, Sarah <sarah.berenji <at> gmail.com> wrote: > Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > > >

Thank you, I tried to compile it with llvm 3.4 through these commands: petsas at shinigami:~/software/poolalloc$ ./configure --with-llvmsrc=/home/petsas/software/llvm --with-llvmobj=/home/petsas/software/llvm petsas at shinigami:~/software/poolalloc$ make but I'm getting get this error: make[1]: Entering directory `/home/petsas/software/poolalloc/lib' make[2]: Entering directory

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 )

Hi Sarah, On Sun, Jul 24, 2011 at 6:28 AM, Sarah <sarah.berenji at gmail.com> wrote: > > I created links in "/usr/local/classpath/lib" where my classpath objects > are > installed. Since it didn't work I tried these paths too: in classpath's > source > "/usr/local/classpath-0.97.2/lib" & also in "/lib"!! The error didn't >

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: > >

I have noticed that I was installing LLVM according to: http://llvm.org/docs/GettingStarted.html#getting-started so it was no the 3.1 but the 3.2 version from svn (trunk 167573). Maybe in the svn, not stable version, there is a bug? 2012/11/9 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > Does anybody have Idea why I get such error? The LLVM is compiled from > source - is is the