public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [64bit] cygwin-devel headers broken
Date: Fri, 01 May 2015 05:03:00 -0000	[thread overview]
Message-ID: <5543090D.9030409@gmail.com> (raw)
In-Reply-To: <554279F0.5040505@towo.net>



On 4/30/2015 8:52 PM, Thomas Wolff wrote:
> There is a crash issue induced on cygwin-64 (not on -32) after
> compilation with cygwin-devel 2.0.0 include files. I am recompiling my
> editor mined and it crashes, maybe immediately or after typing
> non-trivial input (like function keys, waiting for input with select()).
> It does not occur after recompiling only certain source files, but it
> happens after recompiling only io.c which makes heavy use of terminal
> I/O like read(), select(), ioctl().
>
> Reverting the cygwin-devel package to 1.7 (and leaving everything else
> up-to-date) solves the issue.
> Selective copying of files from the cygwin-devel 2.0 package further
> reveals:
> /lib: all from 2.0: no problem.
> /usr/include/sys: all from 2.0 except the following: no problem.
> But if signal.h, stat.h, time.h, types.h, and associated dependencies
> are used, the compiled program crashes.
> I can try to narrow down the issue further but maybe this is a clue
> already?
>
> ------
> Thomas
>

I had a similar issue. But in my case the compilation fails as
select seems gone:

In file included from 
/pub/devel/singular/prova/singular-4.0.2a-1.x86_64/src/sin
gular-4.0.2a/libpolys/reporter/s_buff.cc:16:0:
/pub/devel/singular/prova/singular-4.0.2a-1.x86_64/src/singular-4.0.2a/libpolys/
reporter/si_signals.h: In function ‘int si_select(int, _types_fd_set*, 
_types_fd
_set*, _types_fd_set*, timeval*)’:
/pub/devel/singular/prova/singular-4.0.2a-1.x86_64/src/singular-4.0.2a/libpolys/
reporter/si_signals.h:47:63: error: ‘select’ was not declared in this scope
                     (nfds,readfds, writefds, exceptfds, timeout)
                                                                ^
/pub/devel/singular/prova/singular-4.0.2a-1.x86_64/src/singular-4.0.2a/libpolys/
reporter/si_signals.h:33:16: note: in definition of macro 
‘SI_EINTR_SAVE_FUNC_TE
MPLATE’
      res = func args;           \
                 ^
/pub/devel/singular/prova/singular-4.0.2a-1.x86_64/src/singular-4.0.2a/libpolys/
reporter/si_signals.h:44:1: note: in expansion of macro ‘SI_EINTR_SAVE_FUNC’
  SI_EINTR_SAVE_FUNC(int, select,
  ^

cheers
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

  reply	other threads:[~2015-05-01  5:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 18:52 Thomas Wolff
2015-05-01  5:03 ` Marco Atzeri [this message]
2015-05-01 12:10   ` Jon TURNEY
2015-05-01 18:19     ` Thomas Wolff
2015-05-01 20:12       ` Michael Enright
2015-05-02 17:38         ` Csaba Raduly
2015-05-01 20:23       ` Marco Atzeri
2015-05-01 20:38         ` Eric Blake
2015-05-02 13:38           ` Corinna Vinschen
2015-05-01 20:25     ` J. Offerman

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=5543090D.9030409@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).