Jeff:
Thank you!
Paul
On Apr 21, 2010, at 7:41 AM, Jeff Squyres wrote:
> On Apr 20, 2010, at 7:03 PM, Paul Cizmas wrote:
>
>> Is it possible to have two openmpi-s on the same computer?
>
> Yes. As an OMPI developer, I have dozens of different OMPI installs on my
> cluster (for various sta
On Apr 20, 2010, at 7:03 PM, Paul Cizmas wrote:
> Is it possible to have two openmpi-s on the same computer?
Yes. As an OMPI developer, I have dozens of different OMPI installs on my
cluster (for various stages of development and testing, etc.). The only real
issue is to ensure that you set
Is it possible to have two openmpi-s on the same computer? I have
openmpi 1.3.2 working fine with gfortran but I cannot build openmpi
1.4.1 with Absoft - I get this message from libtool:
/bin/sh ../../../libtool --mode=compile /Applications/Absoft11.0/bin/
f90 -I../../../ompi/include -I..
On Apr 19, 2010, at 12:11 PM, Paul Cizmas wrote:
> Here there was a difference - it did work for both cases:
>
> ~$ ABSOFT=foo
> ~$ testme
> ABSOFT=foo
> ~$ export ABSOFT=foo
> ~$ testme
> ABSOFT=foo
> ~$
This could well be because you had previously exported ABSOFT...? (I forget
the exact se
On Apr 19, 2010, at 8:45 AM, Jeff Squyres wrote:
On Apr 19, 2010, at 9:30 AM, Paul Cizmas wrote:
I do note that the compile command line is:
/bin/sh ../../../libtool --mode=compile /Applications/Absoft11.0/
bin/f90 -I../../../ompi/include -I../../../ompi/include -p. -I. -
I../../../ompi/mp
On Apr 19, 2010, at 8:43 AM, Ricardo Reis wrote:
On Mon, 19 Apr 2010, Paul Cizmas wrote:
The ABSOFT is set and exported. I can double check this by doing
"echo $ABSOFT" and it appears that it is okay.
Is it in the path? Besides being set, I mean...
like
export PATH=$ABSOFT:$PATH
just t
On Apr 19, 2010, at 9:30 AM, Paul Cizmas wrote:
> > I do note that the compile command line is:
> >
> > /bin/sh ../../../libtool --mode=compile /Applications/Absoft11.0/
> > bin/f90 -I../../../ompi/include -I../../../ompi/include -p. -I. -
> > I../../../ompi/mpi/f90 -m64 -lU77 -c -o mpi.lo mpi.
On Mon, 19 Apr 2010, Paul Cizmas wrote:
The ABSOFT is set and exported. I can double check this by doing "echo
$ABSOFT" and it appears that it is okay.
Is it in the path? Besides being set, I mean...
like
export PATH=$ABSOFT:$PATH
just trying to cover all corners...
and maybe
export PATH
The ABSOFT is set and exported. I can double check this by doing
"echo $ABSOFT" and it appears that it is okay.
On Apr 19, 2010, at 7:11 AM, Jeff Squyres wrote:
I have not seen this before; environment variables that are defined
in the shell where you invoked "make" should propagate down to
I have not seen this before; environment variables that are defined in the
shell where you invoked "make" should propagate down to the actual process
where the compilers (etc.) are invoked. Is ABSOFT exported, or just set?
I do note that the compile command line is:
/bin/sh ../../../libtool
Ricardo:
Thank you for your reply. The variable ABSOFT is currently defined in the
.bashrc file. One can check this by doing "echo $ABSOFT" that returns the
location "/Applications/Absoft11.0". However, the makefile (or one of its
depend files) does not know the $ABSOFT value.
Paul
On Apr
On Fri, 16 Apr 2010, Paul Cizmas wrote:
I tried to add in the makefile the following line
ABSOFT = /Applications/Absoft11.0
but this did not help. I wonder if this definition of ABSOFT must be added
to another file. If so, what this file should be?
generally ABSOFT should be an environmen
Hello:
I am trying to install openmpi with Absoft on Mac running OS X
10.5.8. When I do "sudo make all install", the installation ends with
the following message:
Making all in scripts
make[4]: Nothing to be done for `all'.
/bin/sh ../../../libtool --mode=compile /Applications/Absoft11.0
13 matches
Mail list logo
