similar to: [LLVMdev] Trouble with sample project's autoconf

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

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 $

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, I am just starting a new project. I found that the above script rejects Autoconf versions later than 2.59, whereas it ought to accept them, imho. I had to edit the scrip to be able to use it with Autoconf 2.61. Also, aclocal gave the following warning: /usr/share/aclocal/oaf.m4:4: warning: underquoted definition of AM_PATH_OAF /usr/share/aclocal/oaf.m4:4: run info '(automake)Extending

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.

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

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

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

I'm attempting to build some PECL modules on fully updated CentOS 4.2 system. Preferably pack them into nice RPM packages. However, seems I'm missing something. For example, this is what I get for sqlite module: $ pear makerpm SQLite-1.0.3.tgz `phpize' failed The php-devel package is installed (so I do have phpize command). It's just that it is failing. If I unpack the

I am converting a Debian box running Postfix, Courier and MySQL to a CentOS box running Postfix, Dovecot and MySQL. I have the Postfix with MySQL support taken care of with the RPM from the centosplus repo. It appears that the stock RPM for Dovecot comes with Postgres, but not MySQL support. It looks like I need to download the source RPM and then rebuild it with MySQL support. Could

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :

Hi, autoreconf -i -f which is called by autogen.sh gives these errors with git 31c9f0582260817777348c96a3576e5955f44ab3: rm at eurasia:~/swfdec/swfdec$ autoreconf -i -f /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of AM_PATH_LIBMCRYPT run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending%20aclocal

Hello all, I am a beginner of LLVM and want to add a new Target for LLVM. I follow the document (http://llvm.org/docs/WritingAnLLVMBackend.html) to modify autotools/configure.ac. However when I type ./AutoRegen.sh There is an error that "Your autoconf was not detected as being 2.60" I download the source of autoconf 2.60 and install it. And there is the other error that "Your

After downloading libogg-1.1.tar.gz, libvorbis-1.0.1.tar.gz, and libtheora-1.0alpha3.tar.gz; building and installing them in that order, and trying the alpha3 theora encoder, I decided to try to build theora from svn. Using svn to checkout theoratrunk worked ok. The first time I tried to execute ./autogen.sh, it complained that I didn't have automake. Mandrake 10.0 comes with automake