On Sun, 16 Nov 2003 [EMAIL PROTECTED] wrote:
> I am having the same problem with malloc failing on my Linux From Scratch
> system.
Very strange. The only thing that comes to mind is that 'M' is
getting corrupted/overwritten somehow and causing mpeg2enc to
request a bogus amount of memory.
What's even stranger is that this is happening with the tarball
that others have used without encountering the malloc problem.
> Today was my first time trying cvs for mjpegtools and to get it to compile
> I had to upgrade autotools 1.6.x-1.7.x. After that it compiled fine but
> when I try mpeg2enc it keeps failing.
Hmmm, I've been using automake 1.7.3 without any trouble but 1.6.x
should have been sufficient to build mjpegtools. In fact 1.5 is
the minimum version (and autogen.sh checks for automake being at
least 1.5) required.
What version of autoconf is being used?
> darkshadow:~/mjpegtools-1.6.1.90$ 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 update your `aclocal.m4' by running aclocal.
> Running aclocal -I ./movtar ...
> aclocal: couldn't open directory `./movtar': No such file or directory
Now that is very puzzling because the tarball should have
contained a 'movtar/' directory.
> Running autoheader...
> Running automake --gnu ...
> configure.in:12: version mismatch. This is Automake 1.7.9,
> configure.in:12: but the definition used by this AM_INIT_AUTOMAKE
> configure.in:12: comes from Automake 1.6.3. You should recreate
> configure.in:12: aclocal.m4 with aclocal and run automake again.
> /usr/local/share/automake-1.7/am/depend2.am: am__fastdepCC does not appear in
> AM_CONDITIONAL
Yep - typical automake/autoconf woes that are a PITA to resolve.
That's familiar but it's been so long since it happened to me I
forget how I fixed it.
After you ran 'aclocal' did you then run automake?
libtoolize --force --copy
aclocal
autoheader
automake --force --add-missing --copy
autoconf
./configure
repeat until it works? :)
> darkshadow:~/mjpegtools-1.6.1.90$ make
No sense in doing that because automake didn't run correctly and
that leaves incorrect/corrupt Makefiles which won't work.
As long as you're going the ./autogen.sh route it might be worth
checking out the cvs version (the tarball is several months old by
now):
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/mjpeg login
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/mjpeg -z9 co mjpeg_play
cd mjpeg_play
cvs logout
./autogen.sh
movtar has been removed, a number of bugs fixed and a new option or
two in mpeg2enc.
Good Luck.
Steven Schultz
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
