/opt/local/bin/glibtool appears in both libtool and libtool-devel, and they conflict: ---> Activating libtool 1.5.22_0 Error: Activating libtool 1.5.22_0 failed: Image error: /opt/local/bin/glibtool is being used by the active libtool-devel port. Please deactivate this port first, or use the -f flag to force the activation. $ sudo port deactivate libtool-devel Password: ---> Deactivating libtool-devel tna@csx:~/software/transcode/transcode$ sudo port activate libtool ---> Activating libtool Dave
David Liontooth wrote:
/opt/local/bin/glibtool appears in both libtool and libtool-devel, and they conflict:
---> Activating libtool 1.5.22_0 Error: Activating libtool 1.5.22_0 failed: Image error: /opt/local/bin/glibtool is being used by the active libtool-devel port. Please deactivate this port first, or use the -f flag to force the activation.
$ sudo port deactivate libtool-devel Password: ---> Deactivating libtool-devel tna@csx:~/software/transcode/transcode$ sudo port activate libtool ---> Activating libtool Sorry, I see these are simply two different versions of libtool -- I was used to a complementary -devel package.
Dave
On Apr 30, 2007, at 15:15, David Liontooth wrote:
/opt/local/bin/glibtool appears in both libtool and libtool-devel, and they conflict:
---> Activating libtool 1.5.22_0 Error: Activating libtool 1.5.22_0 failed: Image error: /opt/local/bin/glibtool is being used by the active libtool-devel port. Please deactivate this port first, or use the -f flag to force the activation.
$ sudo port deactivate libtool-devel Password: ---> Deactivating libtool-devel tna@csx:~/software/transcode/transcode$ sudo port activate libtool ---> Activating libtool
That's... probably true. I think you can probably only install one or the other.
participants (2)
-
David Liontooth
-
Ryan Schmidt