Comment 19 for bug 814280

Revision history for this message
hvdwolf (hvdwolf) wrote :

>2. no enblend found!?!?!?
>
>EMRimac:~ ernstmichaelreicher$ /Applications/Hugin.app/Contents/MacOS/enblend -v --version
>-bash: /Applications/Hugin.app/Contents/MacOS/enblend: No such file or directory
>

Sorry. I forgot you are on an older version. The path should be as below:

/Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/enblend

>Good news--the tiger version version of enblend runs without any problems on Lion.
>I tried it on three different sets of pics, and at the command line several times without errors.
>
>Fusing works too (using the standard enfuse in RC3).

This confirms what I was already afraid of. It means that the openmp setup has been changed from (Snow)Leopard to Lion. That's the reason why the normal enblend crashes and the "old" Tiger enblend functions OK. The only "issue" in using the "old" Tiger enblend is that it doesn't make use of multiple cores when available. In a dual-core machine it will improve performance by 10-15%. On a quad-core machine it will improve performance by about 30-40%. Note that this is only the enblend step.

At least we have a work-around now.
enfuse is not an openmp binary. That's why ity simply functions.