Trace should probably just be eliminated. I "championed" it a long time
ago, but the reason for doing it has long passed - and as a result, it is
virtually unused in the code base.
On Wed, Jul 10, 2013 at 12:40 PM, Vasiliy <testtest_2...@ukr.net> wrote:
> Nothing special, for a trace it's just --enable-trace. I'm not
> building libompitrace though, following marco's suggestion, only
> arbitrary defined MCA_BASE_VAR_VERBOSE_MPIDEV_ALL = 2 (it wasn't
> defined anyway), and did not change the library ordering.
>
> It wonderfully passes almost all the tests even though -Ofast is
> present, however, the full string is awfully long as I'm pretty picky
> in choosing the components to compile, patching the sources before
> that, what in no way should interfere with the main compilation line.
> There's a nasty trick with coll/hcoll and coll/coll_ml in DSO mode
> though, since the configure script doesn't provide the easy way of
> disabling DSO components - only during runtime. There's still some
> work to be done about few missing dependencies to have all components
> DSO-compile.
>
> On Wed, Jul 10, 2013 at 9:13 PM, Jeff Squyres (jsquyres)
> <jsquy...@cisco.com> wrote:
> > What command are you using to configure OMPI?
> >
> >
> > On Jul 10, 2013, at 2:58 PM, Vasiliy <testtest_2...@ukr.net>
> > wrote:
> >
> >> not exactly the subject, however, since I've mentioned 'trace' here,
> >> it's for this thread:
> >> - undeclared 'value', or should I have configured it with
> >> -Dvalue=<something>, it wouldn't compile anyway
> >> <code>
> >> make[3]: Entering directory
> >> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/opal/util'
> >> CC trace.lo
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:
> >> In function ‘opal_trace_init’:
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:44:13:
> >> error: ‘value’ undeclared (first use in this function)
> >> if (0 > value) {
> >> ^
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:44:13:
> >> note: each undeclared identifier is reported only once for each
> >> function it appears in
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:63:35:
> >> error: incompatible type for argument 11 of ‘mca_base_var_register’
> >> &tracer.lds_verbose_level);
> >> ^
> >> In file included from
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/base/base.h:35:0,
> >> from
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:23:
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/base/mca_base_var.h:503:19:
> >> note: expected ‘mca_base_var_scope_t’ but argument is of type ‘int *’
> >> OPAL_DECLSPEC int mca_base_var_register (const char *project_name,
> >> const char *framework_name,
> >> ^
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:63:35:
> >> error: too few arguments to function ‘mca_base_var_register’
> >> &tracer.lds_verbose_level);
> >> ^
> >> In file included from
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/base/base.h:35:0,
> >> from
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:23:
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/base/mca_base_var.h:503:19:
> >> note: declared here
> >> OPAL_DECLSPEC int mca_base_var_register (const char *project_name,
> >> const char *framework_name,
> >> ^
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:
> >> In function ‘opal_trace_finalize’:
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:72:5:
> >> warning: implicit declaration of function ‘mca_base_var_dereg_group’
> >> [-Wimplicit-function-declaration]
> >> mca_base_var_dereg_group (mca_base_var_find_group ("opal", "trace",
> NULL));
> >> ^
> >>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/util/trace.c:72:5:
> >> warning: implicit declaration of function ‘mca_base_var_find_group’
> >> [-Wimplicit-function-declaration]
> >> Makefile:1708: recipe for target 'trace.lo' failed
> >> </code>
> >>
> >> There're also 'misqueried' dependencies as shown in the next excerpt:
> >> <code>
> >> make[3]: Entering directory
> >>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/ompi/mpi/fortran/mpif-h'
> >> CCLD libmpi_mpifh.la
> >> .libs/abort_f.o: In function `ompi_abort_f':
> >> ... (a LOT of unjustified 'undefined references', likely, resulted
> >> from mis-ordered libraries)
> >> profile/.libs/libmpi_mpifh_pmpi.a(pregister_datarep_f.o): In function
> >> `opal_obj_new':
> >> /usr/src/debug/openmpi-1.9.0-a1/opal/class/opal_object.h:471:
> >> undefined reference to `opal_class_initialize'
> >> collect2: error: ld returned 1 exit status
> >> Makefile:2366: recipe for target 'libmpi_mpifh.la' failed
> >> </code>
> >>
> >> also in:
> >> <code>
> >> Making install in mca/common/sm
> >> make[2]: Entering directory
> >>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/ompi/mca/common/sm'
> >> if test -z "libmca_common_sm.la"; then \
> >> rm -f "libmca_common_sm.la"; \
> >> ln -s "libmca_common_sm_noinst.la" "libmca_common_sm.la"; \
> >> fi
> >> CC common_sm_rml.lo
> >> CC common_sm.lo
> >> CCLD libmca_common_sm.la
> >> .libs/common_sm_rml.o: In function `mca_common_sm_rml_info_bcast':
> >> /usr/src/debug/openmpi-1.9.0-a1/ompi/mca/common/sm/common_sm_rml.c:102:
> >> undefined reference to `opal_progress_event_users_increment'
> >> ...
> >> .libs/common_sm.o:common_sm.c:(.data+0x8): undefined reference to
> >> `opal_list_item_t_class'
> >> collect2: error: ld returned 1 exit status
> >> Makefile:1619: recipe for target 'libmca_common_sm.la' failed
> >> </code>
> >>
> >> On Tue, Jul 9, 2013 at 3:10 PM, Ralph Castain <r...@open-mpi.org> wrote:
> >>> No issue with doing so. If this was someone trying to use it, I'd put
> it at a high priority. If just someone trying all the configure options,
> then a lower priority.
> >>>
> >>> The problem stems from a little bit-rot. Those components are updated
> and working on a side branch being used by my old company, but I didn't
> make it a priority to bring them across as nobody else was using them.
> >>>
> >>>
> >>> On Jul 8, 2013, at 11:44 PM, Vasiliy <testtest_2...@ukr.net> wrote:
> >>>
> >>>> (giggling) No, it's unsafe. I've disabled 'trace' for now. On a more
> >>>> serious note, why not adding those, if they should be here?
> >>>> <code>
> >>>> Making check in mca/sensor/resusage
> >>>> make[2]: Entering directory
> >>>>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/mca/sensor/resusage'
> >>>> CC sensor_resusage.lo
> >>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/orte/mca/sensor/resusage/sensor_resusage.c:35:28:
> >>>> fatal error: orte/mca/db/db.h: No such file or directory
> >>>> #include "orte/mca/db/db.h"
> >>>> ^
> >>>> compilation terminated.
> >>>> Makefile:1594: recipe for target 'sensor_resusage.lo' failed
> >>>> </code>
> >>>>
> >>>> On Tue, Jul 9, 2013 at 1:28 AM, Ralph Castain <r...@open-mpi.org>
> wrote:
> >>>>> Is it safe to say that you are going thru an exercise testing every
> option that exists? Just want to know so I can set expectations
> >>>>>
> >>>>>
> >>>>> On Jul 8, 2013, at 11:47 AM, Vasiliy <testtest_2...@ukr.net> wrote:
> >>>>>
> >>>>>> there're more to come:
> >>>>>> <code>
> >>>>>> Making all in mca/sensor/resusage
> >>>>>> make[2]: Entering directory
> >>>>>>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/mca/sensor/resusage'
> >>>>>> CC sensor_resusage.lo
> >>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/orte/mca/sensor/resusage/sensor_resusage.c:35:28:
> >>>>>> fatal error: orte/mca/db/db.h: No such file or directory
> >>>>>> #include "orte/mca/db/db.h"
> >>>>>> ^
> >>>>>> compilation terminated.
> >>>>>> Makefile:1594: recipe for target 'sensor_resusage.lo' failed
> >>>>>> </code>
> >>>>>>
> >>>>>> On Mon, Jul 8, 2013 at 8:38 PM, Vasiliy <testtest_2...@ukr.net>
> wrote:
> >>>>>>> Oh, well, it does not:
> >>>>>>> <code>
> >>>>>>> Making all in mca/db/sqlite
> >>>>>>> make[2]: Entering directory
> >>>>>>>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/opal/mca/db/sqlite'
> >>>>>>> CC libmca_db_sqlite_la-db_sqlite_component.lo
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:
> >>>>>>> In function ‘sqlite_component_query’:
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:93:17:
> >>>>>>> warning: assignment from incompatible pointer type [enabled by
> >>>>>>> default]
> >>>>>>> *module = (mca_base_module_t*)&opal_db_sqlite_module;
> >>>>>>> ^
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:
> >>>>>>> In function ‘sqlite_component_close’:
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:104:12:
> >>>>>>> error: ‘ORTE_SUCCESS’ undeclared (first use in this function)
> >>>>>>> return ORTE_SUCCESS;
> >>>>>>> ^
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:104:12:
> >>>>>>> note: each undeclared identifier is reported only once for each
> >>>>>>> function it appears in
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:
> >>>>>>> In function ‘sqlite_component_register’:
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:127:12:
> >>>>>>> error: ‘ORTE_SUCCESS’ undeclared (first use in this function)
> >>>>>>> return ORTE_SUCCESS;
> >>>>>>> ^
> >>>>>>> Makefile:1608: recipe for target
> >>>>>>> 'libmca_db_sqlite_la-db_sqlite_component.lo' failed
> >>>>>>> make[2]: *** [libmca_db_sqlite_la-db_sqlite_component.lo] Error 1
> >>>>>>> CC libmca_db_sqlite_la-db_sqlite.lo
> >>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite.c:39:39:
> >>>>>>> fatal error: opal/runtime/opal_globals.h: No such file or directory
> >>>>>>> #include "opal/runtime/opal_globals.h"
> >>>>>>> ^
> >>>>>>> compilation terminated.
> >>>>>>> </code>
> >>>>>>> On Mon, Jul 8, 2013 at 8:28 PM, Ralph Castain <r...@open-mpi.org>
> wrote:
> >>>>>>>> Actually, those headers needed to be deleted - done. I take it
> you were deliberately trying to build that support? Otherwise, it shouldn't
> have built.
> >>>>>>>>
> >>>>>>>> On Jul 8, 2013, at 11:11 AM, Vasiliy <testtest_2...@ukr.net>
> wrote:
> >>>>>>>>
> >>>>>>>>> Could somebody add these required headers to the repository?
> Thank you
> >>>>>>>>> in advance:
> >>>>>>>>> <code>
> >>>>>>>>> Making all in mca/db/sqlite
> >>>>>>>>> make[2]: Entering directory
> >>>>>>>>>
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/opal/mca/db/sqlite'
> >>>>>>>>> CC libmca_db_sqlite_la-db_sqlite_component.lo
> >>>>>>>>> CC libmca_db_sqlite_la-db_sqlite.lo
> >>>>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite_component.c:23:33:
> >>>>>>>>> fatal error: opal/util/proc_info.h: No such file or directory
> >>>>>>>>> #include "opal/util/proc_info.h"
> >>>>>>>>> ^
> >>>>>>>>> compilation terminated.
> >>>>>>>>> Makefile:1608: recipe for target
> >>>>>>>>> 'libmca_db_sqlite_la-db_sqlite_component.lo' failed
> >>>>>>>>> make[2]: *** [libmca_db_sqlite_la-db_sqlite_component.lo] Error 1
> >>>>>>>>> make[2]: *** Waiting for unfinished jobs....
> >>>>>>>>>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sqlite.c:39:39:
> >>>>>>>>> fatal error: opal/mca/errmgr/base/base.h: No such file or
> directory
> >>>>>>>>> #include "opal/mca/errmgr/base/base.h"
> >>>>>>>>> ^
> >>>>>>>>> compilation terminated.
> >>>>>>>>> </code>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> devel mailing list
> >>>>>>>>> de...@open-mpi.org
> >>>>>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> devel mailing list
> >>>>>>>> de...@open-mpi.org
> >>>>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> devel mailing list
> >>>>>> de...@open-mpi.org
> >>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> devel mailing list
> >>>>> de...@open-mpi.org
> >>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>>>
> >>>> _______________________________________________
> >>>> devel mailing list
> >>>> de...@open-mpi.org
> >>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>>
> >>>
> >>> _______________________________________________
> >>> devel mailing list
> >>> de...@open-mpi.org
> >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >>
> >> _______________________________________________
> >> devel mailing list
> >> de...@open-mpi.org
> >> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> >
> > _______________________________________________
> > devel mailing list
> > de...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
