public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105144] [12 Regression] Bootstrap + install failure on aarch64 due to aarch64-tune.md likely since r12-7842
Date: Wed, 01 Feb 2023 04:13:39 +0000 [thread overview]
Message-ID: <bug-105144-4-QaueUuwHU0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105144-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105144
Khem Raj <raj.khem at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |raj.khem at gmail dot com
--- Comment #6 from Khem Raj <raj.khem at gmail dot com> ---
I am seeing a build failure which looks like a race condition to me. Perhaps
related to this or related commits in this series.
| g++ -c
-isystem/mnt/b/yoe/master/build/tmp/work/x86_64-linux/gcc-cross-aarch64/13.0.1-r0/recipe-sysroot-native/usr/include
-O2 -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Wconditionally-supported
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild
-I../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc
-I../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc/build
-I../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc/../include
-I../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc/../libcpp/include
\
| -o build/gencheck.o
../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc/gencheck.cc
| yes
| checking for gethostbyname... yes
|
| checking for exported symbols... In file included from ./tm.h:34,
| from
../../../../../../../work-shared/gcc-13.0.1-r0/gcc-b2ec2504af77b35e748067eeb846821d12a6b6b4/gcc/gencheck.cc:23:
| ./config/aarch64/aarch64.h:164:10: fatal error:
aarch64-option-extensions.def: No such file or directory
| 164 | #include "aarch64-option-extensions.def"
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[1]: *** [Makefile:2855: build/gencheck.o] Error 1
| make[1]: *** Waiting for unfinished jobs....
next prev parent reply other threads:[~2023-02-01 4:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 7:58 [Bug target/105144] New: " jakub at gcc dot gnu.org
2022-04-04 7:58 ` [Bug target/105144] " jakub at gcc dot gnu.org
2022-04-04 8:22 ` jakub at gcc dot gnu.org
2022-04-04 8:49 ` jakub at gcc dot gnu.org
2022-04-04 10:10 ` cvs-commit at gcc dot gnu.org
2022-04-04 11:59 ` cvs-commit at gcc dot gnu.org
2022-04-04 12:13 ` jakub at gcc dot gnu.org
2023-02-01 4:13 ` raj.khem at gmail dot com [this message]
2023-02-01 6:11 ` raj.khem at gmail dot com
2023-02-01 6:21 ` pinskia at gcc dot gnu.org
2023-02-01 6:26 ` pinskia at gcc dot gnu.org
2023-02-01 6:29 ` raj.khem at gmail dot com
2023-02-01 6:32 ` pinskia 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-105144-4-QaueUuwHU0@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).