EV/Makefile.PL

use 5.008002;

use strict qw(vars subs);
use Config;
use ExtUtils::MakeMaker;

unless (-e "libev/ev_epoll.c") {
   print <<EOF;

***
*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV,
*** you also have to check-out the "libev" module from the same CVS
*** repository into the EV dir (i.e. EV/libev from outside).
***

EOF
   exit 1;
}

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Welcome to EV configuration. If you are in a hurry, just press return here
and hope for the best. The defaults should usually do.

EOF

if (prompt ("Skip further questions and use defaults (y/n)?", "y") =~ /[yY]/) {
   $ENV{PERL_MM_USE_DEFAULT} = 1;
}

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


POSIX optionally offers support for a monotonic clock source. EV
can take advantage of this clock source to detect time jumps more
reliably. Unfortunately, some systems are bound to be broken, so you can
disable this here: you can completely disable the detection and use of
the monotonic clock by answering 'n' here. Support for this clock type
will otherwise be autodetected at both compile- and runtime. (this setting
currently affects the use of nanosleep over select as well).

EOF

my $DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


POSIX optionally offers support for a (potentially) high-resolution
realtime clock interface. In a good implementation, using it is faster
than the normal method of using gettimeofday. Unfortunately, this option
is also bound to be broken on some systems, and current EV versions do not
actually call gettimeofday very often, so it defaults to no.

EOF

$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


EV can use various backends with various portability issues. The select
backend is the most portable and makes for a good fallback, but it can be
limited to a low number of file descriptors and/or might not compile. If
you have problems with compiling ev_select.c, you might try to play around
with disabling it here, or forcing it to use the fd_set provided by your
OS, via the next question. I highly recommend keeping it in.

EOF

if (prompt ("Enable select backend (y/n)?", "y") =~ /[yY]/) {
   $DEFINE .= " -DEV_USE_SELECT=1";

   print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


The select backend can operate in two modes. One uses the system-provided
fd_set and is usually limited to 1024 file descriptors (64 on windows),
the other requires your header files to define NFDBITS and declare a
suitable fd_mask type. If you run into problems compiling ev_select.c, you
can try forcing the use of the system fd_set here.

EOF

   if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) {
      $DEFINE .= " -DEV_SELECT_USE_FD_SET";
   } 
} else {
   $DEFINE .= " -DEV_USE_SELECT=0";
} 

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


The second very portable backend is poll(2). It does not exist on windows
and various versions of Mac OS X (and on the other versions it simply
doesn't work), but works basically everywhere else. It is recommended to use
the default here unless you run into compile problems in ev_poll.c.

EOF

$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (-e "/usr/include/poll.h") ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Select and poll make it hard to write efficient servers, especially if the
number of active connections is much lower than the watched ones. GNU/Linux
systems have a more scalable method called "epoll", which EV can use. For
this to work, both your kernel and glibc have to support epoll, but if you
can compile it, the detection will be done at runtime, and EV will safely
fall back to using select when epoll isn't available. If unsure, accept
the default.

EOF

my $can_epoll = -e "/usr/include/sys/epoll.h";
$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Similarly to the epoll backend above, EV can take advantage of kqueue on
many BSD systems. Support for kqueue will be detected at runtime, with a
safe fallback to other methods when it cannot be used.

Note that kqueue is broken on most operating systems, so by default it
won't be used on many platforms, but you can still create your own event
loop with kqueue backend if you ask specifically for it.

Here is what we know:

NetBSD:  partially working in at least 3.1 and later. Yeah! :)
FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
         sockets *likely* work, ptys definitely don't.
OpenBSD: reports indicate that it likely doesn't work
         (similar problems as on FreeBSD).
OS X:    completely, utterly broken on at least <= 10.6.

EOF

my $can_kqueue = -e "/usr/include/sys/event.h";
$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Similarly to the kqueue backend above, EV can take advantage of the
solaris 10 event port interface. Support for event ports will be detected
at runtime, with a safe fallback to other methods when it cannot be used.

EOF

$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


EV needs the functions pthread_atfork and clock_gettime. On most systems
you need some special libraries for this (such as -lrt and -lpthread). You
can specify additional libraries to provide these calls (and any other
required by EV) now, or accept the default.

On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function
to avoid the dependency on libpthread, and directly uses the clock_gettime
syscall to avoid a dependency on librt.

