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

Comparing EV/Makefile.PL (file contents):
Revision 1.28 by root, Fri Dec 21 04:41:12 2007 UTC vs.
Revision 1.67 by root, Fri Dec 20 21:05:49 2019 UTC

1use 5.006; 1use strict qw(vars subs);
2 2use Canary::Stability EV => 1, 5.008002;
3use Config; 3use Config;
4use ExtUtils::MakeMaker; 4use ExtUtils::MakeMaker;
5 5
6sub have_inc($) {
7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}
8}
9
10my $DEFINE;
11
6unless (-e "libev/ev_epoll.c") { 12unless (-e "libev/ev_iouring.c") {
7 print <<EOF; 13 print <<EOF;
8 14
9*** 15***
10*** 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,
11*** 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
34 40
35*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 41*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
36 42
37 43
38POSIX optionally offers support for a monotonic clock source. EV 44POSIX optionally offers support for a monotonic clock source. EV
39can take advantage of this clock source to detect time jumps 45can take advantage of this clock source to detect time jumps more
40reliably. Unfortunately, some systems are bound to be broken, so you can 46reliably. Unfortunately, some systems are bound to be broken, so you can
41disable this here: you can completely disable the detection and use of 47disable this here: you can completely disable the detection and use of
42the monotonic clock by answering 'n' here. Support for this clock type 48the monotonic clock by answering 'n' here. Support for this clock type
43will otherwise be autodetected at both compile- and runtime. 49will otherwise be autodetected at both compile- and runtime. (this setting
50currently affects the use of nanosleep over select as well).
44 51
45EOF 52EOF
46 53
47$DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/)); 54unless (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/) {
55 $DEFINE .= " -DEV_USE_MONOTONIC=0";
56}
48 57
49print <<EOF; 58print <<EOF;
50 59
51*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 60*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
52 61
53 62
54POSIX optionally offers support for a (potentially) high-resolution 63POSIX optionally offers support for a (potentially) high-resolution
55realtime clock interface. In a good implementation, using it is faster 64realtime clock interface. In a good implementation, using it is faster
56than the normal method of using gettimeofday. Unfortunately, this option 65than the normal method of using gettimeofday. Unfortunately, this option
57is also bound to be broken on some systems, so you can disable use and 66is also bound to be broken on some systems, and current EV versions do not
58probing of this feature altogether here. Otherwise support for this clock 67actually call gettimeofday very often, so it defaults to no.
59type will be autodetected at compiletime.
60 68
61EOF 69EOF
62 70
63$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "y") =~ /[yY]/)); 71$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));
64 72
65print <<EOF; 73print <<EOF;
66 74
67*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 75*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
68 76
69 77
70EV can use various backends with various portability issue. The select 78EV can use various backends with various portability issues. The select
71backend is the most portable and makes for a good fallback, but it can be 79backend is the most portable and makes for a good fallback, but it can be
72limited to a low number of file descriptors and/or might not compile. If 80limited to a low number of file descriptors and/or might not compile. If
73you have problems with compiling ev_select.c, you might try to play around 81you have problems with compiling ev_select.c, you might try to play around
74with disabling it here, or forcing it to use the fd_set provided by your 82with disabling it here, or forcing it to use the fd_set provided by your
75OS, via the next question. I highly recommend keeping it in. 83OS, via the next question. I highly recommend keeping it in.
92 100
93EOF 101EOF
94 102
95 if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) { 103 if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) {
96 $DEFINE .= " -DEV_SELECT_USE_FD_SET"; 104 $DEFINE .= " -DEV_SELECT_USE_FD_SET";
97 } 105 }
98} else { 106} else {
99 $DEFINE .= " -DEV_USE_SELECT=0"; 107 $DEFINE .= " -DEV_USE_SELECT=0";
100} 108}
101 109
102print <<EOF; 110print <<EOF;
103 111
104*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 112*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
105 113
106 114
107The 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
108and 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
109doesn'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
110the 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.
111 119
112EOF 120EOF
113 121
114$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (-e "/usr/include/poll.h") ? "y" : "n") =~ /[yY]/)); 122$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/));
115 123
116print <<EOF; 124print <<EOF;
117 125
118*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 126*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
119 127
126fall back to using select when epoll isn't available. If unsure, accept 134fall back to using select when epoll isn't available. If unsure, accept
127the default. 135the default.
128 136
129EOF 137EOF
130 138
139my $can_epoll = have_inc "sys/epoll.h";
140$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
131$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", (-e "/usr/include/sys/epoll.h") ? "y" : "n") =~ /[yY]/)); 141$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));
132 142
133print <<EOF; 143print <<EOF;
134 144
135*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 145*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
136 146
137 147
138Similarly to the epoll backend above, EV can take advantage of kqueue on 148Linux 4.18 introduced another event polling interface, this time using
139many BSD systems. Support for kqueue will be detected at runtime, with a 149the Linux AIO API. While this API is far superior to epoll and almost
140safe fallback to other methods when it cannot be used. 150rivals kqueue, it also suffers from the same issues as kqueue typically
151does: only a subset of file types are supported (as of 4.19, I have seen
152eventfd, pipes, sockets files and some devices, but no ttys). It also
153is subject arbitrary system-wide limits imposed on it. Therefore, this
154backend is not used by default, even when it is compiled in, and you have
155to request it explicitly, e.g. with LIBEV_FLAGS=64. If unsure, accept the
156default.
141 157
158EOF
159
160my $can_linuxaio = have_inc "linux/aio_abi.h";
161$can_linuxaio = $ENV{EV_LINUXAIO} if exists $ENV{EV_LINUXAIO};
162$can_linuxaio = 0 + (prompt ("Enable linux aio backend (y/n)?", $can_linuxaio ? "y" : "n") =~ /[yY]/);
163$DEFINE .= " -DEV_USE_LINUXAIO=$can_linuxaio";
164
165if ($can_linuxaio) {
166print <<EOF;
167
168*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
169
170
171The previously mentioned Linux AIO backend is experimental and will not
172be used unless requested explicitly. You can, howeer, choose to make ti a
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.
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
142Note that kqueue is broken on most operating systems, so it defaults to 235Note that kqueue is subtly broken on most operating systems, so by default
143'n' on everything but netbsd. Here is what we know: 236it won't be used on many platforms, but you can still create your own
237event loop with kqueue backend if you ask specifically for it.
144 238
239Here is what we know:
240
145NetBSD: partially working in at least 3.1. Yeah! :) 241NetBSD: partially working in at least 3.1 and later. Yeah! :)
146FreeBSD: broken on at least 6.2-STABLE, 242FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
147 sockets *likely* work, ptys definitely don't. 243 sockets *likely* work, ptys definitely don't.
148OpenBSD: reports indicate that it likely doesn't work 244OpenBSD: reports indicate that it likely doesn't work
149 (similar problems as on FreeBSD). 245 (similar problems as on FreeBSD).
150OS X: completely, utterly broken on at least < 10.5. 246OS X: completely, utterly broken on at least <= 10.6.
151 247
152EOF 248EOF
153 249
154my $can_kqueue = -e "/usr/include/sys/event.h"; 250# minix has all the header files, but no implementation. won-der-ful.
155 251my $can_kqueue = have_inc "sys/event.h" && $^O ne "minix";
252$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
156$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]/));
157 254
158print <<EOF; 255print <<EOF;
159 256
160*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 257*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
164solaris 10 event port interface. Support for event ports will be detected 261solaris 10 event port interface. Support for event ports will be detected
165at runtime, with a safe fallback to other methods when it cannot be used. 262at runtime, with a safe fallback to other methods when it cannot be used.
166 263
167EOF 264EOF
168 265
169$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/)); 266$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (have_inc "sys/port.h") ? "y" : "n") =~ /[yY]/));
170 267
171print <<EOF; 268print <<EOF;
172 269
173*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 270*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
174 271
176EV needs the functions pthread_atfork and clock_gettime. On most systems 273EV needs the functions pthread_atfork and clock_gettime. On most systems
177you need some special libraries for this (such as -lrt and -lpthread). You 274you need some special libraries for this (such as -lrt and -lpthread). You
178can specify additional libraries to provide these calls (and any other 275can specify additional libraries to provide these calls (and any other
179required by EV) now, or accept the default. 276required by EV) now, or accept the default.
180 277
181EOF 278On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function
279to avoid the dependency on libpthread, and directly uses the clock_gettime
280syscall to avoid a dependency on librt.
182 281
282EOF
283
183$SOLARIS_LIBS = $^O =~ /solaris/ ? " -lsocket -lnsl" : ""; 284my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
184 285my $librt = $^O =~ /linux/i ? "" : "-lpthread -lrt";
286my $LIBS = exists $ENV{EV_LIBS} ? $ENV{EV_LIBS} : "$librt $solaris_libs";
185$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt$SOLARIS_LIBS"; 287$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", $LIBS;
186 288
187 289
188print <<EOF; 290print <<EOF;
189 291
190*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 292*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
191 293
192 294
193A backend of a different kind is the Linux inotify(7) interface, which can 295A backend of a different kind is the Linux inotify(7) interface, which can
194be used to speed up (and reduce resource consumption) of stat watchers. If 296be used to speed up (and reduce resource consumption) of stat watchers. If
195you have it, it is usually a good idea to enable it. 297you have the include file and libc support for it, it is usually a good
298idea to enable it, as kernel availability is detected at runtime.
196 299
197EOF 300EOF
198 301
199my $can_inotify = -e "/usr/include/sys/inotify.h"; 302my $can_inotify = have_inc "sys/inotify.h";
200 303$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
201$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/)); 304$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
202 305
203print <<EOF; 306print <<EOF;
204 307
205*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 308*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
206 309
207 310
208EOF 311Another useful bit of functionality is the Linux eventfd, which is useful
312for faster signal handling (don't care) and intra-thread communications
313(more relevant). Kernel support for this will be probed at runtime, but
314your libc must contain the necessary wrapper. Glibc 2.7 and later should
315have this wrapper.
209 316
317EOF
318
319my $can_eventfd = have_inc "sys/eventfd.h";
320$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
321$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
322
323print <<EOF;
324
325*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
326
327
328Another sometimes useful bit of functionality is the Linux signalfd, which
329is useful for faster signal handling (don't care). Kernel support for
330this will be probed at runtime, but your libc must contain the necessary
331wrapper. Glibc 2.7 and later should have this wrapper.
332
333EOF
334
335my $can_signalfd = have_inc "sys/signalfd.h";
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]/));
338
339print <<EOF;
340
341*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
342
343
344Linux kernels can notify userspace about realtime clock timejumps
345using timerfd. Libev by default will try to take advantage of this if
346possible. You can completely disable the detection and use of timerfd for
347this purpose by answering 'n' here. Support for timerfd will otherwise be
348autodetected at both compile- and runtime.
349
350EOF
351
352unless (prompt ("Enable optional support for timerfd to detect timejumps (y/n)?", "y") =~ /[yY]/) {
353 $DEFINE .= " -DEV_USE_TIMERFD=0";
354}
355
356print <<EOF;
357
358*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
359
360
361Libev contains numerous internal assert() invocations to check for
362consistency and user errors. These are normally enabled, but most
363perl builds disable this error reporting mechanism by default. You
364can re-enable these asserts here. Enabling them might help you catch
365programming bugs earlier, but might cause a small slowdown. Also, failures
366will be reported by aboritng your program, instead of throwing a perl
367exception.
368
369If unsure, enable this if you only use this perl installation for
370development, and leave it off for use in production environments.
371
372EOF
373
374my $enable_assertions = 0;
375$enable_assertions = 0 + (prompt ("Make sure assertions are enabled? (y/n)?", $enable_assertions ? "y" : "n") =~ /[yY]/);
376$DEFINE .= " -DEV_ENABLE_ASERTIONS=1" if $enable_assertions;
377
378print <<EOF;
379
380*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
381
382
383Very rarely, people want to tweak EV even more, e.g. to exclude
384or include certain watcher types or backends. This can be done by adding
385extra -D options here, or via the EV_EXTRA_DEFS environment variable.
386
387For example, if you run into compilation problems because of missing memory
388fences (or you just want extra performance), you can tell EV to not support
389smp and threads via -DEV_NO_THREADS.
390
391Most people would just press enter.
392
393EOF
394
395$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
396
397print <<EOF;
398
399*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
400
401
402EOF
403
210my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : (); 404my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();
211 405
212WriteMakefile( 406WriteMakefile(
213 dist => { 407 dist => {
214 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;', 408 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
215 COMPRESS => 'gzip -9v', 409 COMPRESS => 'gzip -9v',
216 SUFFIX => '.gz', 410 SUFFIX => '.gz',
217 }, 411 },
218 depend => { 412 depend => {
219 "EV.c" => "EV/EVAPI.h " 413 "EV.c" => "EV/EVAPI.h "
220 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c " 414 . "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 "
221 . "libev/event.h libev/event.c libev/ev_vars.h libev/ev_wrap.h", 415 . "libev/ev_vars.h libev/ev_wrap.h",
222 }, 416 },
223 INC => "-Ilibev", 417 INC => "-Ilibev",
224 DEFINE => "$DEFINE", 418 DEFINE => "$DEFINE",
225 NAME => "EV", 419 NAME => "EV",
226 LIBS => [$LIBS], 420 LIBS => [$LIBS],
227 PREREQ_PM => { 421 PREREQ_PM => {
228 @anyevent, 422 @anyevent,
423 "common::sense" => 0,
229 }, 424 },
425 CONFIGURE_REQUIRES => { "ExtUtils::MakeMaker" => 6.52, "Canary::Stability" => 0 },
230 VERSION_FROM => "EV.pm", 426 VERSION_FROM => "EV.pm",
231 PM => { 427 PM => {
232 'EV.pm' => '$(INST_LIBDIR)/EV.pm', 428 'EV.pm' => '$(INST_LIB)/EV.pm',
233 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', 429 'EV/EVAPI.h' => '$(INST_LIB)/EV/EVAPI.h',
234 'EV/MakeMaker.pm' => '$(INST_LIBDIR)/EV/MakeMaker.pm', 430 'EV/MakeMaker.pm' => '$(INST_LIB)/EV/MakeMaker.pm',
235 'libev/ev.h' => '$(INST_LIBDIR)/EV/ev.h', 431 'libev/ev.h' => '$(INST_LIB)/EV/ev.h',
432 'libev/ev.pod' => '$(INST_LIB)/EV/libev.pod',
236 }, 433 },
434 MAN3PODS => {
435 'EV.pm' => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
436 'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
437 'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
438 },
237); 439);
238 440
239

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines