[OMPI devel] aclocal-1.14: error: ../../config/autogen_found_items.m4:274: file 'opal/mca/backtrace/configure.m4' does not exist

2013-07-01 Thread Vasiliy
Hello, There is an error while configuring OpenMPI from the svn checkout with aclocal not being able to find 'opal/mca/backtrace/configure.m4', which, in fact, does exist there. What changes are needed to fix that? Note: it has stepped in the 'opal/libltdl' directory just before that error: ***

Re: [OMPI devel] aclocal-1.14: error: ../../config/autogen_found_items.m4:274: file 'opal/mca/backtrace/configure.m4' does not exist

2013-07-01 Thread Vasiliy
764 > Last Changed Date: 2010-09-17 19:04:06 -0400 (Fri, 17 Sep 2010) > Text Last Updated: 2013-05-24 11:39:52 -0400 (Fri, 24 May 2013) > Checksum: a6d3741b6c9ab47daf2a6af6c812c148f91793a2 > > > > On Jul 1, 2013, at 9:58 AM, Vasiliy > wrote: > >> Hello, >> >&g

Re: [OMPI devel] aclocal-1.14: error: ../../config/autogen_found_items.m4:274: file 'opal/mca/backtrace/configure.m4' does not exist

2013-07-01 Thread Vasiliy
trace/configure.m4' if it operates in 'opal/libltdl' ? Vasiliy On Mon, Jul 1, 2013 at 4:07 PM, Ralph Castain wrote: > Or you might try rerunning autogen.pl in case you updated and didn't catch > that something requiring autogen changed > > On Jul 1, 2013, at 7:0

Re: [OMPI devel] aclocal-1.14: error: ../../config/autogen_found_items.m4:274: file 'opal/mca/backtrace/configure.m4' does not exist

2013-07-01 Thread Vasiliy
as gotten really messed up in your checkout or system. You >> might check to ensure you are picking up the right autotools, and perhaps >> re-checkout the trunk. >> >> All I can tell you is that it is building just fine on both my Mac and >> Linux boxes. >>

[OMPI devel] No such file(s) or directory

2013-07-08 Thread Vasiliy
Could somebody add these required headers to the repository? Thank you in advance: 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

Re: [OMPI devel] No such file(s) or directory

2013-07-08 Thread Vasiliy
Castain 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 wrote: > >> Could somebody add these required headers to t

[OMPI devel] the sensors do not compile

2013-07-08 Thread Vasiliy
It has been taken from the compilation log: Making all in mca/sensor/ft_tester make[2]: Entering directory '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/mca/sensor/ft_tester' CC sensor_ft_tester.lo CC sensor_ft_tester_component.lo /usr/src/64bit/release/openmpi/openmp

Re: [OMPI devel] No such file(s) or directory

2013-07-08 Thread Vasiliy
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 On Mon, Jul 8, 2013 at 8:38 PM, Vasi

[OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

2013-07-08 Thread Vasiliy
I haven't checked that yet, however, from my experience, creating a shared library manually from the same compiled objects never was a problem at a later stage, it's usually because of Makefile's inconsistent dependencies ordering: $ uname -srvmo CYGWIN_NT-6.1 1.7.21(0.267/5/3) 2013-06-28 10:03 x8

Re: [OMPI devel] No such file(s) or directory

2013-07-09 Thread Vasiliy
inated. Makefile:1594: recipe for target 'sensor_resusage.lo' failed On Tue, Jul 9, 2013 at 1:28 AM, Ralph Castain 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

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

2013-07-09 Thread Vasiliy
same Vasily from Mellanox? If so, are you saying that Mellanox > is working to support Open MPI under Cygwin? > > > > On Jul 8, 2013, at 3:00 PM, Vasiliy wrote: > >> I haven't checked that yet, however, from my experience, creating a >> shared library manually fro

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

2013-07-09 Thread Vasiliy
While I don't represent any organization view it's still an amateur work done to the detriment of time for job hunting. I probably need to pay more attention to the latter, so, to find out if I could complete a DSO build before the hunting season starts. There is a well-funded hope, thoug

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

2013-07-09 Thread Vasiliy
On Tue, Jul 9, 2013 at 1:21 PM, Jeff Squyres (jsquyres) wrote: > On Jul 9, 2013, at 7:01 AM, Vasiliy wrote: > >> I'll have to look into that. It looks like with all my humble patches >> it should compile and pass the tests successfully even if compiled >> with -march=na

Re: [OMPI devel] a bogus warning: undefined symbols not allowed in x86_64-pc-cygwin shared libraries

2013-07-09 Thread Vasiliy
; > > > Josh > > -Original Message- > From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On > Behalf Of Vasiliy > Sent: Tuesday, July 09, 2013 7:02 AM > To: Open MPI Developers > Subject: Re: [OMPI devel] a bogus warning: undefined symbols not

Re: [OMPI devel] No such file(s) or directory

2013-07-10 Thread Vasiliy
t; > 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 wrote: > &g

Re: [OMPI devel] No such file(s) or directory

2013-07-10 Thread Vasiliy
jsquyres) wrote: > What command are you using to configure OMPI? > > > On Jul 10, 2013, at 2:58 PM, Vasiliy > wrote: > >> not exactly the subject, however, since I've mentioned 'trace' here, >> it's for this thread: >> - undeclared &#

