Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-09-24 15:41:10


On Sep 24, 2007, at 3:15 PM, David Erukhimovich wrote:

> I understand all of This.
> The only thing I did this time is to download v1.2.3 from svn and
> build it
> (without modifying anything!).
> So I got The linkage error I attached last time. As you can see it
> isn't
> connected with ORTE but with opmi_info or something

FYI: The OPAL progress stuff changed quite a bit between v1.2 and the
trunk as well. :-\

Specifically: v1.2 branched a while ago and is our current stable
release. The developent trunk has moved ahead with development and
has changed (sometimes by a lot) as compared to the v1.2 stable
release branch; the development trunk will someday turn into the v1.3
series. The v1.2 branch does *not* get all of these changes; it
generally only gets bug fixes (and sometimes new functionality, but
the focus is on bug fixes).

So if you developed some code against the SVN trunk, you may well be
running into compatibility issues between the v1.2 branch. More
specifically: *any* mixing of v1.2 and trunk may result in Badness.
What might be easiest is to "make clean" and then "make" again to
ensure that you don't have any kind of cross-pollination that is
causing these linker issues (e.g., somehow mistakenly trying to link
together stuff between the v1.2 branch and the trunk).

If you continue to have compiler/linker issues, send the full set of
data requested by the "getting help" page so that we can see the full
errors, etc.

> --David
>
> Tim Mattox wrote:
>
> In the future, please continue to ask your questions on the developer
> mailing list so that others can learn from them later via google, etc.
>
> In this case, it appears the problem is that you originally copied
> the component
> from the development trunk to modify for your own needs. The ORTE
> layer has changed significantly between the 1.2 series and the trunk,
> and thus your new code inherited the newer stuff that isn't
> compatible with
> the 1.2 sources.
>
> You should either make a copy of a component in the 1.2 series to
> modify as you need, or, you should be building from a trunk checkout.
>
> On 9/24/07, David Erukhimovich <daviderukh_at_[hidden]> wrote:
>
>
> ---------- Forwarded message ----------
> Date: Mon, 24 Sep 2007 18:51:28 +0200 (IST)
> From: David Erukhimovich <daviderukh_at_[hidden]>
> To: David Erukhimovich <daviderukh_at_[hidden]>
> Subject: Re: [OMPI devel] Problem with adding new component
>
>
>
> Hello Tom,
> Thanks for your responce.
> I tried to complies the ompi 1.2.3 (and 1.2.0) I downloaded from
> svn
> using:
> $ sh autogen.sh ; configure --prefix $MOSHOME/openmpi-
> install ; make all
> install
>
> and I got the following compilation error:
> components.o: In function `ompi_info::open_components()':
>
> /cs/stud/daviderukh/moshome/v1.2.0/ompi/tools/ompi_info/
> components.cc:221:
> undefined reference to `orte_rml_base'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_mpi_init'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_events'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_mpi_enable'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_event_decrement'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_mpi_disable'
> ../../../ompi/.libs/libmpi.so: undefined reference to
> `opal_progress_event_increment'
> collect2: ld returned 1 exit status
>
> What is the thing now?
>
> Thank you
> --David
>
>
> On 9/23/07, Tim Mattox <timattox_at_[hidden] > wrote:
>
> Hello David,
> The development trunk (towards 1.3) is not binary compatible with
> the 1.2 branch of Open MPI. Actually, AFAIK, no two versions of
> Open MPI are guaranteed to be binary compatible.
>
> You would need to compile and make your component from within
> a 1.2 source tree. To be safe, you should use an svn check out that
> matches the version you want to use, so in your case:
> svn co https://svn.open-mpi.org/svn/ompi/tags/v1.2-series/v1.2.3
> and then go from there. There is a chance things will work from the
> current 1.2 svn HEAD, but we do not test our code changes for
> binary compatibility between versions.
>
> On 9/23/07, David Erukhimovich <daviderukh_at_[hidden]> wrote:
>
> Hello,
> I created a new component by modifying round_robin (on rmaps) a bit. I
> compiled it using autogen. configure and make in the development (1.3)
> version and it works fine.
> Now I tried to copy the the new library I made (.so and .la files) to
>
> the
>
> lib folder of a stable release (1.2.3).
> the release sees the new component but it doesn't work. the output
>
> when I
>
> run the following is:
>
> $ mpirun --mca rmaps mos_round_robin --mca rmaps_base_verbose 1
>
> hostname
>
> [mos204:04929] Scheduling policy: unspec
> [mos204:04929] orte:base:open: querying component mos_round_robin
> [mos204:04929] orte:base:open: component mos_round_robin does NOT want
>
> to
>
> be considered for selection
> [mos204:04929] orte:rmaps:base:map: no components available!
> [mos204:04929] [0,0,0] ORTE_ERROR_LOG: Not found in file
> base/rmaps_base_map_job.c at line 201
> [mos204:04929] *** Process received signal ***
> [mos204:04929] Signal: Segmentation fault (11)
> [mos204:04929] Signal code: Address not mapped (1)
> [mos204:04929] Failing at address: 0xf7f1eb
> [mos204:04929] [ 0] [0xffffe440]
> [mos204:04929] [ 1] /lib/i686/cmov/libc.so.6(vasprintf+0xbc)
>
> [0xb7d8eb6c]
>
> [mos204:04929] [ 2]
> /cs/mosna/daviderukh/openmpi-install2/lib/libopen-pal.so.0[0xb7f18572]
> [mos204:04929] [ 3]
> /cs/mosna/daviderukh/openmpi-install2/lib/libopen-pal.so.0
> (opal_output+0x1e)
>
> [0xb7f18a5e]
> [mos204:04929] [ 4]
> /cs/mosna/daviderukh/openmpi-install2/lib/libopen-rte.so.0
>
> (orte_rmaps_base_map_job+0x5f6)
>
> [0xb7f870b6]
> [mos204:04929] [ 5]
> /cs/mosna/daviderukh/openmpi-install2/lib/openmpi/mca_rmgr_urm.so
> [0xb7c7c368]
> [mos204:04929] [ 6] mpirun(orterun+0x3d9) [0x804a1e9]
> [mos204:04929] [ 7] mpirun(main+0x22) [0x8049e06]
> [mos204:04929] [ 8] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0)
> [0xb7d44050]
> [mos204:04929] [ 9] mpirun [0x8049d81]
> [mos204:04929] *** End of error message ***
> Segmentation fault
>
>
> So... what am I doing wrong and how can I fix it?
>
> Thank you
> --David
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>
> --
> Tim Mattox, Ph.D. - http://homepage.mac.com/tmattox/
> tmattox_at_[hidden] || timattox_at_[hidden]
> I'm a bright... http://www.the-brights.net/
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

-- 
Jeff Squyres
Cisco Systems