Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-30 Thread Terry Dontje 

Ticket 2632 really spells out what the issue is.

On 11/30/2010 10:23 AM, Prentice Bisbal wrote:

Nehemiah Dacres wrote:

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  ?

Yes, that's exactly what I meant. I should have chosen something better
than "-notpath" to say "put a value there that was not '-path'".
I don't think the above will fix the problem because it has to do with 
what how one passes the --rpath option to the linker.  Prior to Studio 
12.2 the --rpath option was passed through to the linker blindly (with a 
warning).  In Studio 12.2 the compiler recognizes -r as a compiler 
option and now "-path" is blindly passed to the linker which has no idea 
what that means.  So one really needs to preface "--rpath" with either 
"-Wl," or "-Qoption ld ".  I don't believe changing the LDFLAGS will 
actually change problem.


--td

Not sure if my suggestion will help, given the bug report below. If
you're really determined, you can always try editing all the makefiles
after configure. Something like this might work:

find . -name Makefile -exec sed -i.bak s/-path/-L/g \{\} \;

Use that at your own risk. You might change instances of the string
'-path' that are actually correct.

Prentice



On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart
>  wrote:

 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 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 override it's value on the configure
 command-line, which is usually easiest/best:

 ./configure LDFLAGS="-notpath ... ... ..."

 --
 Prentice


 Nehemiah Dacres wrote:


 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

 ./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/solstudio12.2/bin/sunf90

compile statement was

 make all install 2>errors


 error below is

 f90: Warning: Option -path passed to ld, if ld is invoked, ignored
 otherwise
 f90: Warning: Option -path passed to ld, if ld is invoked, ignored
 otherwise
 f90: Warning: Option -path passed to ld, if ld is invoked, ignored
 otherwise
 f90: Warning: Option -path passed to ld, if ld is invoked, ignored
 otherwise
 f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
 otherwise
 /usr/bin/ld: unrecognized option '-path'
 /usr/bin/ld: use the --help option for usage information
 make[4]: *** [libmpi_f90.la  
] Error 2
 make[3]: *** [all-recursive] Error 1
 make[2]: *** [all] Error 2
 make[1]: *** [all-recursive] Error 1
 make: *** [all-recursive] Error 1

 am I doing this wrong? are any of those configure flags unnecessary
 or inappropriate



 On Mon, Nov 29, 2010 at 2:06 PM, Gus 
Correa
 >  wrote:

 Nehemiah Dacres wrote:

 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,  it is a fairly homogeneous environment with
 only slight
 variations on the hardware side which could be isolated
 (machinefile flag
 and what-not)
 Please advise


 Hi Nehemiah
 I just answered

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-30 Thread Prentice Bisbal 
Nehemiah Dacres wrote:
> 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 ? 

Yes, that's exactly what I meant. I should have chosen something better
than "-notpath" to say "put a value there that was not '-path'".

Not sure if my suggestion will help, given the bug report below. If
you're really determined, you can always try editing all the makefiles
after configure. Something like this might work:

find . -name Makefile -exec sed -i.bak s/-path/-L/g \{\} \;

Use that at your own risk. You might change instances of the string
'-path' that are actually correct.

Prentice

