Hi Justin (and possibly others), 2011/3/21 Justin Kern <[email protected]>
> Progress so far - running enblend from 2010.4.0 or any of the newer > releases crashes and the program runs in 32-bit. Updating to 10.5.8 did not > help (although needed to happen regardless :)) This seems to be because the > most recent version of enblend, packaged with Hugin 2010.4.0 or later only > has three architectures: > > justins-g5:~ Admin$ file > /Applications/Hugin_2010_4_0/Hugin.app/Contents/MacOS/enblend > /Applications/Hugin_2010_4_0/Hugin.app/Contents/MacOS/enblend: Mach-O > universal binary with 3 architectures > /Applications/Hugin_2010_4_0/Hugin.app/Contents/MacOS/enblend (for > architecture i386): Mach-O executable i386 > /Applications/Hugin_2010_4_0/Hugin.app/Contents/MacOS/enblend (for > architecture ppc7400): Mach-O executable ppc > /Applications/Hugin_2010_4_0/Hugin.app/Contents/MacOS/enblend (for > architecture x86_64): Mach-O 64-bit executable x86_64 > > I should note this is the same enblend-enfuse-4.0 as that available from > sourceforge as: > > justins-g5:enblend Admin$ file enblend-openmp > enblend-openmp: Mach-O universal binary with 3 architectures > enblend-openmp (for architecture ppc7400): Mach-O executable ppc > enblend-openmp (for architecture i386): Mach-O executable i386 > enblend-openmp (for architecture x86_64): Mach-O 64-bit executable > x86_64 > > No, that's not correct even if it seems so. The SourceForge ones are Ingemar Bergmans binaries. When enblend-enfuse 4.0 was released, Ingemar beat me in building these. Another difference is that Ingemar's binaries are static binaries as they need to be able to "stand alone". The enblend binaries inside Hugin are dynamically linked binaries against libraries inside the bundle. You will notice the size difference. > I appear not to have done all my homework: > > http://groups.google.com/group/hugin-ptx/browse_thread/thread/8920ba21b15f10fd?fwc=1&pli=1 > > Basically, the last build supporting 64-bit enblend in Hugin for PPC was > some time ago and no longer is hosted on Harry's site. Downloaded 2010.0.0 > from sourceforge and giving it a shot as well. In the meantime, for any who > are interested, I was able to find an old version of 3.1 that Harry had > compiled which has four architectures supported: > > justins-g5:fuse_tools_64bit Admin$ file enblend > enblend: Mach-O universal binary with 4 architectures > enblend (for architecture ppc750): Mach-O executable ppc > enblend (for architecture i386): Mach-O executable i386 > enblend (for architecture ppc64): Mach-O 64-bit executable ppc64 > enblend (for architecture x86_64): Mach-O 64-bit executable x86_64 > > Although, according to some older posts I was reading, this appears not to > fix the memory leak, this does seem to give it enough space to leak wherever > it wants to so long as it finishes the panorama. This gave me a 3.5 GB > uncompressed TIF as an output. Although not compatible with openmp - this > will at least let me stitch on this machine! Please forget about the old 3.1 version. I dusted off my hard disk and found some "old" 64bit NON-opennmp builds of enblend/enfuse 4.0. You will find a zip with enblend and enfuse 4.0 for x86_64/ppc64. They are stand-alone versions. Look at the bottom of the page on my website. As always: Information and binaries via my website <http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>. (The binaries themselves are served from hugin.panotools.org who kindly provide the disk space and bandwidth). Hoi, Harry -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
