[ViewVC] Diff of: cvs/EV/Makefile.PL

Comparing EV/Makefile.PL (file contents):
Revision 1.56 by root, Sat Sep 6 19:03:28 2014 UTC vs.
Revision 1.68 by root, Tue Feb 18 18:26:47 2020 UTC

…		…
1	use 5.008002;
2
3	use strict qw(vars subs);	1	use strict qw(vars subs);
		2	use Canary::Stability EV => 1, 5.008002;
4	use Config;	3	use Config;
5	use ExtUtils::MakeMaker;	4	use ExtUtils::MakeMaker;
6		5
7	sub have_inc($) {	6	sub have_inc($) {
8	scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}	7	scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}
9	}	8	}
10		9
11	my $DEFINE;	10	my $DEFINE;
12		11
13	unless (-e "libev/ev_epoll.c") {	12	unless (-e "libev/ev_iouring.c") {
14	print <<EOF;	13	print <<EOF;
15		14
16	***	15	***
17	*** 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,
18	*** 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
114		113
115		114
116	The second very portable backend is poll(2). It does not exist on windows	115	The second very portable backend is poll(2). It does not exist on windows
117	and various versions of Mac OS X (and on the other versions it simply	116	and various versions of Mac OS X (and on the other versions it simply
118	doesn't work), but works basically everywhere else. It is recommended to use	117	doesn't work), but works basically everywhere else. It is recommended to use
119	the default here unless you run into compile problems in ev_poll.c.	118	the default here unless you run into compilation problems in ev_poll.c.
120		119
121	EOF	120	EOF
122		121
123	$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]/));
124		123
…		…
144	print <<EOF;	143	print <<EOF;
145		144
146	* * * * * * * * * * * * * * * * * *	145	* * * * * * * * * * * * * * * * * *
147		146
148		147
149	Similarly to the epoll backend above, EV can take advantage of kqueue on	148	Linux 4.18 introduced another event polling interface, this time using
150	many BSD systems. Support for kqueue will be detected at runtime, with a	149	the Linux AIO API. While this API is far superior to epoll and almost
151	safe fallback to other methods when it cannot be used.	150	rivals kqueue, it also suffers from the same issues as kqueue typically
		151	does: only a subset of file types are supported (as of 4.19, I have seen
		152	eventfd, pipes, sockets files and some devices, but no ttys). It also
		153	is subject arbitrary system-wide limits imposed on it. Therefore, this
		154	backend is not used by default, even when it is compiled in, and you have
		155	to request it explicitly, e.g. with LIBEV_FLAGS=64. If unsure, accept the
		156	default.
152		157
		158	EOF
		159
		160	my $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
		165	if ($can_linuxaio) {
		166	print <<EOF;
		167
		168	* * * * * * * * * * * * * * * * * *
		169
		170
		171	The previously mentioned Linux AIO backend is experimental and will not
		172	be used unless requested explicitly. You can, howeer, choose to make ti a
		173	recommended basckend, which means it will be chosen if available even when
		174	not explicitly asked for, in preference to epoll on GNU/Linux. This option
		175	is likely temporary. When unsure, accept the default.
		176
		177	EOF
		178
		179	my $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
		185	print <<EOF;
		186
		187	* * * * * * * * * * * * * * * * * *
		188
		189
		190	Linux 4.19 introduced another event polling interface, "io_uring". While
		191	this API is far superior to epoll and almost rivals linuxaio, it also
		192	suffers from the same issues as kqueue typically does: only a subset of
		193	file types are supported (as of 5.2). It is also very buggy still, and
		194	most importantly, very very slow for most workloads. Therefore, this
		195	backend is not used by default, even when it is compiled in, and you have
		196	to request it explicitly, e.g. with LIBEV_FLAGS=128. If unsure, accept the
		197	default.
		198
		199	EOF
		200
		201	my $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
		206	if ($can_iouring) {
		207	print <<EOF;
		208
		209	* * * * * * * * * * * * * * * * * *
		210
		211
		212	The previously mentioned Linux io_uring is experimental and will not be
		213	used unless requested explicitly. You can, howeer, choose to make ti a
		214	recommended basckend, which means it will be chosen if available even when
		215	not explicitly asked for, in preference to epoll on GNU/Linux. This option
		216	is likely temporary. When unsure, accept the default.
		217
		218	EOF
		219
		220	my $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
		226	print <<EOF;
		227
		228	* * * * * * * * * * * * * * * * * *
		229
		230
		231	EV can take advantage of kqueue on many BSD systems. Support for kqueue
		232	will be detected at runtime, with a safe fallback to other methods when it
		233	cannot be used.
		234
153	Note that kqueue is broken on most operating systems, so by default it	235	Note that kqueue is subtly broken on most operating systems, so by default
154	won't be used on many platforms, but you can still create your own event	236	it won't be used on many platforms, but you can still create your own
155	loop with kqueue backend if you ask specifically for it.	237	event loop with kqueue backend if you ask specifically for it.
156		238
157	Here is what we know:	239	Here is what we know:
158		240
159	NetBSD: partially working in at least 3.1 and later. Yeah! :)	241	NetBSD: partially working in at least 3.1 and later. Yeah! :)
160	FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,	242	FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
…		…
163	(similar problems as on FreeBSD).	245	(similar problems as on FreeBSD).
164	OS X: completely, utterly broken on at least <= 10.6.	246	OS X: completely, utterly broken on at least <= 10.6.
165		247
166	EOF	248	EOF
167		249
		250	# minix has all the header files, but no implementation. won-der-ful.
