On Jul 17, 2013, at 12:16 PM, Nathan Hjelm wrote:
> As Ralph suggested you need to pass the --level or -l option to see all the
> variables. --level 9 will print everything. If you think there are variables
> everyday users should see you are welcome to change them to OPAL_INFO_LVL_1.
> We are
On Wed, Jul 17, 2013 at 03:04:06AM +0200, George Bosilca wrote:
> I would like to question the choice for the new ? spartan ompi_info output? I
> would not mind restoring the default behavior, aka. have a verbose "--all",
> instead of some [random] MCA params.
As Ralph suggested you need to pass
On Jul 17, 2013, at 11:07 AM, Nathan Hjelm wrote:
> Ugh. Thats unfortunate. I guess I could add a type_size.h and put the static
> inline function in there then put the definions of MPI_Type_size_x and
> MPI_Type_size in their own files. This way I can still avoid the extra code.
Or move the
On Wed, Jul 17, 2013 at 03:02:16PM +, Jeff Squyres (jsquyres) wrote:
> On Jul 17, 2013, at 10:48 AM, Nathan Hjelm wrote:
>
> > I must be missing something here. type_size.c contains MPI_Type_size and
> > MPI_Type_size_x and I see all the MPI and PMPI variants in the resulting
> > .so, .dyli
On Jul 17, 2013, at 10:48 AM, Nathan Hjelm wrote:
> I must be missing something here. type_size.c contains MPI_Type_size and
> MPI_Type_size_x and I see all the MPI and PMPI variants in the resulting .so,
> .dylib, and .a.
If you have a nathan.c file with:
-
void MPI_foo() { ... }
void M
On Tue, Jul 16, 2013 at 09:03:22PM +, Jeff Squyres (jsquyres) wrote:
> On Jul 16, 2013, at 4:54 PM, Nathan Hjelm wrote:
>
> >> 3. We had a policy that we only export one single MPI level function per
> >> file in the mpi directory. You changed this as some of the files exports
> >> now two
