Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Different CC for orte and opmi?
From: Doug Reeder (dlr_at_[hidden])
Date: 2008-06-09 16:02:56


I am confused. In your first post you said orted fails, with link
errors, when you try to launch a job. From this I inferred that the
build and install steps for creating openmpi were successful. Was the
build/install step successful. If so what dynamic libraries does ldd
say that orted is using.

Doug Reeder
On Jun 9, 2008, at 12:54 PM, Ashley Pittman wrote:

> Putting to side any religious views I might have about static linking
> how would that help in this case? It appears to be orted itself that
> fails to link, I'm assuming that the application would actually run,
> either because the LD_LIBRARY_PATH is set correctly on the front
> end or
> the --prefix option to mpirun.
> Or do you mean static linking of the tools? I could go for that if
> there is a configure option for it.
> Ashley Pittman.
> On Mon, 2008-06-09 at 08:27 -0700, Doug Reeder wrote:
>> Ashley,
>> It could work but I think you would be better off to try and
>> statically link the intel libraries.
>> Doug Reeder
>> On Jun 9, 2008, at 4:34 AM, Ashley Pittman wrote:
>>> Is there a way to use a different compiler for the orte component
>>> and
>>> the shared library component when using openmpi? We are finding
>>> that if
>>> we use icc to compile openmpi then orted fails with link errors
>>> when I
>>> try and launch a job as the intel environment isn't loaded by
>>> default.
>>> We use the module command heavily and have modules for openmpi-
>>> gnu and
>>> openmpi-intel as well as a intel_compiler module. To use openmpi-
>>> intel
>>> we have to load intel_compiler by default on the compute nodes which
>>> isn't ideal, is it possible to compile the orte component with
>>> gcc and
>>> the library component with icc?
>>> Yours,
>>> Ashley Pittman,
>>> _______________________________________________
>>> users mailing list
>>> users_at_[hidden]
>> _______________________________________________
>> users mailing list
>> users_at_[hidden]
> _______________________________________________
> users mailing list
> users_at_[hidden]