That was the problem that trigger my question. If we remove the
dependence to the libopal in the malloc_interpose we can compile the
module. Otherwise the compilation fails because the generation of the
mca_memory_malloc_interpose happens priori to the libopal.so. However,
reading the last email I now understand why we need the backward
dependence to the libopal and liborte.
But I still see a problem. **Just to refresh the memories, I'm the only
complaining on a regular base about the useless dependencies**. And
there are a lot. I know that most of the shared libraries in ompi use
functions in the opal section. But few of them rely on any of the orte
shared libraries. If the dependencies are set correctly then we don't
have to add
$(top_ompi_builddir)/ompi/libmpi.la
$(top_ompi_builddir)/orte/liborte.la
$(top_ompi_builddir)/opal/libopal.la
all over the Makefiles.
george.
Ralf Wildenhues wrote:
Andrew,
* Ralf Wildenhues wrote on Fri, Sep 23, 2005 at 10:42:34AM CEST:
* Andrew Friedley wrote on Thu, Sep 22, 2005 at 09:09:11PM CEST:
On Sep 22, 2005, at 12:56 PM, George Bosilca wrote:
Now we get this message for all .so file we generate:
libtool: install: warning: relinking `*.la'
I think I found a small error in the patch, see proposed fix below.
Cheers,
Ralf
Index: opal/mca/memory/malloc_interpose/Makefile.am
===================================================================
--- opal/mca/memory/malloc_interpose/Makefile.am (revision 7493)
+++ opal/mca/memory/malloc_interpose/Makefile.am (working copy)
@@ -22,6 +22,5 @@
libmca_memory_malloc_interpose_la_SOURCES = \
memory_malloc_interpose.c
libmca_memory_malloc_interpose_la_LIBADD = \
- $(memory_malloc_interpose_LIBS) \
- $(top_ompi_builddir)/opal/libopal.la
+ $(memory_malloc_interpose_LIBS)
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
