Re: Re: Adding loong architecture to dpkg
Hi:
The following code in https://man7.org/linux/man-pages/man1/dpkg-architecture.1.html:
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
[…]
ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
confflags += --build=$(DEB_HOST_GNU_TYPE)
else
confflags += --build=$(DEB_BUILD_GNU_TYPE) \
--host=$(DEB_HOST_GNU_TYPE)
endif
[…]
./configure $(confflags)
If you use loong64, it will be contrary to the loongarch64 logo used by gcc, so we still want to use loongarch64 as the arch name。
> -----原始邮件-----
> 发件人: "桑猛" <sangmeng@loongson.cn>
> 发送时间:2022-11-01 19:17:38 (星期二)
> 收件人: "Guillem Jover" <guillem@debian.org>
> 抄送: debian-dpkg@lists.debian.org, JiaLingZhang <zhangjialing@loongson.cn>, "王洪虎" <wanghonghu@loongson.cn>
> 主题: Re: Adding loong architecture to dpkg
>
> Hi!
>
> We hope that the arch name can use loongarch64, mainly based on the following considerations:
> 1. The current upstream compilers gcc, llvm, etc. use loongarch64.
> 2. The current upstream kernel uses loongarch64.
> 3. At present, there is no special convention for the length of the architecture name. If loong64 is used, it is easier to be confused with the previously used loongarch64.
>
> > -----原始邮件-----
> > 发件人: "Guillem Jover" <guillem@debian.org>
> > 发送时间:2022-10-08 20:16:35 (星期六)
> > 收件人: debian-dpkg@lists.debian.org
> > 抄送: JiaLingZhang <zhangjialing@loongson.cn>, "桑猛" <sangmeng@loongson.cn>
> > 主题: Adding loong architecture to dpkg
> >
> > Hi!
> >
> > I think most parts are ready now upstream, for Debian AFAIUI the
> > missing piece is a newer glibc currently sitting in experimental.
> >
> > If you want to get this added, it would be nice to do so before the
> > Debian release freeze, or you'll not be able to later add some of the
> > support to other packages or infrastructure in Debian if the version
> > of dpkg in Debian stable does not support it too. (I mean we can
> > always add it in a stable update, but I'd rather avoid it.)
> >
> > For dpkg the usual procedure to add it is described here:
> > <https://wiki.debian.org/Teams/Dpkg/FAQ#Q._Can_we_add_support_for_new_dpkg_architectures.3F>
> >
> > So we'd need to make clear what ABI this is going to describe, etc.
> > And then agree on the arch name. My main concern as I've pointed out
> > elsewhere at least in [D] and [L] is the "arch" part in the name,
> > similar to other distributions such as Gentoo (AFAIR). Depending on
> > whether you'd want also an 32-bit arch, we might want to suffix with
> > 64, etc.
> >
> > [D] https://github.com/guillemj/dpkg/pull/6
> > [L] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989125#15
> >
> > Thanks,
> > Guillem
>
>
> 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
> 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.
本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
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.
Reply to: