From: Patrick Chkoreff <pc@fexl.com>
To: cygwin@cygwin.com
Subject: Re: setrlimit always fails
Date: Tue, 16 Feb 2021 09:53:11 -0500 [thread overview]
Message-ID: <d37ecbe9-491b-fb6d-dac8-f1b333a34a4b@fexl.com> (raw)
In-Reply-To: <YCreBGKMpVwfWrvR@calimero.vinschen.de>
Corinna Vinschen wrote on 2/15/21 3:48 PM:
> On Feb 15 14:54, Patrick Chkoreff wrote:
>> Corinna Vinschen wrote on 2/15/21 4:14 AM:
>> To fix that, I must define _USE_XOPEN
>
> You really, really must not use this macro.
I'm glad to hear something definitive about that. I don't even remember
how I arrived at that hack.
...
> The problem here is that you mix functions only defined under
> _XOPEN_SOURCE with stuff only defined with _DEFAULT_SOURCE from the same
> header. Either define both feature test macros, or define _GNU_SOURCE.
Thank you for the sensible explanation.
> This works:
>
> #define _XOPEN_SOURCE
> #define _DEFAULT_SOURCE
> #include <stdint.h>
> #include <sys/time.h>
> #include <time.h>
> void stuff(void)
> [...]
Yes, that does work on both Cygwin and Linux.
> This works, too:
>
> #define _GNU_SOURCE
> #include <stdint.h>
> #include <sys/time.h>
> #include <time.h>
> void stuff(void)
> [...]
Yes, that also works on both Cygwin and Linux.
Thank you!
-- Patrick
next prev parent reply other threads:[~2021-02-16 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 15:23 Patrick Chkoreff
2021-02-12 2:06 ` Ken Brown
2021-02-12 7:26 ` Brian Inglis
2021-02-12 9:12 ` Corinna Vinschen
2021-02-12 18:56 ` Brian Inglis
2021-02-12 20:38 ` Brian Inglis
2021-02-12 15:11 ` Patrick Chkoreff
2021-02-15 9:14 ` Corinna Vinschen
2021-02-15 19:54 ` Patrick Chkoreff
2021-02-15 20:48 ` Corinna Vinschen
2021-02-16 14:53 ` Patrick Chkoreff [this message]
2021-02-16 15:22 ` Marco Atzeri
2021-02-16 18:33 ` Brian Inglis
2021-02-12 9:11 ` Corinna Vinschen
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=d37ecbe9-491b-fb6d-dac8-f1b333a34a4b@fexl.com \
--to=pc@fexl.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).