Opened 9 years ago

Closed 9 years ago

#33171 closed defect (invalid)

Conflict with libiconv version between /usr/lib and /opt/local/lib

Reported by: john_brownie@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: bibledit

Description

Trying to get Bibledit to work on the Mac, I've worked through the list of required installs, and it now launches but crashes with a problem with libiconv versions:

Dyld Error Message:
  Library not loaded: /opt/local/lib/libiconv.2.dylib
  Referenced from: /opt/local/lib/libXft.2.dylib
  Reason: Incompatible library version: libXft.2.dylib requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0

Binary Images:
       0x100000000 -        0x100050fff +xterm (??? - ???) <7B56057E-FD31-3EBE-9442-2975829B638C> /opt/X11/*/xterm
       0x100071000 -        0x100081fff +libXft.2.dylib (5.0.0 - compatibility 5.0.0) <FF12B0A4-BCF2-391D-8544-AB14F4FD5EBD> /opt/local/lib/libXft.2.dylib
       0x100087000 -        0x1000ccff7 +libXaw.7.dylib (8.0.0 - compatibility 8.0.0) <ED643DE1-9A33-3F65-A07F-849D536228B0> /opt/X11/*/libXaw.7.dylib
       0x1000e9000 -        0x1000f9ff7 +libICE.6.dylib (10.0.0 - compatibility 10.0.0) <CFC53A59-AE8F-3F51-B542-0B348F78C057> /opt/local/lib/libICE.6.dylib
       0x100102000 -        0x100148fff +libXt.6.dylib (7.0.0 - compatibility 7.0.0) <EA7C79BA-9D45-3DE6-B8B8-C54CF825E195> /opt/local/lib/libXt.6.dylib
       0x100160000 -        0x100278ff7 +libX11.6.dylib (10.0.0 - compatibility 10.0.0) <4A7B6D2C-AC99-34D5-8F3A-57CA68201267> /opt/local/lib/libX11.6.dylib
       0x10029b000 -        0x1002abff7 +libXmu.6.dylib (9.0.0 - compatibility 9.0.0) <95929F56-9394-37C0-8FAA-456A7D7A35DD> /opt/X11/*/libXmu.6.dylib
       0x1002b4000 -        0x1002e3fff +libfontconfig.1.dylib (6.4.0 - compatibility 6.0.0) <BE0A2D69-B64A-3CDD-A76C-D194E8A29B87> /opt/local/lib/libfontconfig.1.dylib
    0x7fff6145d000 -     0x7fff61491baf  dyld (195.6 - ???) <0CD1B35B-A28F-32DA-B72E-452EAD609613> /usr/lib/dyld
    0x7fff8ccff000 -     0x7fff8cd39fff  libncurses.5.4.dylib (5.4.0 - compatibility 5.4.0) <387DE593-9CC5-38C7-911B-A5F2264D34F2> /usr/lib/libncurses.5.4.dylib
    0x7fff91070000 -     0x7fff9109dfe7  libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <7BEBB139-50BB-3112-947A-F4AA168F991C> /usr/lib/libSystem.B.dylib
    0x7fff98262000 -     0x7fff98357fff  libiconv.2.dylib (7.0.0 - compatibility 7.0.0) <5C40E880-0706-378F-B864-3C2BD922D926> /usr/lib/libiconv.2.dylib

To me it says that I'm getting the /usr/lib version of libiconv rather than the version in /opt/local/lib.

Part of getting to this point was to remove the definition of DYLD_LIBRARY_PATH from my .profile, which was apparently inserted when installing MacPorts.

I'm very much of a newbie when it comes to this part of development, so I'm looking for some guidance, but haven't been able to find anything that helps so far.

Change History (3)

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Port: bibledit added; Bibledit removed

DYLD_LIBRARY_PATH was not inserted by MacPorts, but having it set will cause problems, so yes, please unset it.

The error "Incompatible library version: XXX requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0" usually means that the architecture of the two libraries does not match. What are their architectures? What architectures are you wanting to use? Is this an old MacPorts install from an old OS X version? If so, did you follow the Migration instructions?

comment:2 in reply to:  1 Changed 9 years ago by john_brownie@…

Replying to ryandesign@…:

DYLD_LIBRARY_PATH was not inserted by MacPorts, but having it set will cause problems, so yes, please unset it.

The error "Incompatible library version: XXX requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0" usually means that the architecture of the two libraries does not match. What are their architectures? What architectures are you wanting to use? Is this an old MacPorts install from an old OS X version? If so, did you follow the Migration instructions?

OK, I had not realised that I had installed MacPorts in April 2010 and installing it now brought me the problems. Following the migration instructions fixed this particular issue. I now have a different one, but one that is hopefully easier for me to work on. Thanks!

comment:3 Changed 9 years ago by mf2k (Frank Schima)

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.