Thank you for your prompt reply.
I checked and found that the "./configure" file was taken from the package file
of libev-4.25.tar.gz.
I forked a code from CVS on my github, and now I think I should delete these
files. :)
By the way, I saw the macro definition of IOCP in "ev.c". Does it mean that
libev will have a plan supported by the Windows platform?
------------------ Original ------------------
From: "Marc Lehmann"<schm...@schmorp.de>;
Date: Wed, Jun 26, 2019 03:27 AM
To: "CandyMI"<869646...@qq.com>;
Cc: "libev"<libev@lists.schmorp.de>;
Subject: Re: About "./configure" Checking the build environment
On Wed, Jun 26, 2019 at 01:15:25AM +0800, CandyMI <869646...@qq.com> wrote:
> When I tried to build libev based on "configure", it didn't try to detect if
> the system contains the following "linux/aio_abi.h" file Unless I build with
> "sh autogen.sh".
>
>
> Does this mean that using "./configure" alone is wrong?
Hi!
linux/aio_abi.h is not checked or used in any released version of libev,
so you must be using a CVS checkout, is this correct? If not, where did
you get your copy?
CVS does not contain a ./configure file, so where is your configure file
from?
When building for CVS, you indeed first need to generate a configure
script by running autogen.sh. The release tarballs would contain all the
necessary files pregenarated, and its configure scirpt should work.
So in short, in a release tarball, ./configure should work. In a CVS
checkout, there shouldn't be a configure script.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/mailman/listinfo/libev
