Re: [Mjpeg-developer] about that new configure stuff

[Steven M. S. <sms@2BSD.COM>]

Howdy Ronald -

On Sun, 29 Aug 2004, Ronald Bultje wrote:

> starting to re-set up my CVS trees locally now that I'm back from the

	Welcome back!

> And I noticed that the new configure stuff doesn't work on my brand shiny 
> new Fedora Core 2 box. Fixing it isn't hard, but I'm trying to understand 
> what's up here so others don't
> need to go down this path as well.

	Hmmm, I set up a Fedora Core3 Test1 system a week or two ago and
	didn't run into any of:

> if /bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
> -I../.. -I../.. -I../../utils    -march=pentium3 -mno-sse2
> -mcpu=pentium3 -g -O2 -pthread -Wall -Wunused -MT build_sub44_mests.lo
> -MD -MP -MF ".deps/build_sub44_mests.Tpo" -c -o build_sub44_mests.lo
> build_sub44_mests.c; \
> then mv -f ".deps/build_sub44_mests.Tpo" ".deps/build_sub44_mests.Plo";
> else rm -f ".deps/build_sub44_mests.Tpo"; exit 1; fi
> ../../libtool: ../../libtool: No such file or directory
> make[3]: *** [build_sub44_mests.lo] Error 1

> So, there's no libtool. Other CVS trees do have libtool in the
> $(top_srcdir).

	That would seem to indicate that the libtoolize part of the auto*
	process didn't get run.

	Are  you sure you did an initial:

	   autoreconf -f -i

> I swapped AC_PROG_LIBTOOL with AM_PROG_LIBTOOL and re-ran autogen.sh
> (wasn't someone going to remove that?), and it works now. I also ran

	Eventually that was the plan.  At the moment it gives a warning
	message but will continue on.  If you think it's time to complete
	the change then I can reduce autogen.sh to the one liner 
	"autoreconf -f  -i"

> that didn't solve it, so I suppose the macro is the problem. What's up
> here? Is this a typo? A new macro that older versions of autoconf don't
> have yet? Something else?

	Don't know what to say.  FC3-test1 worked fine (well, as far as 
	mjpegtools is concerned at least ;)).

	I think the first time you run the autoreconf it's necessary to
	add the "-f" but that's all I can think of.  

	I'm fairly sure FC2 comes with current enough versions of autoconf,
	automake and libtool so I doubt that is the problem.

	Cheers,
	Steven Schultz