On Fri, 7 Nov 2003, Richard Ellis wrote:
> It's my own machine, I don't limit myself :)
I do - mainly as a safety measure to keep a runaway program from
completely trashing the machine.
> > Having multiple versions of mjpegtools on a system might cause the
> > problem due to the libraries that get installed into
> > /usr/local/lib. When building the new version I wonder if it's
> Yes, that can cause weird problems, but as far as I can tell,
> mpeg2enc cvs version is linking with it's intended lib:
> ldd mpeg2enc.cvs.2003.11.04
> libmpeg2encpp-1.6.so.0 =>
> /mnt/maxtor/rellis/video/mjpt-1.6.1.90/lib/libmpeg2encpp-1.6.so.0 (0x40015000)
>
> Yes, the locations are non-standard. libmpeg2encpp-1.6 is only
> created and used by the cvs mpeg2enc, I had to freshly move it over
> when I made the first cvs version a couple days ago. I've moved it
> plus mpeg2enc over for each new compile I've made. The released
> mpeg2enc does not link to it, and I think it's part of Andrew's
> restructuring of the code.
Correct. At the moment only mpeg2enc links against the
shared library.
There are static (.a) libraries though tha are created and
installed and those are the ones I had in mind.
What's supposed to happen is that locally built versions
(in the source tree) are used when building a new version but
I have seen cases where previously installed versions would
be used.
I'm not convinced that's the problem in this case but it's
about the only thing left that i can think of.
I'm stumped (for now).
Steven Schultz
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
