[MacPorts] #29142: libintl and libiconv versions not compatible

MacPorts noreply at macports.org
Fri Apr 15 06:41:38 PDT 2011


#29142: libintl and libiconv versions not compatible
---------------------------------------+------------------------------------
 Reporter:  stephane.jacobs@…          |       Owner:  macports-tickets@…                   
     Type:  defect                     |      Status:  new                                  
 Priority:  Normal                     |   Milestone:                                       
Component:  ports                      |     Version:  1.9.2                                
 Keywords:                             |        Port:  gettext libiconv                     
---------------------------------------+------------------------------------

Comment(by stephane.jacobs@…):

 Replying to [comment:3 jmr@…]:

 Thanks for your response!

 >>I'm trying to run an open source software
 >Which software? Another port installed with MacPorts? or something you've
 built by hand?

 It's a package of tcl scripts for data analysis
 (http://www.fmrib.ox.ac.uk/fsl/fsl/list.html), not installed with
 MacPorts.
 As far as I understand, the (characters in the) scripts are not
 interpreted correctly because of the libraries issue, and thus won't
 run...


 >>dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
 >>Referenced from: /opt/local/lib/libintl.8.dylib
 >>Reason: Incompatible library version: libintl.8.dylib requires version
 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
 >The usual cause of this error that the iconv library built by MacPorts
 (library version 8) is built for the wrong architecture, thus it tries to
 fall back to the iconv library provided by Mac OS X (library version 7).
 The usual reason for this >architecture mismatch is upgrading to Snow
 Leopard without following Migration instructions. But you're on Leopard,
 and you've demonstrated that the libraries are built for the right
 architecture -- at least, the libraries installed by MacPorts. >Is it
 possible there is another iconv library that's built for the wrong
 architecture, perhaps in /usr/local/lib, /usr/lib or /sw/lib?

 /usr/local/lib contains the same version for the same architecture:
 {{{
 otool -L /usr/local/lib/libiconv.2.dylib
 /usr/local/lib/libiconv.2.dylib:
         /usr/local/lib/libiconv.2.dylib (compatibility version 8.0.0,
 current version 8.0.0)
         /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
 version 1.0.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 111.1.5)
 lipo -info /usr/local/lib/libiconv.2.dylib
 Non-fat file: /usr/local/lib/libiconv.2.dylib is architecture: i386
 }}}

 The problem seems to be in /usr/lib: wrong version, wrong architecture!
 :-)
 {{{
 otool -L /usr/lib/libiconv.2.dylib
 /usr/lib/libiconv.2.dylib:
         /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current
 version 7.0.0)
         /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
 version 1.0.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 111.1.1)
 lipo -info /usr/lib/libiconv.2.dylib
 Architectures in the fat file: /usr/lib/libiconv.2.dylib are: ppc7400
 ppc64 i386 x86_64
 }}}

 Nothing in /sw/lib.


 Now, I'm not sure how to update the iconv library in /usr/lib, or why the
 intl library is looking there but reports problems regading the library in
 /usr/opt/lib (which on top of it is fine)???

-- 
Ticket URL: <https://trac.macports.org/ticket/29142#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list