It is very easy to reproduce - configure with:
enable_mem_debug=no
enable_mem_profile=no
enable_memchecker=no
with_memory_manager=no
I’m not sure which of those is required. However, your assertion is incorrect.
The person who introduced the original violation went to great lengths to
ensure it
Ralph,
this is being discussed at https://github.com/open-mpi/ompi/pull/1351
btw, how do you get this warning ? i do not see it.
fwiw, the abstraction violation was kind of already here, so i am
surprised it pops up now only
Cheers,
Gilles
On 2/16/2016 1:17 PM, Ralph Castain wrote:
Looks l
Looks like someone broke the master build on Linux:
../../../ompi/.libs/libmpi.so: undefined reference to
`opal_memory_linux_malloc_init_hook'
I suspect it was a hard-coded reference to some component’s variable?
Ralph
