From: WANG Xuerui <g...@xen0n.name>
There is only full support for the LP64D ABI in the initial upstream
submissions for the various low-level pieces, so full multilib
combinations are not pursued at the moment; but the expected library
search path of gcc (`lib64`) means the default of `lib` does not work
in our case.
Signed-off-by: WANG Xuerui <g...@xen0n.name>
---
eclass/multilib.eclass | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/eclass/multilib.eclass b/eclass/multilib.eclass
index 483f8d10c72..b14b0ef7785 100644
--- a/eclass/multilib.eclass
+++ b/eclass/multilib.eclass
@@ -368,6 +368,15 @@ multilib_env() {
;;
esac
;;
+ loongarch64*)
+ export CFLAGS_lp64d=${CFLAGS_lp64d--mabi=lp64d}
+ export CHOST_lp64d=${CTARGET}
+ export CTARGET_lp64d=${CTARGET}
+ export LIBDIR_lp64d=${LIBDIR_lp64d-lib64}
+
+ : ${MULTILIB_ABIS=lp64d}
+ : ${DEFAULT_ABI=lp64d}
+ ;;
mips64*|mipsisa64*)
export CFLAGS_o32=${CFLAGS_o32--mabi=32}
export CHOST_o32=${CTARGET/mips64/mips}
--
2.34.0
