Sorry folks -- I hadn't noticed that several pending 1.5 CMRs hadn't been
rolled in yet. I'll ping George.
On Feb 26, 2012, at 5:42 PM, Paul Hargrove wrote:
>
>
> On Sun, Feb 26, 2012 at 6:37 AM, Ralph Castain wrote:
> [snip]
> In the example you gave, the library you
On Sun, Feb 26, 2012 at 6:37 AM, Ralph Castain wrote:
[snip]
> 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.
>
But "dummy mt" was injected by the broken configure logic, not by me. It
was
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
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
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
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?
>
> [...]
> ***
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
>