Re: [OMPI devel] Patcher on MacOS
I didn't start working on a patch -- all I did was open #5671. > On Sep 28, 2018, at 5:51 PM, Nathan Hjelm via devel > wrote: > > Nope. We just never bothered to disable it on osx. I think Jeff was working > on a patch. > > -Nathan > >> On Sep 28, 2018, at 3:21 PM, Barrett, Brian via devel >> wrote: >> >> 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 >> devel@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/devel > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Patcher on MacOS
I asked a similar question recently: https://github.com/open-mpi/ompi/issues/5671 > On Sep 28, 2018, at 5:21 PM, Barrett, Brian via devel > wrote: > > 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 > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Patcher on MacOS
Nope. We just never bothered to disable it on osx. I think Jeff was working on a patch. -Nathan > On Sep 28, 2018, at 3:21 PM, Barrett, Brian via devel > wrote: > > 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 > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
