On Sun, 11 Jan 2004, James Finnall wrote:
> I was working from an article in Linux Journal, Dec 2003. I
> downloaded the mjpegtools and built/installed. Received "malloc
> faliure" from mpeg2enc. Searching the archive list turned up a
> thread in regard to a bug in glibc 2.2.5. That I believe I am
Yep - and 2.2.4 was even worse believe it or not.
2.2.5 is a bit old (current's 2.3.2 or 2.3.3 I believe) so I'm surprised
so many folks are encountering the problem.
> The thread went on to discuss updating autoconf, automake, and
> libtool. So I have also done that as well. But it still reports
libtool-1.5 is required, but autoconf 2.5x should be adequate.
I forget if automake 1.7.x is required or not - but having it won't
hurt anything (I use 1.7.6 on one system and 1.7.9 on others). But
come to think of it.
What versions did you install/upgrade to?
> ./configure: line 1440: syntax error near unexpected token
> `AM_INIT_AUTOMAKE(mjpegtools,'
> ./configure: line 1440: `AM_INIT_AUTOMAKE(mjpegtools,
> $MJPEG_VERSION)'
That says that ./autogen.sh's creation of the ./configure
script was not correct - no sense going proceeding further.
> There are also numerous warnings and other errors reported from
> automake prior to this. But it dosen't stop the process. I can
Those might be useful.
> post all of the output but it is probably about a hundred lines.
> But the error above stops the configuration part. The beginning of
*any* error is bad in this case - indicates something is not
setup or installed quite right.
> bash-2.05a# ./autogen.sh
> **Warning**: I am going to run `configure' with no arguments.
> If you wish to pass any to it, please specify them on the
> `./autogen.sh' command line.
>
> processing .
> Running libtoolize...
> You should add the contents of `/usr/local/share/aclocal/libtool.m4'
> to `aclocal.m4'.
> Running aclocal ...
> aclocal: configure.in: 174: macro `AM_PATH_GLIB' not found in
> library
> aclocal: configure.in: 368: macro `AM_PATH_GTK' not found in library
> aclocal: configure.in: 380: macro `AM_PATH_SDL' not found in library
Hmmm, the GLIB error I can understand - the use of that in
configure.in is unconditional. The GTK and SDL errors are a bit
of a puzzle because those are checked for inside 'ifdef' calls.
If you do have the libglib, libgtk and the SDL installed then
their .m4 files are not being found. This can be caused by
installing automake/autoconf into /usr/local/{share,bin,...} but
the various installed packages have their .m4 files in /usr/{share,lib,
bin,...}. Thus the glib.m4 file might be in /usr/lib/aclocal/glib.m4
but the newly installed autoconf/automake only look in /usr/local/*
One way to work around that problem (if that is part of what is
causing the errors you're seeing) is to copy the files from the
system's directory into the new version's directory - something like
this:
cp /usr/share/aclocal/*.m4 /usr/local/share/aclocal
Dumb question - but are you sure you're running the newly installed
versions? If the system had autoconf/automake/libtool installed
and /usr/local/bin is not first in your path you could still be
running the old versions...
This is what it should look like:
moe.1-> ./autogen.sh
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.
processing .
Running libtoolize...
Running aclocal ...
Running autoheader...
Running automake --gnu ...
Running autoconf ...
Running ./configure --enable-maintainer-mode --enable-compile-warnings ...
checking build system type... i386-pc-bsdi4.3.1
...
> I was not able to locate the file aclocal.m4 in the top directory,
That's because it is generated during the ./autogen.sh run - if that
fails then aclocal.m4 won't have been created.
> so I copied the libtool.m4 there instead, and it removed that
> beginning message, but the missing macro messages remained.
That is not necessary - autogen.sh will do that too.
I'd make certain that libglib is installed and that glib.m4 is in
a place that autoconf/automake can find it. Then double check that
the new autoconf/automake/libtool are actually being used by putting
/usr/local/bin first in $PATH.
Good Luck!
Steven Schultz
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
