public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrfsousa at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100907] Bind(c): failure handling wide character
Date: Sun, 06 Jun 2021 15:32:31 +0000	[thread overview]
Message-ID: <bug-100907-4-hdQMQ64kjv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100907-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100907

--- Comment #6 from José Rui Faustino de Sousa <jrfsousa at gcc dot gnu.org> ---
> Shouldn't the C11 standard headers be provide by GCC12?
> 

AFAIK gcc uses the system's libc. In Linux the default will be GNU libc "glibc"
in Mas OS the default libc will be BSD libc which is missing some of the
headers... Or so it says in GNU portability library "gnulib" documentation...

Thank you very much.

Best regards,
José Rui

  parent reply	other threads:[~2021-06-06 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 17:47 [Bug fortran/100907] New: " jrfsousa at gcc dot gnu.org
2021-06-04 17:47 ` [Bug fortran/100907] " jrfsousa at gcc dot gnu.org
2021-06-05 12:17 ` dominiq at lps dot ens.fr
2021-06-06  0:24 ` jrfsousa at gcc dot gnu.org
2021-06-06  0:24 ` jrfsousa at gcc dot gnu.org
2021-06-06 13:15 ` dominiq at lps dot ens.fr
2021-06-06 15:32 ` jrfsousa at gcc dot gnu.org [this message]
2021-06-13 18:50 ` jrfsousa at gcc dot gnu.org
2021-06-18 11:01 ` dominiq at lps dot ens.fr
2021-09-02 23:42 ` cvs-commit at gcc dot gnu.org
2021-10-21 23:26 ` sandra at gcc dot gnu.org
2021-10-22 12:44 ` burnus at gcc dot gnu.org
2021-10-22 12:57 ` dominiq at lps dot ens.fr

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=bug-100907-4-hdQMQ64kjv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).