- Arch-ports - lists.archlinux.org

Re: [arch-ports] Advice on bootstrapping Arch onto a new
by Sijie Bu 26 Apr '21

26 Apr '21

Thank you! The information are indeed useful! ________________________________ From: Andreas Baumann Sent: Monday, April 26, 2021 02:27 To: Discussion regarding the porting of Arch Linux to non-x86_64 architectures Cc: Sijie Bu Subject: Re: [arch-ports] Advice on bootstrapping Arch onto a new architecture? Reply-To: Andreas Baumann <mail(a)andreasbaumann.cc> In-Reply-To: <BY5PR14MB3669ACC64AF81801392F1F64DA429(a)BY5PR14MB3669.namprd14.prod.outlook.com> On Mon, Apr 26, 2021 at 09:00:04AM +0000, Sijie Bu via arch-ports wrote: > (This message was originally posted on arch-general and I was redirected by a member to this list.) > > Hello, Hi, > I am about to start working as an intern at CIP United, a company focusing on MIPS chips, and I will be bootstrapping Arch Linux onto the MIPS64r6 architecture, in a fashion similar to Arch Linux ARM. > > I have checked the Arch Linux MIPS project, but it seems to be inactive for years now. I have checked ArchWiki's DeveloperWiki section, but it seems to lack guidelines or suggestions on bootstrapping Arch onto a new architecture. Therefore I have a few questions: > - Intuitively, I think I should cross-compile the packages of the "core" section (sans a few x64-specific packages) and build a bootable rootfs, but I was having some trouble finding how should I set makepkg to cross-compile. Do I just set up an Arch developer environment as usual, but substitute the toolchain with the cross ones? I did a "cross-compile" from x86_64 to i486 some time ago, you can maybe find some useful information in https://git.archlinux32.org/bootstrap32/. I can also recommend the oakensource's RISC-V port at https://github.com/oaken-source/parabola-cross-bootstrap Basically yes, you'll need a cross toolchain for MIPS, either from the AUR or use a cross-platorm distro like http://t2sde.org/ to bootstrap directly from MIPS (in qemu or so). > - Does adding a new architecture require modifications to the pacman source code? Or pacman itself should support new architectures? I have also tried looking at pacman source code, and it seems to not have hard-coded list of architectures, but I am not 100% sure about this (if I'll have to modify the source code of pacman, I will be emailing the pacman-dev mailing list regarding their policies on patches etc.). In theory pacman should be quite portable (it runs at least on x86_64, IA32, ARM 32-bit, AARCH64). So the typical 32-/64-bit issues should have been fixed. You will have to make pacman know about your new architecture (and eventually subarchitectures). See our fork of pacman on https://git.archlinux32.org/pacman/ (basically auto-detection for SSE2, support for sub-architectures 'i486', 'i686', 'pentium4'). Most work I expect in breaking cycles and dependencies in PKGBUILDs. > > Thank you for your time and have a nice day. > Sincerely > _______________________________________________ > arch-ports mailing list > arch-ports(a)lists.archlinux.org > https://lists.archlinux.org/listinfo/arch-ports Happy porting, feel free to ask questions on IRC at #archinux-ports or #archlinux32. :-) Cheers Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc<http://www.andreasbaumann.cc>

1 0

Re: [arch-ports] Advice on bootstrapping Arch onto a new
by Sijie Bu 26 Apr '21

26 Apr '21

It's MIPS64 Rev6. Currently it seems that there are no available processors, but QEMU is available. ________________________________________ From: Andreas Baumann Sent: Monday, April 26, 2021 02:27 To: Discussion regarding the porting of Arch Linux to non-x86_64 architectures Cc: Sijie Bu Subject: Re: [arch-ports] Advice on bootstrapping Arch onto a new architecture? Reply-To: Andreas Baumann <mail(a)andreasbaumann.cc> In-Reply-To: <BY5PR14MB3669ACC64AF81801392F1F64DA429(a)BY5PR14MB3669.namprd14.prod.outlook.com> On Mon, Apr 26, 2021 at 09:00:04AM +0000, Sijie Bu via arch-ports wrote: > (This message was originally posted on arch-general and I was redirected by a member to this list.) > > Hello, Hi, > I am about to start working as an intern at CIP United, a company focusing on MIPS chips, and I will be bootstrapping Arch Linux onto the MIPS64r6 architecture, in a fashion similar to Arch Linux ARM. > > I have checked the Arch Linux MIPS project, but it seems to be inactive for years now. I have checked ArchWiki's DeveloperWiki section, but it seems to lack guidelines or suggestions on bootstrapping Arch onto a new architecture. Therefore I have a few questions: > - Intuitively, I think I should cross-compile the packages of the "core" section (sans a few x64-specific packages) and build a bootable rootfs, but I was having some trouble finding how should I set makepkg to cross-compile. Do I just set up an Arch developer environment as usual, but substitute the toolchain with the cross ones? I did a "cross-compile" from x86_64 to i486 some time ago, you can maybe find some useful information in https://git.archlinux32.org/bootstrap32/. I can also recommend the oakensource's RISC-V port at https://github.com/oaken-source/parabola-cross-bootstrap Basically yes, you'll need a cross toolchain for MIPS, either from the AUR or use a cross-platorm distro like http://t2sde.org/ to bootstrap directly from MIPS (in qemu or so). > - Does adding a new architecture require modifications to the pacman source code? Or pacman itself should support new architectures? I have also tried looking at pacman source code, and it seems to not have hard-coded list of architectures, but I am not 100% sure about this (if I'll have to modify the source code of pacman, I will be emailing the pacman-dev mailing list regarding their policies on patches etc.). In theory pacman should be quite portable (it runs at least on x86_64, IA32, ARM 32-bit, AARCH64). So the typical 32-/64-bit issues should have been fixed. You will have to make pacman know about your new architecture (and eventually subarchitectures). See our fork of pacman on https://git.archlinux32.org/pacman/ (basically auto-detection for SSE2, support for sub-architectures 'i486', 'i686', 'pentium4'). Most work I expect in breaking cycles and dependencies in PKGBUILDs. > > Thank you for your time and have a nice day. > Sincerely > _______________________________________________ > arch-ports mailing list > arch-ports(a)lists.archlinux.org > https://lists.archlinux.org/listinfo/arch-ports Happy porting, feel free to ask questions on IRC at #archinux-ports or #archlinux32. :-) Cheers Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc

