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 gcov-profile/100289] [11/12 Regression] libgcc/libgcov.h: bootstrap failure due to missing #include <sys/mman.h>
Date: Fri, 30 Apr 2021 07:11:31 +0000 [thread overview]
Message-ID: <bug-100289-4-m2lrF63Am7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100289-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100289
--- Comment #13 from rudi at heitbaum dot com ---
I have looked further into this; and here are the locations of sys/mman.h, this
include comes from the glibc package. gcc builds in package #80, whilst glibc
builds in package #82. The dependancies - given the way the gcc11 configure
script works (and must be pulling from
/usr/include/x86_64-linux-gnu/sys/mman.h) is a recursive dependency.
Here are the packages in question. gcc:bootstrap does not have a glibc
dependency.
== gcc package ==
PKG_NAME="gcc"
PKG_DEPENDS_BOOTSTRAP="ccache:host autoconf:host binutils:host gmp:host
mpfr:host mpc:host zstd:host"
PKG_DEPENDS_TARGET="toolchain"
PKG_DEPENDS_HOST="ccache:host autoconf:host binutils:host gmp:host mpfr:host
mpc:host zstd:host glibc"
PKG_DEPENDS_INIT="toolchain"
== glibc package ==
PKG_NAME="glibc"
PKG_DEPENDS_TARGET="ccache:host autotools:host linux:host gcc:bootstrap
pigz:host Python3:host"
PKG_DEPENDS_INIT="glibc"
== here is the actual creation of mman.h (using gcc10.3.0) ==
grep sys/mman.h 82.log /usr/bin/install -c -m 644 sys/mman.h
/storage/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-10.0-devel/.sysroot/glibc.target/usr/include/sys/mman.h
/usr/bin/install -c -m 644 sys/mman.h
/storage/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-10.0-devel/install_pkg/glibc-2.33/usr/include/sys/mman.h
== the find after a full build ==
find . -name mman.h | grey sys/
./build.LibreELEC-Generic.x86_64-10.0-devel/install_pkg/glibc-2.33/usr/include/sys/mman.h
./build.LibreELEC-Generic.x86_64-10.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/include/sys/mman.h
./build.LibreELEC-Generic.x86_64-10.0-devel/build/glibc-2.33/misc/sys/mman.h
./build.LibreELEC-Generic.x86_64-10.0-devel/build/glibc-2.33/include/sys/mman.h
./build.LibreELEC-Generic.x86_64-10.0-devel/build/gcc-10.3.0/fixincludes/tests/base/sys/mman.h
./build.LibreELEC-Generic.x86_64-10.0-devel/build/xorg-intel-gpu-tools-1.26/lib/stubs/syscalls/sys/mman.h
next prev parent reply other threads:[~2021-04-30 7:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:13 [Bug libgcc/100289] New: " rudi at heitbaum dot com
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 [this message]
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-m2lrF63Am7@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).