On Aug 14, 2013, at 09:18, j. van den hoff wrote: > On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery wrote: > >> 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. > > indeed, that did the trick (it went through with the warning > > Warning: Skipping upgrade since openmpi 1.7.2_0 >= openmpi 1.7.2_0, even > though installed variants "+gcc43" do not match "+gcc47". Use 'upgrade > --enforce-variants' to switch to the requested variants. > > which I hope is innocuous?
I'm not sure. What variants of openmpi and arpack are now installed? Determine with: port -v installed arpack openmpi Both ports should be using the same gcc variant. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
