+1 on what George says.
If you look at various components around Open MPI, many component and/or module
functions *are* actually static because they aren't needed outside that .c file
in the component. It just depends on the individual component code base.
> On Feb 25, 2016, at 8:48 PM, Georg
On Feb 25, 2016, at 7:02 PM, Gilles Gouaillardet
wrote:
>
> on master/v2.x, you also have to
>
> rm -f opal/mca/btl/lf/.opal_ignore
Gilles is exactly right. It's a bit buried in the autogen output, but you can
see this:
--- Found opal / btl / lf component
=> Ignored (found .opal_ignore
Durga,
If we declare these functions as static we are forced to have the functions
defined and used in the same source file. The fact that they are declared
as extern allows us to use these functions in all files in the same
component. Once linked in the corresponding shared library, all symbols n
Hello Gilles
Thank you; the build is successful now.
I do have a generic, unrelated question, though:
I really appreciate how all the principle of object oriented design
principles have been used in OMPI architecture and have been implemented in
a language that is not object oriented. It is a te
on master/v2.x, you also have to
rm -f opal/mca/btl/lf/.opal_ignore
(and this file would have been .ompi_ignore on v1.10)
Cheers,
Gilles
On Fri, Feb 26, 2016 at 7:44 AM, dpchoudh . wrote:
> Hello Jeff and other developers:
>
> Attached are five files:
> 1-2: Full output from autogen.pl and co
Hello Jeff and other developers:
Attached are five files:
1-2: Full output from autogen.pl and configure, captured with: ./ 2>&1
| tee .log
3. Makefile.am of the specific BTL directory
4. configure.m4 of the same directory
5. config.log, as generated internally by autotools
Thank you
Durga
Life
> On Feb 25, 2016, at 3:39 PM, Paul Hargrove wrote:
>
> A "bare" function name (without parens) is the address of the function, which
> can be converted to an int, long, etc.
> So the "rank" identifier can validly refer to the function in this context.
I understand that there's logic behind thi
On Thu, Feb 25, 2016 at 1:27 PM, Jeff Squyres (jsquyres) wrote:
> I still find it fairly astounding that the naked word "rank" (vs "rank()")
> is ambiguous with a variable and a function call. I wouldn't be surprised
> by this in a scripting language; if this really is true in C++, that's
> quit
On Feb 25, 2016, at 3:14 PM, Dave Goodell (dgoodell) wrote:
>
>> So you can't have a local variable named "rank" any more? That's...
>> terrible!
>
> Or you could avoid "using namespace std". Or qualify it using "::rank" (I
> think, my C++ is rusty).
Yeah, fair enough. But I don't think we
On Thu, Feb 25, 2016 at 1:05 PM, Jeff Squyres (jsquyres) wrote:
> On Feb 25, 2016, at 2:59 PM, Paul Hargrove wrote:
> >
> > Not an error - a new API in C++11 to get number of dimensions in a
> multi-dimensional array.
> > http://en.cppreference.com/w/cpp/types/rank
>
> So you can't have a local
On Feb 25, 2016, at 4:05 PM, Jeff Squyres (jsquyres) wrote:
>
> On Feb 25, 2016, at 2:59 PM, Paul Hargrove wrote:
>>
>> Not an error - a new API in C++11 to get number of dimensions in a
>> multi-dimensional array.
>> http://en.cppreference.com/w/cpp/types/rank
>
> So you can't have a local v
On Feb 25, 2016, at 2:59 PM, Paul Hargrove wrote:
>
> Not an error - a new API in C++11 to get number of dimensions in a
> multi-dimensional array.
> http://en.cppreference.com/w/cpp/types/rank
So you can't have a local variable named "rank" any more? That's... terrible!
--
Jeff Squyres
jsqu
Jeff,
Not an error - a new API in C++11 to get number of dimensions in a
multi-dimensional array.
http://en.cppreference.com/w/cpp/types/rank
-Paul
On Thu, Feb 25, 2016 at 12:06 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> That looks like the c++ headers in gcc 6.0 beta are busted
That looks like the c++ headers in gcc 6.0 beta are busted - it looks like
there's a "rank" variable in the local scope from the STL headers somehow...?
Sent from my phone. No type good.
> On Feb 25, 2016, at 10:52 AM, Adrian Reber wrote:
>
> I installed a pre-release gcc 6.0
>
> gcc version
I installed a pre-release gcc 6.0
gcc version 6.0.0 20160221 (experimental) (GCC)
on my MTT systems (ppc64 and x86_64) and I now get a
test build failure:
https://mtt.open-mpi.org/index.php?do_redir=2269
Just as a FYI.
Adrian
15 matches
Mail list logo
