ice-cpp conflicts with xorg-libice

[stromnov (Andrey Stromnov)]

--->  Installing ice-cpp @3.3.0_3
--->  Activating ice-cpp @3.3.0_3
Error: Target org.macports.activate returned: Image error:
/opt/local/lib/libIce.dylib is being used by the active xorg-libice port.
Please deactivate this port first, or use the -f flag to force the activation.

[blb@…]

Looks like other OS's deal with this more easily since this installs libIce whereas X11 uses libICE...

[blair (Blair Zajac)]

[Adding the xorg-libice port maintiner to the cc].

Do you have a suggested fix for this?

At first glance, I don't have any intentions of changing the shared library name, esepcially given that Mac OS X provides a libICE.dylib in /usr/X11R6/lib.

[jeremyhu (Jeremy Huddleston Sequoia)]

case insensitivity FTL.

X11 dependencies are going to be transitioning over to port: based rather than lib: based and Macports provided X11 libs are going to be used by default. There is really no feasible way of changing libICE to be named different. That would lead to massive breakage.

[mvfranz@…]

what OS is this? Tiger? Panther?

[blair (Blair Zajac)]

Consider putting the X11 libs into a subdirectory, as they are on Mac OS X in /usr/X11R6/lib.

[blair (Blair Zajac)]

This is fixed in the latest ice-cpp, ice-python and ice-python26 ports. I also updated Ice to 3.3.1.

A number of commits went in, from r49193 to r49203, but the changes particular to this bug were fixed in r49193, r49195, r49200, r49203.

[(none)]

Milestone Port Bugs deleted