date:20100530

[OMPI users] Configuring with torque: error and patch

2010-05-30 Thread John Cary


Upon configuring and building openmpi on a system with
torque, I repeatedly got build errors of the sort,

/bin/sh ../../../libtool --tag=CXX   --mode=link g++  -O3 -DNDEBUG 
-finline-functions -pthread   -o ompi_info components.o ompi_info.o 
output.o param.o version.o ../../../ompi/libmpi.la -lnsl -lutil  -lm
libtool: link: g++ -O3 -DNDEBUG -finline-functions -pthread -o 
.libs/ompi_info components.o ompi_info.o output.o param.o version.o  
../../../ompi/.libs/libmpi.so -L/usr/local/torque-2.4.0b1/lib 
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so 
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/opal/.libs/libopen-pal.so 
-ldl -lnsl -lutil -lm -pthread -Wl,-rpath 
-Wl,/usr/local/contrib/openmpi-1.4.2-nodl/lib
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so: 
undefined reference to `tm_spawn'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so: 
undefined reference to `tm_poll'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so: 
undefined reference to `tm_finalize'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so: 
undefined reference to `tm_init'

collect2: ld returned 1 exit status

which I fixed by adding one or the other of

$(ORTE_WRAPPER_EXTRA_LDFLAGS) $(ORTE_WRAPPER_EXTRA_LIBS)

$(OMPI_WRAPPER_EXTRA_LDFLAGS) $(OMPI_WRAPPER_EXTRA_LIBS)

to various LDADD variables.  I doubt that this is consistent
with how your build system is designed, but it works for me.
I am sending you the diff in case it helps you in any way.
BTW, I also fixed some blanks after backslashes in
contrib/Makefile.am.  This is also in the attached patch.

BestJohn Cary
diff -ruN ./contrib/Makefile.am ../openmpi-1.4.2.new/contrib/Makefile.am
--- ./contrib/Makefile.am   2010-04-13 11:30:27.0 -0600
+++ ../openmpi-1.4.2.new/contrib/Makefile.am2010-05-30 08:39:58.0 
-0600
@@ -100,9 +100,9 @@
 platform/win32/ConfigFiles/mpif77-wrapper-data.txt.cmake \
 platform/win32/ConfigFiles/opal_config.h.cmake \
 platform/win32/ConfigFiles/revision.in \
-platform/ibm/debug-ppc32-gcc \ 
-platform/ibm/debug-ppc64-gcc \ 
-platform/ibm/optimized-ppc32-gcc \ 
-platform/ibm/optimized-ppc64-gcc 
+platform/ibm/debug-ppc32-gcc \
+platform/ibm/debug-ppc64-gcc \
+platform/ibm/optimized-ppc32-gcc \
+platform/ibm/optimized-ppc64-gcc

 dist_pkgdata_DATA = openmpi-valgrind.supp
diff -ruN ./contrib/Makefile.in ../openmpi-1.4.2.new/contrib/Makefile.in
--- ./contrib/Makefile.in   2010-05-04 10:06:10.0 -0600
+++ ../openmpi-1.4.2.new/contrib/Makefile.in2010-05-30 08:40:31.0 
-0600
@@ -743,6 +743,7 @@
 PACKAGE_NAME = @PACKAGE_NAME@
 PACKAGE_STRING = @PACKAGE_STRING@
 PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_URL = @PACKAGE_URL@
 PACKAGE_VERSION = @PACKAGE_VERSION@
 PATH_SEPARATOR = @PATH_SEPARATOR@
 PERL = @PERL@
@@ -1003,7 +1004,7 @@
 platform/ibm/debug-ppc32-gcc \
 platform/ibm/debug-ppc64-gcc \
 platform/ibm/optimized-ppc32-gcc \
-platform/ibm/optimized-ppc64-gcc 
+platform/ibm/optimized-ppc64-gcc

 dist_pkgdata_DATA = openmpi-valgrind.supp
 all: all-am
diff -ruN ./ompi/tools/ompi_info/Makefile.am 
../openmpi-1.4.2.new/ompi/tools/ompi_info/Makefile.am
--- ./ompi/tools/ompi_info/Makefile.am  2009-12-08 13:36:19.0 -0700
+++ ../openmpi-1.4.2.new/ompi/tools/ompi_info/Makefile.am   2010-05-30 
08:58:40.0 -0600
@@ -66,7 +66,7 @@
 output.cc \
 param.cc \
 version.cc 
