Arm-dev May 2015

arm-dev@lists.centos.org

13 participants
9 discussions

armv7hl - centos 7.1 rebuild status
by Fabian Arrotin 20 Jun '15

20 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks ! Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop) Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..) As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki. Volunteers ? :-) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVoaBEACgkQnVkHo1a+xU6FRACgkSCATUH+XLztEXxfuXjuXmi5 GCsAniJN/S/AudeL4ffuCqWbfbBi5PJJ =Z4Av -----END PGP SIGNATURE-----

6 33

CentOS-7 beta candidate for AArch64 platforms
by Jim Perrin 27 May '15

27 May '15

We are pleased to announce the public beta release of CentOS Linux 7 for AArch64 compatible hardware. We've addressed a number of issues discovered from the previous 2 weeks of alpha testing, and feel that the release is stable enough to transition to beta. Improvements from Alpha ======================= Improved package selection: A number of additional packages have been added, including libreoffice, evolution, abrt, and more. Updated kernel: Some non-fatal kernel errors have been address by moving to a 4.1rc based kernel version. This also adds ACPI functionality to the platform. Improved Group selection: The installer now offers a larger group selection from the previous minimal-only install. Installation ============ Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Download ======== The full (unsigned) install tree is available at http://buildlogs.centos.org/centos/7/os/aarch64/ ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch), and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a loose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

CentOS 7 ARMv7 build status
by Fabian Arrotin 25 May '15

25 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been busy on various things (including personal and family related issues) but I had some time to work on the plague build farm. After a discussion with Johnny, KB and Jim, we thought that it would be a good idea to try to focus first on a "self-contained" buildroot, and only then trying to rebuild the 7.1503 SRPMS against that buildroot, and not against F19/F20 (there will be some issues that will need to be solved though) I got a "self-contained" buildroot, rebuilt from 7.1503 packages, and I started with gcc, then glibc, then kernel (4.0.0-1, for compat reason with aarch64), and each time repodata was regenerated , so glibc has been rebuilt with gcc from 7.1.1503, etc .. The current c7-buildroot is here : http://armv7.dev.centos.org/repodir/c7-buildroot/ Then I put all the 7.1503 in the queue, and target name being c7-pass-1 , and the built packages are located here : http://armv7.dev.centos.org/repodir/c7-pass-1/ As plague-server required mod_python (deprecated now) we don't have any Web UI people can have a look at. But I created a "quick-and-dirty" script that gathers information from the mysql DB, and outputs that here : - - Packages in the current queue : http://armv7.dev.centos.org/queue.html - - Packages in a "failed" status : http://armv7.dev.centos.org/report.html (with link to the log files) Those pages are generated every 5 minutes, through a cron job. Now that we have something that can be used, I'll work on the access for contributors (two names are on my list). Actually, I'm also using the list of packages in failed status, to requeue those at the end, automatically. A best option would be to do that in a "clever" way, so trying to build a map of BuildRequires: and so which package would need to be built before another one, but my time is limited at the moment ( <hint> welcome ! </hint> ) I'm not expecting that to work for a complete and final tree though. So we'll have to have a look at the build logs, and sometimes we'll probably have to use a specific mock config file for one or two packages (or even a "patch" will be needed too) so the best/easiest/fastest will probably be to do that "locally" and not use plague (even if using the same build nodes) I had to exclude some packages from the queue, as armv7hl was excluded, but we can probably investigate if that can be built or not ... I guess people don't want me to spam the list every day with a long list of packages still in the queue :-) , so everybody can have a look at the website. If you have brilliant ideas, opinions, etc .. feel free to comment and participate. Sorry if that took more time that what I was expecting ... Kind Regards - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVdySwACgkQnVkHo1a+xU6x6ACdGbZrnpCpJAxaNkezmSnQreiz iIAAnAlK1zMJ3BRq+3TsA1wbe0HlAnBt =elV4 -----END PGP SIGNATURE-----

4 4

opening up the armv7hl plague builders (was plague farm)
by Fabian Arrotin 19 May '15

19 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there ! We've all been busy on various things in parallel, but I wanted to give a status update to the list, about those armv7hl nodes that we can use to bootstrap/build CentOS 7. I just tested that the plague setup was running fine (so basically plague-server accepting jobs, and distributing those jobs amongs the builders nodes). We'd like now to open access to that plague build farm. I've just started a wiki page dedicated to this (http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32) containing some basic info on how to install and configure plague-client. We still have to discuss a good target/mock config files naming convention, including which repo are already available for dev/users. As a reminder, those nodes are currently running Fedora 21, and as plague WebUI needed mod_python, but not available anymore, we currently have no http/web ui that people can have a look at. OTOH, plague-server now sends the build logs/reports fine, and everybody can access the repodata/files/build logs at the following location (just using mod index for now) : http://armv7.dev.centos.org/repodir (for the built packages, including repodata) http://armv7.dev.centos.org/rpmbuild (for the log files) As an example, I submitted blindly all CentOS 7.0.1406 SRPMS to plague, using a f19 as buildroot. If we consider gcc : - - build log is available at http://armv7.dev.centos.org/rpmbuild/centos-f19-7-0-arm/515-gcc-4.8.2-16.el… - - artifact/rpm[s] are available at http://armv7.dev.centos.org/repodir/centos-f19-7-0-arm/gcc/4.8.2-16.el7/arm… If you need/want access, feel free to discuss that on this list, but also to create a bug report on https://bugs.centos.org, in the Buildsys project, category "community buildsys - arm32" Let's discuss what would be the best option for the target names/mock config files, and I can then let $cfgmgmt distribute that to server/builders. Happy Monday ! :-) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVQmxsACgkQnVkHo1a+xU4NmACeObf3iINOAUo7sC8k99H+DmlE B6cAmwQsSsTy6+dLqI4OijOUAEpSXUqm =DXgQ -----END PGP SIGNATURE-----