[OMPI devel] basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-11 Thread Vasiliy
upon inspecting: $ /usr/share/automake-1.14/test-driver --help Usage: test-driver --test-name=NAME --log-file=PATH --trs-file=PATH [--expect-failure={yes|no}] [--color-tests={yes|no}] [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT The '--test-name', '--log-file' and

[OMPI devel] Fwd: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-11 Thread Vasiliy
river' either because a testsuite does not provide --test-name=NAME or because --log-file=/tmp or --log-file=/tmp/delme is wrongly considered an invalid option. It applies to automake 1.13 as well. Could an Open MPI Team suggest if we could change that behavior, or, at least, make omitting --test

Re: [OMPI devel] Fwd: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-11 Thread Vasiliy
mp='2013-06-10' On Thu, Jul 11, 2013 at 1:51 PM, marco atzeri wrote: > Il 7/11/2013 1:47 PM, Vasiliy ha scritto: > >> I've also tracked down that problem with 'test-driver'. Look at that: >> >> $ gdb --args /usr/bin/sh /usr/share/automake-1.14/test-d

Re: [OMPI devel] basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-12 Thread Vasiliy
11, 2013 at 11:18 PM, Jeff Squyres (jsquyres) wrote: > I'm not sure what you're saying -- isn't this an Automake bug? > > Or are you saying that we're doing something wrong in OMPI's Makefile.am's? > > > > On Jul 11, 2013, at 7:47 AM, Vasiliy wrote: &g

Re: [OMPI devel] basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-12 Thread Vasiliy
re: > > http://www.open-mpi.org/community/help/ > > 3. We don't have a test named "basename" or "test-driver"; basename is > usually an OS utility, and test-driver is part of the new Automake testing > framework. If there's a mistake in how these are

Re: [OMPI devel] basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-12 Thread Vasiliy
ar with a test suite may want to look into it. On Fri, Jul 12, 2013 at 5:17 PM, Vasiliy wrote: > Sorry again, my report was a stub because I didn't have enough time to > investigate the issue. Due to the verbose level was set to zero, I've > assumed from the log that 'basena

Re: [OMPI devel] basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail

2013-07-14 Thread Vasiliy
st/asm/run_tests' why it was passed through. On Fri, Jul 12, 2013 at 9:30 PM, Vasiliy wrote: > I've just gone through a test suite, and in 'test/asm/run_tests' there > is a statement: > > progname="`basename $*`" > > where '--test-name' cou

[OMPI devel] 'make re-install' : remove 'ortecc' symlink also

2013-07-14 Thread Vasiliy
Makefile: please, remove/check for 'ortecc' symlink before proceeding with install make[4]: Entering directory '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/tools/wrappers' test -z "/usr/bin" || /usr/bin/mkdir -p "/usr/bin" make install-data-hook (cd /usr/bin; rm -f ortecc.exe; ln -

Re: [OMPI devel] 'make re-install' : remove 'ortecc' symlink also

2013-07-14 Thread Vasiliy
for target 'install-exec-hook' failed ... On Sun, Jul 14, 2013 at 11:35 PM, Vasiliy wrote: > Makefile: please, remove/check for 'ortecc' symlink before proceeding > with install > > make[4]: Entering directory > '/usr/src/64bit/release/openmpi/openmpi-1.9