From: Mao Han <han_mao@c-sky.com>
To: buildroot@buildroot.org
Cc: linux-csky@vger.kernel.org, Mao Han <han_mao@c-sky.com>,
Qu Xianmiao <xianmiao_qu@c-sky.com>,
Chen Hongdeng <hongdeng_chen@c-sky.com>,
Guo Ren <ren_guo@c-sky.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Mark Corbin <mark.corbin@embecosm.com>
Subject: [PATCH 1/2] package/toolchain-external: ensure ARCH_LIB_DIR exist
Date: Thu, 2 Jan 2020 11:57:20 +0800 [thread overview]
Message-ID: <1577937441-18703-1-git-send-email-han_mao@c-sky.com> (raw)
Different architecture may have different arch library folder structure
for their multilib toolchain. RISC-V toolchain has folder structure
like:
/sysroot/lib64/
/sysroot/lib64/lp64
/sysroot/lib64/lp64d
The first level is for ISA and the second level is for ABI.
Current buildroot only creat lib and lib64, some error is reported
while installing the external toolchain:
>>> toolchain-external-custom Installing to staging directory
/usr/bin/install -D -m 0755 /.../build/toolchain-external-custom/toolchain-wrapper /.../host/bin/toolchain-wrapper
ln: failed to create symbolic link '/.../host/riscv64-buildroot-linux-gnu/sysroot/lib64/lp64': No such file or directory
ln: failed to create symbolic link '/.../host/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64': No such file or directory
Signed-off-by: Qu Xianmiao <xianmiao_qu@c-sky.com>
Signed-off-by: Chen Hongdeng <hongdeng_chen@c-sky.com>
Signed-off-by: Guo Ren<ren_guo@c-sky.com>
Signed-off-by: Mao Han <han_mao@c-sky.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Mark Corbin <mark.corbin@embecosm.com>
---
toolchain/toolchain-external/pkg-toolchain-external.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/toolchain/toolchain-external/pkg-toolchain-external.mk b/toolchain/toolchain-external/pkg-toolchain-external.mk
index baf719a..13b2468 100644
--- a/toolchain/toolchain-external/pkg-toolchain-external.mk
+++ b/toolchain/toolchain-external/pkg-toolchain-external.mk
@@ -454,6 +454,8 @@ create_lib_symlinks = \
ARCH_LIB_DIR="$(call toolchain_find_libdir,$(TOOLCHAIN_EXTERNAL_CC) $(TOOLCHAIN_EXTERNAL_CFLAGS))" ; \
if [ ! -e "$${DESTDIR}/$${ARCH_LIB_DIR}" -a ! -e "$${DESTDIR}/usr/$${ARCH_LIB_DIR}" ]; then \
relpath="$(call relpath_prefix,$${ARCH_LIB_DIR})" ; \
+ mkdir -p "$${DESTDIR}/$${ARCH_LIB_DIR}" ; \
+ mkdir -p "$${DESTDIR}/usr/$${ARCH_LIB_DIR}" ; \
ln -snf $${relpath}lib "$${DESTDIR}/$${ARCH_LIB_DIR}" ; \
ln -snf $${relpath}lib "$${DESTDIR}/usr/$${ARCH_LIB_DIR}" ; \
fi
--
2.7.4
next reply other threads:[~2020-01-02 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:57 Mao Han [this message]
2020-01-02 3:57 ` [PATCH 2/2] toolchain: Get ld.so name if available Mao Han
2020-01-26 15:31 ` [Buildroot] " Yann E. MORIN
2020-02-05 10:30 ` Thomas De Schampheleire
2020-01-10 10:57 ` [Buildroot] [PATCH 1/2] package/toolchain-external: ensure ARCH_LIB_DIR exist Thomas De Schampheleire
2020-01-10 11:15 ` Thomas Petazzoni
2020-01-13 3:34 ` Mao Han
2020-01-16 9:36 ` Thomas De Schampheleire
2020-01-17 2:35 ` Mao Han
2020-01-24 15:00 ` Thomas De Schampheleire
2020-01-26 15:34 ` Yann E. MORIN
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=1577937441-18703-1-git-send-email-han_mao@c-sky.com \
--to=han_mao@c-sky.com \
--cc=buildroot@buildroot.org \
--cc=hongdeng_chen@c-sky.com \
--cc=linux-csky@vger.kernel.org \
--cc=mark.corbin@embecosm.com \
--cc=ren_guo@c-sky.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=xianmiao_qu@c-sky.com \
/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 NNTP newsgroup(s).