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 06:29:41 +0000	[thread overview]
Message-ID: <bug-105144-4-5INxs1wsdY@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

--- Comment #10 from Khem Raj <raj.khem at gmail dot com> ---
(In reply to Andrew Pinski from comment #9)
> (In reply to Andrew Pinski from comment #8)
> > (In reply to Khem Raj from comment #7)
> > > in Yocto we build outside the source tree. And during cross-build it will
> > > copy aarch64.h into builddir and use it from there but then build can not
> > > find files it includes since its being included from builddir. This patch
> > > below helps
> > 
> > aarch64.h is never copied into the builddir.
> 
> Even for cross builds.
> I think something else is wrong.  Please file a different bug with the full
> log? Including the part where the copy happens because I just did a:
> find . -name aarch64.h
> in the build directory of the cross build of GCC 12 I had around and there
> was no such file happening.

you are right. I should have mentioned that these copying is done by yocto
builds  for working though its notion of multilibs [1]. However, I think if we
apply this fix it should not regress builds and we will have one less patch to
carry in yocto.

[1]
https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/gcc/gcc-multilib-config.inc#n30

  parent reply	other threads:[~2023-02-01  6:29 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
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 [this message]
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-5INxs1wsdY@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).