public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/99406] [11 regression] MAP_ANONYMOUS undeclared in libgcov.h
Date: Sat, 06 Mar 2021 15:23:21 +0000 [thread overview]
Message-ID: <bug-99406-4-VXOwkKVc4R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99406-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99406
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:73a9216b8a47889234c94e3aaec193391ee6604d
commit r11-7543-g73a9216b8a47889234c94e3aaec193391ee6604d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat Mar 6 16:22:27 2021 +0100
libgcov: Fix build on Darwin [PR99406]
As reported, bootstrap currently fails on older Darwin because
MAP_ANONYMOUS
is not defined.
The following is what gcc/system.h does, so I think it should work for
libgcov.
2021-03-06 Jakub Jelinek <jakub@redhat.com>
PR gcov-profile/99406
* libgcov.h (MAP_FAILED, MAP_ANONYMOUS): If HAVE_SYS_MMAN_H is
defined, define these macros if not defined already.
next prev parent reply other threads:[~2021-03-06 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 13:32 [Bug gcov-profile/99406] New: " ro at gcc dot gnu.org
2021-03-05 13:33 ` [Bug gcov-profile/99406] " ro at gcc dot gnu.org
2021-03-05 13:37 ` iains at gcc dot gnu.org
2021-03-05 13:39 ` jakub at gcc dot gnu.org
2021-03-05 13:42 ` marxin at gcc dot gnu.org
2021-03-05 13:43 ` jakub at gcc dot gnu.org
2021-03-06 15:23 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-06 15:24 ` jakub at gcc dot gnu.org
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-99406-4-VXOwkKVc4R@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).