Re: Re: Re: Adding loong architecture to dpkg

[桑猛 <sangmeng@loongson.cn>]

Hi:

> do we need to enable multilib? corrently only lp64d available?
Download gcc from the link below：
ftp://ftp.lip6.fr/pub/gcc/releases/gcc-12.2.0/gcc-12.2.0.tar.gz
Currently gcc supports lp64d, lp64f, lp64s, but our glibc does not support lp64f yet.
Considering that loongarch is a new architecture and in its infancy, we want to start with only lp64d.


> -----原始邮件-----
> 发件人: "Zhang Ning" <zhangn1985@outlook.com>
> 发送时间:2022-11-03 20:46:32 (星期四)
> 收件人: "桑猛" <sangmeng@loongson.cn>
> 抄送: "Guillem Jover" <guillem@debian.org>, debian-dpkg@lists.debian.org, JiaLingZhang <zhangjialing@loongson.cn>, "王洪虎" <wanghonghu@loongson.cn>, "张丹丹" <zhangdandan@loongson.cn>
> 主题: Re: Re: Adding loong architecture to dpkg
> 
> On Thu, Nov 03, 2022 at 03:50:10PM +0800, 桑猛 wrote:
> > Hi:
> > 
> > > I think loong64 (and potentially loong32) would be both fine.
> > We agree with the above point of view。
> > 
> > > dpkg architecture: aarch64 → arm64, x86_64 → amd64
> > We want the dpkg architecture to use loong64:
> > loongarch64 → loong64，loongarch32 → loong32
> > 
> now we have agreement on the name, should we discuss more about abi?
> 
> from gcc code, I know there are 3 abi: lp64d, lp64f, lp64s.
> 
> do we need to enable multilib? corrently only lp64d available?
> 
>  # Don't define MULTILIB_OSDIRNAMES if multilib is disabled.
>  ifeq ($(filter LA_DISABLE_MULTILIB,$(tm_defines)),)
> 
>      MULTILIB_OSDIRNAMES = \
>       mabi.lp64d=../lib64$\
>       $(call if_multiarch,:loongarch64-linux-gnuf64)
> 
>      MULTILIB_OSDIRNAMES += \
>       mabi.lp64f=../lib64/f32$\
>       $(call if_multiarch,:loongarch64-linux-gnuf32)
> 
>      MULTILIB_OSDIRNAMES += \
>       mabi.lp64s=../lib64/sf$\
>       $(call if_multiarch,:loongarch64-linux-gnusf)
> 
>  endif


本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。 
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.