public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rudi at heitbaum dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/100289] New: libgcc/libgcov.h: bootstrap failure due to missing #include <sys/mman.h>
Date: Tue, 27 Apr 2021 12:13:13 +0000 [thread overview]
Message-ID: <bug-100289-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100289
Bug ID: 100289
Summary: libgcc/libgcov.h: bootstrap failure due to missing
#include <sys/mman.h>
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: rudi at heitbaum dot com
Target Milestone: ---
Performing a bootstrap on Ubuntu 18.04 for a LibreELEC10 build, with just an
update from gcc 10.3.0 to 11.1.0, the bootstrap fails. Configure incorrectly
defines HAVE_SYS_MMAN_H as 1. Removing sys/mmap.h allows the successful build
of gcc:bootstrap.
Gcc:host subsequently fails build with -
/storage/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-10.0-devel/build/gcc-11.1.0/libgcc/libgcov.h:426:10:
warning: implicit declaration of function 'mmap'
[-Wimplicit-function-declaration]
Failure log of bootstrap build -
Failure logs of host build - http://paste.ubuntu.com/p/tCtc4nRfkV/
next reply other threads:[~2021-04-27 12:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:13 rudi at heitbaum dot com [this message]
2021-04-27 12:17 ` [Bug gcov-profile/100289] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-04-27 12:18 ` rguenth at gcc dot gnu.org
2021-04-27 12:20 ` rudi at heitbaum dot com
2021-04-27 12:22 ` rudi at heitbaum dot com
2021-04-28 6:06 ` rguenth at gcc dot gnu.org
2021-04-28 10:21 ` jakub at gcc dot gnu.org
2021-04-28 11:23 ` rudi at heitbaum dot com
2021-04-28 11:28 ` rudi at heitbaum dot com
2021-04-28 12:06 ` rudi at heitbaum dot com
2021-04-28 12:06 ` rudi at heitbaum dot com
2021-04-28 12:16 ` rudi at heitbaum dot com
2021-04-28 12:16 ` rudi at heitbaum dot com
2021-04-30 7:11 ` rudi at heitbaum dot com
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2021-07-28 11:34 ` rudi at heitbaum dot com
2022-02-18 22:30 ` j at uriah dot heep.sax.de
2022-02-20 10:21 ` rudi at heitbaum dot com
2022-02-20 13:40 ` j at uriah dot heep.sax.de
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2023-03-31 18:43 ` [Bug gcov-profile/100289] [11/12/13 " jbglaw@lug-owl.de
2023-03-31 18:55 ` jbglaw@lug-owl.de
2023-05-29 10:04 ` [Bug gcov-profile/100289] [11/12/13/14 " 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-100289-4@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).