I am reasonable sure that last time, long time ago,
there was not this problem on building guile 2.0.11.
I suspect is due to the re shuffle of cygwin header
plus the local version of "signal.h".
But I am a bit lost in following all the chain:
------------------------------------------------------
make[4]: Entering directory
'/cygdrive/e/cyg_pub/devel/guile/prova20/guile-2.0.11-1.x86_64/build/lib'
CC binary-io.lo
In file included from /usr/include/sys/signal.h:112:0,
from /usr/include/signal.h:6,
from ./signal.h:52,
from ./sys/select.h:107,
from /usr/include/sys/time.h:47,
from ./sys/time.h:39,
from ./sys/select.h:86,
from /usr/include/sys/types.h:68,
from ./sys/types.h:27,
from ./fcntl.h:50,
from
/cygdrive/e/cyg_pub/devel/guile/prova20/guile-2.0.11-1.x86_64/src/guile-2.0.11/lib/binary-io.h:22,
from
/cygdrive/e/cyg_pub/devel/guile/prova20/guile-2.0.11-1.x86_64/src/guile-2.0.11/lib/binary-io.c:3:
/usr/include/cygwin/signal.h:178:3: error: unknown type name
'pthread_attr_t'
pthread_attr_t *sigev_notify_attributes; /* notification attributes */
^
/usr/include/cygwin/signal.h:213:3: error: unknown type name 'pid_t'
pid_t si_pid; /* sender's pid */
^
/usr/include/cygwin/signal.h:214:3: error: unknown type name 'uid_t'
uid_t si_uid; /* sender's uid */
^
/usr/include/cygwin/signal.h:230:2: error: unknown type name 'timer_t'
timer_t si_tid; /* timer id */
^
/usr/include/cygwin/signal.h:238:7: error: unknown type name 'clock_t'
clock_t si_utime; /* user time */
----------------------------------------------------------
local signal.h has a structure like:
-------------------------------------------------
/* Define pid_t, uid_t.
Also, mingw defines sigset_t not in <signal.h>, but in <sys/types.h>.
On Solaris 10, <signal.h> includes <sys/types.h>, which eventually
includes
us; so include <sys/types.h> now, before the second inclusion guard. */
#include <sys/types.h>
/* The include_next requires a split double-inclusion guard. */
#include_next <signal.h>
---------------------------------------------------
PS: I rebuilt 1.8.8 and it has no problem.
But it clearly has a different structure.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple