Re: [Mjpeg-users] Building from CVS
On Tue, 21 Dec 2004, Ray Cole wrote: > Ugh. I give :-) > I completely erase any sign of autoconf, automake, aclocal, and m4 from my > system. I then installed the following from RedHat 9's distribution: > > autoconf-2.57-3.noarch.rpm > automake-1.6.3-5.noarch.rpm Well, automake 1.6.3 is too old - the minimum version was bumped up to 1.7 a while back. > gtk+-devel-1.2.10-25.i386.rpm > gtk2-devel-2.2.1-4.i386.rpm > m4-1.4.1-11.i386.rpm > SDL-devel-1.2.5-3.i386.rpm > > After all of that I now get: > >configure.ac:71: error: possibly undefined macro: AC_PROG_LIBTOOL Hmmm, that would seem to point at libtool not being installed _or_ to old > I've never had so much trouble getting something to install before. Been > using Linux for 5 or so years now, but this autoconf stuff seems to be But have you re-installed the system during that time? :) RH9 is getting a bit old - automake 1.6.3 for example is going _way_ back... It's the mixing-in/intertwining the older system's stuff with the newer versions that current software needs. I had a similar type of problem when trying to get the gtk/glib 1.2.10 stuff to build on OS/X a year or so ago - the problem then was that autoconf was too _new_ and didn't like the old configure.in and automake stuff that gtk/glib used (the newer gtk2/glib2 was a breeze since it uses newer autoconf files). > really problematic from what I can tell :-) But I have 4 or 5 different OSs (including OS/X, a niche/old BSD variant, FreeBSD, and two or three linux distributions) and have had _none_ of the problems you've encountered - it's not any magic on my part that I can tell, the stuff "just works". Lucky I guess :) > I had tried autoconf-2.53-8 and it seemed to get further than 2.57, but I > received a ton of errors later on and noticed a message saying I needed at > least 2.57, but at least I didn't get this AC_DEFINE message :-) One thing to be mindful of - did you toast/rm any "autom4te.cache" and/or "config.cache" directories/files? Autoconf creates a "cache" of information when it runs - and having an old cache directory or file around _will_ cause grief if you use a different version of autoconf/automake! Gotten bit a few times by that myself - and I think that might have contributed to 'autoreconf -i' not working correctly for you. "autoreconf -i" should work fine - but with all the versions of auto* that have been rotated thru the system I think the 'cache' directory/file may have been causing the problems. Try removing the config.cache or autom4te.cache directory and run ./autogen.sh - should work fine. I see from your followup that you've achieved a degree of success - you're just in time for the daily cvs update festival, lots of work in progress these days :) Cheers, Steven Schultz --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] Building from CVS
Got it. I ran aclocal, autoconf, and automake separately (without using autoreconf) and ended up with a functioning setup. Odd... Anyway, I ran ./configure, then make, and now have a new set of executables to play with that appear to work :-) -- Ray Ray Cole wrote: Ugh. I give :-) I completely erase any sign of autoconf, automake, aclocal, and m4 from my system. I then installed the following from RedHat 9's distribution: autoconf-2.57-3.noarch.rpm automake-1.6.3-5.noarch.rpm gtk+-devel-1.2.10-25.i386.rpm gtk2-devel-2.2.1-4.i386.rpm m4-1.4.1-11.i386.rpm SDL-devel-1.2.5-3.i386.rpm After all of that I now get: configure.ac:71: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:108: error: possibly undefined macro: AC_DEFINE I've never had so much trouble getting something to install before. Been using Linux for 5 or so years now, but this autoconf stuff seems to be really problematic from what I can tell :-) I assume AC_PROG_LIBTOOL is because some other .m4 file (whatever those are) is missing (why can't autoconf tell me something is missing? :-) but the AC_DEFINE seems like it'd be something internal to autoconf so that one really bothers me. I had tried autoconf-2.53-8 and it seemed to get further than 2.57, but I received a ton of errors later on and noticed a message saying I needed at least 2.57, but at least I didn't get this AC_DEFINE message :-) All I'm really wanting to try is the new y4mdenoise stuff. Sigh :-) -- Ray Ray Cole wrote: Well, I think I was in the wrong branch. I now re-fetched the code without specifying a branch. It looks like more modern stuff. Anyway, when I try to run autogen.sh with it I get: configure.ac:107: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. -- Ray --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
Re: [Mjpeg-users] Building from CVS
Ugh. I give :-) I completely erase any sign of autoconf, automake, aclocal, and m4 from my system. I then installed the following from RedHat 9's distribution: autoconf-2.57-3.noarch.rpm automake-1.6.3-5.noarch.rpm gtk+-devel-1.2.10-25.i386.rpm gtk2-devel-2.2.1-4.i386.rpm m4-1.4.1-11.i386.rpm SDL-devel-1.2.5-3.i386.rpm After all of that I now get: configure.ac:71: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:108: error: possibly undefined macro: AC_DEFINE I've never had so much trouble getting something to install before. Been using Linux for 5 or so years now, but this autoconf stuff seems to be really problematic from what I can tell :-) I assume AC_PROG_LIBTOOL is because some other .m4 file (whatever those are) is missing (why can't autoconf tell me something is missing? :-) but the AC_DEFINE seems like it'd be something internal to autoconf so that one really bothers me. I had tried autoconf-2.53-8 and it seemed to get further than 2.57, but I received a ton of errors later on and noticed a message saying I needed at least 2.57, but at least I didn't get this AC_DEFINE message :-) All I'm really wanting to try is the new y4mdenoise stuff. Sigh :-) -- Ray Ray Cole wrote: Well, I think I was in the wrong branch. I now re-fetched the code without specifying a branch. It looks like more modern stuff. Anyway, when I try to run autogen.sh with it I get: configure.ac:107: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. -- Ray --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
