Re: [Mjpeg-users] libtool: link: cannot find the library `'

2004-03-04 Thread Steven M. Schultz
On Thu, 4 Mar 2004, Maxwell Sayles wrote: > I'm trying to build mjpegtools1.6.2. I managed to build jmpeg-mmx-0.1.5 ... > make[2]: Entering directory `/home/max/tmp/mjpegtools-1.6.2/lavtools' > /bin/sh ../libtool --mode=link gcc -mcpu=i686 -march=i686 -g -O2 -Wall > -Wunused -o lavplay la

Re: [Mjpeg-users] Re: Bug in mp2enc program

2004-03-04 Thread Matto Marjanovic
>On Sat, 2004-02-28 at 14:08, Carlos Sierra wrote: >> I've been using mp2enc from long but in the last release from the debian >> unstable repository it crashes whe the filename specified with -o option is >> too long. ... > >It has always been like that. We reserve MAX_NAME_SIZE (defined

[Mjpeg-users] Re: Bug in mp2enc program

2004-03-04 Thread Ronald S. Bultje
Hi Carlos, On Sat, 2004-02-28 at 14:08, Carlos Sierra wrote: > I've been using mp2enc from long but in the last release from the debian > unstable repository it crashes whe the filename specified with -o option is > too long. > > I tried with C and POSIX locale, but none worked. > Here is an e

[Mjpeg-users] libtool: link: cannot find the library `'

2004-03-04 Thread Maxwell Sayles
I'm trying to build mjpegtools1.6.2. I managed to build jmpeg-mmx-0.1.5 without a hitch, and then libquicktime-0.9.2 again no problem. I unpackage mjpegtools and did a configure with ./configure --with-jpeg-mmx=/home/max/tmp/jpeg-mmx-0.1.5 again, it didn't seem to complain. when i do the mak

Re: [Mjpeg-users] Segmentation Fault

2004-03-04 Thread Bernhard Praschinger
Hallo > mpeg2enc segfaulted on me. Please also check your hardware, after 6 hours. It could be that everything got a little bit war. And that could cause a memory or CPU problem. > So...I suppose I need to build it with debug information and such. > Would someone mind giving me a list of step

[Mjpeg-users] Segmentation Fault

2004-03-04 Thread Ray Cole
mpeg2enc segfaulted on me. First time I've had that happen. It happened about 6 hours into encoding... I want to re-run the script/stream that caused this to happen for the purpose of getting enough information that someone might be able to debug it, but obviously with it taking 6 hours to re