From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: [64bit] cygwin-devel headers broken
Date: Fri, 01 May 2015 20:12:00 -0000 [thread overview]
Message-ID: <CAOC2fq_4n_AXbTCEzL0herVbHhQ_mC=somEnhv-=mduiRnKWBw@mail.gmail.com> (raw)
In-Reply-To: <5543BEAE.3000703@towo.net>
When changing from compiler to compiler, even if it be just an OS
point version upgrade, implicit header inclusions go away all the
time. As a developer, I just shrug this off as one of the trade-offs
of choosing to develop in C or C++, which lack proper module systems.
On Fri, May 1, 2015 at 10:58 AM, Thomas Wolff <towo@towo.net> wrote:
> Am 01.05.2015 um 14:10 schrieb Jon TURNEY:
>>
>> On 01/05/2015 06:03, Marco Atzeri wrote:
>>>
>>> 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()).
>>>> ...
>>>>
>>>
>>> I had a similar issue. But in my case the compilation fails as
>>> select seems gone:
>>
>>
>> It seems that sys/select.h is no longer implicitly included by some other
>> header, I think probably sys/time.h.
>
> Thanks for the hint, adding an include solves the issue.
> It had compiled without because I have a plain extern int select()
> declaration. It's obviously not a good declaration because the pointer
> arguments can now be 64 bit. (I think I could not unconditionally include
> select.h for porting compatibility with some legacy systems that don't have
> it.)
>
> Not sure whether it's a bug then as arguably a program using select should
> declare it properly. On the other hand this issue has not appeared on any
> other system and if traditionally include time.h used to imply include
> select.h maybe that should be maintained.
> ------
> Thomas
>
>
> --
> 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
>
--
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:[~2015-05-01 19:29 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
2015-05-01 12:10 ` Jon TURNEY
2015-05-01 18:19 ` Thomas Wolff
2015-05-01 20:12 ` Michael Enright [this message]
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='CAOC2fq_4n_AXbTCEzL0herVbHhQ_mC=somEnhv-=mduiRnKWBw@mail.gmail.com' \
--to=mike@kmcardiff.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).