similar to: [LLVMdev] Trouble with sample project template (Autoconf problem?)

On Feb 24, 2010, at 11:04 AM, Trevor Harmon wrote: > $ ./AutoRegen.sh > LLVM source root not found. > Enter full path to LLVM source:/Users/twharmon/Development/LLVM/src/ > llvm-trunk/llvm > Enter full path to LLVM objects (empty for same as source):/Users/ > twharmon/Development/LLVM/llvm/ Actually, I think this part is wrong. If I supply the same path as the source,

I'm just getting started with an LLVM-based project, using the Sample template as a guide: http://llvm.org/docs/Projects.html#create But I can't even get the Sample project itself to build without errors. It works fine if I do "configure" and then "make", but if I run "AutoRegen.sh" first, then do "configure", I get: configure: error:

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 )

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 $

This CL is probably apropos to the issue described below.. We here in the PNaCL team are building llvm+clang using a specially bootstrapped version of llvm-gcc. Unfortunately, the configure is picking up system clang even though we force set CC and CXX during the configure process. llvm[2]: Compiling CommandLine.cpp for Release+Asserts build if clang++ -I<LLVMSRC>/include

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:

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

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

FYI, The changes to make libtool appear as mklib have now also been committed. If you want to have support for mklib in your build tree, here's what you do: cd $objdir rm libtool $srcdir/configure --prefix=... --llvmgccdir=... After configure runs, you should have a "mklib" script in your $objdir and the Makefile.rules have been configured to use it. Reid. On Sun, 2004-09-19 at

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

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'm trying to run some of the test suite using the instructions here: > > http://llvm.org/docs/TestingGuide.html#quicktestsuite > > I've built llvm myself, but I'm using pre-built binaries of llvm-gcc > (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). > > Here's what happens: the llvm testsuite (from svn, right?) uses

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)

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

I'm trying to run some of the test suite using the instructions here: http://llvm.org/docs/TestingGuide.html#quicktestsuite I've built llvm myself, but I'm using pre-built binaries of llvm-gcc (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). Here's what happens: foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure

On Jan 3, 2009, at 10:20 AM, Martin Geisse wrote: > > 2. The line > > AutoRegen.sh > > ("Create a Project from the Sample Project", step 5) should be > changed to > > ./AutoRegen.sh > > so it will work if . is not in the path. Fixed. > > > 3. In "Create a Project from the Sample Project", step 6 the > arguments are used to