Is there any practical reason to have the memory patcher component enabled for MacOS? As far as I know, we don’t have any transports which require memory hooks on MacOS, and with the recent deprecation of the syscall interface, it emits a couple of warnings. It would be nice to crush said warnings and the easiest way would be to not build the component.
Thoughts? Brian _______________________________________________ devel mailing list email@example.com https://lists.open-mpi.org/mailman/listinfo/devel