On Jan 30, 2008, at 10:05 AM, Thomas Ropars wrote:
Sorry, I made a mistake ... I works fine for me too with LT 1.5.22
It seems that the problem is with LT 1.5.24
With this version, I only have in my sys_dl_open():
lt_module module = dlopen (filename, LT_LAZY_OR_NOW);
Yoinks! LT changed t
Jeff Squyres wrote:
On Jan 30, 2008, at 4:43 AM, Thomas Ropars wrote:
After running autogen.sh, the file opal/libltdl/loaders/dlopen.c
doesn't
exist and more generally the directory opal/libltdl/loaders/ doesn't
exist.
That's why I need to add the RTLD_GLOBAL flag after running
autogen.
On Jan 30, 2008, at 4:43 AM, Thomas Ropars wrote:
After running autogen.sh, the file opal/libltdl/loaders/dlopen.c
doesn't
exist and more generally the directory opal/libltdl/loaders/ doesn't
exist.
That's why I need to add the RTLD_GLOBAL flag after running
autogen.sh.
I'm using the foll
After running autogen.sh, the file opal/libltdl/loaders/dlopen.c doesn't
exist and more generally the directory opal/libltdl/loaders/ doesn't exist.
That's why I need to add the RTLD_GLOBAL flag after running autogen.sh.
I'm using the following version of the autotools.
autoconf (GNU Autoconf)
We are testing for a specific line when looking for this patch:
test ! -z "`grep 'filename, LT_LAZY_OR_NOW' opal/libltdl/
loaders/dlopen.c`"; then
If this line is different in your dlopen.c, then it doesn't find it
and therefore autogen.sh doesn't patch it.
Did you already patc
I've solved the problem by adding the flag RTLD_GLOBAL in the call to
dlopen() in function "sys_dl_open (loader_data, filename)"
(opal/libltdl/ltdl.c)
It seems that I need this flag. However when I run autogen.sh, I get the
following:
** Adjusting libltdl for OMPI :-(
++ patching for argz bu
Hi,
I have the same error message when fault tolerance is activated.
I'm using gcc version 4.1.3, with Ubuntu 7.10 (i686) (kernel
2.6.22-14-generic)
Thomas
Aurelien Bouteiller wrote:
If you want to use the pessimist message logging you have to use the "-
mca vprotocol pessimist" flag on your
If you want to use the pessimist message logging you have to use the "-
mca vprotocol pessimist" flag on your command line. This should work
despite the bug because if I understand correctly, the issue you
experience should occur only when fault tolerance is disabled.
I have troubles to reprod
I still have the same error after update (r16951).
I have the lib/openmpi/mca_pml_v.so file in my builld and the command
line I use is: mpirun -np 4 my_application
Thomas
Aurelien Bouteiller wrote:
I could reproduce and fix the bug. It will be corrected in trunk as
soon as the svn is onlin
I could reproduce and fix the bug. It will be corrected in trunk as
soon as the svn is online again. Thanks for reporting the problem.
Aurelien
Le 11 déc. 07 à 15:02, Aurelien Bouteiller a écrit :
I cannot reproduce the error. Please make sure you have the lib/
openmpi/mca_pml_v.so file in y
I cannot reproduce the error. Please make sure you have the lib/
openmpi/mca_pml_v.so file in your build. If you don't, maybe you
forgot to run autogen.sh at the root of the trunk when you
removed .ompi_ignore.
If this does not fix the problem, please let me know your command line
options
Mmm, I'll investigate this today.
Aurelien
Le 11 déc. 07 à 08:46, Thomas Ropars a écrit :
Hi,
I've tried to test the message logging component vprotocol pessimist.
(svn checkout revision 16926)
When I run an mpi application, I get the following error :
mca: base: component_find: unable to ope
Hi,
I've tried to test the message logging component vprotocol pessimist.
(svn checkout revision 16926)
When I run an mpi application, I get the following error :
mca: base: component_find: unable to open vprotocol pessimist:
/local/openmpi/lib/openmpi/mca_vprotocol_pessimist.so: undefined sy
13 matches
Mail list logo