168	my $can_kqueue = have_inc "sys/event.h";	251	my $can_kqueue = have_inc "sys/event.h" && $^O ne "minix";
169	$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};	252	$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
170	$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]/));
171		254
172	print <<EOF;	255	print <<EOF;
173		256
…		…
256	print <<EOF;	339	print <<EOF;
257		340
258	* * * * * * * * * * * * * * * * * *	341	* * * * * * * * * * * * * * * * * *
259		342
260		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
		361	Libev contains numerous internal assert() invocations to check for
		362	consistency and user errors. These are normally enabled, but most
		363	perl builds disable this error reporting mechanism by default. You
		364	can re-enable these asserts here. Enabling them might help you catch
		365	programming bugs earlier, but might cause a small slowdown. Also, failures
		366	will be reported by aboritng your program, instead of throwing a perl
		367	exception.
		368
		369	If unsure, enable this if you only use this perl installation for
		370	development, and leave it off for use in production environments.
		371
		372	EOF
		373
		374	my $enable_assertions = 0;
		375	$enable_assertions = 0 + (prompt ("Make sure assertions are enabled? (y/n)?", $enable_assertions ? "y" : "n") =~ /[yY]/);
		376	$DEFINE .= " -DEV_ENABLE_ASSERTIONS=1" if $enable_assertions;
		377
		378	print <<EOF;
		379
		380	* * * * * * * * * * * * * * * * * *
		381
		382
261	Very rarely, people want to tweak EV even more, e.g. to exclude	383	Very rarely, people want to tweak EV even more, e.g. to exclude
262	or include certain watcher types or backends. This can be done by adding	384	or include certain watcher types or backends. This can be done by adding
263	extra -D options here, or via the EV_EXTRA_DEFS environment variable.	385	extra -D options here, or via the EV_EXTRA_DEFS environment variable.
264		386
265	For example, if you run into compile problems because of missing memory	387	For example, if you run into compilation problems because of missing memory
266	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
267	smp and threads via -DEV_NO_THREADS.	389	smp and threads via -DEV_NO_THREADS.
268		390
269	Normal persons just press enter.	391	Most people would just press enter.
270		392
271	EOF	393	EOF
272		394
273	$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";	395	$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
274		396
…		…
287	COMPRESS => 'gzip -9v',	409	COMPRESS => 'gzip -9v',
288	SUFFIX => '.gz',	410	SUFFIX => '.gz',
289	},	411	},
290	depend => {	412	depend => {
291	"EV.c" => "EV/EVAPI.h "	413	"EV.c" => "EV/EVAPI.h "
292	. "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 "
293	. "libev/ev_vars.h libev/ev_wrap.h",	415	. "libev/ev_vars.h libev/ev_wrap.h",
294	},	416	},
295	INC => "-Ilibev",	417	INC => "-Ilibev",
296	DEFINE => "$DEFINE",	418	DEFINE => "$DEFINE",
297	NAME => "EV",	419	NAME => "EV",
298	LIBS => [$LIBS],	420	LIBS => [$LIBS],
299	PREREQ_PM => {	421	PREREQ_PM => {
300	@anyevent,	422	@anyevent,
301	"common::sense" => 0,	423	"common::sense" => 0,
302	},	424	},
		425	CONFIGURE_REQUIRES => { "ExtUtils::MakeMaker" => 6.52, "Canary::Stability" => 0 },
303	VERSION_FROM => "EV.pm",	426	VERSION_FROM => "EV.pm",
304	PM => {	427	PM => {
305	'EV.pm' => '$(INST_LIB)/EV.pm',	428	'EV.pm' => '$(INST_LIB)/EV.pm',
306	'EV/EVAPI.h' => '$(INST_LIB)/EV/EVAPI.h',	429	'EV/EVAPI.h' => '$(INST_LIB)/EV/EVAPI.h',
307	'EV/MakeMaker.pm' => '$(INST_LIB)/EV/MakeMaker.pm',	430	'EV/MakeMaker.pm' => '$(INST_LIB)/EV/MakeMaker.pm',
…		…
313	'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',	436	'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
314	'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',	437	'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
315	},	438	},
316	);	439	);
317		440
318

Diff Legend

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

Comparing EV/Makefile.PL (file contents): Revision 1.56 by root, Sat Sep 6 19:03:28 2014 UTC vs. Revision 1.68 by root, Tue Feb 18 18:26:47 2020 UTC

Diff Legend

Comparing EV/Makefile.PL (file contents):
Revision 1.56 by root, Sat Sep 6 19:03:28 2014 UTC vs.
Revision 1.68 by root, Tue Feb 18 18:26:47 2020 UTC