laration specifiers or '...'
>>> before string constant
>>> extern void *realloc (void *__ptr, size_t __size)
>>> ^
>>> /usr/include/malloc.h:49:1: error: expected declaration specifiers or '...'
>>> before numeric constant
>>> In file included fr
nstant
> > In file included from ../../../opal/include/opal_config.h:2750:0,
> > from base/mpool_base_frame.c:21:
> > ../../../opal/include/opal_config_bottom.h:393:33: error: expected
> > declaration specifiers or '...' before '(' token
>
_free((ptr), __FILE__, __LINE__)
> ^
> In file included from base/mpool_base_frame.c:28:0:
> /usr/include/malloc.h:53:1: error: expected declaration specifiers or '...'
> before string constant
> extern void free (void *__ptr) __THROW;
> ^
>
tern void free (void *__ptr) __THROW;
^
/usr/include/malloc.h:53:1: error: expected declaration specifiers or '...'
before numeric constant
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
Sent: Monday, August 04, 2014 10:09 AM
To: Open MPI Developers
Subje
I believe the issue is actually in opal/util/malloc.h, Howard. I noticed this
while looking around this weekend - someone included opal_config.h in the
malloc.h file even though it explicitly says "DON'T DO THIS" in that header
file.
#ifndef OPAL_MALLOC_H
#define OPAL_MALLOC_H
#include "opal_
Hi Folks,
As I said last week, I'm noticing now that on my opensuse 13.1 system and gcc
4.8.1, when I do a fresh
checkout of trunk ompi and try to build, without any configure options,
mca_base_mpool_frame.c
does not compile.
The reason is there is a conflict in opal_config_bottom.h and the co
