Hi Shiqing,
I must have missed your response among all the e-mails that get sent to
the mailing list. Here are a little more details about the issues that I
am having. My client/server programs seem to run sometimes, but then
after a successful run I always seem to get the error that I include
Jeff Squyres wrote:
Please note that this is an English-speaking list.
I don't know if Tim speaks ?Spanish?,
Portuguese.
but I unfortunately don't. :-)
Also note that I asked for some specific information,
but you ignored it when you replied. Please see the following web page:
htt
thanks.
FYI: its openmpi-1.4.2 from a tarball like you assume
I changed this line
*Sun\ F* | *Sun*Fortran*)
# Sun Fortran 8.3 passes all unrecognized flags to the linker
_LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
_LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
With the increasing gap between network bandwidth and processor computing
power, the current trend in linear algebra is toward communication avoiding
algorithms (aka. replacing communications with redundant computations). You're
taking the exact opposite path, I wonder if you can get any benefit
We're in process of analyzing this issue. I'll keep you updated.
george.
On Nov 13, 2010, at 08:40 , Nicolai Stange wrote:
> Hi everybody,
>
> gcc 4.5.1 with -O2 optimizes the 'ret = newval' away because %0 is
> declared as being write only.
> Fix is attached.
>
> Regards
>
> Nicolai
> <02
Please note that this is an English-speaking list. I don't know if Tim speaks
?Spanish?, but I unfortunately don't. :-)
Also note that I asked for some specific information, but you ignored it when
you replied. Please see the following web page:
http://www.open-mpi.org/community/help/
You can use the tcp_if_include/tcp_if_exclude with address ranges instead of
names. ompi_info --mca btl tcp give you some hints:
> MCA btl: parameter "btl_tcp_if_include" (current value:
> , data
> source: default value)
> Comm
No, I do not believe so. First, I assume you are trying to build either
1.4 or 1.5, not the trunk.
Secondly, I assume you are building from a tarfile that you have
downloaded. Assuming these
two things are true, then (as stated in the bug report), prior to
running configure, you want to
make t
senhor Tim Prince,
Gostaria de agradecer o email que me enviou sobre openmpi, na verdade,
estou tentando compilar o Regcm 4, e quando uso o comando, make regcm,
aparece um erro "mpif90" por isso fui em busca da solução do problema do
openmpi,utilizo um computador de plataforma 64 bits com sistema
I believe the user specifically wishes to use the special debugging tools in
Solaris Studio. The flag in question seems to be -rpath according to the
logs, It would be suspicious if this was a flag for the Solaris linker. I
don't have access to any solaris machines but I may try make a virtual
ins
I put the ld flag on the command line ( ./configure
--prefix=/state/partition1/apps/sunmpi/ --enable-mpi-threads --with-sge
--enable-static --enable-sparse-groups
CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/s
On Nov 24, 2010, at 4:55 PM, Hicham Mouline wrote:
> The tree is not symmetrical in that the valid values for the 10th parameter
> depends on the values selected in the 0th to 9th parameter (all the ancestry
> in the tree), for e.g., we may have a lot of nodes in the left of the tree
> than in the
Hi Nehemiah
Hard to tell, I never tried Sun/Oracle Studio compilers.
However, the Intel compilers, for instance, require you to setup
environment variables that include PATH and LD_LIBRARY_PATH at least.
Would this be the case with Sun Studio?
Do you have its full environment set?
As for the err
that looks about right. So the suggestion:
./configure LDFLAGS="-notpath ... ... ..."
-notpath should be replaced by whatever the proper flag should be, in
my case -L ?
On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart wrote:
> This problem looks a lot like a thread from earlier today. Can y
On Nov 29, 2010, at 2:29 PM, Hicham Mouline wrote:
> If the GUI's on windows, and the compute processes are on linux for
> instance, no MPI communication is possible right.
> That means, I do need to write custom code to communicate between the GUI
> process (win) and the mpi master (linux)
With
On Nov 24, 2010, at 4:41 PM, Hicham Mouline wrote:
>> Sadly true. There has been (very) little demand for this, so we
>> haven't spent much (any) time on making it work.
>
> Is it the same for MacOSX? can't mix MacOsX and linux?
> Can't mix Win and MacOSX?
The issue is mainly Windows, I believe
On Nov 23, 2010, at 8:34 AM, Hicham Mouline wrote:
>> MPI doesn't necessarily mean SPMD -- you can certainly have the GUI call
>> MPI_INIT and then call MPI_COMM_SPAWN to launch a different >executable to
>> do the compute working stuff.
>
> This is confusing to me.
> If the GUI does that, wil
This problem looks a lot like a thread from earlier today. Can you look
at this
ticket and see if it helps? It has a workaround documented in it.
https://svn.open-mpi.org/trac/ompi/ticket/2632
Rolf
On 11/29/10 16:13, Prentice Bisbal wrote:
No, it looks like ld is being called with the optio
No, it looks like ld is being called with the option -path, and your
linker doesn't use that switch. Grep you Makefile(s) for the string
"-path". It's probably in a statement defining LDFLAGS somewhere.
When you find it, replace it with the equivalent switch for your
compiler. You may be able to o
it may have been that I didn't set ld_library_path
On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres wrote:
> thank you, you have been doubly helpful, but I am having linking errors and
> I do not know what the solaris studio compiler's preferred linker is. The
>
> the configure statement was
>
thank you, you have been doubly helpful, but I am having linking errors and
I do not know what the solaris studio compiler's preferred linker is. The
the configure statement was
./configure --prefix=/state/partition1/apps/sunmpi/ --enable-mpi-threads
--with-sge --enable-static --enable-sparse-gro
Hi Nehemiah
I never tried to build OpenMPI with SunStudio, but it should work.
(I did with Gnu, Intel, PGI and Open64, the latter still has Fortran90
problems.)
For starters, I would just try the recipe in the OpenMPI FAQ:
http://www.open-mpi.org/faq/?category=building#build-compilers
replacin
On 11/29/2010 11:31 AM, Gus Correa wrote:
Hi Mauricio
Check if you have icc (in the Intel compiler bin
directory/subdirectories).
Check also if it is in your PATH environment variable.
"which icc" will tell.
If not, add it to PATH.
Actually, the right way to do it
is to run the Intel scripts
I want to compile openmpi to work with the solaris studio express or
solaris studio. This is a different version than is installed on
rockscluster 5.2 and would like to know if there any gotchas or configure
flags I should use to get it working or portable to nodes on the cluster.
Software-wise,
Hi Mauricio
Check if you have icc (in the Intel compiler bin directory/subdirectories).
Check also if it is in your PATH environment variable.
"which icc" will tell.
If not, add it to PATH.
Actually, the right way to do it
is to run the Intel scripts to set the whole compiler environment,
not o
>> therefore, I guess I need to separate the GUI binary from the
mpi-processes
>> binary and have the GUI process talk to the "master" mpi process (on
linux)
>> for calc requests.
>>
>> I was hoping I wouldn't have to write a custom code to do that.
>MPI doesn't necessarily mean SPMD -- you ca
I would guess that the problem is that your path and ld_library_path aren't
correctly pointing to the Intel compiler. Try ensuring they are and then
rebuild.
On Nov 29, 2010, at 11:07 AM, Maurício Rodrigues wrote:
> I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to
> s
Hi all,
I'm noticing a strange problem with Open MPI 1.4.2 on Mac OS X 10.6. We
use both Intel Ifort 11.1 and gfortran 4.3 on the same machine and
switch between them to test and debug code.
I had runtime problems when I compiled openmpi in my usual way of no
shared libraries so I switched t
On Nov 29, 2010, at 11:46 AM, George Wm Turner wrote:
> Is there a rough, order of magnitude timeline for v1.5.2? I have a user
> wanting to do some serious testing on the Lustre filesystem and he's
> wondering what options he should consider.
Definitely not before January. I'd estimate the F
Gilbert Grosdidier wrote:
I found this parameter mpool_sm_max_size in this post:
http://www.open-mpi.org/community/lists/devel/2008/11/4883.php
But I was unable to spot it back into the 'ompi_info -all'
output for v 1.4.3.
Is it still existing ?
No.
If not, which
I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to
solve this problem.
I would like to help if possible.
Thank you from the alreadyá
2010/11/29 Jeff Squyres
> That's a lot of exclamation points. :-)
>
> It looks like the Intel compiler executable (icc) is simply not found
I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to
solve this problem.
I would like to help if possible.
Thank you from the already
Em 29 de novembro de 2010 16:06, Maurício Rodrigues <
mauriciopaulorodrig...@gmail.com> escreveu:
> usando o Intel® C++ Composer XE 2011 for
usando o Intel® C++ Composer XE 2011 for Linux, nao tenho nenhuma idéia de
como resolver este problema.
gostaria de ajuda se possivel.
obrigado desde de já
2010/11/29 Ralph Castain
> Are you using the Intel compiler? The build system is looking for an "icc"
> command and not finding it. Perhap
Are you using the Intel compiler? The build system is looking for an "icc"
command and not finding it. Perhaps something in your environment is defining
CC to be "icc"?
On Nov 29, 2010, at 10:43 AM, Maurício Rodrigues wrote:
> HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving
That's a lot of exclamation points. :-)
It looks like the Intel compiler executable (icc) is simply not found.
However, I'm surprised you got so far in the build process before that error
occurs -- that doesn't seem right.
Please send all the information listed here:
http://www.open-mpi.
icc is the Intel C/C++ compiler. Do you have it installed on your system?
Damien
On 29/11/2010 10:43 AM, Maurício Rodrigues wrote:
HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving
this error all the time ... I would like to help.
below follows the lines of the error.
Thank
HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this
error all the time ... I would like to help.
below follows the lines of the error.
Thank you!
/home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not
found
libtool: install: error: relink `libopen-rte.la'
Is there a rough, order of magnitude timeline for v1.5.2? I have a user
wanting to do some serious testing on the Lustre filesystem and he's wondering
what options he should consider.
Thanks,
george wm turner
high performance systems
812 855 5156
On Nov 29, 2010, at 11:01 AM, Jeff Squyres w
Hi,
Has anyone observed similar behaviour? Is it something that I'll have to
deal with it in my code or does it indeed qualify as an issue to be
looked into?
Thanks
Yiannis Papadopoulos wrote:
It is a quad core machine (Intel Core2 Quad CPU Q9550 - 64bit).
OpenMPI is the one that comes with
On Mon, 29 Nov 2010, Jeff Squyres wrote:
There's work going on right now to update the ROMIO in the OMPI v1.5
series. We hope to include it in v1.5.2.
Cheers Jeff :)
Mark
--
-
Mark Dixon Email: m.c.di..
There's work going on right now to update the ROMIO in the OMPI v1.5 series.
We hope to include it in v1.5.2.
On Nov 29, 2010, at 10:34 AM, Mark Dixon wrote:
> Hi,
>
> I notice that there's been quite a bit of work recently on ROMIO's Lustre
> driver. As far as I can see from openmpi's SVN,
Bonjour John,
Thanks for your feedback, but my investigations so far did not help:
the memlock limit on the compute nodes are actually set to unlimited.
This most probably means that even if the btl_openib hits some memory
allocation
limit, the message I got is inaccurate because the memlock re
Bonjour,
I found this parameter mpool_sm_max_size in this post:
http://www.open-mpi.org/community/lists/devel/2008/11/4883.php
But I was unable to spot it back into the 'ompi_info -all' output for
v 1.4.3.
Is it still existing ?
If not, which other one is replacing it, please ?
Also, is
I just replied on your previous thread -- sorry for the delay.
On Nov 29, 2010, at 8:27 AM, Tushar Andriyas wrote:
> and the openmpi-1.2.7-pgi??
>
> On Mon, Nov 29, 2010 at 6:27 AM, Tushar Andriyas
> wrote:
> Hi there,
> The thing is I did not write the code myself and am just trying to get i
Sorry for the delay in replying; many of us were at SC10 and then most of us
were off for the US Thanksgiving holiday last week.
This error means that your application called MPI_ABORT -- meaning that your
application intentionally chose to quit. You might need to look through the
source code
Hi,
I notice that there's been quite a bit of work recently on ROMIO's Lustre
driver. As far as I can see from openmpi's SVN, this doesn't seem to have
landed there yet (README indicates V04, yet V05 is in MPICH2 and
MVAPICH2).
Is there a timescale for when this will be make it into a releas
This is ticket 2632 https://svn.open-mpi.org/trac/ompi/ticket/2632. A
fix has been put into the trunk last week. We should be able to CMR
this fix to the 1.5 and 1.4 branches later this week.The ticket
actually has a workaround for 1.5 branch.
--td
On 11/29/2010 09:46 AM, Siegmar Gross w
Hi,
in the meantime we have installed gcc-4.5.1 and now I get a different error,
when I try to build OpenMPI-1.5 with Oracle Studio 12 Update 2 on Linux.
linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 121 head -18 config.log
...
$ ../openmpi-1.5/configure --prefix=/usr/local/openmpi-1.5_32_cc
and the openmpi-1.2.7-pgi??
On Mon, Nov 29, 2010 at 6:27 AM, Tushar Andriyas wrote:
> Hi there,
> The thing is I did not write the code myself and am just trying to get it
> to work. So, would it help if i change the version of the compiler or is
> that it happens with every pgi compiler suite??
Hi there,
The thing is I did not write the code myself and am just trying to get it to
work. So, would it help if i change the version of the compiler or is that
it happens with every pgi compiler suite??
On Sun, Nov 28, 2010 at 11:45 PM, Simon Hammond wrote:
> Hi,
>
> This isn't usually an error
Hi,
This isn't usually an error - you get this by using conventional
Fortran exit methods. The Fortran stop means the program hit the exit
statements in the code. I have only had this with PGI.
--
Si Hammond
Research F
51 matches
Mail list logo
