similar to: [LLVMdev] Path to AutoRegen.sh

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

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

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

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:

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) --- > --enable-optimized Compile with optimizations enabled (default is NO) I am wondering to know

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

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

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

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

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 $

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

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

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

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 replying to me. As you recommended, I modified configure.ac in autoconf folder. But I’m not sure about how to regenerate configure. Sorry… I tried to follow the way introduced in README.TXT in the autoconf folder. It asks me to run autoupdate on all the m4 and configure.ac. And then it asks me to regenerate configure script with AutoRegen.sh. However, when I did that, I got an error