> 
> 
> On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart
> > wrote:
> 
> 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 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 override it's value on the configure
>> command-line, which is usually easiest/best:
>>
>> ./configure LDFLAGS="-notpath ... ... ..."
>>
>> --
>> Prentice
>>
>>
>> Nehemiah Dacres wrote:
>>   
>>> 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
>>>
>>> ./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/solstudio12.2/bin/sunf90
>>>
>>>compile statement was
>>>
>>> make all install 2>errors
>>>
>>>
>>> error below is
>>>
>>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>>> otherwise
>>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>>> otherwise
>>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>>> otherwise
>>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>>> otherwise
>>> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
>>> otherwise
>>> /usr/bin/ld: unrecognized option '-path'
>>> /usr/bin/ld: use the --help option for usage information
>>> make[4]: *** [libmpi_f90.la  
>>> ] Error 2
>>> make[3]: *** [all-recursive] Error 1
>>> make[2]: *** [all] Error 2
>>> make[1]: *** [all-recursive] Error 1
>>> make: *** [all-recursive] Error 1
>>>
>>> am I doing this wrong? are any of those configure flags unnecessary
>>> or inappropriate
>>>
>>>
>>>
>>> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa >> 
>>> > wrote:
>>>
>>> Nehemiah Dacres wrote:
>>>
>>> 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,  it is a fairly homogeneous environment with
>>> only slight
>>> variations on the hardware side which could be isolated
>>> (machinefile flag
>>> and what-not)
>>> Please advise
>>>
>>>
>>> Hi Nehemiah
>>> I just answered your email to the OpenMPI list.
>>> I want to add that if you build OpenMPI with Torque support,
>>> the machine file for each is not needed, it is provided by 
>>> Torque.
>>> I believe the same is true for SGE (but I don't use SGE).
>>> Gus Correa
>>>
>>>
>>>
>>>
>>> -- 
>>>

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-30 Thread Terry Dontje 
A slight note for the below there should be a space between "ld" and the 
ending single quote mark so it should be '-Qoption ld ' not '-Qoption ld'


--td
On 11/30/2010 06:31 AM, Terry Dontje wrote:
Actually there is a way to modify the configure file that will not 
require the autogen.sh to be ran.
If you go into configure and search for "Sun F" a few lines down will 
be one of three assignments:

lt_prog_compiler_wl
lt_prog_compiler_wl_F77
lt_prog_compiler_wl_FC

If you change them all to '-Qoption ld' and then do the configure 
things should work.


Good luck,

--td

On 11/30/2010 06:19 AM, Terry Dontje wrote:

On 11/29/2010 05:41 PM, Nehemiah Dacres wrote:

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'
  _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '

 unfortunately my autoconf tool is out of date (2.59 , it says it 
wants 2.60+ )


The build page (http://www.open-mpi.org/svn/building.php) show's the 
versions of the tools you need to build OMPI.  Sorry, unfortunately 
in order for this workaround to work you need to re-autogen.sh no way 
around that.


On Mon, Nov 29, 2010 at 4:11 PM, Rolf vandeVaart 
> wrote:


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 the following edits to config/libtool.m4 in all the places
you see it. ( I think just one place)

FROM:

 *Sun\ F*)
   # 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'
   _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
   ;;

TO:

 *Sun\ F*)
   # 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'
   _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
   ;;



Note the difference in the lt_prog_compiler_wl line.

I ran ./configure anyway, but I don't think it did anything
It didn't, the change to libtool.m4 only affects the build system 
when you do an autogen.sh.


--td



Then, you need to run ./autogen.sh.  Then, redo your configure
but you do not need to do anything
with LDFLAGS.  Just use your original flags.  I think this
should work, but I am only reading
what is in the ticket.

Rolf



On 11/29/10 16:26, Nehemiah Dacres wrote:

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 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 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 override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
   

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

 ./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

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-30 Thread Terry Dontje 
Actually there is a way to modify the configure file that will not 
require the autogen.sh to be ran.
If you go into configure and search for "Sun F" a few lines down will be 
one of three assignments:

lt_prog_compiler_wl
lt_prog_compiler_wl_F77
lt_prog_compiler_wl_FC

If you change them all to '-Qoption ld' and then do the configure things 
should work.


Good luck,

--td

On 11/30/2010 06:19 AM, Terry Dontje wrote:

On 11/29/2010 05:41 PM, Nehemiah Dacres wrote:

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'
  _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '

 unfortunately my autoconf tool is out of date (2.59 , it says it 
wants 2.60+ )


The build page (http://www.open-mpi.org/svn/building.php) show's the 
versions of the tools you need to build OMPI.  Sorry, unfortunately in 
order for this workaround to work you need to re-autogen.sh no way 
around that.


On Mon, Nov 29, 2010 at 4:11 PM, Rolf vandeVaart 
> wrote:


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 the following edits to config/libtool.m4 in all the places
you see it. ( I think just one place)

FROM:

 *Sun\ F*)
   # 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'
   _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
   ;;

TO:

 *Sun\ F*)
   # 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'
   _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
   ;;



Note the difference in the lt_prog_compiler_wl line.