EOF

my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
my $librt = $^O =~ /linux/i ? "" : "-lpthread -lrt";
my $LIBS = exists $ENV{EV_LIBS} ? $ENV{EV_LIBS} : "$librt $solaris_libs";
$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", $LIBS;


print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


A backend of a different kind is the Linux inotify(7) interface, which can
be used to speed up (and reduce resource consumption) of stat watchers. If
you have the include file and libc support for it, it is usually a good
idea to enable it, as kernel availability is detected at runtime.

EOF

my $can_inotify = -e "/usr/include/sys/inotify.h";
$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Another useful bit of functionality is the Linux eventfd, which is useful
for faster signal handling (don't care) and intra-thread communications
(more relevant). Kernel support for this will be probed at runtime, but
your libc must contain the necessary wrapper. Glibc 2.7 and later should
have this wrapper.

EOF

my $can_eventfd = -e "/usr/include/sys/eventfd.h";
$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Another sometimes useful bit of functionality is the Linux signalfd, which
is useful for faster signal handling (don't care). Kernel support for
this will be probed at runtime, but your libc must contain the necessary
wrapper. Glibc 2.7 and later should have this wrapper.

EOF

my $can_signalfd = -e "/usr/include/sys/signalfd.h";
$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


Very rarely, people want to tweak EV even more, e.g. to exclude
or include certain watcher types or backends. This can be done by adding
extra -D options here, or via the EV_EXTRA_DEFS environment variable.

For example, if you run into compile problems because of missing memory
fences (or you just want extra performance), you can tell EV to not support
smp and threads via -DEV_NO_THREADS.

Normal persons just press enter.

EOF

$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";

print <<EOF;

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


EOF

my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();

WriteMakefile(
    dist        => {
                    PREOP       => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
                    COMPRESS    => 'gzip -9v',
                    SUFFIX      => '.gz',
                   },
    depend => {
       "EV.c" => "EV/EVAPI.h "
               . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c "
               . "libev/ev_vars.h libev/ev_wrap.h",
    },
    INC       => "-Ilibev",
    DEFINE    => "$DEFINE",
    NAME => "EV",
    LIBS => [$LIBS],
    PREREQ_PM => {
       @anyevent,
       "common::sense" => 0,
    },
    VERSION_FROM => "EV.pm",
    PM           => {
                    'EV.pm'             => '$(INST_LIBDIR)/EV.pm',
                    'EV/EVAPI.h'        => '$(INST_LIBDIR)/EV/EVAPI.h',
                    'EV/MakeMaker.pm'   => '$(INST_LIBDIR)/EV/MakeMaker.pm',
                    'libev/ev.h'        => '$(INST_LIBDIR)/EV/ev.h',
                    'libev/ev.pod'      => '$(INST_LIBDIR)/EV/libev.pod',
                 },
    MAN3PODS => {
                    'EV.pm'           => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
                    'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
                    'libev/ev.pod'    => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
                },
);


Revision:	1.53
Committed:	Tue Jan 15 21:49:38 2013 UTC (11 years, 4 months ago) by root
Content type:	text/plain
Branch:	MAIN
CVS Tags:	EV-rel-4_15
Changes since 1.52:	+7 -3 lines
Log Message:	atfork, gettime
#	Content
1	use 5.008002;
2
3	use strict qw(vars subs);
4	use Config;
5	use ExtUtils::MakeMaker;
6
7	unless (-e "libev/ev_epoll.c") {
8	print <<EOF;
9
10	***
11	*** ERROR: libev is missing or damaged. If you used a CVS check-out of EV,
12	*** you also have to check-out the "libev" module from the same CVS
13	*** repository into the EV dir (i.e. EV/libev from outside).
14	***
15
16	EOF
17	exit 1;
18	}
19
20	print <<EOF;
21
22	* * * * * * * * * * * * * * * * * *
23
24
25	Welcome to EV configuration. If you are in a hurry, just press return here
26	and hope for the best. The defaults should usually do.
27
28	EOF
29
30	if (prompt ("Skip further questions and use defaults (y/n)?", "y") =~ /[yY]/) {
31	$ENV{PERL_MM_USE_DEFAULT} = 1;
32	}
33
34	print <<EOF;
35
36	* * * * * * * * * * * * * * * * * *
37
38
39	POSIX optionally offers support for a monotonic clock source. EV
40	can take advantage of this clock source to detect time jumps more
41	reliably. Unfortunately, some systems are bound to be broken, so you can
42	disable this here: you can completely disable the detection and use of
43	the monotonic clock by answering 'n' here. Support for this clock type
44	will otherwise be autodetected at both compile- and runtime. (this setting
45	currently affects the use of nanosleep over select as well).
46
47	EOF
48
49	my $DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));
50
51	print <<EOF;
52
53	* * * * * * * * * * * * * * * * * *
54
55
56	POSIX optionally offers support for a (potentially) high-resolution
57	realtime clock interface. In a good implementation, using it is faster
58	than the normal method of using gettimeofday. Unfortunately, this option
59	is also bound to be broken on some systems, and current EV versions do not
60	actually call gettimeofday very often, so it defaults to no.
61
62	EOF
63
64	$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));
65
66	print <<EOF;
67
68	* * * * * * * * * * * * * * * * * *
69
70
71	EV can use various backends with various portability issues. The select
72	backend is the most portable and makes for a good fallback, but it can be
73	limited to a low number of file descriptors and/or might not compile. If
74	you have problems with compiling ev_select.c, you might try to play around
75	with disabling it here, or forcing it to use the fd_set provided by your
76	OS, via the next question. I highly recommend keeping it in.
77
78	EOF
79
80	if (prompt ("Enable select backend (y/n)?", "y") =~ /[yY]/) {
81	$DEFINE .= " -DEV_USE_SELECT=1";
82
83	print <<EOF;
84
85	* * * * * * * * * * * * * * * * * *
86
87
88	The select backend can operate in two modes. One uses the system-provided
89	fd_set and is usually limited to 1024 file descriptors (64 on windows),
90	the other requires your header files to define NFDBITS and declare a
91	suitable fd_mask type. If you run into problems compiling ev_select.c, you
92	can try forcing the use of the system fd_set here.
93
94	EOF
95
96	if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) {
97	$DEFINE .= " -DEV_SELECT_USE_FD_SET";
98	}
99	} else {
100	$DEFINE .= " -DEV_USE_SELECT=0";
101	}
102
103	print <<EOF;
104
105	* * * * * * * * * * * * * * * * * *
106
107
108	The second very portable backend is poll(2). It does not exist on windows
109	and various versions of Mac OS X (and on the other versions it simply
110	doesn't work), but works basically everywhere else. It is recommended to use
111	the default here unless you run into compile problems in ev_poll.c.
112
113	EOF
114
115	$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (-e "/usr/include/poll.h") ? "y" : "n") =~ /[yY]/));
116
117	print <<EOF;
118
119	* * * * * * * * * * * * * * * * * *
120
121
122	Select and poll make it hard to write efficient servers, especially if the
123	number of active connections is much lower than the watched ones. GNU/Linux
124	systems have a more scalable method called "epoll", which EV can use. For
125	this to work, both your kernel and glibc have to support epoll, but if you
126	can compile it, the detection will be done at runtime, and EV will safely
127	fall back to using select when epoll isn't available. If unsure, accept
128	the default.
129
130	EOF
131
132	my $can_epoll = -e "/usr/include/sys/epoll.h";
133	$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
134	$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));
135
136	print <<EOF;
137
138	* * * * * * * * * * * * * * * * * *
139
140
141	Similarly to the epoll backend above, EV can take advantage of kqueue on
142	many BSD systems. Support for kqueue will be detected at runtime, with a
143	safe fallback to other methods when it cannot be used.
144
145	Note that kqueue is broken on most operating systems, so by default it
146	won't be used on many platforms, but you can still create your own event
147	loop with kqueue backend if you ask specifically for it.
148
149	Here is what we know:
150
151	NetBSD: partially working in at least 3.1 and later. Yeah! :)
152	FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
153	sockets likely work, ptys definitely don't.
154	OpenBSD: reports indicate that it likely doesn't work
155	(similar problems as on FreeBSD).
156	OS X: completely, utterly broken on at least <= 10.6.
157
158	EOF
159
160	my $can_kqueue = -e "/usr/include/sys/event.h";
161	$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
162	$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
163
164	print <<EOF;
165
166	* * * * * * * * * * * * * * * * * *
167
168
169	Similarly to the kqueue backend above, EV can take advantage of the
170	solaris 10 event port interface. Support for event ports will be detected
171	at runtime, with a safe fallback to other methods when it cannot be used.
172
173	EOF
174
175	$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/));
176
177	print <<EOF;
178
179	* * * * * * * * * * * * * * * * * *
180
181
182	EV needs the functions pthread_atfork and clock_gettime. On most systems
183	you need some special libraries for this (such as -lrt and -lpthread). You
184	can specify additional libraries to provide these calls (and any other
185	required by EV) now, or accept the default.
186
187	On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function
188	to avoid the dependency on libpthread, and directly uses the clock_gettime
189	syscall to avoid a dependency on librt.
190
191	EOF
192
193	my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
194	my $librt = $^O =~ /linux/i ? "" : "-lpthread -lrt";
195	my $LIBS = exists $ENV{EV_LIBS} ? $ENV{EV_LIBS} : "$librt $solaris_libs";
196	$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", $LIBS;
197
198
199	print <<EOF;
200
201	* * * * * * * * * * * * * * * * * *
202
203
204	A backend of a different kind is the Linux inotify(7) interface, which can
205	be used to speed up (and reduce resource consumption) of stat watchers. If
206	you have the include file and libc support for it, it is usually a good
207	idea to enable it, as kernel availability is detected at runtime.
208
209	EOF
210
211	my $can_inotify = -e "/usr/include/sys/inotify.h";
212	$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
213	$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
214
215	print <<EOF;
216
217	* * * * * * * * * * * * * * * * * *
218
219
220	Another useful bit of functionality is the Linux eventfd, which is useful
221	for faster signal handling (don't care) and intra-thread communications
222	(more relevant). Kernel support for this will be probed at runtime, but
223	your libc must contain the necessary wrapper. Glibc 2.7 and later should
224	have this wrapper.
225
226	EOF
227
228	my $can_eventfd = -e "/usr/include/sys/eventfd.h";
229	$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
230	$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
231
232	print <<EOF;
233
234	* * * * * * * * * * * * * * * * * *
235
236
237	Another sometimes useful bit of functionality is the Linux signalfd, which
238	is useful for faster signal handling (don't care). Kernel support for
239	this will be probed at runtime, but your libc must contain the necessary
240	wrapper. Glibc 2.7 and later should have this wrapper.
241
242	EOF
243
244	my $can_signalfd = -e "/usr/include/sys/signalfd.h";
245	$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
246	$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));
247
248	print <<EOF;
249
250	* * * * * * * * * * * * * * * * * *
251
252
253	Very rarely, people want to tweak EV even more, e.g. to exclude
254	or include certain watcher types or backends. This can be done by adding
255	extra -D options here, or via the EV_EXTRA_DEFS environment variable.
256
257	For example, if you run into compile problems because of missing memory
258	fences (or you just want extra performance), you can tell EV to not support
259	smp and threads via -DEV_NO_THREADS.
260
261	Normal persons just press enter.
262
263	EOF
264
265	$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
266
267	print <<EOF;
268
269	* * * * * * * * * * * * * * * * * *
270
271
272	EOF
273
274	my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();
275
276	WriteMakefile(
277	dist => {
278	PREOP => 'pod2text EV.pm \| tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
279	COMPRESS => 'gzip -9v',
280	SUFFIX => '.gz',
281	},
282	depend => {
283	"EV.c" => "EV/EVAPI.h "
284	. "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c "
285	. "libev/ev_vars.h libev/ev_wrap.h",
286	},
287	INC => "-Ilibev",
288	DEFINE => "$DEFINE",
289	NAME => "EV",
290	LIBS => [$LIBS],
291	PREREQ_PM => {
292	@anyevent,
293	"common::sense" => 0,
294	},
295	VERSION_FROM => "EV.pm",
296	PM => {
297	'EV.pm' => '$(INST_LIBDIR)/EV.pm',
298	'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h',
299	'EV/MakeMaker.pm' => '$(INST_LIBDIR)/EV/MakeMaker.pm',
300	'libev/ev.h' => '$(INST_LIBDIR)/EV/ev.h',
301	'libev/ev.pod' => '$(INST_LIBDIR)/EV/libev.pod',
302	},
303	MAN3PODS => {
304	'EV.pm' => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
305	'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
306	'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
307	},
308	);
309
310