-ompi_info_LDADD = $(top_builddir)/ompi/libmpi.la
+ompi_info_LDADD = $(top_builddir)/ompi/libmpi.la $(OMPI_WRAPPER_EXTRA_LDFLAGS) 
$(OMPI_WRAPPER_EXTRA_LIBS)

 clean-local:
test -z "$(OMPI_CXX_TEMPLATE_REPOSITORY)" || $(RM) -rf 
$(OMPI_CXX_TEMPLATE_REPOSITORY)
diff -ruN ./ompi/tools/ompi_info/Makefile.in 
../openmpi-1.4.2.new/ompi/tools/ompi_info/Makefile.in
--- ./ompi/tools/ompi_info/Makefile.in  2010-05-04 10:06:50.0 -0600
+++ ../openmpi-1.4.2.new/ompi/tools/ompi_info/Makefile.in   2010-05-30 
08:59:17.0 -0600
@@ -254,7 +254,9 @@
 am_ompi_info_OBJECTS = components.$(OBJEXT) ompi_info.$(OBJEXT) \
output.$(OBJEXT) param.$(OBJEXT) version.$(OBJEXT)
 ompi_info_OBJECTS = $(am_ompi_info_OBJECTS)
-ompi_info_DEPENDENCIES = $(top_builddir)/ompi/libmpi.la
+am__DEPENDENCIES_1 =
+ompi_info_DEPENDENCIES = $(top_builddir)/ompi/libmpi.la \
+   $(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1)
 DEFAULT_INCLUDES = -I.@am__isrc@ -I$(top_builddir)/opal/include 
-I$(top_builddir)/orte/include -I$(top_builddir)/ompi/include 
-I$(top_builddir)/opal/mca/paffinity/linux/plpa/src/libplpa
 depcomp = $(SHELL) $(top_srcdir)/config/depcomp
 am__depfiles_maybe = depfiles
@@ -785,6 +787,7 @@
 PACKAGE_NAME = @PACKAGE_NAME@
 PACKAGE_STRING = @PACKAGE_STRING@
 PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_URL =

Re: [OMPI users] Configuring with torque: error and patch

2010-05-30 Thread Doug Reeder


John,

I haven't done a build with torque lately, but I think you need to  
have a -ltorque argument in the load step.


Doug Reeder
On May 30, 2010, at 9:13 AM, John Cary wrote:


Upon configuring and building openmpi on a system with
torque, I repeatedly got build errors of the sort,

/bin/sh ../../../libtool --tag=CXX   --mode=link g++  -O3 -DNDEBUG - 
finline-functions -pthread   -o ompi_info components.o ompi_info.o  
output.o param.o version.o ../../../ompi/libmpi.la -lnsl -lutil  -lm
libtool: link: g++ -O3 -DNDEBUG -finline-functions -pthread -o .libs/ 
ompi_info components.o ompi_info.o output.o param.o  
version.o  ../../../ompi/.libs/libmpi.so -L/usr/local/torque-2.4.0b1/ 
lib /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/ 
orte/.libs/libopen-rte.so /scr_multipole/cary/facetspkgs/builds/ 
openmpi-1.4.2/nodl/opal/.libs/libopen-pal.so -ldl -lnsl -lutil -lm - 
pthread -Wl,-rpath -Wl,/usr/local/contrib/openmpi-1.4.2-nodl/lib
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/ 
libopen-rte.so: undefined reference to `tm_spawn'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/ 
libopen-rte.so: undefined reference to `tm_poll'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/ 
libopen-rte.so: undefined reference to `tm_finalize'
/scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/ 
libopen-rte.so: undefined reference to `tm_init'

collect2: ld returned 1 exit status

which I fixed by adding one or the other of

$(ORTE_WRAPPER_EXTRA_LDFLAGS) $(ORTE_WRAPPER_EXTRA_LIBS)

$(OMPI_WRAPPER_EXTRA_LDFLAGS) $(OMPI_WRAPPER_EXTRA_LIBS)

to various LDADD variables.  I doubt that this is consistent
with how your build system is designed, but it works for me.
I am sending you the diff in case it helps you in any way.
BTW, I also fixed some blanks after backslashes in
contrib/Makefile.am.  This is also in the attached patch.

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

Re: [OMPI users] Configuring with torque: error and patch

