similar to: [LLVMdev] Note: auto* tools updated

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

I'm forwarding this bug resolution because it has a pretty wide impact on LLVM developers. This bug (451) has been resolved (well, works for me anyway). If you have reconfigured your build tree since October 4th, you need to reconfigure again. The bug produced shared objects that don't have a .so extension. Reconfiguring will fix this problem. The notes below show what was needed to

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 $

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 want to compile and install FLAC 1.1.4 from source code and I have run this like explained in the README: ./configure && make && make install I have left out the "make check". Everything builds OK and is installed. But then when I want to run "flac", I get this error: $ flac flac: error while loading shared libraries: libFLAC.so.8: cannot open shared

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, building OPENSSH v4.3p2 on OSX 10.4.7, all's fine (config, nake, install, exec) out-of-the-box. so, to be clear, this is NOT a blocker, by any stretch ... that said, however ... if, instead of a don't-monkey-with-it build, prior to ./configure, i: autoreconf -i -f then, a subsequent: ./configure \ --prefix=/usr/local/openssh \

On Fri, 2006-11-17 at 17:19 -0800, Tanya M. Lattner wrote: > On Fri, 17 Nov 2006, Seung Jae Lee wrote: > > > 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

On Fri, 17 Nov 2006, Seung Jae Lee wrote: > 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

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

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

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.

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

Hello Timo, On FreeBSD 6.1-STABLE, rc7 doesn't build (rc6 didn't either) because of a broken "sed" in the genarated "libtool" script, at least with the "zsh" shell comming from the ports (zsh-4.3.2). This has occured starting from your move from Autoconf 2.59 to Autoconf 2.60 since for some reason, now "libtool" is run by zsh (instead of sh as in

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.

so, this is my problem, very weird. i have both cedega and wine for some win32 executables(games and software). i can't execute none of win32 exe's cause my system locks up :roll: , so i have to reset my computer :x . if you have any idea pls tell me. thx! my emerge info: Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r1 i686)

On 21/06/2012, Douglas Gregor <dgregor at apple.com> wrote: > > On Jun 20, 2012, at 5:13 PM, Nick Lewycky <nlewycky at google.com> wrote: > >> Is there anybody who is certain that our autoconf dependency needs to stay >> around? Are there developers stuck on systems that don't have a recent >> enough cmake in their most recent release, or maybe are using

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

The autoreconf tool is provided by autoconf to do what custom autogen.sh scripts in many projects used to do. Only it is more robust and widely tested. It has been available for several years, too. No reason to rely on custom code for this. Signed-off-by: Max Horn <max at quendi.de> --- Makefile.am | 2 - autogen.sh | 168