Paul,
i missed a step indeed :
opal is required by rte, that is in turn required by mpi
the attached patch does the job (tested on a solaris10/x86_64 vm with
gnu compilers)
Cheers,
Gilles
On 2014/08/06 4:40, Paul Hargrove wrote:
> Gilles,
>
> I have not tested your patch.
> I've only read it.
Gilles,
I have not tested your patch.
I've only read it.
It looks like it could work, except that libopen-rte.a depends on libsocket
and libnsl on Solaris.
So, one probably needs to add $LIBS to the ORTE wrapper libs as well.
Additionally,if your approach is the correct one, then I think one can
Here is a patch that has been minimally tested.
this is likely an overkill (at least when dynamic libraries can be used),
but it does the job so far ...
Cheers,
Gilles
On 2014/08/05 16:56, Gilles Gouaillardet wrote:
> from libopen-pal.la :
> dependency_libs=' -lrdmacm -libverbs -lscif -lnuma -l
from libopen-pal.la :
dependency_libs=' -lrdmacm -libverbs -lscif -lnuma -ldl -lrt -lnsl
-lutil -lm'
i confirm mpicc fails linking
but FWIT, using libtool does work (!)
could the bug come from the mpicc (and other) wrappers ?
Gilles
$ gcc -g -O0 -o hw /csc/home1/gouaillardet/hw.c
-I/tmp/insta
My thought was to post initially as a blocker, pending a discussion with Jeff
at tomorrow's telecon. If he thinks this is something we can fix in some
central point (thus catching it everywhere), then it could be quick and worth
doing. However, I'm skeptical as I tried to do that in the most obv
Ralph and Jeff,
I've been digging and find the problem is wider than just the one library
and has manifestations specific to FreeBSD, NetBSD and Solaris. I am
adding new info to the ticket as I unearth it.
Additionally, it appears this existed in 1.8, 1.8.1 and in the 1.7 series
as well.
So, wou
Okay, I filed a blocker on this for 1.8.2 and assigned it to Jeff. I took a
crack at fixing it, but came up short :-(
On Aug 3, 2014, at 10:46 PM, Paul Hargrove wrote:
> I've identified the difference between the platform that does link libutil
> and the one that does not.
>
> 1) libutil is
I've identified the difference between the platform that does link libutil
and the one that does not.
1) libutil is linked (as an OMPI dependency) only on the working system:
Working system:
$ grep 'checking for .* LIBS' configure.out
checking for OPAL LIBS... -lm -lpciaccess -ldl
checking for OR
