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_config.h" #include <stdlib.h> /* * THIS FILE CANNOT INCLUDE ANY OTHER OPAL HEADER FILES!!! * * It is included via <opal_config_bottom.h>. Hence, it should not * include ANY other files, nor should it include "opal_config.h". * */ Don't know why someone did that, but you might see if it fixes your problem On Aug 4, 2014, at 9:00 AM, Pritchard Jr., Howard <howa...@lanl.gov> wrote: > 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 contents of > malloc.h, > which for my system is pulled in by the preprocessor. > > If I undefine HAVE_MALLOC_H in this file, the code compiles fine. > Alternatively, > one can also move the malloc.h include prior to the opal_config.h include and > things > work. Alternatively, one can add the OPAL_DISABLE_ENABLE_MEM_DEBUG define > as in mpool_base_lookup.c , and the compile problem similarly goes away. > > I’d like to check in a fix for this. I’d prefer to just move the std include > files ahead > of the opal_config.h include. I’d like to do this today unless someone > objects. > > I’m somewhat surprised I’m the only one seeing this though. > > Howard > > > ------------------------------------------------- > Howard Pritchard > HPC-5 > Los Alamos National Laboratory > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/08/15495.php
