On Donnerstag, 26. März 2020, 16:28:39 CET wrote Johanna Amann:
Hi,
sorry - that was just me mistyping things. The gcc that one gets from devtoolset-7 on opensuse build service is 7.2.1 - which is too old.
When installing a CentOS release at home, updating everything, and installing devtoolset-7 I get 7.3.1 - which is new enough.
would be interessting via which repo-md metadata. Because even though the 7.3.1 rpm is out there the meta data of the repo http://mirror.centos.org/centos-7/7/sclo/x86_64/rh/repodata/ is outdated. And the devtoolset-7 subdir has no repo data at all.
I would love to use devtoolset-8 or 9 on here. However - when I try that - I just get the following message: “nothing provides devtoolset-8-gcc-c++, nothing provides devtoolset-8-elfutils, nothing provides devtoolset-8-binutils, nothing provides devtoolset-8-make, nothing provides devtoolset-8-toolchain”. Same with devtoolset-9.
yeah, most likely because they just put rpms there but not refresh meta data. But when you get it in your installed system it must be somewhere...
Thanks for the help, Johanna
On 25 Mar 2020, at 4:33, Ondrej Musil wrote:
Why don't you use the devtoolset-7 GCC (aka GCC 7.x)? (or devtoolset 6, 8 or 9) -- ONDŘEJ MUSIL | Core System Developer M: +420603305490
QORE Technologies s.r.o. Přemyslovská 1939/28 • 130 00 Prague 3 – Žižkov • Czech Republic www.qoretechnologies.com
On Wed, 25 Mar 2020 at 11:21, Adrian Schröter
wrote: On Dienstag, 24. März 2020, 20:56:24 CET wrote Johanna Amann:
Hi,
thank you very much - this really helped. I excluded EPEL, and am just using packets from scl-rhscl now, giving an exact list. The problematic one apparently was cmake3 from EPEL, which leads to the block. Luckily cmake3 is also available in scl-rhscl via the llvm toolchain.
I have one additional question/request. Would it potentially be possible to update the scl-rhscl repo to a newer version? Currently it comes with
It used whatever is behind
http://mirror.centos.org/centos-7/7/sclo/x86_64/rh/
this should be a moving target always using the latest
gcc 4.2 - which has a few bugs which prevents complication of the package I want to build. gcc 4.3 — which is in the current version of devtoolset7 for CentOs 7 — does not have this problem.
Thank you very much, Johanna
On 20 Mar 2020, at 4:38, Ondrej Musil wrote:
Few things:
1) You don't need the epel-release package since you already have the Fedora:EPEL:7 repo in the project meta configuration.
2) You are requiring devtoolset-7 for the build, but then you never enable the devtoolset before the actual configure and make commands. You should add something like the following before: %if 0%{?el7} # enable devtoolset7 . /opt/rh/devtoolset-7/enable %endif
3) I remember that for me, requiring the whole devtoolset-7 was broken, and since I needed just the basics for building, I solved it by requiring only the following packages: devtoolset-7-gcc-c++ devtoolset-7-elfutils devtoolset-7-binutils devtoolset-7-make devtoolset-7-toolchain
-- ONDŘEJ MUSIL | Core System Developer M: +420603305490
QORE Technologies s.r.o. Přemyslovská 1939/28 • 130 00 Prague 3 – Žižkov • Czech Republic www.qoretechnologies.com
On Fri, 20 Mar 2020 at 09:00, Adrian Schröter
wrote: On Freitag, 20. März 2020, 00:53:08 CET wrote Johanna Amann: > Hi Adrian, > >>> I am trying to build a package for CentOS that requires some >>> packages >>> from epel + the developer toolset to be built. >>> >>> I added the repositories in the project meta configuration - >>> which >>> looks >>> like this: >>> >>> <repository name="CentOS_7"> >>> <path project="security:zeek" repository="CentOS_7"/> >>> <path project="Fedora:EPEL:7" repository="standard"/> >>> <path project="CentOS:CentOS-7" repository="scl-rhscl"/> >>> <path project="CentOS:CentOS-7" repository="standard"/> >>> <arch>x86_64</arch> >>> </repository> >>> >>> The spec file then require some packages from the repository, >>> speficically: >>> >>> BuildRequires: epel-release kernel-devel cmake3 devtoolset-7 >>> >>> After trying this, the build has been blocked with the status >>> “downloading 6 dod packages”. >>> >>> Could anyone point me to what I am doing wrong? >> >> this shouldn't be a problem anymore, right? >> >> I see that there were unsigned repos in the past on the mirrors >> we use. So the download was blocked... > > This is actually still broken. I made a new example package at > https://build.opensuse.org/package/show/home:0xxon:branches:security:zeek/ze.... > It again shows that it is waiting for the download of 6 DOD > packages.
hm, structure and signing keys on centos server seem to have changed again. That will need some research later :/
--
Adrian Schroeter email: adrian@suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5 90409 Nürnberg Germany
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
--
Adrian Schroeter email: adrian@suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5 90409 Nürnberg Germany
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org