[MacPorts] #29543: hugin-app built as 32bit binary
MacPorts
noreply at macports.org
Sun May 22 06:17:07 PDT 2011
#29543: hugin-app built as 32bit binary
-----------------------------+----------------------------------------------
Reporter: thimo@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: hugin-app
-----------------------------+----------------------------------------------
I've run "port install hugin-app" on my Snow Leopard machine and got the
following message:
{{{
---> Computing dependencies for hugin-app
---> Building hugin-app
Error: Target org.macports.build returned: shell command failed (see log
for details)
Log for hugin-app is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
.org_release_ports_graphics_hugin-app/main.log
Error: Status 1 encountered during processing.
}}}
The error inside the log is:
{{{
:info:build ld: in /opt/local/lib/libxml2.2.dylib, file was built for
unsupported file format which is not the architecture being linked (i386)
for architecture i386
:info:build collect2: ld returned 1 exit status
:info:build make[2]: *** [src/hugin_base/libhuginbase.0.0.dylib] Error 1
:info:build make[1]: *** [src/hugin_base/CMakeFiles/huginbase.dir/all]
Error 2
:info:build make: *** [all] Error 2
:info:build shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_ports_graphics_hugin-app/work/hugin-2010.4.0" &&
/usr/bin/make all " returned error 2
}}}
The library file is
{{{
mymac /Users/thimo% file /opt/local/lib/libxml2.2.dylib
/opt/local/lib/libxml2.2.dylib: Mach-O 64-bit dynamically linked shared
library x86_64
}}}
and to my suprise the log shows that "-arch i386" is passed during the
compilation.
My guess is that either hugin-app needs to depend on libxml2+universal
(such that the 32bit version is always available) or cmake without
+universal (to build in 64bit mode). As the usecase for hugin is to work
on huge pictures I'd definitely prefer the latter.
--
Ticket URL: <https://trac.macports.org/ticket/29543>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list