> Hmmm, cpfind works here with "--ncores 4" on my 64-bit Athlon II x4,
> running Linux. Maybe threading problem is more specific to Windows?
Yes, I haven't seen this problem reported on Linux, but as the
problems Greg and Harry refer to are not on Linux or Windows, it may
still be a worthwhile avenue of investigation on freeBSD and OSX...at
least to be able to rule it out.
> Anyway, Linux version prior to what I have now automatically used all
> available cores without me specifying the number to use. Version I
> currently have (from Debian Sid) required me to specify the number of
> cores, or it used only a single core.
I just ran a test on a build of the current source (on Fedora 17
x86_64) and it automatically uses available cores.
Cheers,
Terry
--
You received this message because you are subscribed to the Google Groups
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
