Re: Devtoolset for epel7 for build in Copr
Miroslav Suchý writes: > [...] Springdale provides > devtoolset-3-elfutils there, and it in some strange way badly > correlates with the initial Copr build environment (even before > the rpmbuild process starts). Some python2 module cannot find > libelf.so.1 ... I believe what's going on is that the old scl build of elfutils also happens to include rpmbuild-generated libelf.so() virtual provides. That tricks yum into sometimes installing that scl elfutils instead of baseos elfutils to satisfy other packages' dependency on libelf.so. And it won't satisfy the dependency without a custom LD_LIBRARY_PATH (or scl enable). Modern scl builds of elfutils go to some effort to suppress that virtual rpm-provide. - FChE ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
On Fri, 2022-02-25 at 02:43 +0300, Dmitry Butskoy wrote: > Sérgio Basto wrote: > > On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote: > > > Miroslav Suchý wrote: > > > > > Second, the alternate Springdale Linux repo > > > > > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ s > > > > > ee > > > > > ms > > > > > to have all the ones (which are provided in sources by RedHat), > > > > > but > > > > > cannot be used in Copr. Springdale provides devtoolset-3- > > > > > elfutils > > > > > there, and it in some strange way badly correlates with the > > > > > initial > > > > > Copr build environment (even before the rpmbuild process > > > > > starts). > > > > > Some python2 module cannot find libelf.so.1 ... > > > > > > > > That is because it is SCL package. It installs the library to > > > > > > > > /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 > > > > > > > > You have to run > > > > > > > > scl enable devtools-3 $COMMAND > > > > > > > But where to run it exactly? > > > > > yes is not easy find an example unfortunately , first line of %build > > %build is in the .spec file. It is readed after the start of the build. > The start of the build is performed after the "bootstrap" stage. At > this > stage "yum install" creates an initial environment. Probably I'm wrong > -- Sorry this thread have different topics, after reading it . libelf.so.1: cannot open shared object file: No such file , should we a mixup of devtools set , you just can Buildrequires one devtool set Second llvm-toolset-11.0 is only available on RedHat EL 7 , that is why koji builds seamonkey which uses RHEL 7 and copr don't, it uses Centos 7 Third, search on goggle I found that is also available on Scientific Linux 7 http://rpm.pbone.net/results_srodzaj_1_search_libLLVM-11.so%28%29%2864bit%29.html > could you pls look at: > > Start: yum install > > There was a problem importing one of the Python modules > > required to run yum. The error leading to this problem was: > > > > libelf.so.1: cannot open shared object file: No such file or > > directory > fragment in the correspond log: > https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz > > ? > > IOW: there is no "yum install" in the .spec file. So where to run > "scl-enable ..." to take it effect before that "yum install" ? > > > ~buc > > > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
On Fri, 2022-02-25 at 02:43 +0300, Dmitry Butskoy wrote: > Sérgio Basto wrote: > > On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote: > > > Miroslav Suchý wrote: > > > > > Second, the alternate Springdale Linux repo > > > > > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ > > > > > see > > > > > ms > > > > > to have all the ones (which are provided in sources by > > > > > RedHat), > > > > > but > > > > > cannot be used in Copr. Springdale provides devtoolset-3- > > > > > elfutils > > > > > there, and it in some strange way badly correlates with the > > > > > initial > > > > > Copr build environment (even before the rpmbuild process > > > > > starts). > > > > > Some python2 module cannot find libelf.so.1 ... > > > > > > > > That is because it is SCL package. It installs the library to > > > > > > > > /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 > > > > > > > > You have to run > > > > > > > > scl enable devtools-3 $COMMAND > > > > > > > But where to run it exactly? > > > > > yes is not easy find an example unfortunately , first line of > > %build > > %build is in the .spec file. It is readed after the start of the > build. > The start of the build is performed after the "bootstrap" stage. At > this > stage "yum install" creates an initial environment. Probably I'm > wrong . /opt/rh/devtoolset-9/enable before cd mozilla instead `source scl_source enable devtoolset-9` > -- could you pls look at: > > Start: yum install > > There was a problem importing one of the Python modules > > required to run yum. The error leading to this problem was: > > > > libelf.so.1: cannot open shared object file: No such file or > > directory > fragment in the correspond log: > https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz > > ? > > IOW: there is no "yum install" in the .spec file. So where to run > "scl-enable ..." to take it effect before that "yum install" ? > > > ~buc > > > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Sérgio Basto wrote: On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote: Miroslav Suchý wrote: Second, the alternate Springdale Linux repo http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ see ms to have all the ones (which are provided in sources by RedHat), but cannot be used in Copr. Springdale provides devtoolset-3-elfutils there, and it in some strange way badly correlates with the initial Copr build environment (even before the rpmbuild process starts). Some python2 module cannot find libelf.so.1 ... That is because it is SCL package. It installs the library to /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 You have to run scl enable devtools-3 $COMMAND But where to run it exactly? yes is not easy find an example unfortunately , first line of %build %build is in the .spec file. It is readed after the start of the build. The start of the build is performed after the "bootstrap" stage. At this stage "yum install" creates an initial environment. Probably I'm wrong -- could you pls look at: Start: yum install There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: libelf.so.1: cannot open shared object file: No such file or directory fragment in the correspond log: https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz ? IOW: there is no "yum install" in the .spec file. So where to run "scl-enable ..." to take it effect before that "yum install" ? ~buc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote: > Miroslav Suchý wrote: > > > > > > > > Second, the alternate Springdale Linux repo > > > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ see > > > ms > > > to have all the ones (which are provided in sources by RedHat), > > > but > > > cannot be used in Copr. Springdale provides devtoolset-3-elfutils > > > there, and it in some strange way badly correlates with the > > > initial > > > Copr build environment (even before the rpmbuild process starts). > > > Some python2 module cannot find libelf.so.1 ... > > > > > > That is because it is SCL package. It installs the library to > > > > /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 > > > > You have to run > > > > scl enable devtools-3 $COMMAND > > > > But where to run it exactly? > yes is not easy find an example unfortunately , first line of %build see this example : https://src.fedoraproject.org/rpms/mkvtoolnix/blob/4400f88779be30d35d909545b76346dc218c24d4/f/mkvtoolnix.spec#_76 > It seems it happens on some early stage (so I cannot alter anything in > the .spec file). > > Could anybody look into the prolem log: > https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz > > ? > > > ~buc > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Miroslav Suchý wrote: Second, the alternate Springdale Linux repo http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ seems to have all the ones (which are provided in sources by RedHat), but cannot be used in Copr. Springdale provides devtoolset-3-elfutils there, and it in some strange way badly correlates with the initial Copr build environment (even before the rpmbuild process starts). Some python2 module cannot find libelf.so.1 ... That is because it is SCL package. It installs the library to /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 You have to run scl enable devtools-3 $COMMAND But where to run it exactly? It seems it happens on some early stage (so I cannot alter anything in the .spec file). Could anybody look into the prolem log: https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz ? ~buc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Miroslav Suchý writes: > You have to run > > scl enable devtools-3 $COMMAND > > to make this library available. I used to do that, but it's rather easier to source the enable script (conditionally) in %build and perhaps %check or %install. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
[epel-devel seems a better place for this.] Dmitry Butskoy writes: > Ben Beasley wrote: >> Yes, the devtoolsets work nicely if you supply the appropriate >> incantations. I haven’t tried in COPR specifically > I've just tried and it seems that devtoolset are not available for > epel7 builds in Copr. (For epel7, I successfully build seamonkey with > devtoolset already for years :) ) > > There is a possibility to use an additional external repo for > Copr. But there are issues with this. I'm unclear what's actually required, but CentOS 7 has up to devtoolset-11, and some version worked for me whenever I last did a build in copr which needed it. > First, the appropriate CentOS repo > http://mirror.centos.org/centos/7/sclo/x86_64/rh/ does not have the > latest llvm packages (for clang) -- say, llvm-toolset-11-* . (BTW, why??) There's no RHEL7 llvm-toolset as far as I know, so if you want exactly that you'll have to build it, which is probably non-trivial. EPEL 7 has llvm11, but I don't know where to find a recent clang, if that's what you actually want. EL7 development is a losing battle at this stage, though. We're even forced off it by IBM saying RHEL 7.9 for POWER doesn't exist. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Dne 23. 02. 22 v 19:22 Dmitry Butskoy napsal(a): Ben Beasley wrote: Yes, the devtoolsets work nicely if you supply the appropriate incantations. I haven’t tried in COPR specifically I've just tried and it seems that devtoolset are not available for epel7 builds in Copr. (For epel7, I successfully build seamonkey with devtoolset already for years :) ) There is a possibility to use an additional external repo for Copr. But there are issues with this. First, the appropriate CentOS repo http://mirror.centos.org/centos/7/sclo/x86_64/rh/ does not have the latest llvm packages (for clang) -- say, llvm-toolset-11-* . (BTW, why??) Second, the alternate Springdale Linux repo http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ seems to have all the ones (which are provided in sources by RedHat), but cannot be used in Copr. Springdale provides devtoolset-3-elfutils there, and it in some strange way badly correlates with the initial Copr build environment (even before the rpmbuild process starts). Some python2 module cannot find libelf.so.1 ... That is because it is SCL package. It installs the library to /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1 You have to run scl enable devtools-3 $COMMAND to make this library available. More about SCL here: https://www.softwarecollections.org/en/ including Packaging guide. So the general questions are: - Whether it is possible to enable "rhel7-server-rhscl-7" and friends for epel7 builds in Copr? (See https://koji.fedoraproject.org/koji/taginfo?tagID=259 for more info); Copr tries to use as much as possible upstream Mock's config. AFAIK it is enabled there: https://github.com/rpm-software-management/mock/blob/main/mock-core-configs/etc/mock/templates/centos-7.tpl#L81 Miroslav___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Kevin Kofler via devel wrote: I guess the easiest workaround would be to create an llvm-toolset-11.0 Copr and to build llvm-toolset-11.0-*.src.rpm from: http://springdale.princeton.edu/data/springdale/SCL/7/SRPMS/ in it. Unfortunately, the rebiuld of all the llvm-toolset stuff from the sources is hard enough thing (a lot of cpu resources, disk space etc.). Anyway, why the additional repo is used not for rpmbuild time only, but for creating the initial build system environment too? Whether the proper RHEL/CentOS repos plus EPEL should be enough for it? ~buc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Dmitry Butskoy wrote: > Second, the alternate Springdale Linux repo > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ seems to > have all the ones (which are provided in sources by RedHat), but cannot > be used in Copr. Springdale provides devtoolset-3-elfutils there, and it > in some strange way badly correlates with the initial Copr build > environment (even before the rpmbuild process starts). Some python2 > module cannot find libelf.so.1 ... The problem there is that they stuff all SCLs into one single repo instead of one per SCL, and that Copr only allows you to input a baseurl for the repo and not a complete mock config group with includepkgs= or excludepkgs= options (which would be needed to filter what you actually want from the repo). I guess the easiest workaround would be to create an llvm-toolset-11.0 Copr and to build llvm-toolset-11.0-*.src.rpm from: http://springdale.princeton.edu/data/springdale/SCL/7/SRPMS/ in it. (I believe you can point Copr directly to the SRPM URLs, so you do not even have to download and upload them.) Then it can be referenced from your Copr using a copr: reference. Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Ben Beasley wrote: Yes, the devtoolsets work nicely if you supply the appropriate incantations. I haven’t tried in COPR specifically I've just tried and it seems that devtoolset are not available for epel7 builds in Copr. (For epel7, I successfully build seamonkey with devtoolset already for years :) ) There is a possibility to use an additional external repo for Copr. But there are issues with this. First, the appropriate CentOS repo http://mirror.centos.org/centos/7/sclo/x86_64/rh/ does not have the latest llvm packages (for clang) -- say, llvm-toolset-11-* . (BTW, why??) Second, the alternate Springdale Linux repo http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ seems to have all the ones (which are provided in sources by RedHat), but cannot be used in Copr. Springdale provides devtoolset-3-elfutils there, and it in some strange way badly correlates with the initial Copr build environment (even before the rpmbuild process starts). Some python2 module cannot find libelf.so.1 ... So the general questions are: - Whether it is possible to enable "rhel7-server-rhscl-7" and friends for epel7 builds in Copr? (See https://koji.fedoraproject.org/koji/taginfo?tagID=259 for more info); - Why the user specified additional repos affect the initial set of packages used for the build environment? ~buc P.S. Does anybody know a repo (besides Springdale) with the latest llvm-toolset-* provided? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Devtoolset for epel7 for build in Copr
Yes, the devtoolsets work nicely if you supply the appropriate incantations. I haven’t tried in COPR specifically, but I assume the situation is the same as in EPEL proper. Please see the very clean example in the epel7 branch for sleef[1], which was kindly contributed by Dave Love. – Ben [1] https://src.fedoraproject.org/rpms/sleef/blob/epel7/f/sleef.spec On Wed, Feb 23, 2022, at 11:25 AM, Dmitry Butskoy wrote: > Is it possible to use RHEL7 devtoolsets (aka devtoolset-8, > llvm-toolset-11 and so on) for the correspond builds in Copr, as well as > it is possible for builds for Fedora EPEL7 ? > > ~buc > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Devtoolset for epel7 for build in Copr
Is it possible to use RHEL7 devtoolsets (aka devtoolset-8, llvm-toolset-11 and so on) for the correspond builds in Copr, as well as it is possible for builds for Fedora EPEL7 ? ~buc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
