In the boldface line it refers to an openmpi-2.0.4 installation. It appears
that the 3.0 build is trying to use libraires or includes from the 2.04 install
instead of the 3.0 build. Can you carefully define your PATH and
LD_LIBRARY_PATH (or whatever linux calls it) to prevent the 3.0 build from
Neil,
In csh or tcsh type
make [optons etc] |& tee make.out.
The file make.out will contain the information you are looking for.
Doug
> On Aug 5, 2017, at 2:57 PM, Neil Carlson wrote:
>
> How do I get the build system to echo the commands it is issuing? My
> Fortran compiler is throwing a
Andy,
What allocation scheme are you using on the cluster. For some codes we see
noticeable differences using fillup vs round robin, not 4x though. Fillup is
more shared memory use while round robin uses more infinniband.
Doug
> On Feb 1, 2017, at 3:25 PM, Andy Witzig wrote:
>
> Hi Tom,
>
>
nd the missing
> function ompi_mpi_byte in any of those other libraries. I'll keep looking! I
> wonder if I failed to configure mpich properly when I built it.
> Dick
>
>
> On Tue, Aug 23, 2016 at 4:01 PM, Douglas L Reeder <mailto:d...@centurylink.net>> wrote:
>
Richard,
It looks like you need to add some -l arguments to the the specific openmpi
libraries hat you need (e.g., -lmpi -lmpi_cxx)
Doug
> On Aug 23, 2016, at 1:43 PM, Richard G French wrote:
>
> Hi, all -
> I'm trying to build the SPH code Gadget2
> (http://wwwmpa.mpa-garching.mpg.de/gad
David,
I you use modules to mange your PATH and LD_LIBRARY_PATH and load only the gcc
tht you want when you build openmpi and your applications that sould fix it
going forward.
Doug
> On Feb 10, 2016, at 10:58 AM, David Shrader wrote:
>
> Hello,
>
> Is it possible to use a single build of O
Ken,
Why are the qsub ncpus and mpiirun -np different values.
Doug
On Jun 11, 2015, at 12:08 PM, Leiter, Kenneth W CIV USARMY ARL (US)
wrote:
> Hi Howard,
>
> My qsub command is:
> qsub -l select=10:ncpus=32:mpiprocs=32 -q debug -l walltime=01:00:00 -I
>
> I have also tried using ccm mode wi
David,
You can figure out quite a bit from the output ompi_info.
Doug
On May 5, 2015, at 12:54 PM, David Shrader wrote:
> Hello,
>
> Is there a way to tell what configure line was used in building Open MPI from
> the installation itself? That is, not from config.log but from issuing some
> c
Building as root is a bad idea. Try building it as a regular user, using sudo
make install if necessary.
Doug Reeder
On Mar 28, 2015, at 4:53 PM, LOTFIFAR F. wrote:
> when you said --debug-enable is not activated, I installed it again to make
> sure. I have only one mpi installed on all VMs.
David,
Try “locate mpirun”, or “find / -name mpirun -print.
Doug
On Aug 10, 2014, at 10:45 AM, Yang, David wrote:
> Hi,
>
> I just upgraded my Mac from Mountain Lion to Mavericks. Before upgrading, I
> had Open MPI installed on the Mac, though I don’t quite remember where,
> probably under /
tty cool. Thanks for the heads up.
>
>
> On May 16, 2014, at 6:23 PM, Douglas L Reeder wrote:
>
> > Maxime,
> >
> > I was unaware of Lmod. Thanks for bringing it to my attention.
> >
> > Doug
> > On May 16, 2014, at 4:07 PM, Maxime Boissonne
nd debugged. There are litteraly new features every month or so.
> If it does not do what you want, odds are that the developper will add it
> shortly (I've had it happen).
>
> Maxime
>
> Le 2014-05-16 17:58, Douglas L Reeder a écrit :
>> Ben,
>>
Ben,
You might want to use module (source forge) to manage paths to different mpi
implementations. It is fairly easy to set up and very robust for this type of
problem. You would remove contentious application paths from you standard PATH
and then use module to switch them in and out as needed.
13 matches
Mail list logo
