ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/Makefile.PL
(Generate patch)

Comparing EV/Makefile.PL (file contents):
Revision 1.59 by root, Sat Jun 22 16:43:05 2019 UTC vs.
Revision 1.65 by root, Fri Nov 22 14:43:49 2019 UTC

… …
7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} 7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}
8} 8}
9 9
10my $DEFINE; 10my $DEFINE;
11 11
12unless (-e "libev/ev_epoll.c") { 12unless (-e "libev/ev_iouring.c") {
13 print <<EOF; 13 print <<EOF;
14 14
15*** 15***
16*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV, 16*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV,
17*** you also have to check-out the "libev" module from the same CVS 17*** you also have to check-out the "libev" module from the same CVS
… …
113 113
114 114
115The second very portable backend is poll(2). It does not exist on windows 115The second very portable backend is poll(2). It does not exist on windows
116and various versions of Mac OS X (and on the other versions it simply 116and various versions of Mac OS X (and on the other versions it simply
117doesn't work), but works basically everywhere else. It is recommended to use 117doesn't work), but works basically everywhere else. It is recommended to use
118the default here unless you run into compile problems in ev_poll.c. 118the default here unless you run into compilation problems in ev_poll.c.
119 119
120EOF 120EOF
121 121
122$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/)); 122$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/));
123 123
… …
157 157
158EOF 158EOF
159 159
160my $can_linuxaio = have_inc "linux/aio_abi.h"; 160my $can_linuxaio = have_inc "linux/aio_abi.h";
161$can_linuxaio = $ENV{EV_LINUXAIO} if exists $ENV{EV_LINUXAIO}; 161$can_linuxaio = $ENV{EV_LINUXAIO} if exists $ENV{EV_LINUXAIO};
162$DEFINE .= " -DEV_USE_LINUXAIO=" . (0 + (prompt ("Enable linux aio backend (y/n)?", $can_linuxaio ? "y" : "n") =~ /[yY]/)); 162$can_linuxaio = 0 + (prompt ("Enable linux aio backend (y/n)?", $can_linuxaio ? "y" : "n") =~ /[yY]/);
163$DEFINE .= " -DEV_USE_LINUXAIO=$can_linuxaio";
163 164
165if ($can_linuxaio) {
164print <<EOF; 166print <<EOF;
165 167
166*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 168*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
167 169
168 170
169Similarly to the epoll backend above, EV can take advantage of kqueue on 171The previously mentioned Linux AIO backend is experimental and will not
170many BSD systems. Support for kqueue will be detected at runtime, with a 172be used unless requested explicitly. You can, howeer, choose to make ti a
171safe fallback to other methods when it cannot be used. 173recommended basckend, which means it will be chosen if available even when
174not explicitly asked for, in preference to epoll on GNU/Linux. This option
175is likely temporary. When unsure, accept the default.
172 176
177EOF
178
179my $recommend_linuxaio = 0;
180$recommend_linuxaio = $ENV{EV_RECOMMEND_LINUXAIO} if exists $ENV{EV_RECOMMEND_LINUXAIO};
181$recommend_linuxaio = 0 + (prompt ("Treat linux aio as a recommended backend (y/n)?", $recommend_linuxaio ? "y" : "n") =~ /[yY]/);
182$DEFINE .= " -DEV_RECOMMEND_LINUXAIO=$recommend_linuxaio";
183}
184
185print <<EOF;
186
187*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
188
189
190Linux 4.19 introduced another event polling interface, "io_uring". While
191this API is far superior to epoll and almost rivals linuxaio, it also
192suffers from the same issues as kqueue typically does: only a subset of
193file types are supported (as of 5.2). It is also very buggy still, and
194most importantly, very very slow for most workloads. Therefore, this
195backend is not used by default, even when it is compiled in, and you have
196to request it explicitly, e.g. with LIBEV_FLAGS=128. If unsure, accept the
197default.
198
199EOF
200
201my $can_iouring = have_inc "linux/fs.h";
202$can_iouring = $ENV{EV_IOURING} if exists $ENV{EV_IOURING};
203$can_iouring = 0 + (prompt ("Enable linux io_uring backend (y/n)?", $can_iouring ? "y" : "n") =~ /[yY]/);
204$DEFINE .= " -DEV_USE_IOURING=$can_iouring";
205
206if ($can_iouring) {
207print <<EOF;
208
209*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
210
211
212The previously mentioned Linux io_uring is experimental and will not be
213used unless requested explicitly. You can, howeer, choose to make ti a
214recommended basckend, which means it will be chosen if available even when
215not explicitly asked for, in preference to epoll on GNU/Linux. This option
216is likely temporary. When unsure, accept the default.
217
218EOF
219
220my $recommend_iouring = 0;
221$recommend_iouring = $ENV{EV_RECOMMEND_IOURING} if exists $ENV{EV_RECOMMEND_IOURING};
222$recommend_iouring = 0 + (prompt ("Treat io_uring as a recommended backend (y/n)?", $recommend_iouring ? "y" : "n") =~ /[yY]/);
223$DEFINE .= " -DEV_RECOMMEND_IOURING=$recommend_iouring";
224}
225
226print <<EOF;
227
228*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
229
230
231EV can take advantage of kqueue on many BSD systems. Support for kqueue
232will be detected at runtime, with a safe fallback to other methods when it
233cannot be used.
234
173Note that kqueue is broken on most operating systems, so by default it 235Note that kqueue is subtly broken on most operating systems, so by default
174won't be used on many platforms, but you can still create your own event 236it won't be used on many platforms, but you can still create your own
175loop with kqueue backend if you ask specifically for it. 237event loop with kqueue backend if you ask specifically for it.
176 238
177Here is what we know: 239Here is what we know:
178 240
179NetBSD: partially working in at least 3.1 and later. Yeah! :) 241NetBSD: partially working in at least 3.1 and later. Yeah! :)
180FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, 242FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
… …
183 (similar problems as on FreeBSD). 245 (similar problems as on FreeBSD).
184OS X: completely, utterly broken on at least <= 10.6. 246OS X: completely, utterly broken on at least <= 10.6.
185 247
186EOF 248EOF
187 249
250# minix has all the header files, but no implementation. won-der-ful.
188my $can_kqueue = have_inc "sys/event.h"; 251my $can_kqueue = have_inc "sys/event.h" && $^O ne "minix";
189$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE}; 252$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
190$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/)); 253$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
191 254
192print <<EOF; 255print <<EOF;
193 256
… …
276print <<EOF; 339print <<EOF;
277 340
278*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 341*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
279 342
280 343
344Libev contains numerous internal assert() invocations to check for
345consistency and user errors. These are normally enabled, but most
346perl builds disable this error reporting mechanism by default. You
347can re-enable these asserts here. Enabling them might help you catch
348programming bugs earlier, but might cause a small slowdown. Also, failures
349will be reported by aboritng your program, instead of throwing a perl
350exception.
351
352If unsure, enable this if you only use this perl installation for
353development, and leave it off for use in production environments.
354
355EOF
356
357my $enable_assertions = 0;
358$enable_assertions = 0 + (prompt ("Make sure assertions are enabled? (y/n)?", $enable_assertions ? "y" : "n") =~ /[yY]/);
359$DEFINE .= " -DEV_ENABLE_ASERTIONS=1" if $enable_assertions;
360
361print <<EOF;
362
363*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
364
365
281Very rarely, people want to tweak EV even more, e.g. to exclude 366Very rarely, people want to tweak EV even more, e.g. to exclude
282or include certain watcher types or backends. This can be done by adding 367or include certain watcher types or backends. This can be done by adding
283extra -D options here, or via the EV_EXTRA_DEFS environment variable. 368extra -D options here, or via the EV_EXTRA_DEFS environment variable.
284 369
285For example, if you run into compile problems because of missing memory 370For example, if you run into compilation problems because of missing memory
286fences (or you just want extra performance), you can tell EV to not support 371fences (or you just want extra performance), you can tell EV to not support
287smp and threads via -DEV_NO_THREADS. 372smp and threads via -DEV_NO_THREADS.
288 373
289Normal persons just press enter. 374Normal persons just press enter.
290 375
… …
307 COMPRESS => 'gzip -9v', 392 COMPRESS => 'gzip -9v',
308 SUFFIX => '.gz', 393 SUFFIX => '.gz',
309 }, 394 },
310 depend => { 395 depend => {
311 "EV.c" => "EV/EVAPI.h " 396 "EV.c" => "EV/EVAPI.h "
312 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c " 397 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c libev/ev_linuxaio.c "
313 . "libev/ev_vars.h libev/ev_wrap.h", 398 . "libev/ev_vars.h libev/ev_wrap.h",
314 }, 399 },
315 INC => "-Ilibev", 400 INC => "-Ilibev",
316 DEFINE => "$DEFINE", 401 DEFINE => "$DEFINE",
317 NAME => "EV", 402 NAME => "EV",
… …
334 'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)', 419 'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
335 'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)', 420 'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
336 }, 421 },
337); 422);
338 423
339

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines