> When I was switching between lam and ompi, something similar happened to me > and I also had to resort to update-alternatives. IIRC I used --auto but I > didn't write that down. > > Now, having gotten here, would you agree that is not a bug in the Open MPI > packages but rather than some fragility in update-alternatives? Is it ok if > we close this?
Sure, close it. Open MPI seems to be fine. I also managed to build petsc thanks to this. Now I am going to try to fix libmesh and petsc4py. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