5 6

best kernel for armv7hl ?
by cc35359 gma 13 May '15

13 May '15

Fabian, I dont normally travel to these CentOS mailing lists, however, I wanted to mention about how I shoved Fedora Rawhide on a number of raspberry pis, because i think it would be a highly advantageous idea to push out at least a minimal image for the raspberry pi with the armv7 release for CentOS 7. If not that, at least have a clear path for those wanting it. In my adventures with rawhide on the raspis, i've found that the best way to handle the hardware is by using the kernel actually distributed by the raspi foundation, versus compiling my own. unfortunately there are a few broadcom pieces that make it difficult. In order to get rawhide running, it was a very simple process. 1. mount the fedora image 2. make an sd card paritioned how you want it (i dont use swap on sd card, so just 500 mb for /boot, and the rest for /. 3. rsync the data to the sd card, except the boot. 4. copy the boot directory from the raspi's git with the necessary firmware. 5. copy the kernel libraries. 6. i created a dracut initrd because i needed to have dm-crypt available because i normally encrypt the / partition myself. 7. modify fstab, boot.txt, cmdline.txt as necessary 8. boot, and its magic. I dont mind repeating the process for a centos image if help is needed, perhaps creating a scripted method to generate the images for the future would be something to look into. So that was a lot of rambling, but long story short, i can assist you with a raspberry pi image based on my fedora creations if we feel that centos can provide such an image. otherwise once the armv7 packages are ready, i can create documentation and a potential "offsite" image if there are legal reasons for not supplying it. thanks for listening, -David

2 3

best kernel for armv7hl ?
by Fabian Arrotin 11 May '15

11 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As Jim used kernel 4.0.0-1 for the aarch64 (alpha) build (announced today), I was wondering what would be the best kernel to use/target for armv7hl. Is patching the el7 kernel the way to go, or do we prefer/want to use the same one everywhere if possible (so also using 4.0.0-1, and tracking the aarch64 version). Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVQ5ZgACgkQnVkHo1a+xU6BFgCfbIaaP1kpWUKHTIKuW55cUiaS 4NYAn3cjUVikbTqYvXllMb4l4B9PMSZO =xI8e -----END PGP SIGNATURE-----

2 1

Release of CentOS-7 (alpha candidate) for AArch64 platforms
by Jim Perrin 11 May '15

11 May '15

We are pleased to announce the public alpha release of CentOS Linux 7 for AArch64 compatible hardware. This is the initial alpha release based on CentOS Linux 7 1503 ( Rebuilt from Red Hat Enterprise Linux 7.1 sources ), with architecture and modifications patching as necessary. Because this hardware is very new and support for it is still evolving, there is no expectation for kernel ABI compatibility. Additionally, until the alpha period ends both the OS repository and the Updates repository are subject to change. This release was built on an X-Gene system from Applied Micro. We are working to test against other platforms to ensure broad compatibility. ======== Download You can find the install tree and repositories at http://buildlogs.centos.org/centos/7/os/aarch64/ While the build is in alpha, we are not releasing full isos as you would traditionally find with the x86_64 builds. Please use the boot.iso which has been pre-configured for a network install, or pxe from a locally hosted mirror of the installation tree. We plan to make disk images available soon to help vendors bootstrap their platforms. ============ Installation Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Because several packages are not yet available, the group information has been reduced and the only available installation option is 'minimal'. If you perform kickstart based installs, please note the only available group is currently 'Core'. We will improve upon this throughout the alpha process. ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch), and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a lose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. In the next few days, we'll be adding a branch to git for modified packages so that patches are available to the community, as well as providing a repository for the debug-info packages. ================================== Coming Soon // Future Improvements * Rebase to 4.1rc kernel * Improve package and group availability * Add additional hardware support * Disk images to support install via dd -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

a plague farm ?
by Karanbir Singh 07 May '15

07 May '15

hi guys, We have a few nodes that can be used, public facing, for builds - and we have Howards's bootstrap image in place. With that in mind, can we as a group help with the wider armv7 effort at this point ? One option might be to see if we can get this image loaded onto the nodes we have from online.net ? and then get a plague builder thread on each node. We can host the plague server on a different machine, as long as network latency isnt too high we should be fine. This would then allow people to setup and submit jobs without needing the entire setup at their own place. Plague, since koji isnt suiteable here, yet. Plus we have some plague expertise already ( we still use it for CentOS-5 builds ). Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

11 39

EPEL 7 packages for arm
by Troy Dawson 06 May '15

06 May '15

I'm not sure if this question belongs here or on a fedora mailing list. Or maybe it's already been discussed somewhere and I just missed it. Is there a plan on what to do with EPEL7 packages, for arm? Is Fedora thinking of adding arm to the EPEL7 build arch? Is CentOS planning on hosting a repo that contains those? If so, will it be all EPEL7 or just a subset? Right now, if you had all the CentOS7 arm packages compiled and ready to go, you wouldn't be able to create a build/plague machine, because mock, and several of it's dependencies, are in EPEL7, and not RHEL7. Anyway, if this has already been discussed, could someone point me at it. If it hasn't, where would be the appropriate place to discuss it? Thanks Troy

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev May 2015