public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108505] [13 Regression] Arm: arm-none-eabi toolchain build failing with compiler error.
Date: Mon, 23 Jan 2023 18:40:40 +0000 [thread overview]
Message-ID: <bug-108505-4-2v5oCzi9En@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108505-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108505
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-01-23
Ever confirmed|0 |1
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>'--with-multilib-list=aprofile,rmprofile'
is the key here really.
The problem is there is a loop around the multilib list and
tm_file="$tm_file
arm/arm-mlib.h"
gets executed twice.
So you get arm/arm-mlib.h in the list twice and gengtype does not like that.
next prev parent reply other threads:[~2023-01-23 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 18:04 [Bug c/108505] New: " srinath.parvathaneni at arm dot com
2023-01-23 18:07 ` [Bug target/108505] [13 Regression] " pinskia at gcc dot gnu.org
2023-01-23 18:27 ` pinskia at gcc dot gnu.org
2023-01-23 18:33 ` srinath.parvathaneni at arm dot com
2023-01-23 18:34 ` srinath.parvathaneni at arm dot com
2023-01-23 18:40 ` pinskia at gcc dot gnu.org [this message]
2023-01-24 9:58 ` cvs-commit at gcc dot gnu.org
2023-01-24 10:04 ` srinath.parvathaneni at arm dot com
2023-02-08 18:40 ` cvs-commit 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-108505-4-2v5oCzi9En@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).