[MacPorts] #22493: Incompatible library version
MacPorts
noreply at macports.org
Thu Nov 12 20:49:31 PST 2009
#22493: Incompatible library version
-------------------------------------------+--------------------------------
Reporter: vash_the__typhoon@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.1
Keywords: | Port: libiconv
-------------------------------------------+--------------------------------
Comment(by ryandesign@…):
Replying to [comment:4 vash_the__typhoon@…]:
> I've tried adding [[BR]]
> [[BR]]
> http_proxy="http://<user>:<pass>@<my-proxy>:<proxy-port>/" [[BR]]
> export http_proxy [[BR]]
> HTTP_PROXY="http://<user>:<pass>@<my-proxy>:<proxy-port>/" [[BR]]
> export HTTP_PROXY [[BR]]
> [[BR]]
> to my ~/.profile but it still didn't work ... So I don't know what else
to do ?
Hmm, looks like our [wiki:howto/Proxy how-to entry on this topic] hasn't
been written yet. You should set the proxy options in
/opt/local/etc/macports/macports.conf. MacPorts clears environment
variables before running, so anything you set in ~/.profile will have no
effect, by design.
> >'''port''' set to ''libiconv'' [[BR]]
> [[BR]]
> Sorry I don't know what you mean by this?[[BR]]
Joshua was setting the "port" field in this ticket to the value
"libiconv". However, it sounds to me like there may be something more
general amiss in your MacPorts install. Hopefully we'll soon be able to
identify what.
> I really don't know why I have (or need) half of the ports that I have
installed, I think most of them came down as dependencies on the ones I
actually wanted so I ''guess'' I need them???
You can try to "sudo port uninstall" ports you don't think you need; if
you need them, MacPorts will tell you and prevent the uninstall. You can
also install and use the port-cutleaves port; port-cutleaves is an
interactive program that helps you identify and uninstall ports that have
no dependencies. If a port it lists is one you don't directly need, you
can let it be uninstalled.
> The reason I installed coreutils was so I could get the GNU '''ls'''
rather than the OSX '''ls''' so I can colour code the terminal.
Deactivating coreutils did fix all the other programs so thank-you [[BR]]
> ...but I don't have my '''gls''' anymore .. which I would really like
back. I tried to install the '''coreutils''' without the
'''+with_default_names'''
That would be the solution...
> but it fails to install as[[BR]]
> [snip] [[BR]]
> dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib [[BR]]
> Referenced from: /opt/local/lib/libintl.8.dylib [[BR]]
> Reason: Incompatible library version: libintl.8.dylib requires version
8.0.0 or later, but libiconv.2.dylib provides version 7.0.0 [[BR]]
> [snip] [[BR]]
> It still can't find a proper version of libiconv.2.dylib
So here, it's not the parts of coreutils, but the internationalization
library libintl (which is part of gettext) which can't find the libiconv
it wants.
> Is there some way I can force Macports to install the correct version of
libiconv.2.dylb ?
Let's first try to find out whether it's libiconv that's installed
incorrectly, or everything that's trying to use it. What is the
architecture of libiconv.dylib and libintl.dylib? To find out:
{{{
lipo -info /opt/local/lib/{libiconv,libintl}.dylib
}}}
With what variants are the gettext and libiconv ports now installed? To
find out:
{{{
port installed gettext libiconv
}}}
What computer is this? What are the values of build_arch and
universal_archs in /opt/local/etc/macports/macports.conf? What's in
/opt/local/etc/macports/variants.conf?
--
Ticket URL: <http://trac.macports.org/ticket/22493#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list