FWIW: I wouldn’t have seen that because I don’t have IB on my system.
> On Feb 17, 2016, at 10:11 AM, Nysal Jan K A <jny...@gmail.com> wrote:
>
> So this seems to be still broken.
>
> mca_btl_openib.so: undefined symbol: opal_memory_linux_malloc_set_alignment
>
> I built with "--with-memory-manager=none"
>
> Regards
> --Nysal
>
> On Tue, Feb 16, 2016 at 10:19 AM, Ralph Castain <r...@open-mpi.org
> <mailto:r...@open-mpi.org>> wrote:
> 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 didn’t create a problem if the referenced component was
> not built. I’m not saying it was a good thing to do, but we spent a lot of
> time discussing it and figuring out how to do it without causing the problem.
>
> So whatever was done missed those precautions and introduced this symbol
> regardless of the configuration.
>
>
>> On Feb 15, 2016, at 8:39 PM, Gilles Gouaillardet <gil...@rist.or.jp
>> <mailto:gil...@rist.or.jp>> wrote:
>>
>> Ralph,
>>
>> this is being discussed at https://github.com/open-mpi/ompi/pull/1351
>> <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 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
>>>
>>>
>>>
>>> _______________________________________________
>>> devel mailing list
>>> de...@open-mpi.org <mailto:de...@open-mpi.org>
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
>>> Link to this post:
>>> http://www.open-mpi.org/community/lists/devel/2016/02/18598.php
>>> <http://www.open-mpi.org/community/lists/devel/2016/02/18598.php>
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org <mailto:de...@open-mpi.org>
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/02/18599.php
>> <http://www.open-mpi.org/community/lists/devel/2016/02/18599.php>
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org <mailto:de...@open-mpi.org>
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> <http://www.open-mpi.org/mailman/listinfo.cgi/devel>
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/02/18600.php
> <http://www.open-mpi.org/community/lists/devel/2016/02/18600.php>
>
> _______________________________________________
> 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/2016/02/18601.php
