[MacPorts] #32348: Lion's libcups expects _iconv in libiconv.

[MacPorts]

#32348: Lion's libcups expects _iconv in libiconv.
------------------------------------------------------------+---------------
 Reporter:  k.polezhaiev@…                                  |       Owner:  macports-tickets@…                   
     Type:  request                                         |      Status:  new                                  
 Priority:  Normal                                          |   Milestone:                                       
Component:  ports                                           |     Version:  2.0.3                                
 Keywords:  libcups, CUPS, _iconv, Lion, DYLD_LIBRARY_PATH  |        Port:  libiconv                             
------------------------------------------------------------+---------------

Comment(by ryandesign@…):

 Replying to [ticket:32348 k.polezhaiev@…]:
 > I am trying to build .app bundle of application that uses GStreamer. I
 have Snow Leopard computer with macports installed. I've copied all the
 dependencies of my binary in Content/Resources/lib subdir and made
 launcher that modifies DYLD_LIBRARY_PATH before call of main binary. It
 seems .app works good on my computer. But as soon as I run it on Lion
 computer, application fails to start cause of /usr/lib/libcups expects
 _iconv symbol in my libiconv.2.dylib.

 It sounds like you're trying to do a whole bunch of stuff that MacPorts
 was designed to do (compiling on one OS version and running on another;
 compiling against MacPorts libs and expecting things to work with non-
 MacPorts libs).

 > If I will not ship libiconv.2.dylib, libgio (and may be other libs) will
 try to use Apple's libiconv.2.dylib, which is of version 7.0.0 (but 8.0.0
 is required).

 libiconv library version 8.0.0 is only required because that is the
 version of libiconv in MacPorts which was used when building libgio. If
 libgio had been built against a libiconv with a different library version
 then only that version would be required.

 > Is there possibility to link all the libraries with Apple native
 libiconv instead of macports one,

 MacPorts does not provide the option to link ports with Apple's libiconv,
 no. See wiki:FAQ#syslibs and wiki:FAQ#ownlibs.

 > or to exclude CUPS from dependencies?

 I don't know which port it is that's making use of CUPS here.

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