I ran ./configure anyway, but I don't think it did anything
It didn't, the change to libtool.m4 only affects the build system when 
you do an autogen.sh.


--td



Then, you need to run ./autogen.sh.  Then, redo your configure
but you do not need to do anything
with LDFLAGS.  Just use your original flags.  I think this should
work, but I am only reading
what is in the ticket.

Rolf



On 11/29/10 16:26, Nehemiah Dacres wrote:

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 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 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 override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
   

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

 ./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/solstudio12.2/bin/sunf90

compile statement was

 make all install 2>errors


 error below is

 f90: Warning: Option -path passed to ld, if ld

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Nehemiah Dacres 
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'
  _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '

 unfortunately my autoconf tool is out of date (2.59 , it says it wants
2.60+ )


On Mon, Nov 29, 2010 at 4:11 PM, Rolf vandeVaart  wrote:

>  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 the following edits to config/libtool.m4 in all the places you see it.
> ( I think just one place)
>
> FROM:
>
> *Sun\ F*)
>   # 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'
>   _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
>   ;;
>
> TO:
>
> *Sun\ F*)
>   # 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'
>   _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
>   ;;
>
>
>
> Note the difference in the lt_prog_compiler_wl line.
>
I ran ./configure anyway, but I don't think it did anything

>
> Then, you need to run ./autogen.sh.  Then, redo your configure but you do
> not need to do anything
> with LDFLAGS.  Just use your original flags.  I think this should work, but
> I am only reading
> what is in the ticket.
>
> Rolf
>
>
>
> On 11/29/10 16:26, Nehemiah Dacres wrote:
>
> 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 <
> rolf.vandeva...@oracle.com> wrote:
>
>> 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 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 override it's value on the configure
>> command-line, which is usually easiest/best:
>>
>> ./configure LDFLAGS="-notpath ... ... ..."
>>
>> --
>> Prentice
>>
>>
>> Nehemiah Dacres wrote:
>>
>>
>>  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
>>
>> ./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/solstudio12.2/bin/sunf90
>>
>>compile statement was
>>
>> make all install 2>errors
>>
>>
>> error below is
>>
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
>> otherwise
>> /usr/bin/ld: unrecognized option '-path'
>> /usr/bin/ld: use the --help option for usage information
>> make[4]: *** [libmpi_f90.la  
>> ] Error 2
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all-recursive] Error 1
>>
>> am I doing this wrong? are any of those configure flags unnecessary
>> or inappropriate
>>
>>
>>
>> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa >  > wrote:
>>
>> Nehemiah Dacres wrote:
>>
>> I want to compile

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Rolf vandeVaart 
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 the following edits to config/libtool.m4 in all the places you see 
it. ( I think just one place)


FROM:

   *Sun\ F*)
 # 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'
 _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
 ;;

TO:

   *Sun\ F*)
 # 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'
 _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
 ;;



Note the difference in the lt_prog_compiler_wl line. 

Then, you need to run ./autogen.sh.  Then, redo your configure but you 
do not need to do anything
with LDFLAGS.  Just use your original flags.  I think this should work, 
but I am only reading

what is in the ticket.

Rolf


On 11/29/10 16:26, Nehemiah Dacres wrote:

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
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 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 override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
  

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

./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/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la  
] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary
or inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa 
> wrote:

Nehemiah Dacres wrote:

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,  it is a fairly homogeneous environment with
only slight
variations on the hardware side which could be isolated
(machinefile flag
and what-not)
Please advise

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Nehemiah Dacres 
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
install to investigate.



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 error message,
indeed, "man ld" doesn't show "-path" as a possible option.
Would this be a "Solaris thing", perhaps an option
to the Solaris linker?

For what it is worth, OpenMPI compiles with gcc,g++ and gfortran,
which may be a workaround for you, if you want to stick to free compilers.
Likewise, it also compiles with Open64 compilers, although later
on I had trouble with the Open64 Fortran compiler (not to compile OpenMPI,
but MPI applications).
Do you have any specific requirement for Sun/Oracle software?

OpenMPI also compiles with Intel and PGI compilers,
but those aren't free.

Finally, make sure you are passing the Sun compilers to the OpenMPI
configure script correctly.
Somehow your warning messages are labeled "f90", not "sunf90" as I
would expect, but this may be just the way Sun decided to spell their
own error messages.

If you are in Rocks, better install the compilers in /share/apps,
not in /opt as it is now.
That will make the Sun compilers and their possible shared libraries
available to all nodes.
/share/apps is the right place to install mostly anything that doesn't
come in the Rocks/CentOS distribution.

Good luck,

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Nehemiah Dacres 
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/solstudio12.2/bin/sunf90
LD_LIBRARY_PATH=/opt/oracle/solstudio12.2/lib/amd64/lib CFLAGS=-m64
CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64
LDFLAGS=-L/opt/oracle/solstudio12.2/lib/amd64/lib)
which may have been redundant but it still didn't work.

the last line before the same error is thus:

libtool: link: /opt/oracle/solstudio12.2/bin/sunf90 -G  .libs/mpi.o
.libs/mpi_sizeof.o .libs/mpi_comm_spawn_multiple_f90.o
.libs/mpi_testall_f90.o .libs/mpi_testsome_f90.o .libs/mpi_waitall_f90.o
.libs/mpi_waitsome_f90.o .libs/mpi_wtick_f90.o .libs/mpi_wtime_f90.o
-rpath /home/dacresni/openmpi/openmpi-1.4.2/ompi/.libs -rpath
/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs -rpath
/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs -rpath
/opt/oracle/solstudio12.2/lib
-L/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs
-L/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs
-L/opt/oracle/solstudio12.2/lib/amd64/lib ../../../ompi/.libs/libmpi.so
/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs/libopen-rte.so
/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs/libopen-pal.so -ldl -lnsl
-lutil -lm  -m64   -mt -soname libmpi_f90.so.0 -o .libs/libmpi_f90.so.0.0.0


which, if I'm not mistaken, specifically what i told it NOT to do.

On Mon, Nov 29, 2010 at 3:26 PM, Nehemiah Dacres  wrote:

> 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 <
> rolf.vandeva...@oracle.com> wrote:
>
>>  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 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 override it's value on the configure
>> command-line, which is usually easiest/best:
>>
>> ./configure LDFLAGS="-notpath ... ... ..."
>>
>> --
>> Prentice
>>
>>
>> Nehemiah Dacres wrote:
>>
>>
>>  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
>>
>> ./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/solstudio12.2/bin/sunf90
>>
>>compile statement was
>>
>> make all install 2>errors
>>
>>
>> error below is
>>
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
>> otherwise
>> /usr/bin/ld: unrecognized option '-path'
>> /usr/bin/ld: use the --help option for usage information
>> make[4]: *** [libmpi_f90.la  
>> ] Error 2
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all-recursive] Error 1
>>
>> am I doing this wrong? are any of those configure flags unnecessary
>> or inappropriate
>>
>>
>>
>> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa >  > wrote:
>>
>> Nehemiah Dacres wrote:
>>
>> 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.
>>

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Gus Correa 

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 error message,
indeed, "man ld" doesn't show "-path" as a possible option.
Would this be a "Solaris thing", perhaps an option
to the Solaris linker?

For what it is worth, OpenMPI compiles with gcc,g++ and gfortran,
which may be a workaround for you, if you want to stick to free compilers.
Likewise, it also compiles with Open64 compilers, although later
on I had trouble with the Open64 Fortran compiler (not to compile 
OpenMPI, but MPI applications).

Do you have any specific requirement for Sun/Oracle software?

OpenMPI also compiles with Intel and PGI compilers,
but those aren't free.

Finally, make sure you are passing the Sun compilers to the OpenMPI
configure script correctly.
Somehow your warning messages are labeled "f90", not "sunf90" as I
would expect, but this may be just the way Sun decided to spell their
own error messages.

If you are in Rocks, better install the compilers in /share/apps,
not in /opt as it is now.
That will make the Sun compilers and their possible shared libraries 
available to all nodes.

/share/apps is the right place to install mostly anything that doesn't
come in the Rocks/CentOS distribution.

Good luck,
Gus Correa


