Hi again,
I have attached a very small example which raise the assertion.
The problem is arising from a process which does not have any element to
write in the file (and then in the MPI_File_set_view)...
You can see this "bug" with openmpi 1.6.3, 1.6.4 and 1.7.0 configured with:
./configure
On Apr 5, 2013, at 12:33 AM, Siegmar Gross
wrote:
> Hi
>
> today I tried to install openmpi-1.9r28290 and got the following errors.
>
> Solaris 10, Sparc, Sun C 5.12, 32-bit version of openmpi
> Solaris 10, x86_64, Sun C 5.12, 32-bit version of openmpi
> Solaris 10, Sparc, Sun C 5.12, 64-bit
Hi all,
I have a well working (large) code which is using openmpi 1.6.3 (see
config.log here:
http://www.giref.ulaval.ca/~ericc/bug_openmpi/config.log_nodebug)
(I have used it for reading with MPI I/O with success over 1500 procs
with very large files)
However, when I use openmpi compiled
I believe with 99%prob this is not an Open MPI issue, but an issue of the used
fortran compiler (PPFC) itself.
You can verify this by going to the build subdir ('Entering directory...') and
trying to find out _what command was called_. If your compiler crashes again,
build a reproducer and sen
Hi
today I tried to install openmpi-1.7 and got the following error
on my Linux system.
openSuSE Linux 12.1, x86_64, Sun C 5.12, 32-bit version of openmpi
--
linpc1 openmpi-1.7-Linux.x86_64.32_cc 103 tail log.make.Linux.x86_64.32_
You can get the headers installed by adding --with-devel-headers to the
configure line.
On Apr 5, 2013, at 5:10 AM, chandan basu wrote:
> Hi,
>
> I want to use OpenMPI dynamic collective algorithm selection using rules
> file, e.g.
>
> mpirun --mca coll_tuned_use_dynamic_rules 1
> --mca_col
Hi,
I want to use OpenMPI dynamic collective algorithm selection using rules
file, e.g.
mpirun --mca coll_tuned_use_dynamic_rules 1
--mca_coll_tuned_dynamic_rules_file rules.txt ./myexe
I can see some examples in earlier discussions (given below). My question
is how do I know the ID for the diff
It looks like you configured with gfortran 4.7.2
(/nm/programs/third_party/gcc-4.7.2-rhel5/bin/gfortran).
Did you change your path after that, such that a different gfortran was
found/used to build Open MPI?
I ask because real*16 (etc.) were all found and used successfully in configure,
but
AFAICS problem is in the middle of (it's often not directly at the end):
Am 05.04.2013 um 03:21 schrieb Alan Sayre:
>
configure:17615: g++ -o conftest -O3 -DNDEBUG -finline-functions conftest.cpp
>&5
In file included from /usr/include/stdio.h:929:0,
from conftest.cpp:141:
/
Hi
today I tried to install openmpi-1.9r28290 and got the following errors.
Solaris 10, Sparc, Sun C 5.12, 32-bit version of openmpi
Solaris 10, x86_64, Sun C 5.12, 32-bit version of openmpi
Solaris 10, Sparc, Sun C 5.12, 64-bit version of openmpi
Solaris 10, x86_64, Sun C 5.12, 64-bit version of
10 matches
Mail list logo