From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: build of coreutils fails with many many messages
Date: Fri, 01 Apr 2016 11:03:00 -0000 [thread overview]
Message-ID: <56FE558B.1030205@cornell.edu> (raw)
In-Reply-To: <59531E97-547C-48F8-9735-8F50C2741C87@Denis-Excoffier.org>
On 4/1/2016 2:18 AM, Denis Excoffier wrote:
> Hello,
>
> I tried to build coreutils-8.25 with the latest cygwin (2.5.0-0.10 or 2.4.1-1)
> and all the latest packages, and as 'configure' seems to pass ok, 'make'
> fails with hundreds of lines of messages like below.
>
> Please can someone reproduce this (Windows 7, 32bits)?
>
> Regards,
>
> Denis Excoffier
>
>
> In file included from /usr/include/sys/signal.h:112:0,
> from /usr/include/signal.h:6,
> from ./lib/signal.h:52,
> from ./lib/sys/select.h:108,
> from /usr/include/sys/time.h:47,
> from ./lib/sys/time.h:39,
> from ./lib/sys/select.h:87,
> from /usr/include/sys/types.h:85,
> from ./lib/sys/types.h:28,
> from /usr/include/sys/unistd.h:12,
> from /usr/include/unistd.h:4,
> from ./lib/unistd.h:40,
> from ./lib/stdlib.h:96,
> from lib/malloca.h:23,
> from lib/malloca.c:22:
> /usr/include/cygwin/signal.h:178:3: error: unknown type name 'pthread_attr_t'
> pthread_attr_t *sigev_notify_attributes; /* notification attributes */
This looks like the gnulib issue that I reported in
http://lists.gnu.org/archive/html/bug-gnulib/2016-03/msg00054.html. Try
applying the fix from that thread to the gnulib tree in the coreutils
sources.
Ken
--
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
next prev parent reply other threads:[~2016-04-01 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 6:18 Denis Excoffier
2016-04-01 11:03 ` Ken Brown [this message]
2016-04-01 19:28 ` Denis Excoffier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56FE558B.1030205@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).