Nehemiah Dacres wrote:

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

./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/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary or
inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  wrote:


Nehemiah Dacres wrote:


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,  it is a fairly homogeneous environment with only slight
variations on the hardware side which could be isolated (machinefile flag
and what-not)
Please advise



Hi Nehemiah
I just answered your email to the OpenMPI list.
I want to add that if you build OpenMPI with Torque support,
the machine file for each is not needed, it is provided by Torque.
I believe the same is true for SGE (but I don't use SGE).
Gus Correa




--
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Nehemiah Dacres 
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 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 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 override it's value on the configure
> command-line, which is usually easiest/best:
>
> ./configure LDFLAGS="-notpath ... ... ..."
>
> --
> Prentice
>
>
> Nehemiah Dacres wrote:
>
>
>  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
>
> ./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/solstudio12.2/bin/sunf90
>
>compile statement was
>
> make all install 2>errors
>
>
> error below is
>
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
> otherwise
> /usr/bin/ld: unrecognized option '-path'
> /usr/bin/ld: use the --help option for usage information
> make[4]: *** [libmpi_f90.la  
> ] Error 2
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
>
> am I doing this wrong? are any of those configure flags unnecessary
> or inappropriate
>
>
>
> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa   > wrote:
>
> Nehemiah Dacres wrote:
>
> 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,  it is a fairly homogeneous environment with
> only slight
> variations on the hardware side which could be isolated
> (machinefile flag
> and what-not)
> Please advise
>
>
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
>
>
>
>
> --
> Nehemiah I. Dacres
> System Administrator
> Advanced Technology Group Saint Louis University
>
>
>
>
> --
> Nehemiah I. Dacres
> System Administrator
> Advanced Technology Group Saint Louis University
>
>
> 
>
> ___
> users mailing 
> listusers@open-mpi.orghttp://www.open-mpi.org/mailman/listinfo.cgi/users
>
>  ___
> users mailing 
> listusers@open-mpi.orghttp://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>



-- 
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Rolf vandeVaart 
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 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 override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
  

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

./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/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la ] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary
or inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa > wrote:

Nehemiah Dacres wrote:

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,  it is a fairly homogeneous environment with
only slight
variations on the hardware side which could be isolated
(machinefile flag
and what-not)
Please advise


Hi Nehemiah
I just answered your email to the OpenMPI list.
I want to add that if you build OpenMPI with Torque support,
the machine file for each is not needed, it is provided by Torque.
I believe the same is true for SGE (but I don't use SGE).
Gus Correa




-- 
Nehemiah I. Dacres
System Administrator 
Advanced Technology Group Saint Louis University





--
Nehemiah I. Dacres
System Administrator 
Advanced Technology Group Saint Louis University





___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users



___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Prentice Bisbal 
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 override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
> 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
> 
> ./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/solstudio12.2/bin/sunf90
> 
>compile statement was
> 
> make all install 2>errors
> 
> 
> error below is
> 
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
> otherwise
> /usr/bin/ld: unrecognized option '-path'
> /usr/bin/ld: use the --help option for usage information
> make[4]: *** [libmpi_f90.la ] Error 2
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
> 
> am I doing this wrong? are any of those configure flags unnecessary
> or inappropriate
> 
> 
> 
> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  > wrote:
> 
> Nehemiah Dacres wrote:
> 
> 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,  it is a fairly homogeneous environment with
> only slight
> variations on the hardware side which could be isolated
> (machinefile flag
> and what-not)
> Please advise
> 
> 
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
> 
> 
> 
> 
> -- 
> Nehemiah I. Dacres
> System Administrator 
> Advanced Technology Group Saint Louis University
> 
> 
> 
> 
> -- 
> Nehemiah I. Dacres
> System Administrator 
> Advanced Technology Group Saint Louis University
> 
> 
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

2010-11-29 Thread Nehemiah Dacres 
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-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/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary or
inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  wrote:

> Nehemiah Dacres wrote:
>
>> 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,  it is a fairly homogeneous environment with only slight
>> variations on the hardware side which could be isolated (machinefile flag
>> and what-not)
>> Please advise
>>
>>
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
>



-- 
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University