`port selfupdate; port upgrade outdated' fails

Brandon Allbery allbery.b at gmail.com
Wed Aug 14 07:07:11 PDT 2013


On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
<veedeehjay at googlemail.com>wrote:

> --->  Cleaning apr-util
> Error: arpack: Variant openmpi conflicts with gcc43
> Error: Unable to open port: Error evaluating variants
> To report a bug, follow the instructions in the guide:
>     http://guide.macports.org/#**project.tickets<http://guide.macports.org/#project.tickets>
>
> on a second machine essentially the same happens but a conflict with gcc47
> is stated instead of with gcc43. any ideas?
>

The openmpi variant used to incorrectly allow that, but openmpi is itself a
(wrapper around a) compiler so you must either consistently use it
everywhere or risk odd build issues due to conflicting C++ runtime support
libraries and such. You must determine which compiler to use yourself in
this case; it's not something ports can do for you --- although probably
manually deactivating the non-openmpi compiler via "port upgrade arpack
+openmpi -gcc43" or etc. is probably the "right" choice in many cases.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130814/bb6a2071/attachment.html>


More information about the macports-users mailing list