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<path> ?
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<path>/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
<rolf.vandeva...@oracle.com<mailto: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<dacre...@slu.edu<mailto:dacre...@slu.edu>
<mailto:dacre...@slu.edu>> 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<http://libmpi_f90.la>
<http://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<g...@ldeo.columbia.edu<mailto:g...@ldeo.columbia.edu>
<mailto:g...@ldeo.columbia.edu>> 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<mailto:us...@open-mpi.org>
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
us...@open-mpi.org<mailto:us...@open-mpi.org>
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
us...@open-mpi.org<mailto:us...@open-mpi.org>
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
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
--
Oracle
Terry D. Dontje | Principal Software Engineer
Developer Tools Engineering | +1.781.442.2631
Oracle *- Performance Technologies*
95 Network Drive, Burlington, MA 01803
Email terry.don...@oracle.com <mailto:terry.don...@oracle.com>
