similar to: [LLVMdev] Question of executing AutoRegen.sh to regen configure file

On Mon, Jan 3, 2011 at 11:01 AM, Eric Christopher <echristo at apple.com> wrote: > On Dec 26, 2010, at 8:38 AM, Lu Mitnick wrote: >> $diff configure configure.bak >> >> 1394c1394 >> <   --enable-optimized      Compile with optimizations enabled (default is YES) >> --- >> >   --enable-optimized      Compile with optimizations enabled (default is

On Dec 26, 2010, at 8:38 AM, Lu Mitnick wrote: > Hello all, > > I download the src of llvm 2.8 and run ./autoconf/AutoRegen.sh > > However there is a little difference between origin configure file and the generated one > > $diff configure configure.bak > > 1394c1394 > < --enable-optimized Compile with optimizations enabled (default is YES) > ---

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

Hello, people I'm developing a small code analysis project with LLVM (I hope I can concentrate on it next semester and make it a really functional tool, but, for now, it's an college end course project, and I'm more focused on theoretical issues than on the implementation). I'm using Ubuntu Linux and had a lot of trouble starting the project by copping the "sample

Hi, I think I have quite an identical patch lying around somewhere here, but I thought that the AutoRegen.sh was something someone wrote here in-house, so I never bothered to send it somewhere. I do remember someone saying (on this list) one should really not use another version of autoconf, but in my experience 2.6 works just as fine for building an addon project (but perhaps not for rebuilding

Good morning, Lu. You may do; 1) build and install certain autotools with --prefix=/path/to/your/autotools 2) run the line; PATH=/path/to/your/autotools/bin:$PATH autoconf/AutoRegen.sh Good luck! ...Takumi

Hi, I'm not sure where I should post this small patch to. The `AutoRegen.sh' script in poolalloc branch (under autoconf directory) is unusable (and seems for a long time) to regenerate `configure'. Probably few use it. But before it's purged, please consider the attached patch. Regards, Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL:

> * I'm using Autoconf 2.61, and it is compatible with the syntax used > by LLVM, but AutoRegen.sh insists I need 2.5x. > > * There is a bug in the AutoRegen.sh that appears when you try to > regenerate configure scripts for your project outside the LLVM > source tree: an shell "read" command missing a parameter. > > The patch was tested on 2.2, but I think

Hi, Matthijs Tanya addressed some of these issues on her response to my patch. You can see there some comments. Thanks about the ubuntu 'dash' issue. Never minded which shell I was using here... it's very like bash from user viewpoint. I think it's another reason to have the variable on the command line. Alexandre Em Qua, 2008-05-07 às 18:26 +0200, Matthijs Kooijman escreveu:

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

Hy, Tanya > Some comments: > - Please follow the developers policy for making patches: > http://llvm.org/docs/DeveloperPolicy.html#patches > OK. My fault here. Will check some of your observations and resubmit. > - I think if we are going to upgrade, we should totally switch to 2.6 > instead of allowing both. This will make diffs easier to read when people > regenerate

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.

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

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

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

It's complaining about the LLVM autoconf/m4 directory which contains the m4 macros that are used in your project's configure.ac. By convention, your project should be in the llvm/projects directory so that you have: 1. llvm/autoconf 2. llvm/projects/yourProj/autoconf The AutoRegen.sh in #2 is looking for #1. By convention that should be located at ../../../autoconf/m4. AC_CONFIG_AUX_DIR

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