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 ? Ye

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

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

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 '-

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

2010-11-30 Thread Terry Dontje
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_

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'

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 t

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 ins

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

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 err

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 y

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 optio

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 o

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

2010-11-29 Thread Nehemiah Dacres
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 >

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-gro