r32467 should fix the problem. George.
On Fri, Aug 8, 2014 at 1:20 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > That'll do it... > > George: can you fix? > > > On Aug 8, 2014, at 1:11 PM, Ralph Castain <r...@open-mpi.org> wrote: > > > I think it might be getting pulled in from this include: > > > > opal/mca/common/sm/common_sm.h:37:#include "ompi/group/group.h" > > > > > > On Aug 8, 2014, at 5:33 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > > > >> Weirdness; I don't see any name like that in the SM BTL. > >> > >> I see it used in the OMPI layer... not sure how it's being using down > in the btl SM component file...? > >> > >> > >> On Aug 7, 2014, at 11:25 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > >> > >>> Testing r32448 on trunk for trac issue #4834, I encounter the > following which appears unrelated to #4834: > >>> > >>> CCLD orte-info > >>> Undefined first referenced > >>> symbol in file > >>> ompi_proc_local_proc > > /sandbox/hargrove/OMPI/openmpi-trunk-solaris10-sparcT2-ss12u3-v9-static/BLD/opal/.libs/libopen-pal.a(libmca_btl_sm_la-btl_sm_component.o) > >>> ld: fatal: Symbol referencing errors. No output written to orte-info > >>> > >>> Note that this is *static* linking. > >>> > >>> This appears to indicate a call from OPAL to OMPI, and I am guessing > this is a side-effect of the BTL move. > >>> > >>> Since OMPI contains (many) calls to OPAL this is a circular library > dependence. > >>> Unfortunately, some linkers process their argument strictly > left-to-right. > >>> Thus if this dependence is not eliminated one may need "-lmpi > -lopen-pal -lmpi" (or similar) to resolve it. >
