wget & libiconv problem

[facardillo@…]

After upgrading to Yosemite I decide to start with a fresh install of MacPorts. So I removed it using the instructions provided on the MacPorts website. I am having a lot of problems with many ports that used to work, including gcc and, now wget.

So:

• I removed completely MacPorts and all the ports installed;
• I installed MacPorts using the dpkg installer
• I run a selfupdate to sync the ports - you never know

As a first port, I installed wget. Installation was fine, but now when I run it I get:

$-> wget
dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
  Referenced from: /opt/local/bin/wget
  Reason: Incompatible library version: wget requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
Trace/BPT trap: 5

[facardillo@…]

After upgrading to Yosemite I decide to start with a fresh install of MacPorts. So I removed MacPorts and all the ports using the instructions provided on the MacPorts website.

After a first re-installation of MacPorts I had a lot of problems with many ports that used to work, including gcc and, now wget. So, to keep things simple, I decided to start over: I removed MacPorts again and started a second fresh install.

• I removed completely MacPorts and all the ports installed;
• I installed MacPorts using the dpkg installer
• I run a selfupdate to sync the ports - you never know
• As the first port, I chose wget.

Installation was fine, but now when I run it I get:

$-> wget
dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
  Referenced from: /opt/local/bin/wget
  Reason: Incompatible library version: wget requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
Trace/BPT trap: 5

[neverpanic (Clemens Lang)]

You likely have DYLD_LIBRARY_PATH set in your environment. Unset it and wget should start to work fine again. Note that DYLD_LIBRARY_PATH is only meant for developers to test their binaries against new library versions. You should never set it in normal usage, and any binary that doesn't run without it should be considered broken on OS X.

You can re-open if that doesn't fix your problem, but this is very likely not a bug in the wget port. For this reason, I'd recommend you use our MailingLists for technical support.