Opened 12 years ago
Closed 11 years ago
#38323 closed defect (fixed)
lammpi @7.1.4_0 fails to activate because of conflict with openmpi
Reported by: | dstrubbe (David Strubbe) | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: | lammpi, openmpi |
Description
lammpi fails to activate with openmpi @1.6.4_0+gcc45 installed. I think they should be marked as conflicting, but they are not. I am using OSX 10.8.2 and Xcode 4.6.
Error: org.macports.activate for port lammpi returned: Image error: /opt/local/lib/libmpi.la is being used by the active openmpi port. Please deactivate this port first, or use 'port -f activate lammpi' to force the activation. Please see the log file for port lammpi for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_lammpi/lammpi/main.log
Change History (4)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to mww@… |
---|---|
Port: | openmpi added |
Summary: | lammpi @7.1.4_0 fails to activate → lammpi @7.1.4_0 fails to activate because of conflict with openmpi |
comment:2 follow-up: 3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 12 years ago by seanfarley (Sean Farley)
Replying to ryandesign@…:
The lam homepage recommends lam users migrate to openmpi. Perhaps we should remove the lammpi port or mark it
replaced_by openmpi
.
Sorry for the delay (been conference traveling). I believe I suggested we replace lammpi by openmpi on the mailing list a few weeks ago, so that we could remove it in a year or so. It has been deprecated for quite some time now.
comment:4 Changed 11 years ago by seanfarley (Sean Farley)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The lam homepage recommends lam users migrate to openmpi. Perhaps we should remove the lammpi port or mark it
replaced_by openmpi
.