similar to: [LLVMdev] Re: IMPORTANT: autoconf changes

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

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

Defaults to disabled --- .gitignore | 2 + acinclude.m4 | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.ac | 4 +++ shave-libtool.in | 69 +++++++++++++++++++++++++++++++++++++++++++++++ shave.in | 79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 231 insertions(+), 0 deletions(-) create mode 100644 acinclude.m4

Hi. I want to add some code to flac and am having trouble building it out of cvs. I've had several problems, most of which were pretty easy to work around or had already been discussed here. But this one has me stumped (though I am admittedly new to autoconf, automake, and libtool). Here's the problem. autoconf does not see any definition for AC_PROG_LIBTOOL. There is such a

I don't know if this is the right solution, but you can use -I with aclocal to point right at .m4 files: aclocal -I <libtool directory>/share/aclocal --- Brady Patterson <brady@spaceship.com> wrote: > > Hi. > > I want to add some code to flac and am having trouble building it out > of cvs. > I've had several problems, most of which were pretty easy to work

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

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

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:

i ran into the same issue yesterday. i had to revert back to 1.6 here is the link to the exact file that helped me ftp://ftp.gnu.org/gnu/automake/automake-1.6.tar.gz then tar -zxf automake-1.6.tar.gz; cd automake-1.6l; ./configure; make; make install <p><p>Dave St John CEO Mediacast1 www.mediacast1.com ----- Original Message ----- From: "Tano M Fotang"

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

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

>> Patch attached. >> >> This patch with header installation patch ( >> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html ) >> let external project (I am test it at my YAFL frontend for LLVM) build >> using installed LLVM version instead using LLVM obj/src dirs. > > I think the patch looks basically sane. The one wierd thing I notice

Hello All: I just checked out the whole icecast but cannot build anything because autogen wouldn't cooperate. I have automake-1.7.6 just installed from ftp.gnu.org. Below is an example output in trying to build "icecast"; it's not very short... Thanks in advance for any help. --- $~/icecast/icecast> ./autogen.sh Checking for automake version found automake found

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.

Vladimir, I took a *very quick* look at your patch. I won't be able to look at it in more detail until this weekend, but perhaps you can address a couple of concerns: 1. I don't understand the need for LLVMToolDirSlash. This seems like a gratuitous change to me. 2. I don't think the change to CPP.Flags is right. It won't find the LLVM header files 3. Removing the

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.

On Jun 19, 2017, at 4:02 AM, Manuel Wolfshant wrote: > On 06/18/2017 05:42 PM, Charles Lepple wrote: >> On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant wrote: >>> >>> running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: >>> + autoreconf -i

[this time compeled the mail]. The autogen.sh of opusfile doesn't work for me: Updating build configuration files for opusfile, please wait.... configure.ac:8: installing `./install-sh' configure.ac:8: installing `./missing' Makefile.am:10: Libtool library used but `LIBTOOL' is undefined Makefile.am:10: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'

On Sat, May 19, 2001 at 12:19:39PM +0000, Christian Weisgerber wrote: > Christian Weisgerber <naddy@mips.inka.de> wrote: > > > Problems in FLAC 0.9: > > Also: > > ===> Building for flac-0.9 > cd . && aclocal > aclocal: configure.in: 7: macro `AM_PROG_LIBTOOL' not found in library > aclocal: configure.in: 22: macro `AM_PATH_XMMS' not