devel

devel@lists.centos.org

4 participants
4640 discussions

Re: [CentOS-devel] Ceph on arm32 - failing to compile devtoolset-8-gcc-8.3.1-3.1.el7.src.rpm
by Oliver Weinmann 12 Dec '20

12 Dec '20

Hi Pablo, thanks a lot for your reply. The src.rpm I'm using is this one: https://cbs.centos.org/kojifiles/packages/devtoolset-8-gcc/8.3.1/3.1.el7/sr… It's gcc8 so the patch you linked is not really fitting. :( If you have time and could take a look that would be really cool. Best Regards, Oliver Am 12.12.2020 um 10:26 schrieb Pablo Sebastián Greco: > > On 11/12/20 11:28, Oliver Weinmann via CentOS-devel wrote: >> Hi Folks, >> >> For a small home project I would like to get cephadm working on my >> Odroid HC-2 (armhf 32). Maybe this is not going to work but I want to >> at least give it a try. I see that there are only arm64 packages and >> containers available from the Ceph repo. So I thought I just go ahead >> and compile the dependency packages myself and build a new container >> with CentOS7 arm32. Luckily there is a CentOS 7 arm32 container but I >> still need to compile the packages. After downloading all the src >> rpms i started building them and now I ended up to compile this >> package from the SCL repo as it is not available for arm32: >> >> devtoolset-8-gcc-8.3.1-3.1.el7.src.rpm >> >> It fails with an error of: >> >> checking if mkdir takes one argument... no >> *** Configuration armv7hl-redhat-linux-gnu7E not supported >> make[2]: *** [configure-stage1-gcc] Error 1 >> make[2]: Leaving directory >> `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/obj-armv7hl-redhat-linux7E' >> make[1]: *** [stage1-bubble] Error 2 >> make[1]: Leaving directory >> `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/obj-armv7hl-redhat-linux7E' >> make: *** [profiledbootstrap] Error 2 >> error: Bad exit status from /var/tmp/rpm-tmp.knxvjm (%build) > This looks very close to this fix we had to add to make gcc work on > arm > https://git.centos.org/rpms/devtoolset-7-gcc/blob/c7/f/SPECS/gcc.spec#_319 > (I'm linking to gcc7 because I can't find the other commit, but it is > the same thing). > Let me know if that helps and if it is still failing, point me to as > spec file or an srpm and I'll take a look. >> >> >> RPM build errors: >> Bad exit status from /var/tmp/rpm-tmp.knxvjm (%build) >> >> real 13m36.412s >> user 17m57.828s >> sys 3m47.905s >> >> I looked up the build log for arm64 and so I figured out that the >> next step is to access a directory called arm here: >> >> /root/rpmbuild/BUILD/gcc-8.3.1-20190311/gcc/config >> >> in the extracted source. Somehow the build process thinks my system >> is armv7hl-redhat-linux-gnu7E instead of arm and so it tries to >> access the armv7hl-redhat-linux-gnu7E directory which doesn't exist >> and fails. I simply created a symlink and this seems to be working. >> >> ln -sf arm armv7hl-redhat-linux-gnu7E >> >> Not sure if this is in general a bad idea. So I got a lot further. >> But then it fails again with this error: >> >> In file included from /usr/include/features.h:399, >> from /usr/include/stdio.h:27, >> from ../.././libgcc/../gcc/tsystem.h:87, >> from ../.././libgcc/libgcc2.c:27: >> /usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-soft.h: No such >> file or directory >> # include <gnu/stubs-soft.h> >> ^~~~~~~~~~~~~~~~~~ >> compilation terminated. >> make[3]: *** [_muldi3.o] Error 1 >> make[3]: Leaving directory >> `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/armv7l-unknown-linux-gnueabihf/libgcc' >> make[2]: *** [all-stage1-target-libgcc] Error 2 >> make[2]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311' >> make[1]: *** [stage1-bubble] Error 2 >> make[1]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311' >> make: *** [all] Error 2 >> >> real 88m2.283s >> user 67m23.211s >> sys 6m7.984s >> >> I can't find any good info on google on how to deal with this one. >> Any ideas? >> >> Best Regards, >> >> Oliver >> >> >> > Pablo.

1 0

Ceph on arm32 - failing to compile devtoolset-8-gcc-8.3.1-3.1.el7.src.rpm
by Oliver Weinmann 11 Dec '20

11 Dec '20

Hi Folks, For a small home project I would like to get cephadm working on my Odroid HC-2 (armhf 32). Maybe this is not going to work but I want to at least give it a try. I see that there are only arm64 packages and containers available from the Ceph repo. So I thought I just go ahead and compile the dependency packages myself and build a new container with CentOS7 arm32. Luckily there is a CentOS 7 arm32 container but I still need to compile the packages. After downloading all the src rpms i started building them and now I ended up to compile this package from the SCL repo as it is not available for arm32: devtoolset-8-gcc-8.3.1-3.1.el7.src.rpm It fails with an error of: checking if mkdir takes one argument... no *** Configuration armv7hl-redhat-linux-gnu7E not supported make[2]: *** [configure-stage1-gcc] Error 1 make[2]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/obj-armv7hl-redhat-linux7E' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/obj-armv7hl-redhat-linux7E' make: *** [profiledbootstrap] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.knxvjm (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.knxvjm (%build) real 13m36.412s user 17m57.828s sys 3m47.905s I looked up the build log for arm64 and so I figured out that the next step is to access a directory called arm here: /root/rpmbuild/BUILD/gcc-8.3.1-20190311/gcc/config in the extracted source. Somehow the build process thinks my system is armv7hl-redhat-linux-gnu7E instead of arm and so it tries to access the armv7hl-redhat-linux-gnu7E directory which doesn't exist and fails. I simply created a symlink and this seems to be working. ln -sf arm armv7hl-redhat-linux-gnu7E Not sure if this is in general a bad idea. So I got a lot further. But then it fails again with this error: In file included from /usr/include/features.h:399, from /usr/include/stdio.h:27, from ../.././libgcc/../gcc/tsystem.h:87, from ../.././libgcc/libgcc2.c:27: /usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-soft.h: No such file or directory # include <gnu/stubs-soft.h> ^~~~~~~~~~~~~~~~~~ compilation terminated. make[3]: *** [_muldi3.o] Error 1 make[3]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311/armv7l-unknown-linux-gnueabihf/libgcc' make[2]: *** [all-stage1-target-libgcc] Error 2 make[2]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/root/rpmbuild/BUILD/gcc-8.3.1-20190311' make: *** [all] Error 2 real 88m2.283s user 67m23.211s sys 6m7.984s I can't find any good info on google on how to deal with this one. Any ideas? Best Regards, Oliver

1 0

mdevctl missing in AppStream
by Sandro Bonazzola 11 Dec '20

11 Dec '20

Hi, I'm looking for mdevctl package which should be in AppStream but I can't find it. I see the package is on git: https://git.centos.org/rpms/mdevctl/tree/c8 Any clue? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

CentOS-Gold3 at Arizona State University
by Nick Piacentine 11 Dec '20

11 Dec '20

Hello, Could you please confirm that you are no longer using this server? I'm trying to clear out rack space, and my firewall doesn't show any use in the past 2+ years. Would you like us to dispose of the hardware, or is there another use you have for the 7+ year old hardware? Thanks, Nick ----- Nick Piacentine Director, Information Technology Mars Space Flight Facility & Instrument Development Lab Arizona State University

1 0

koji-ansible and CentOS Stream
by Ken Dreyer 10 Dec '20

10 Dec '20

Hey folks, I'm not sure where the current CentOS Stream Koji configuration is stored at the moment, but I wanted to link to this project for managing Koji configs with Ansible: https://github.com/ktdreyer/koji-ansible Some teams are using this to manage some large Koji instances inside Red Hat, and it's been working well. It's good for managing initial configurations ("day 1 operations") as well as making changes over time ("day 2 operations"). Like most stuff with Ansible, it makes configurations repeatable and easier to review. As an example, I captured some of our Storage SIG CBS tag and target configurations in Ansible here: https://github.com/ktdreyer/storage-sig-utils/tree/master/ansible It would be great to use koji-ansible as we ramp up CentOS Stream. I'd be happy to help answer any questions about this tool. - Ken

1 0

https://blog.centos.org/2020/12/future-is-centos-stream/
by Konstantin Boyandin 10 Dec '20

10 Dec '20

Hello, > The future of the CentOS Project is CentOS Stream, and over the next > year we’ll be shifting focus from CentOS Linux, the rebuild of Red Hat > Enterprise Linux (RHEL), to CentOS Stream, which tracks just ahead of a > current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will end > at the end of 2021. CentOS Stream continues after that date, serving as > the upstream (development) branch of Red Hat Enterprise Linux. > > Meanwhile, we understand many of you are deeply invested in CentOS Linux > 7, and we’ll continue to produce that version through the remainder of > the RHEL 7 life cycle. > https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates Yeah, deeply, in many a sense. I am a sysadmin, attending to quite a lot of systems, and CentOS was a real blessing. Now, as I see it, CentOS is becoming a sandbox for upcoming RHEL minor releases, so one can bid farewell to free to use, stable, reliable and predictable OS. I am currently in process of upgrading multiple CentOS-driven systems, so this piece of news has become a nasty surprise. Looks like a major decision should be taken right now. Apart from migrating to Oracle Linux (which I wouldn't like at all), and buying RHEL itself, what are other possible alternatives (just curious)? Thanks. Sincerely, Konstantin

12 16

Re: [CentOS-devel] [CentOS] CentOS 8 future
by Matthew Miller 09 Dec '20

09 Dec '20

On Tue, Dec 08, 2020 at 12:44:36PM -0600, Robert G. (Doc) Savage via CentOS wrote: > > CentOS 8's future is not looking bright. Recently deployed CentOS8 on my > > production workload and now hearing this. What do other folks think > > about this? > Speaking only for myself, I am ready to give up on CentOS (and Red Hat) > entirely. Fedora meets all my clients' needs with none of the chaos. I definitely appreciate the vote of confidence in Fedora! You're not alone in using Fedora in a lot of serious ways. However, I really encourage everyone to give this a chance. This is (post-Fedora) RHEL development opening up in a new way, and CentOS is central to it. That's a good place to be! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

11 15

Re: [CentOS-devel] [CentOS] CentOS 8 future
by Leon Fauster 09 Dec '20

09 Dec '20

Am 09.12.20 um 20:28 schrieb Jon Pruente: > On Wed, Dec 9, 2020 at 5:24 AM Leon Fauster via CentOS > <centos(a)centos.org <mailto:centos@centos.org>> wrote: > > > The relatively fewer that are on CentOS Linux 8 have some > decisions to > > make. The end of 2021 is sooner than they were expecting *but* > there is > > a fully available upgrade path from CentOS Linux 8 to CentOS > Stream 8 > > (IE: not a reinstall), and that will take them to 2024. That's > half of > > the 10 years they might have expected, but it should let them give > > Stream a try and see if it is for them or not. > > If "Stream" is the base for the next RHEL8.x where are the updates > until > 2029 coming from, when CentOS Stream 8 will be shutdown at 2024? > > > I think you've confused some dates, unless you have a link to the > 2024 date for Stream 8. CentOS 7 will continue until 2024. CentOS Stream > 8 doesn't have a clear EOL, but it is presumably at or before the end of > RHEL 8 in 2029. CentOS 8 EOL has been yanked back to 2021. > > https://centos.org/centos-stream/ <https://centos.org/centos-stream/> > > End-of-life > > N/A No, its exactly as I said: https://lists.centos.org/pipermail/centos/2020-December/352340.html https://centos.org/distro-faq/#q13-can-i-start-up-a-sig-that-will-maintain-… (full-support -> 2024). -- Leon

1 0

RedHat potential kernel bug 1904817
by H 09 Dec '20

09 Dec '20

I reported a potential kernel bug in the USB subsystem of CentOS 7.9 a couple of days ago, bug 1904817, but accidentally locked myself out of viewing the bug report a few minutes ago... Could someone who has the ear of whoever is running the RedHat Bugzilla system change it back so that I, the reporter, am able to view the report again? Further, I saw that this bug was locked and not accessible to anyone besides the reporter and the cc-list. Not clear why this would be?? Again, I am the reporter. Thank you in advance.

2 2

Re: [CentOS-devel] [CentOS] CentOS 8 future
by Strahil Nikolov 09 Dec '20

09 Dec '20

It seems another Fork will come up... or we switch to openSUSE (at least they haven't mentioned it will become a testing ground for their clients). Best Regards, Strahil Nikolov В 12:44 -0600 на 08.12.2020 (вт), Robert G. (Doc) Savage via CentOS написа: > On Tue, 2020-12-08 at 11:58 -0500, Satish Patel wrote: > > Folks, > > > > What is going on here > > https://blog.centos.org/2020/12/future-is-centos-stream/ > > > > CentOS 8's future is not looking bright. Recently deployed CentOS8 > > on > > my production workload and now hearing this. What do other folks > > think > > about this? > > Speaking only for myself, I am ready to give up on CentOS (and Red > Hat) > entirely. Fedora meets all my clients' needs with none of the chaos. > > I shall miss the stability of past CentOS releases, much as I did > those > of Scientific Linux. > > --Doc Savage > Fairview Heights, IL > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel