From: Deepthi.Hemraj@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com
Subject: [PATCH] gcc-target.inc: Fix gcc symlink handling for multilib support
Date: Wed, 13 Nov 2024 04:51:47 -0800 [thread overview]
Message-ID: <20241113125147.4193489-1-Deepthi.Hemraj@windriver.com> (raw)
From: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Enabling multilib support and adding both lib32-gcc-symlinks and gcc-symlinks
to the image installation results in a conflict between
gcc-symlinks-13.3.0-r0.corei7_64 and lib32-gcc-symlinks-13.3.0-r0.corei7_32.
Following error occurs because of the conflict:
"file /usr/bin/gcc conflicts between attempted installs of gcc-symlinks-13.3.0-r0.corei7_64 and lib32-gcc-symlinks-13.3.0-r0.corei7_32"
The conflict occurs because both packages try to install files in the same location,
causing installation errors during the build process.
Updated the gcc target recipe to correctly handle symlinks for multilib support by using ${MLPREFIX}gcc
instead of just gcc for the gcc binary symlink in ${PN}-symlinks.
This ensures that the symlinks point to the appropriate multilib gcc binary for 32-bit and 64-bit configurations.
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
---
meta/recipes-devtools/gcc/gcc-target.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/gcc/gcc-target.inc b/meta/recipes-devtools/gcc/gcc-target.inc
index 6b47c10413..ff59eb1b52 100644
--- a/meta/recipes-devtools/gcc/gcc-target.inc
+++ b/meta/recipes-devtools/gcc/gcc-target.inc
@@ -71,7 +71,7 @@ FILES:${PN}-dev = "\
"
FILES:${PN}-symlinks = "\
${bindir}/cc \
- ${bindir}/gcc \
+ ${bindir}/${MLPREFIX}gcc \
${bindir}/gccbug \
"
@@ -182,7 +182,7 @@ do_install () {
ln -sf gfortran f95 || true
fi
ln -sf ${TARGET_PREFIX}g++ g++
- ln -sf ${TARGET_PREFIX}gcc gcc
+ ln -sf ${TARGET_PREFIX}gcc ${MLPREFIX}gcc
ln -sf ${TARGET_PREFIX}cpp cpp
ln -sf ${TARGET_PREFIX}gcov gcov
ln -sf ${TARGET_PREFIX}gcov-tool gcov-tool
--
2.43.0
next reply other threads:[~2024-11-13 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 12:51 Deepthi.Hemraj [this message]
2024-11-13 13:23 ` [OE-core] [PATCH] gcc-target.inc: Fix gcc symlink handling for multilib support Richard Purdie
2024-11-13 19:58 ` Randy MacLeod
2024-11-13 21:00 ` Richard Purdie
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=20241113125147.4193489-1-Deepthi.Hemraj@windriver.com \
--to=deepthi.hemraj@windriver.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.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