public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: SRINATH PARVATHANENI <sripar01@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5322] arm: Fix inclusion of arm-mlib.h header more than once (pr108505). Date: Tue, 24 Jan 2023 09:58:40 +0000 (GMT) [thread overview] Message-ID: <20230124095840.44ABF3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:275820c09e5f397040cbff69c90012dc1e220faf commit r13-5322-g275820c09e5f397040cbff69c90012dc1e220faf Author: Srinath Parvathaneni <srinath.parvathaneni@arm.com> Date: Tue Jan 24 09:57:52 2023 +0000 arm: Fix inclusion of arm-mlib.h header more than once (pr108505). The patch fixes the build issue for arm-none-eabi target configured with --with-multilib-list=aprofile,rmprofile, in which case the header file arm/arm-mlib.h is being included more than once and the toolchain build is failing (PR108505). gcc/ChangeLog: 2023-01-24 Srinath Parvathaneni <srinath.parvathaneni@arm.com> PR target/108505 * config.gcc (tm_file): Move the variable out of loop. Diff: --- gcc/config.gcc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config.gcc b/gcc/config.gcc index 771bd35e803..d828223c16d 100644 --- a/gcc/config.gcc +++ b/gcc/config.gcc @@ -4350,7 +4350,6 @@ case "${target}" in case ${arm_multilib} in aprofile|rmprofile) tmake_profile_file="arm/t-multilib" - tm_file="$tm_file arm/arm-mlib.h" ;; @*) ml=`echo "X$arm_multilib" | sed '1s,^X@,,'` @@ -4389,6 +4388,7 @@ case "${target}" in # through to the multilib selector with_float="soft" tmake_file="${tmake_file} ${tmake_profile_file}" + tm_file="$tm_file arm/arm-mlib.h" TM_MULTILIB_CONFIG="$with_multilib_list" fi fi
reply other threads:[~2023-01-24 9:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230124095840.44ABF3858D28@sourceware.org \ --to=sripar01@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).