2010-05-30 Thread Ralph Castain

That's strange - haven't seen that on other Torque systems. How did you 
configure it?


On May 30, 2010, at 10:13 AM, John Cary wrote:

> Upon configuring and building openmpi on a system with
> torque, I repeatedly got build errors of the sort,
> 
> /bin/sh ../../../libtool --tag=CXX   --mode=link g++  -O3 -DNDEBUG 
> -finline-functions -pthread   -o ompi_info components.o ompi_info.o output.o 
> param.o version.o ../../../ompi/libmpi.la -lnsl -lutil  -lm
> libtool: link: g++ -O3 -DNDEBUG -finline-functions -pthread -o 
> .libs/ompi_info components.o ompi_info.o output.o param.o version.o  
> ../../../ompi/.libs/libmpi.so -L/usr/local/torque-2.4.0b1/lib 
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so
>  
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/opal/.libs/libopen-pal.so
>  -ldl -lnsl -lutil -lm -pthread -Wl,-rpath 
> -Wl,/usr/local/contrib/openmpi-1.4.2-nodl/lib
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so:
>  undefined reference to `tm_spawn'
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so:
>  undefined reference to `tm_poll'
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so:
>  undefined reference to `tm_finalize'
> /scr_multipole/cary/facetspkgs/builds/openmpi-1.4.2/nodl/orte/.libs/libopen-rte.so:
>  undefined reference to `tm_init'
> collect2: ld returned 1 exit status
> 
> which I fixed by adding one or the other of
> 
> $(ORTE_WRAPPER_EXTRA_LDFLAGS) $(ORTE_WRAPPER_EXTRA_LIBS)
> 
> $(OMPI_WRAPPER_EXTRA_LDFLAGS) $(OMPI_WRAPPER_EXTRA_LIBS)
> 
> to various LDADD variables.  I doubt that this is consistent
> with how your build system is designed, but it works for me.
> I am sending you the diff in case it helps you in any way.
> BTW, I also fixed some blanks after backslashes in
> contrib/Makefile.am.  This is also in the attached patch.
> 
> BestJohn Cary
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] Process doesn't exit on remote machine when using hostfile

2010-05-30 Thread Shiqing Fan


Hi,

Sorry for the late reply.

It seems something is still missing on Windows for supporting hostfiles, 
I'll fix it ASAP.


Regards,
Shiqing


On 2010-5-25 11:41 AM, Rajnesh Jindel wrote:
disabled the firewall and using admin account so security isnt the 
issue here. like I said this problem only occurs when using a 
hostfile,  if I actually specify the hostname on the commandfline it 
works fine
On 25 May 2010 09:08, Shiqing Fan mailto:f...@hlrs.de>> 
wrote:


Hi,

What's the firewall setting on the remote node? Could you try to
add an exception for the application, or turn off the firewall
completely?

Regards,
Shiqing




On 2010-5-24 4:44 PM, Rajnesh Jindel wrote:

When I specify the hosts separately on the commandline, as
follows, the process completes as expected.
mpirun -np 8 -host remotehost,localhost myapp
Output appears for the localhost and a textfile is created on the
remotehost

However when I use a hostfile the remote processes never
complete. I can see the output from the local processes and by
remote login I can see that that processes are being started on
the remote machine but never complete.

The is a simple reduce example using boost.mpi (v1.43) I'm using
windows 7 x64 pro on both machines and openmpi 1.4.2 the hostfile
and athe app are in the same locaion on both machines.

Any idea why this is happening?

Raj


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



-- 
--

Shiqing Fanhttp://www.hlrs.de/people/fan
High Performance Computing   Tel.: +49 711 685 87234
   Center Stuttgart (HLRS)Fax.: +49 711 685 65832
Address:Allmandring 30   email:f...@hlrs.de  

70569 Stuttgart
 






--
--
Shiqing Fan  http://www.hlrs.de/people/fan
High Performance Computing   Tel.: +49 711 685 87234
  Center Stuttgart (HLRS)Fax.: +49 711 685 65832
Address:Allmandring 30   email: f...@hlrs.de
70569 Stuttgart

[OMPI users] Configuring with torque: error and patch

Re: [OMPI users] Configuring with torque: error and patch

Re: [OMPI users] Configuring with torque: error and patch

Re: [OMPI users] Process doesn't exit on remote machine when using hostfile

4 matches

Site Navigation

Mail list logo

Footer information