1 0

Re: [arch-ports] Advice on bootstrapping Arch onto a new
by Andreas Baumann 26 Apr '21

26 Apr '21

architecture? Reply-To: Andreas Baumann <mail(a)andreasbaumann.cc> In-Reply-To: <BY5PR14MB3669ACC64AF81801392F1F64DA429(a)BY5PR14MB3669.namprd14.prod.outlook.com> On Mon, Apr 26, 2021 at 09:00:04AM +0000, Sijie Bu via arch-ports wrote: > (This message was originally posted on arch-general and I was redirected by a member to this list.) > > Hello, Hi, > I am about to start working as an intern at CIP United, a company focusing on MIPS chips, and I will be bootstrapping Arch Linux onto the MIPS64r6 architecture, in a fashion similar to Arch Linux ARM. > > I have checked the Arch Linux MIPS project, but it seems to be inactive for years now. I have checked ArchWiki's DeveloperWiki section, but it seems to lack guidelines or suggestions on bootstrapping Arch onto a new architecture. Therefore I have a few questions: > - Intuitively, I think I should cross-compile the packages of the "core" section (sans a few x64-specific packages) and build a bootable rootfs, but I was having some trouble finding how should I set makepkg to cross-compile. Do I just set up an Arch developer environment as usual, but substitute the toolchain with the cross ones? I did a "cross-compile" from x86_64 to i486 some time ago, you can maybe find some useful information in https://git.archlinux32.org/bootstrap32/. I can also recommend the oakensource's RISC-V port at https://github.com/oaken-source/parabola-cross-bootstrap Basically yes, you'll need a cross toolchain for MIPS, either from the AUR or use a cross-platorm distro like http://t2sde.org/ to bootstrap directly from MIPS (in qemu or so). > - Does adding a new architecture require modifications to the pacman source code? Or pacman itself should support new architectures? I have also tried looking at pacman source code, and it seems to not have hard-coded list of architectures, but I am not 100% sure about this (if I'll have to modify the source code of pacman, I will be emailing the pacman-dev mailing list regarding their policies on patches etc.). In theory pacman should be quite portable (it runs at least on x86_64, IA32, ARM 32-bit, AARCH64). So the typical 32-/64-bit issues should have been fixed. You will have to make pacman know about your new architecture (and eventually subarchitectures). See our fork of pacman on https://git.archlinux32.org/pacman/ (basically auto-detection for SSE2, support for sub-architectures 'i486', 'i686', 'pentium4'). Most work I expect in breaking cycles and dependencies in PKGBUILDs. > > Thank you for your time and have a nice day. > Sincerely > _______________________________________________ > arch-ports mailing list > arch-ports(a)lists.archlinux.org > https://lists.archlinux.org/listinfo/arch-ports Happy porting, feel free to ask questions on IRC at #archinux-ports or #archlinux32. :-) Cheers Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc

1 0

[arch-ports] Advice on bootstrapping Arch onto a new architecture?
by Sijie Bu 26 Apr '21

26 Apr '21

