Hi all,
> With a mix of Athlon and Intel cpus that might not be wise depending
> on which blend of cpu specific optimizations are used. Might work,
> might not - I'd expect illegal instruction faults and so on but
> not a hard lock that requires "the button". Perhaps using the
> "--disable-simd-accel' would help but that *seriously* slows things
> down. Might be worth trying as a test though to narrow the scope
> of the problem.
Mixing Athlon and post Pentium Intel CPU's should not be a problem. The
builds would be identical and the CPU-dependent routines are selected at
runtime.
However, what may be causing a problem is that some bleeding edge distros seem
to have moved to a new threading library which has more 'normal' Posix
behaviour. At the very least you probably need to build from CVS to get
these to work, at worst I'll need to mess around via ssh on some suitable
machine to figure out what's going wrong...
Andrew
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
