… | |
… | |
339 | print <<EOF; |
339 | print <<EOF; |
340 | |
340 | |
341 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
341 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
342 | |
342 | |
343 | |
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 | } |
|
|
355 | |
|
|
356 | print <<EOF; |
|
|
357 | |
|
|
358 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
359 | |
|
|
360 | |
344 | Libev contains numerous internal assert() invocations to check for |
361 | Libev contains numerous internal assert() invocations to check for |
345 | consistency and user errors. These are normally enabled, but most |
362 | consistency and user errors. These are normally enabled, but most |
346 | perl builds disable this error reporting mechanism by default. You |
363 | perl builds disable this error reporting mechanism by default. You |
347 | can re-enable these asserts here. Enabling them might help you catch |
364 | can re-enable these asserts here. Enabling them might help you catch |
348 | programming bugs earlier, but might cause a small slowdown. Also, failures |
365 | programming bugs earlier, but might cause a small slowdown. Also, failures |
… | |
… | |
369 | |
386 | |
370 | For example, if you run into compilation problems because of missing memory |
387 | For example, if you run into compilation problems because of missing memory |
371 | fences (or you just want extra performance), you can tell EV to not support |
388 | fences (or you just want extra performance), you can tell EV to not support |
372 | smp and threads via -DEV_NO_THREADS. |
389 | smp and threads via -DEV_NO_THREADS. |
373 | |
390 | |
374 | Normal persons just press enter. |
391 | Most people would just press enter. |
375 | |
392 | |
376 | EOF |
393 | EOF |
377 | |
394 | |
378 | $DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}"; |
395 | $DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}"; |
379 | |
396 | |