On Feb 26, 2012, at 1:32 AM, Paul Hargrove 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?
In the example you gave, the library you were adding ("dummy mt") has a space
in it. We don't handle that case - that was my point.
However, your other note is also correct - the vpath builds need to be fixed
with the other CMR.
>
> 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 <r...@open-mpi.org> 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 phhargr...@lbl.gov
>> Future Technologies Group
>> HPC Research Department Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> _______________________________________________
>> 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
>
>
>
> --
> Paul H. Hargrove phhargr...@lbl.gov
> Future Technologies Group
> HPC Research Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