(This message was originally posted on arch-general and I was redirected by a member to this list.) Hello, I am about to start working as an intern at CIP United, a company focusing on MIPS chips, and I will be bootstrapping Arch Linux onto the MIPS64r6 architecture, in a fashion similar to Arch Linux ARM. I have checked the Arch Linux MIPS project, but it seems to be inactive for years now. I have checked ArchWiki's DeveloperWiki section, but it seems to lack guidelines or suggestions on bootstrapping Arch onto a new architecture. Therefore I have a few questions: - Intuitively, I think I should cross-compile the packages of the "core" section (sans a few x64-specific packages) and build a bootable rootfs, but I was having some trouble finding how should I set makepkg to cross-compile. Do I just set up an Arch developer environment as usual, but substitute the toolchain with the cross ones? - Does adding a new architecture require modifications to the pacman source code? Or pacman itself should support new architectures? I have also tried looking at pacman source code, and it seems to not have hard-coded list of architectures, but I am not 100% sure about this (if I'll have to modify the source code of pacman, I will be emailing the pacman-dev mailing list regarding their policies on patches etc.). Thank you for your time and have a nice day. Sincerely

1 0

[arch-ports] Linux-zen failing builds.
by Aseem Athale 14 Feb '21

14 Feb '21

I created an issue on upstream linux-zen about our builds failing, no reply yet. In the meanwhile, the errors are related to TCP BBR modules, specifically, the BBR v2 module that was added (recently?) to the kernel. And related to that, linux-zen has a flag, >CONFIG_TCP_CONG_BBR2=m which no other kernel of ours have. Maybe this is why every kernel except linux-zen is building? Also, is there a mechanism for Arch32 builds, where we test out patches by building, without committing the patch to the packages repo? I ask, because I have a patch disabling that option for linux-zen, but I want to see if it builds first, as I am not sure if disabling that option will fix our issue. Here's the patch anyways. -- Aseem Athale

1 0

Re: [arch-ports] Issue with package community/facter 3.14.11-1.0
by Andreas Baumann 14 Jan '21

14 Jan '21

Hi, Sorry for the late answer, I rebuilt facter and pushed it to stable. Also we are collecting icu67 related issues in the following bug report now: https://bugs.archlinux32.org/index.php?do=details&task_id=121 Temporarily there is a shim package 'icu67' for packages still requiring the old ICU version and we either were not able yet or the package refuses to rebuild currently. Cheers Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: mail(a)andreasbaumann.cc Homepage: www.andreasbaumann.cc

1 0

[arch-ports] Issue with package community/facter 3.14.11-1.0
by Quien Sabe 14 Jan '21

14 Jan '21

Following a system update this morning my puppet agent began failing. I am sure there are probably more package that need rebulding but fact is now missing these shared library rquirements $ ldd libfacter.so | grep 'not found' libicudata.so.67 => not found libicui18n.so.67 => not found libicuuc.so.67 => not found libicudata.so.67 => not found libicui18n.so.67 => not found libicuuc.so.67 => not found libicudata.so.67 => not found libicui18n.so.67 => not found libicuuc.so.67 => not found I created symlinks to the .68 versions of the library which apparently came with the system update which resulted in this error sudo ruby -W0 /usr/bin/puppet config print config libfacter was not found. Please make sure it was installed to the expected location. /usr/lib/libboost_regex.so.1.72.0: undefined symbol: u_isspace_67 - /usr/lib/libfacter.so I searched https://archlinux32.org/ thoroughly and the closest place I found to report an issue was this mailing list. Sent from Mailspring (https://getmailspring.com/), the best free email app for work

2 1

[arch-ports] New IPs for gr.mirror
by Polichronucci 29 Oct '20

29 Oct '20

Hello list, I changed hosting platforms for the VM hosting the mirror, so I now have new IPs. I would like you to change the DNS records to point to the new IPs please. IPv4: 83.212.170.30 IPv6: 2001:648:2ffc:1116:a800:ff:fea9:2a63 Please notify me as soon as you make the change. I will leave the old VM running for a few more days in order for the DNS TTLs to expire. -- polichronucci(a)archlinux32.org GPG: 0x7E8A06A6C80574E4

2 2

[arch-ports] Main achlinux23.org site
by Polichronucci 10 Apr '20

10 Apr '20

Hello list, we had to move the VM that the archlinux32.org main site runs on to new hardware nodes. Sadly I was responsible to inform the list but I never got around to it, sorry about that. By moving the VM we had to change IPs, but we are also able to acquire more resources now. The VM now runs on nodes with 20Gbit uplink, the storage sits on a ceph cluster and the CPU clock of the nodes hits 3GHz at max. Things should be back online now. -- polichronucci(a)archlinux32.org GPG: 0x7E8A06A6C80574E4

1 0

[arch-ports] Mirror in Greece
by Polichronucci 10 Apr '20

10 Apr '20

Hello list, I just created a mirror for the archlinux32 repositories. It is served under the following IPs and the web server is listening for the host "gr.mirror.archlinux32.org", there is no https yet. If you would be so kind to create records for the domain and add it to the mirrorlist. - 83.212.111.94 - 2001:648:2ffc:1225:a800:1ff:fe40:e178 PS. I currently sync from "mirror.archlinux32.org", if this creates any problem just let me know so I can use another mirror. -- polichronucci(a)archlinux32.org GPG: 0x7E8A06A6C80574E4

1 0