| … | |
… | |
| 333 | EOF |
333 | EOF |
| 334 | |
334 | |
| 335 | my $can_signalfd = have_inc "sys/signalfd.h"; |
335 | my $can_signalfd = have_inc "sys/signalfd.h"; |
| 336 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
336 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
| 337 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
337 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
|
|
338 | |
|
|
339 | print <<EOF; |
|
|
340 | |
|
|
341 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
342 | |
|
|
343 | |
|
|
344 | Linux kernels can notify userspace about realtime clock timejumps |
|
|
345 | using timerfd. Libev by default will try to take advantage of this if |
|
|
346 | possible. You can completely disable the detection and use of timerfd for |
|
|
347 | this purpose by answering 'n' here. Support for timerfd will otherwise be |
|
|
348 | autodetected at both compile- and runtime. |
|
|
349 | |
|
|
350 | EOF |
|
|
351 | |
|
|
352 | unless (prompt ("Enable optional support for timerfd to detect timejumps (y/n)?", "y") =~ /[yY]/) { |
|
|
353 | $DEFINE .= " -DEV_USE_TIMERFD=0"; |
|
|
354 | } |
| 338 | |
355 | |
| 339 | print <<EOF; |
356 | print <<EOF; |
| 340 | |
357 | |
| 341 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
358 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
| 342 | |
359 | |
