[
https://issues.apache.org/jira/browse/MESOS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880249#comment-13880249
]
Benjamin Mahler commented on MESOS-895:
---------------------------------------
We could also do this at run-time according to the
[manual|http://doc.dvgu.ru/devel/ev.html#overriding_the_builtin_processing]:
{quote}
Overriding the Built-In Processing
Libev offers no special support for overriding the built-in child processing,
but if your application collides with libev's default child handler, you can
override it easily by installing your own handler for SIGCHLD after
initialising the default loop, and making sure the default loop never gets
destroyed. You are encouraged, however, to use an event-based approach to child
reaping and thus use libev's support for that, so other libev users can use
ev_child watchers freely.
{quote}
> Removal of libev patch
> ----------------------
>
> Key: MESOS-895
> URL: https://issues.apache.org/jira/browse/MESOS-895
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 0.17.0
> Reporter: Timothy St. Clair
>
> The libev patch can easily be removed and update the configuration flags and
> possibly the accompanying code prior to include.
> For configure pass in:
> CFLAGS=-DEV_CHILD_ENABLE=0
> For inclusion:
> #define EV_CHILD_ENABLE 0
> include <ev.h>
> excerpt from maintainer:
> <schmorp> that patch is unnecessary
> <tstclair> schmorp, so if they wanted to just set EV_CHILD_ENABLE=0 they
> could just pass CFLAGS=-DEV_CHILD_ENABLE=0 through.
> <schmorp> tstclair: yes, or use a wrapper
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
