Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] Odd build breakage seen with 1.5.5rc2
From: Paul Hargrove (phhargrove_at_[hidden])
Date: 2012-02-26 04:30:01


I believe the problem originates with

> r26014 | bosilca | 2012-02-22 19:25:51 -0800 (Wed, 22 Feb 2012) | 7 lines
> Fixes #3033: Fix lt_dladvise search in v1.5
> ---svn-pre-commit-ignore-below---
> r26006
> Fix the search for ltdl_advise support in VPATH builds.

That changeset appears to INCORRECTLY use $srcdir on lines 179 and 181.
I am fairly certain both should be an explicit $builddir or nothing at all.

The same issue, of course, exists in r26006 on trunk.
However, Jeff corrected it in r26023.

It appears ticket #3033 already requests cmr of r26023 to the v1.5 branch.
So, I guess I've just encountered a known problem.

Since my scripts only do VPATH, you won't get any test results from me for
1.5.5rc2.

-Paul

P.S. I have no clue how a "make distcheck" could have completed with this
problem.

On Sun, Feb 26, 2012 at 12:32 AM, Paul Hargrove <phhargrove_at_[hidden]> wrote:

> I don't think the GNU autotools all work correctly for pathnames with
> spaces.
> So, I don't that is not something to worry too much about for the moment.
>
> HOWEVER, there are NO spaces in my srcdir, blddir, or even in prefix.
> There are no characters other than "[-._/0-9a-zA-Z]".
> So, how then am I hitting this problem?
>
> I've been testing just fine 1 day before w/o seeing this problem.
> It is possible something changed in my testing setup, but I can't recall
> anything.
>
> I am going to keep poking at this, but would appreciate any clues as to
> where to look.
>
> -Paul
>
> On Sat, Feb 25, 2012 at 11:28 PM, Ralph Castain <rhc_at_[hidden]> wrote:
>
>> No, I ran into it last week. The problem is that we don't handle spaces
>> in path names - apparently, we never have, so far as Jeff could determine.
>>
>> On Feb 25, 2012, at 11:27 PM, Paul Hargrove wrote:
>>
>> Am I the only one seeing the following odd behavior when running
>> configure?
>>
>> [...]
>>> *** GNU libltdl setup
>>> checking location of libltdl... internal copy
>>> configure: OMPI configuring in opal/libltdl
>>> [....]
>>> configure: creating ./config.status
>>> config.status: creating Makefile
>>> config.status: creating config.h
>>> config.status: executing depfiles commands
>>> config.status: executing libtool commands
>>> configure: /bin/sh '[srcdir]/opal/libltdl/configure' succeeded for
>>> opal/libltdl
>>> grep: [srcdir]/opal/libltdl/Makefile: No such file or directory
>>> checking for libtool-supplied linker flags... ACLOCAL='${SHELL}
>>> [srcir]/config/missing --run aclocal-1.11'
>>> AMDEPBACKSLASH='\'
>>> AMDEP_FALSE='#'
>>> AMDEP_TRUE=
>>> AMTAR='$${TAR-tar}'
>>> [...dump of every shell variable, as from running "set"...]
>>> dummy mt
>>> *** Compiler flags
>>> checking which of CFLAGS are ok for debugger modules... -DNDEBUG
>>> -fno-strict-aliasing -pthread
>>> checking for debugger extra CFLAGS... -g
>>>
>>
>>
>> *** Wrapper compiler final setup
>>> checking for perl... /usr/bin/perl
>>> checking for OPAL CPPFLAGS...
>>> checking for OPAL CFLAGS... -pthread
>>> checking for OPAL CXXFLAGS... -pthread
>>> checking for OPAL LDFLAGS...
>>> checking for OPAL LIBS... -ldl -lm dummy mt
>>> checking for OPAL extra include dirs...
>>> checking for ORTE CPPFLAGS...
>>> checking for ORTE CXXFLAGS... -pthread
>>> checking for ORTE CFLAGS... -pthread
>>> checking for ORTE LDFLAGS...
>>> checking for ORTE LIBS... -ldl -lm dummy mt
>>> checking for ORTE extra include dirs...
>>> checking for OMPI CPPFLAGS...
>>> checking for OMPI CFLAGS... -pthread
>>> checking for OMPI CXXFLAGS... -pthread
>>> checking for OMPI FFLAGS... -pthread
>>> checking for OMPI FCFLAGS... -pthread
>>> checking for OMPI LDFLAGS...
>>> checking for OMPI LIBS... -ldl -lm dummy mt
>>> checking for OMPI extra include dirs...
>>> *** Final output
>>> [....]
>>
>>
>>
>> The presence of "dummy mt" in the LIBS vars renders the resulting wrapper
>> compilers unusable.
>>
>> This is a VPATH (blddir != srcdir) build and it appears that something is
>> looking for a Makefile in [srcdir]/opal/libltdl when it almost certainly
>> should be looking in [blddir]/opal/libltdl.
>>
>> -Paul
>>
>> --
>> Paul H. Hargrove PHHargrove_at_[hidden]
>> Future Technologies Group
>> HPC Research Department Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Paul H. Hargrove PHHargrove_at_[hidden]
> Future Technologies Group
> HPC Research Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>

-- 
Paul H. Hargrove                          PHHargrove_at_[hidden]
Future Technologies Group
HPC Research Department                   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900