| … | |
… | |
| 7 | scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} |
7 | scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth} |
| 8 | } |
8 | } |
| 9 | |
9 | |
| 10 | my $DEFINE; |
10 | my $DEFINE; |
| 11 | |
11 | |
| 12 | unless (-e "libev/ev_epoll.c") { |
12 | unless (-e "libev/ev_linuxaio.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 |
| … | |
… | |
| 143 | print <<EOF; |
143 | print <<EOF; |
| 144 | |
144 | |
| 145 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
145 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
| 146 | |
146 | |
| 147 | |
147 | |
|
|
148 | Linux 4.18 introduced another event polling interface, this time using |
|
|
149 | the Linux AIO API. While this API is far superior to epoll and almost |
|
|
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. |
|
|
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 | |
| 148 | Similarly to the epoll backend above, EV can take advantage of kqueue on |
190 | Similarly to the epoll backend above, EV can take advantage of kqueue on |
| 149 | many BSD systems. Support for kqueue will be detected at runtime, with a |
191 | many BSD systems. Support for kqueue will be detected at runtime, with a |
| 150 | safe fallback to other methods when it cannot be used. |
192 | safe fallback to other methods when it cannot be used. |
| 151 | |
193 | |
| 152 | Note that kqueue is broken on most operating systems, so by default it |
194 | Note that kqueue is broken on most operating systems, so by default it |
| … | |
… | |
| 249 | EOF |
291 | EOF |
| 250 | |
292 | |
| 251 | my $can_signalfd = have_inc "sys/signalfd.h"; |
293 | my $can_signalfd = have_inc "sys/signalfd.h"; |
| 252 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
294 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
| 253 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
295 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
|
|
296 | |
|
|
297 | print <<EOF; |
|
|
298 | |
|
|
299 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
300 | |
|
|
301 | |
|
|
302 | Libev contains numerous internal assert() invocations to check for |
|
|
303 | consistency and user errors. These are normally enabled, but most |
|
|
304 | perl builds disable this error reporting mechanism by default. You |
|
|
305 | can re-enable these asserts here. Enabling them might help you catch |
|
|
306 | programming bugs earlier, but might cause a small slowdown. Also, failures |
|
|
307 | will be reported by aboritng your program, instead of throwing a perl |
|
|
308 | exception. |
|
|
309 | |
|
|
310 | If unsure, enable this if you only use this perl installation for |
|
|
311 | development, and leave it off for use in production environments. |
|
|
312 | |
|
|
313 | EOF |
|
|
314 | |
|
|
315 | my $enable_assertions = 0; |
|
|
316 | $enable_assertions = 0 + (prompt ("Make sure assertions are enabled? (y/n)?", $enable_assertions ? "y" : "n") =~ /[yY]/); |
|
|
317 | $DEFINE .= " -DEV_ENABLE_ASERTIONS=1" if $enable_assertions; |
| 254 | |
318 | |
| 255 | print <<EOF; |
319 | print <<EOF; |
| 256 | |
320 | |
| 257 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
321 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
| 258 | |
322 | |
