public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Arjen Markus <arjen.markus895@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	Fortran List <fortran@gcc.gnu.org>
Subject: Re: Build problems: mpfr, mpc
Date: Fri, 20 Aug 2021 14:09:43 +0100	[thread overview]
Message-ID: <CAH6eHdQGQTbxs5GUxnktGoAiNV+7_L3oKTGtyqu7gN1HVPWCcw@mail.gmail.com> (raw)
In-Reply-To: <CAMCbSMpPd8mbcfPPXM5zOh=ZNOM6prnQQUE+4F4qGw7a5mtJ2w@mail.gmail.com>

On Fri, 20 Aug 2021 at 13:59, Arjen Markus wrote:
>
> Going the WSL2 route (I am not all that familiar with WSL) or a Linux emulation may be the way to go, indeed, but your remark triggered me to do a bit of searching: there is some discussion about the secure_getenv() function wrt Cygwin but there actually is a prototype for it in Cygwin's stdlib.h. It is protected by a symbol __GNU_VISIBLE. I will try to define that and see what happens.

Don't do that. Define _GNU_SOURCE to tell Cygwin you want the GNU
extensions like secure_getenv, and then <sys/features.h> will define
__GNU_VISIBLE.

I am curious why _GNU_SOURCE would be defined during configure but not
when compiling.

  reply	other threads:[~2021-08-20 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20  7:58 Arjen Markus
2021-08-20  9:54 ` Richard Biener
2021-08-20 10:10   ` Arjen Markus
2021-08-20 10:55     ` Arjen Markus
2021-08-20 12:31       ` Richard Biener
2021-08-20 12:59         ` Arjen Markus
2021-08-20 13:09           ` Jonathan Wakely [this message]
2021-08-20 13:11             ` Jonathan Wakely
2021-08-20 13:17               ` Arjen Markus
2021-08-23  7:07                 ` Arjen Markus

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=CAH6eHdQGQTbxs5GUxnktGoAiNV+7_L3oKTGtyqu7gN1HVPWCcw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=arjen.markus895@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).