public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw@lug-owl.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/100289] [11/12/13 Regression] libgcc/libgcov.h: bootstrap failure due to missing #include <sys/mman.h>
Date: Fri, 31 Mar 2023 18:43:57 +0000 [thread overview]
Message-ID: <bug-100289-4-IiKjaFlVOC@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 #20 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
I see this as well for my CI builds using a (slightly hacked to use local
copies of the GIT trees) build-many-glibcs.py (from glibc.)
If you call call:
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/glibc/scripts/build-many-glibcs.py
--keep all --replace-sources -j 1
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21 checkout binutils-vcs-master
gcc-vcs-master glibc-vcs-master linux-vcs-master
log_execute host-libraries
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/glibc/scripts/build-many-glibcs.py
--keep all --replace-sources -j 1
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21 host-libraries
log_execute compilers
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/glibc/scripts/build-many-glibcs.py
--keep all --replace-sources -j 1
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21 --full-gcc compilers
alpha-linux-gnu
(as an example, use the Alpha builds at
http://toolchain.lug-owl.de/laminar/jobs/glibcbot-alpha-linux-gnu , with the
actual breakage for example at
http://toolchain.lug-owl.de/archive/glibcbot-alpha-linux-gnu/21/logs/compilers/alpha-linux-gnu/012-compilers-alpha-linux-gnu-gcc-first-build-log.txt)
...we're ending up at the same spot:
echo 'int __libgcc_eh_dummy;' > eh_dummy.c; \
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/build/compilers/alpha-linux-gnu/gcc-first/./gcc/xgcc
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/build/compilers/alpha-linux-gnu/gcc-first/./gcc/
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/lib/
-isystem
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/include
-isystem
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/sys-include
-g -O2 -mieee -O2 -g -O2 -mieee -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W
-Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mieee
-mfp-rounding-mode=d -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector
-Dinhibit_libc -fPIC -mieee -mfp-rounding-mode=d -I. -I. -I../.././gcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/.
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/../gcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/../include
-DHAVE_CC_TLS -fvisibility=hidden -DHIDE_EXPORTS -c eh_dummy.c \
-o eh_dummy.o; \
objects=eh_dummy.o; \
fi; \
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/ar
rc libgcc.a $objects
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/ranlib
libgcc.a
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/build/compilers/alpha-linux-gnu/gcc-first/./gcc/xgcc
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/build/compilers/alpha-linux-gnu/gcc-first/./gcc/
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/
-B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/lib/
-isystem
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/include
-isystem
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/sys-include
-g -O2 -mieee -O2 -g -O2 -mieee -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W
-Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mieee
-mfp-rounding-mode=d -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector
-Dinhibit_libc -fPIC -mieee -mfp-rounding-mode=d -I. -I. -I../.././gcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/.
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/../gcc
-I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/../include
-DHAVE_CC_TLS -o _gcov_merge_add.o -MT _gcov_merge_add.o -MD -MP -MF
_gcov_merge_add.dep -DL_gcov_merge_add -c
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/libgcov-merge.c
In file included from
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/libgcov-merge.c:26:
/var/lib/laminar/run/glibcbot-alpha-linux-gnu/21/src/gcc/libgcc/libgcov.h:49:10:
fatal error: sys/mman.h: No such file or directory
49 | #include <sys/mman.h>
| ^~~~~~~~~~~~
compilation terminated.
ISTR that it worked without --full-gcc (which enables all languages), so I
wonder if I'd try a build round with --disable-gcov and maybe submit a patch
for glibc's build-many-glibcs.py?
next prev parent reply other threads:[~2023-03-31 18:43 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
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 ` jbglaw@lug-owl.de [this message]
2023-03-31 18:55 ` [Bug gcov-profile/100289] [11/12/13 " 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-IiKjaFlVOC@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).